Privacy Policy
Effective October 31, 2026. Plain English. No dark patterns.
1. The short version
We collect the minimum we need to run DNS.pizza: your email, the domains you ask us to watch, and some usage data. We don’t sell your data. We share it only with the service providers we need to run the product. You can export or delete your data any time.
2. Who this applies to
This policy covers anyone using the site at https://dns.pizza — visitors, signed-in users, and paying subscribers. By using the service you consent to the data practices described here.
3. What we collect
Information you give us directly:
- Email address (for your account and alerts).
- Name and avatar (if provided via Google / GitHub sign-in).
- Password (stored as a salted bcrypt hash — we can’t read your password).
- Domains you choose to monitor or look up, and any notification channel configuration (webhook URLs, Slack/Discord incoming-webhook URLs, extra email addresses). Webhook signing secrets are encrypted at rest with AES-256-GCM.
- Name Watch: the email address and the words you ask us to watch, when you confirm and when we last emailed you. Used only to send that daily email; you can unsubscribe from any of them.
- Payment information — actually handled by Stripe, we only see a customer ID and subscription status.
Information we collect automatically:
- Lookup history: domains you queried, timestamps, results. Used to give you history and (for Pro users) exports.
- DNS snapshots: the DNS records of domains you monitor, kept so we can detect changes. Not personal data, but it’s your data.
- Basic request logs (IP address, user agent, timing) for rate limiting, security, and debugging. Retained for up to 30 days.
- Cookies include the session cookie needed to keep you signed in, and dp_src, a first-party cookie that remembers for 90 days how you first reached the site: the referring site’s name, the page you landed on, any campaign tags in that link, and the date. We don’t add your name or email address to it, and we filter what we copy from a link to keep email addresses and sign-in tokens out. If you sign up or start a checkout, the referring site, landing page and campaign tags go with that record to PostHog or Stripe. No third-party advertising cookies.
Information from third parties:
- If you sign in with Google / GitHub, we receive your email, name, and avatar from them.
- When you look up an IP, we enrich it with ASN and country data from IPinfo.
- When you look up a domain, we query public registries (RDAP / WHOIS) and public DNS. Those systems may log the query server-side; they’re outside our control.
4. Why we collect it
- To operate the service (run lookups, monitor domains, deliver alerts).
- To bill paid plans.
- To prevent abuse and enforce rate limits.
- To diagnose errors and improve reliability.
- To communicate with you about account, billing, and service changes.
We do not use your data to train AI models. We do not run advertising networks. We do not profile or track you across the web.
5. Who we share it with (subprocessors)
To run DNS.pizza, we hand some data to the companies below. Each of them has their own privacy policy. We only share what’s necessary for them to do their job.
| Provider | What they do | Data involved |
|---|---|---|
| Vercel | Hosting, request routing, edge delivery, page-speed and visit statistics, storage for screenshots of monitored pages | Page requests, IP addresses, request logs; screenshots of the pages you monitor |
| Neon | Postgres database | All app data (accounts, domains, alerts, snapshots) |
| Fly.io | Background monitor checks and alert delivery, regional DNS probes, WHOIS lookups, page screenshots | The domains and URLs you watch or look up and what each check finds. For monitor checks, also the ID, name and email of the account that owns the monitor, its subscription record (plan, status and Stripe reference IDs), and its alert settings: where alerts are sent and any webhook credentials you gave us |
| Amazon Web Services | Runs our own reader of the public certificate logs | The domains certificate monitors watch. The reader gets no account IDs, names or email addresses |
| Stripe | Payments and subscriptions | Email, billing address, payment method (stored by Stripe, not us), and how you first reached the site |
| Resend | Alert email | Email address, alert contents |
| Mailgun | Account, digest and support email, alert email, operational email, and receiving your replies to us | Email address, message contents |
| PostHog | Usage analytics: which pages and features get used and what gets clicked | Pages viewed, clicks and product events, including domains you look up; how you first reached the site, when you sign up; your account ID and email address when you are signed in |
| Sentry | Error and performance monitoring | Error stack traces, user ID, request metadata, page timings, and when an error happens a recording of the page with its text masked and media blocked |
| IPinfo | IP address to ASN / country enrichment | IP addresses (typically of domains you’re inspecting, not yours) |
| Anthropic | AI narratives in reports, the in-product assistant, first drafts of replies to support email | Domain data and the questions you put to the assistant. If you email support, your address and message |
| TypeSafe | AI summaries on public domain pages | The domain and text from its current and archived public web pages; no account info |
| Google / GitHub (optional) | OAuth sign-in | Email, name, avatar (if you choose this sign-in method) |
| Upstash | Rate limiting, the queues of pending checks and alerts, lookup caches, working state for monitors | IP address or user ID with per-route counters, and at sign-in the email address being tried; internal IDs of queued checks and alerts; cached lookup results; the domains certificate monitors watch and the certificates seen for them |
We may also query public DNS resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1, Quad9), the Internet Archive’s Wayback Machine, crt.sh and Cert Spotter for certificate transparency, and public RDAP servers. These queries contain the domain you’re looking up; they don’t contain your account information.
If you point alerts at Slack, Discord, Pushover or your own webhook, we send the alert to that service. If you import zones from Cloudflare or Amazon Route 53, we call that provider with the credentials you give us.
6. How long we keep data
- Account data: until you delete your account.
- Monitored domains: until you remove the domain. Your monitors, incident timeline, and distilled change history are kept while the domain is monitored.
- Snapshot, lookup, and per-check history: retained for your plan’s history window — 30 days on Free, 90 days on Starter, 1 year on Pro, and 3 years on Business — then deleted by a daily sweep.
- Alert delivery records: 90 days, then deleted.
- Request logs: up to 90 days.
- Billing records: retained as long as required by law (typically 7 years) via Stripe.
- Closed accounts: personal data deleted within 30 days, except where we must retain it (e.g. billing records above).
7. Your rights
You can access, export, correct, or delete your data any time. Just email us or do it from the dashboard.
You have the right to:
- Access — get a copy of the personal data we hold about you.
- Correct — fix anything inaccurate.
- Delete — close your account or remove specific data.
- Export — download your monitored domains and history as JSON.
- Opt out of alerts — toggle email in settings or use the unsubscribe link in any alert email.
- Complain — if you believe we’ve mishandled your data, you can complain to your local data-protection authority. We’d rather you email us first so we can try to fix it.
To exercise any of these rights, email hello@dns.pizza. We’ll respond within 30 days.
8. Security
We encrypt data in transit with TLS everywhere. Passwords are stored with bcrypt. Webhook signing secrets are encrypted at rest with AES-256-GCM using a key that lives only on our servers. We use short-lived secrets with automatic rotation where possible.
No system is perfectly secure. If we ever experience a breach that affects your personal data, we’ll notify you without undue delay — within 72 hours where legally required.
9. International transfers
DNS.pizza is hosted in the United States. If you use the service from outside the US, your data will be transferred to and processed in the US and other countries where our subprocessors operate. We rely on the legal mechanisms (standard contractual clauses, adequacy decisions) that each subprocessor provides.
10. Children
DNS.pizza isn’t designed for children. Don’t create an account if you’re under 13, or under the digital consent age in your country (16 in much of Europe). If we learn we’ve collected data from a child, we delete it.
11. Changes to this policy
We may update this policy. When we do, we’ll change the effective date at the top and record what changed in the change log below. If a change materially affects how we use your personal data, we’ll tell account holders by email before it takes effect.
Change log
- October 31, 2026 — Added the dp_src cookie, which remembers how you first reached the site, and said where that information goes.
- October 21, 2026 — Added Name Watch: the email address and words you ask us to watch, kept to send its daily email.
- October 2, 2026 — Named Fly.io and Amazon Web Services as providers and corrected the Upstash entry. Replaced the fixed 14-day notice period with notice before a material change takes effect. Added this change log. Also named Mailgun, PostHog and TypeSafe, and widened the Vercel, Sentry and Anthropic entries to cover everything they do.
- October 1, 2026 — Named Cert Spotter beside crt.sh as a source of certificate transparency data.
12. Contact
Privacy questions, access requests, or concerns: hello@dns.pizza. We treat privacy requests as a priority and reply within 30 days.