How windows work
- A window runs from when a record is written. Deletion runs in the background, so data can outlast its window briefly.
- Upgrading lengthens the window for data already stored. Downgrading applies only to new data.
- Deleting a monitor deletes its check results and summaries. Deleting other items, such as an application or alert destination, does not erase their history; ask us (below).
Retention periods
| Data | Retention |
|---|---|
| Logs and traces | 7 days free, 30 days with a paid pack |
| Metrics | Raw points 7 days free or 15 days paid; minute rollups 45 days; hour rollups 30 days free or 395 days paid |
| Log summary statistics (no message content) | 90 days |
| Real user monitoring measures (page views, Core Web Vitals, URLs, user agent, country) | 458 days; you can set a lower per-application limit |
| Real user monitoring events (errors, actions, resources, and user details attached to them) | 30 days; you can set a lower per-application limit |
| Session replay recordings and indexes | 30 days, or 7 or 14 days if you set a lower per-application limit |
| Shared replay stylesheets | 400 days |
| Uptime check results (HTTP, TCP, ping, TLS, domain and PageSpeed) | 90 days, or up to 1 year for a failed HTTP check when your plan keeps its response body longer |
| Hourly and daily uptime summaries | 25 months |
| Stored response bodies of failed HTTP checks | Viewable for 5 days free, 30 days paid, or up to 1 year with the body retention add-on, while the check result is kept |
| Browser check results | 1 year; videos and HAR files 30 days; web vitals 90 days |
| HTTP check results and timings in our older store (written until October 29, 2026) | Timings 1 year; results not deleted automatically (see below) |
| Alerts received by an alert source | 30 days; bodies kept by a debug capture 7 days |
| Status page subscribers | Until they unsubscribe or the page is deleted; unconfirmed sign-ups 7 days after the link expires; delivery and bounce records up to 90 days |
| “Is it down?” alert sign-ups | Until you unsubscribe; unconfirmed sign-ups 2 days |
| “Is it down?” problem reports | 3 days |
| Dashboard query history | 7 days |
| Infrastructure and API gateway logs (including IP addresses) | 30 days for most; a few kept up to 545 days |
| Backups | Database backups 7 days, snapshots up to 8 days, analytics store backups 35 days. We do not restore a backup to re-apply an erasure. |
Account admins can lower real user monitoring and replay limits in RUM → Settings → Data settings or through the API. Lowering a limit also deletes older data. See the retention guide.
No automatic deletion
The following are kept until deleted on request:
- Account, user, API key, integration, notification, usage and activity records, including after an account is closed
- HTTP check results in our older store, and the archived response bodies of historical checks
- Notification delivery records (recipient and message content) and email bounce and complaint records, except for status page mail
- The customer audit log (the dashboard shows the last 90 days) and the staff audit log
- Expired invitations
- Cron heartbeat request records
- Uploaded source maps and status page branding
Third-party services
- Google Analytics 4: under Google’s retention rules.
- Microsoft Clarity: recordings 30 days, with selected recordings, clicks and heatmaps up to 9 months, per Microsoft’s retention policy.
- AWS Amplify access logs for the dashboard and status pages: for as long as the application exists.
- Support email (Zoho Mail) and our internal Slack alert channel: kept until deleted.
Deleting data
Account admins can erase a person’s real user monitoring data in RUM → Settings → Data requests or through the API; see the privacy guide. For anything else, write to privacy@siteqwality.com. If you are a visitor to a website that uses Site Qwality, contact that website’s operator.