StatusOwl provides hosted status pages and the uptime, certificate, domain and server-metric monitoring that keeps them current. This policy covers the marketing site at statusowl.net, the dashboard at dash.statusowl.net, the public API, and every status page we host on statusowl.app or on a customer’s own domain.
Who we are
StatusOwl (“we”, “us”) is the operator of the service and the data controller for account data — the information you give us to have an account and be billed for one.
For the content you put into StatusOwl — monitor configurations, incident titles and updates, maintenance notes, status-page copy, the addresses you send notifications to — we act as a processor on your behalf. You decide what goes in; we store it, display it where you tell us to, and do not use it for anything else.
What we collect
Account and organisation data
Your name, email address and a hashed password. Your organisation name, the members you invite, and each member’s role (owner, admin, billing or member). We never store your password in a readable form.
Configuration you enter
The URLs, hostnames, IP addresses and ports you ask us to check; request headers and bodies you attach to an HTTP monitor; status-page titles, descriptions and slugs; custom domains; uploaded logos; incident and maintenance text; and the destinations you configure for notifications — email addresses, Slack, Discord and Microsoft Teams webhook URLs, ntfy topics and your own webhook endpoints.
Request headers on a monitor are stored so the check can be repeated. If you put a bearer token or an API key in one, we hold it. Use a scoped, read-only credential where you can.
Check results
For every check we run: the timestamp, whether it passed, the HTTP status code, the response time, and any error string returned. For certificate and domain monitors: issuer, subject, validity dates, nameservers and days remaining. For Watch Owl, the agent you install yourself: CPU, memory, per-mount disk, per-interface network counters, host metadata and OS patch or reboot state.
We do not store response bodies. A check records the status code, the timing and any error it produced — not the content that came back.
Billing data
If you subscribe, Stripe collects and holds your payment details. We receive and store a Stripe customer identifier, the plan you are on, the billing interval, and the subscription status. Card numbers never reach our servers.
Operational logs
Our servers record ordinary request logs — IP address, user agent, path, response code and timing — to keep the service running and to investigate abuse. Sampled request logs are retained by Cloudflare and Fly.io under their own platform retention.
Audit logs
Every incident, maintenance window and status-page change is recorded with the actor, the action and the time, on every plan including Free. That record is yours; it exists so your team can answer “who changed this?”.
Analytics
The marketing site uses Plausible Analytics. It sets no cookies, stores no device identifier, and cannot follow a visitor across sites. We see aggregate page views, referrers and country — not people.
Why we process it
- To run the checks you configure and store their results.
- To render your status pages, incidents, maintenance windows and uptime history to the people you publish them for.
- To open an incident automatically when a monitor attached to a page fails 3 checks in a row, and to resolve it on recovery.
- To send the notifications you set up, and the scheduled uptime reports you subscribe to.
- To authenticate you and enforce your organisation’s roles.
- To take payment, issue invoices and manage your subscription.
- To send service email you cannot opt out of while you have an account: security notices, billing failures, and material changes to the service.
- To answer you when you contact us.
- To detect and stop abuse, and to keep the platform up and within its limits.
We do not sell personal information, we do not share it with advertisers, and we do not use your data to train models.
Lawful basis
For anyone covered by the UK or EU GDPR, we rely on the following bases:
- Performance of a contract — running your account, your monitors, your status pages and your billing. Without this data there is no service to provide.
- Legitimate interests — aggregate analytics, request logging, abuse prevention and platform security. We have balanced these against your rights and kept the data minimal and non-identifying wherever the job allows it.
- Legal obligation — retaining invoices and payment records for tax and accounting.
- Consent — when you email us or submit the contact form, and when you opt in to a scheduled uptime report. Consent can be withdrawn at any time; every report email carries a signed unsubscribe link.
Cookies and storage
There is no cookie banner on this site because there is nothing to consent to. The full list is short:
- Session cookie —
better-auth.session_token, set by the dashboard when you sign in. It is strictly necessary; without it you cannot stay signed in. It carries an opaque session token, not a profile. - Theme preference — the light / dark / system choice on this site and the visitor toggle on public status pages is kept in your browser’s
localStorage, not in a cookie, and never leaves your device.
No advertising cookies, no tracking pixels, no third-party analytics cookies. Plausible uses none.
Sub-processors
These are the third parties that can touch data in the course of running StatusOwl. This list is current as of 2026-08-05 and we update it here when it changes.
| Sub-processor | What it does | Region |
|---|---|---|
| Cloudflare | Marketing site and public API hosting, CDN and DNS, and automatic SSL certificates for customer status-page domains via Cloudflare for SaaS. | Global edge |
| Fly.io | Application hosting for the dashboard, the API, the background workers and the status-page renderer. | iad — Ashburn, US |
| Neon | Managed PostgreSQL. Holds account, organisation, monitor, incident and check data, with 7-day point-in-time recovery. | us-east-1 — N. Virginia, US |
| Amazon Web Services | SQS message queues carrying check dispatch jobs and check results between the API and the checking agents. | us-east-2 — Ohio, US |
| Resend | Transactional and scheduled email: sign-in and account mail, alert notifications, scheduled uptime reports, and messages sent from the contact form. | US |
| Stripe | Subscription payments, invoices and the billing portal. Card details are entered on Stripe and never reach our servers. | US and global |
| Plausible Analytics | Aggregate traffic analytics for statusowl.net. No cookies, no cross-site tracking, no individual visitor profiles. | EU |
Beyond these, we may disclose data where the law requires it, and in connection with a merger or sale of the business — in which case you will be told before your data moves.
Where your data lives
Application data is stored in the United States: the databases sit in AWS us-east-1 via Neon, the applications run on Fly.io in iad, and the message queues are in AWS us-east-2. Cloudflare serves cached pages and terminates TLS from its global edge, so a request may be handled near you before reaching a US origin. Plausible holds the analytics data in the EU.
If you are in the UK or the EEA, that means your data is transferred to the United States. Those transfers rely on the standard contractual clauses in each sub-processor’s own data processing agreement. If you need a data processing agreement with us, email hello@statusowl.net and we will sign one.
How long we keep it
Check results are pruned to your plan’s retention window. Older time-series rows are dropped by a background job; they are not archived somewhere else.
| Plan | Check data retained |
|---|---|
| Free | 30 days |
| Starter | 90 days |
| Growth | 180 days |
| Scale | 365 days |
Everything else:
- Account and organisation data — for as long as the account exists.
- Incidents, maintenance windows and audit logs — for as long as the account exists, because they are the public record of what happened. Deleting an incident deletes it and its updates.
- Database backups — Neon keeps 7 days of point-in-time recovery. Deleted data can therefore persist in recovery state for up to 7 days before it ages out.
- Billing records — retained as long as tax and accounting law requires, which is longer than your account.
- Contact form messages — kept in our support inbox until they are no longer needed to answer you.
Security
Honest version, because a status page company should not oversell its own reliability:
- All traffic is TLS-encrypted in transit, including our connections to the database. Every custom status-page domain gets a certificate issued and renewed automatically.
- Passwords are stored hashed. API keys are stored as SHA-256 hashes — we cannot show you a key again after you create it.
- Outgoing webhooks can be signed with HMAC-SHA256 so you can verify a request came from us, and they are dispatched through a client that blocks requests to internal network ranges.
- Tenant isolation is enforced in application code: every query is scoped by organisation and membership is checked before every read and write. It is not enforced by database row-level security. We would rather tell you that than imply a stronger control than we have.
- Data at rest is held on managed platforms — Neon and Cloudflare — whose own security documentation describes their storage encryption. We do not add an application-level encryption layer on top of it, and we are not going to claim one.
- We hold no security certification today. No SOC 2, no ISO 27001, no HIPAA. If your procurement process requires one, we are not a fit yet and we would rather you knew now.
No system is perfectly secure. If you find a vulnerability, email hello@statusowl.net and we will get back to you.
Your rights
Under the UK and EU GDPR you have the right to access the personal data we hold about you, to have it corrected, to have it erased, to restrict or object to how we process it, to receive it in a portable format, and to withdraw consent where consent is the basis we rely on. You can also complain to your national supervisory authority — in the UK, the Information Commissioner’s Office.
Under the CCPA and CPRA, California residents have the right to know what personal information we collect and why, to request its deletion or correction, and to opt out of its sale or sharing. There is nothing to opt out of: we do not sell or share personal information as those terms are defined by the CCPA, and we never have. We will not treat you differently for exercising any of these rights.
To exercise any of them, email hello@statusowl.net from the address on the account. We will respond within 30 days.
Deleting your data
You can delete individual monitors, incidents and status pages from the dashboard at any time.
To close your account entirely, email hello@statusowl.net from the address on the account. We will remove your personal data within 30 days and confirm when it is done, except for billing records we are legally required to keep. Remember that database backups age out over 7 days.
Cancelling a paid subscription is separate and self-serve — see the Terms of Service.
Children
StatusOwl is a tool for people who run infrastructure. It is not directed at children and we do not knowingly collect data from anyone under 16. If you believe a child has given us data, tell us and we will delete it.
Changes to this policy
When this policy changes we update the date at the top of the page. If a change materially affects how we handle your data — a new sub-processor with access to customer content, a new purpose, a shorter retention window — we will email account owners before it takes effect.
Contact
Privacy questions, rights requests, deletion requests and data processing agreements all go to one place: hello@statusowl.net. It is read by the people who build StatusOwl. There is no separate privacy desk and we are not going to pretend otherwise.