15.2How long we keep your data

This table lists the data with a fixed keeping period.

Data	Kept for	Where you see it
Screenshots of failed browser checks	14 days	Monitor detail, under the failed run. After 14 days you see "screenshot no longer available".
Audit log entries	1 year	The audit log tab (team owners only).
Alert decisions (why a failed check did or did not send an alert)	90 days	The dashboard shows the last 24 hours. Use the API to see up to 90 days (9.2).

The privacy policy also lists these periods:

Server logs: up to 30 days.
Billing and payment records: as long as Indian tax and company law requires, currently up to 8 years.

What your status page shows#

These are display windows. They control what visitors see, not what is deleted.

Uptime for the last 90 days, as one bar per day (UTC).
Open incidents, and incidents resolved in the last 14 days. Incidents opened more than 90 days ago are not listed.

Ask for a short-lived link to a failure screenshot. Replace <key>, <monitorId> and <executionId> with your own values.

Get a screenshot link

bash

curl -H "Authorization: Bearer <key>" \
  "https://www.obsrvly.com/api/gw/result/v1/\
monitors/<monitorId>/executions/<executionId>/\
screenshot"

Type the URL as one line with no breaks. The reply has a url and an expires_at time:

json

{"url": "...", "expires_at": "..."}

The link works for 5 minutes. It needs no key, so keep it private like a key until it expires.
A 404 means one of these: the check passed, the page showed a secret, the screenshot is older than 14 days, or the run is not in your team.

A monitor. The dialog warns: "Its checks stop and its history is not recoverable." Select delete monitor. The monitor's screenshots are deleted with it (3.7).
A secret. You cannot change a secret's value. To replace it, delete the secret and create a new one (8.5).