Account information
The service stores the email address submitted during registration, a salted password hash, session-version data and account creation time. It does not collect payment-card data because billing is not connected.
Monitoring information
The service stores monitor names and public targets, configuration, check results, latency, incidents, certificate details, domain-expiry information, status-page configuration, maintenance events and updates. Public status pages intentionally expose the component names and operational information selected by the workspace owner.
Contact information
If you use the contact form, UptimeLoop stores the email address, subject, message and submission time so Alexis Dufays can review and respond manually. Do not include passwords, API keys, tokens or other secrets.
Technical and analytics data
Web requests naturally provide request metadata such as an IP address, user agent, requested path and timestamps to the hosting stack. Rate limiting stores an HMAC-derived identifier rather than the raw login or registration identity. The public site also loads KeepAnalytics through a first-party path to understand website usage.
Retention
- Detailed monitor checks are retained for 7 days.
- Hourly aggregates and resolved incidents are retained for 90 days.
- Account, monitor, status-page and unresolved operational data remain while needed to provide the workspace.
- Contact requests remain until manually reviewed or removed.
Cookies
An HTTP-only session cookie keeps an authenticated user signed in. It expires after 7 days and is invalidated when the user logs out. The service does not claim that every third-party or infrastructure component is cookie-free.
Requests and limits
There is no self-service account export or account-deletion workflow in the current early-access interface. Use the contact form for a data request. A response time or jurisdiction-specific outcome is not guaranteed by this product page.