1. What we collect
To run the service, we collect and store:
- Account data — your email address, an optional display name, time zone, and plan/trial state.
- Site data — the URLs you register for monitoring, per-site labels or client names, and your alert/notification preferences.
- Check data — the results of automated checks we run against your registered sites (uptime, SSL, domain, DNS, email authentication, blacklist, broken links, and metadata findings), the alerts derived from them, and your acknowledge/ignore decisions on those alerts.
- Product analytics — anonymous-by-default pageview and conversion-funnel events (via PostHog) from our marketing pages, free checker, and dashboard, used to understand what's working and where visitors drop off. We do not use analytics to profile you individually beyond what's needed to measure acquisition and product usage.
- Billing data — if you subscribe to a paid plan, Stripe processes and stores your payment details; we store only your Stripe customer/subscription identifiers, never card numbers.
2. Why we collect it
We use this data to: run the monitoring checks you've asked for; send you opened/resolved alert emails and the weekly digest; let you sign in without a password (magic link); operate billing; and understand and improve the product. We do not sell your data, and we do not use your site's monitored content for advertising.
3. Who else touches it (processors)
SitesRadar runs on a small set of infrastructure and service providers, each processing only what they need to do their job:
- Railway — hosts the web app and the always-on monitoring worker.
- Neon — hosts our Postgres database (accounts, sites, checks, findings, alerts).
- Resend — sends account (magic-link sign-in) and alert/digest email on our behalf, and stores your email address as a waitlist/audience contact if you signed up before launch.
- Stripe — processes payments and stores payment method details for paid plans; we never see or store your card number.
- PostHog — collects the product analytics events described above.
- healthchecks.io — a dead-man's-switch watchdog that confirms our monitoring worker is alive; it does not receive your site or account data.
- Fly.io — hosts a small second-vantage proxy that independently re-checks a suspected uptime outage from a different network location before we alert you on it. It receives only the site URL you monitor, for the duration of that check.
We do not sell or rent your data to third parties, and we do not share it beyond what's needed to run the service above.
4. How long we keep it
Account, site, and check data is kept for as long as your account exists, so your history of checks and alerts stays available to you. Detailed check-run history is retained on a rolling basis for recent activity and diagnostics; older raw run detail may be pruned while the derived alert record is kept. When you delete your account (Section 6), account, site, check, alert, and preference data is removed from our database, not merely hidden.
5. Your choices
You can update your profile, time zone, alert preferences, and alert addresses at any time from Settings. You can acknowledge or permanently ignore individual alert findings from the Alerts page. You can opt out of the weekly digest from Settings.
6. Deleting your account
You can delete your account yourself from Settings → danger zone, by typing your account email to confirm. Deletion is immediate and permanent: it cancels any active subscription first, then removes your account, your registered sites, monitors, check history, findings, alerts, ignore rules, alert channels, and sign-in identity from our database in one operation. We do not keep a hidden copy for later use. A best-effort attempt is made to also remove your email from our Resend contact list; if that step fails, your account data has already been deleted regardless.
You can also email info@sitesradar.com to request deletion if you're unable to use the in-product control.
7. Security
We use encryption in transit (TLS) for all connections to the service and to our infrastructure providers, and we scope database and provider credentials to what each part of the system needs.
8. Children
SitesRadar is a business tool and is not directed to children. We do not knowingly collect data from children.
9. Changes to this policy
We may update this policy as the product changes. If a change materially affects how we handle your data, we will provide notice through the service or by email.
10. Contact
Questions about this policy, or requests about your data, can be sent to info@sitesradar.com.