Privacy policy

Written against what the system actually stores, which you can verify in the repository's schema.

Last updated 27 August 2026

Pending legal review. This document was drafted to describe how the service actually works and is accurate to the implemented architecture. It has not been reviewed by a qualified lawyer in the operating jurisdiction, and must be before launch — see OWNER_ACTION_REQUIRED.md in the repository.

What we collect

When you run a check without an account

  • The domain you entered, and the DNS records returned for it — all of which are public
  • A keyed hash of your IP address, used for rate limiting. The address itself is never stored, and the hash cannot be reversed to recover it
  • An anonymous session identifier and the page you were on, for conversion analytics

When you have an account

  • Your email address
  • The domains you monitor and their check history
  • Notification preferences
  • Subscription status and a Stripe customer identifier. Card details are handled entirely by Stripe and never reach our servers

What we do not collect

  • The contents of any email
  • Credentials for your DNS host, mail provider or anything else
  • Browser fingerprints or cross-site tracking identifiers
  • Raw IP addresses

Why we collect it

To run the checks you ask for, send the alerts you subscribe to, enforce plan limits, prevent abuse, bill you, and understand which parts of the product are useful. The lawful basis is performance of the contract for account data, and legitimate interests for abuse prevention and product analytics.

How long we keep it

  • Anonymous check results: 30 days, then deleted automatically
  • Account check history: the retention window on your plan, 90 to 730 days
  • Rate limiting hashes: 2 days
  • Delivered alerts: 180 days
  • Usage and billing records: up to 400 days, as required for accounting
  • Account data: until you delete your account

These are enforced by a scheduled job, not by policy alone.

Who we share it with

We use a small number of processors, and no others:

  • Supabase — database and authentication
  • Vercel — application hosting
  • Stripe — payments
  • Resend — transactional email

We do not sell personal data and do not share it for advertising. Any aggregate statistics we publish are derived only where the sample is large enough that no individual domain or customer is identifiable.

Your rights

You may access, correct, export or delete your data. Deletion is self-service in your account settings and removes your profile, domains and monitoring history. Anonymous analytics rows are retained but detached from your account, since they contain no personal data once unlinked. For anything else, email privacy@sendercheck.net.

Cookies

We set a session cookie when you sign in, and a first-party analytics identifier that distinguishes visits without identifying you. There are no third-party advertising or tracking cookies, which is why there is no consent banner to click through.

Security

Data is encrypted in transit and at rest. Tenant isolation is enforced by row-level security in the database rather than by application code alone, so a bug in a route handler cannot expose another account’s data. See SECURITY.md in the repository.

Contact

privacy@sendercheck.net