This notice explains what DNS Super collects, why, how long we keep it and what you can do about it. It covers the website, the API and the MCP server.
Who we are
DNS Super is run by MB IO Sprendimai, Perkūnkiemio g. 19, LT-12120 Vilnius, Lithuania, company code 307100077. You can reach us about privacy at hello@dnssuper.com.
We are the controller of the personal data described here. When a business customer has us process personal data of other people, such as data in what it checks or monitors, in the alerts it sends to its members, webhooks or Slack, or about the people it invites, we act as its processor under our data processing agreement, and the customer decides how that data is used.
What we collect and why
Your account. When you sign up we keep your email address and, if you add it, your name, plus the accounts you belong to and your role in each. We need them to sign you in, show your dashboard and bill you. We also record which version of our terms you accepted and when, as proof of our agreement. Legal basis: the contract with you. You need to give an email address to have an account, because we sign you in through it; without one we can't give you an account. You can run free checks without an account.
What you check. Each metered call records the tool, the domain or address you checked, the price, whether the answer came from our cache, and when. We use it for your usage page and exports, for billing records and to keep limits fair. Usage records are kept 13 months, then deleted a month at a time.
Anonymous checks. You can run free checks without an account. We don't store your IP address for this: we keep a keyed hash of it (IPv6 addresses by /64) to count your free checks and protect the service, and those counters expire under 48 hours. Each free check is recorded like a metered call (the tool, the domain or address and when) under our website's own account, with nothing that links it to you, and kept 13 months, then deleted a month at a time. Some results, such as domain availability, are cached under the same hash for a short time, so nobody else sees them. Free tools such as the record generators write no usage record when you use them without an account.
Payments. You buy credits and plans through Stripe Managed Payments. Stripe sells them to you as merchant of record: it takes your payment, charges and pays the VAT and handles payment disputes, while we provide the service. Stripe collects your payment and billing details as an independent controller under its own privacy policy; it isn't a processor working for us, and we never see your card. We give Stripe the email address of the account's owner and the account's internal id, so it can bill you and tell us what you bought. We keep the Stripe ids, the amount, tax, currency and receipt link of each payment, and the account's credit history, for our accounting records. Stripe keeps its own records under its own policy, also after you delete your account.
Email. Through our email provider we send sign-in links, invitations, the alerts you set up, and the confirmation link and notices of an email change. From our own mailbox we email an account's owner the notices our terms and data processing agreement promise: changes to our terms, this notice, our prices, plans or service, a suspension or closure of the account, new subprocessors and personal data breaches. We never send marketing email.
Email to us. When you write to hello@dnssuper.com, abuse@dnssuper.com or security@dnssuper.com, for example to ask for a refund, withdraw from a purchase, use your privacy rights, complain, or report abuse or a vulnerability, we keep your message, your address and our reply. We use them to handle your request and to defend legal claims. Legal basis: the contract with you and our legitimate interest in handling requests and defending claims; for privacy requests, also our legal obligation to answer them. We keep them 3 years after the matter is closed. Our mailbox is hosted by Hostinger in the EU, as the subprocessors page shows.
Security reports. If you report a vulnerability on our security page, we keep the summary, the details and the reply address you chose to give, and nothing else about you. A report you email instead is kept as email to us, above.
Server logs. Our edge and container logs hold truncated IP addresses, paths without any domain you checked, status codes and timings. They are kept 14 days.
Our servers, and the subprocessors listed below, are in the EU. The retention table below lists what we keep and for how long.
Third parties we contact
To answer a check, our servers contact the systems that hold the answer: DNS servers, domain registries (RDAP and WHOIS), domain registrars (when a registry refers us to them), the regional internet registries (RDAP for IP addresses), the websites you check and the files their pages load, the servers whose ports or IPv6 reachability you test and, for BIMI, the hosts of brand logos. They see a request from our server, and website fetches name DNS Super and link to our bot page. They never see you, your IP address or your account.
What we don't do
No analytics, no tracking pixels, no advertising, no third-party scripts and no third-party fonts. We don't sell or rent personal data, and we don't use what you check to build profiles.
We make no decisions about you based solely on automated processing that have legal or similarly significant effects. Our limits only slow down or refuse requests, and a person decides any suspension of an account.
Cookies
We set only the cookies the site needs to work, and a theme cookie when you pick a theme yourself, so there is no cookie banner. Nothing here is used for tracking.
| Cookie | What it does | Set when | Kept for | Why no consent is asked |
|---|---|---|---|---|
| __Host-dnssuper_session | Keeps you signed in (HttpOnly; holds a session token the website sends to our API). | When you sign in | Until you sign out, at most 30 days | Strictly necessary |
| dnssuper_signed_in | Tells our pages that you are signed in (the value is just 1; it grants nothing). | When you sign in | The same as the session cookie | Strictly necessary |
| __Host-dnssuper_signin | Ties an emailed sign-in link to the browser that asked for it (a hash, never your address). | When you ask for a sign-in link | 15 minutes | Strictly necessary |
| __Host-dnssuper_theme | Remembers the light or dark theme you picked. | Only when you pick Light or Dark | 365 days, or until you pick System | Your preference |
We also use the browser's session storage, which never leaves your browser and is gone when the tab closes:
| Storage | What it does | Set when | Kept for | Why no consent is asked |
|---|---|---|---|---|
| Compare and hand-off keys | Carries what you entered from one of our pages to the next, so it never appears in a web address: a domain or web address (search to report, report to compare, email audit to checker, monitor set-up), a DNS record (email audit to record builder) or a certificate request (CSR generator to decoder; never the private key). | When you press a button that opens another page with what you entered | Until the next page reads it, or the tab closes | Strictly necessary |
| dnssuper:pending-check | Fills in the tool you picked from the command menu, without running it. | When you pick a check in the command menu | Until the tool page reads it, or the tab closes | Strictly necessary |
Who processes data for us
Our servers are hosted in the EU. The companies that process data on our behalf are listed on the subprocessors page, which this notice and the data processing agreement refer to. Stripe isn't one of them, because it acts for itself as merchant of record. That page lists it apart, as an independent controller.
| Company | Service | Data it handles | Location | Transfer safeguard | Status |
|---|---|---|---|---|---|
| Hetzner Online GmbH | Hosting | Everything the service stores and processes (servers, disks, backups on the server) | Finland (EU) | None needed (EU) | In use |
| Scaleway SAS (Transactional Email) | Email delivery | Recipients' email addresses and the messages (sign-in links, invitations, email-change confirmations and notices, and alerts) | France (EU) | None needed (EU) | In use |
| Hostinger (Hostinger Mail) | Our mailbox | Emails people send us and our replies (requests, complaints, abuse and security reports), with the sender's address, and the notices we send account owners about changes to our terms, privacy notice, prices, plans, service or subprocessors, suspensions, closures and personal data breaches | EU | None needed (EU) | In use |
| Hetzner Online GmbH (Object Storage) | Off-site backup copy | Encrypted backup files only (Hetzner never holds the key) | Germany (EU) | None needed (EU) | In use |
Not used at all: error tracking, uptime monitoring, analytics, content delivery network, web fonts.
Independent controllers
These companies use the data for their own purposes, under their own terms. They are not our subprocessors.
| Company | Service | Data it handles | Location | Transfer safeguard |
|---|---|---|---|---|
| Stripe (Managed Payments) | Payments (merchant of record) | Billing details, payment details and invoices. As merchant of record, Stripe sells the credits and plans to you and uses this data for itself, not on our behalf. | As Stripe's own terms and privacy policy say | Stripe's own, as an independent controller |
How long we keep it
| Data | Why | Legal basis | Kept for |
|---|---|---|---|
| Tool, target, price, cache hit, status and time of each metered call, and the API key used; free checks without an account are recorded under our website's own account, with nothing that identifies the visitor | Billing records, the usage page and its exports, abuse limits | Contract (GDPR Art. 6(1)(b)); billing records also legal obligation (Art. 6(1)(c)); free checks without an account legitimate interest (Art. 6(1)(f)) in protecting the service | 13 months, then deleted a month at a time |
| Tool, price and time of a deleted account's calls (the checked domains and addresses removed at deletion) | Billing records that must match the ledger | Legal obligation (Art. 6(1)(c)) | Checked domains and addresses removed at deletion; the rest is deleted with its month's records at 13 months |
| Credit ledger rows, payments (Stripe ids, amount, tax, currency, receipt link), the account's Stripe customer id and Stripe event ids | Accounting, refunds, tax records | Contract and legal obligation (Art. 6(1)(b) and (c)) | 10 years, also after the account is deleted, kept only against the account's internal id |
| Account email address and name, plan; users' email addresses and names, and the version of our terms each user accepted and when; member roles | Signing in, the dashboard, billing, and proof of which terms each user accepted | Contract (Art. 6(1)(b)); the terms record also legitimate interest (Art. 6(1)(f)) in being able to prove our agreement | Until the account or user is deleted in Settings |
| Result envelopes of job rows (the checked domain and what was found) | Showing a job's rows and downloads after it ran | Contract (Art. 6(1)(b)) | 7 days after the row ran |
| Jobs and their rows (targets, parameters, status, credits) | Bulk checks and their history | Contract (Art. 6(1)(b)) | 30 days after the job finished |
| Each monitor run's status and snapshot | Change detection and the monitor's history | Contract (Art. 6(1)(b)) | 30 days |
| Changes a monitor found (what changed, before and after) | The monitor's event history and alerts | Contract (Art. 6(1)(b)) | For the monitor's life; deleted with the monitor |
| Alert deliveries (channel, recipients' user ids, status) | Sending alerts once, retries, the channel's delivery log | Contract (Art. 6(1)(b)) | 90 days |
| Daily uptime and response-time figures per monitor | Uptime percentages on the monitor page | Contract (Art. 6(1)(b)) | 400 days |
| Daily state of our own services (no customer data) | The public status page's history | Legitimate interest (Art. 6(1)(f)) in running the service | 400 days |
| PDF exports and their render input (a projection of a result) | Downloading a PDF of a result | Contract (Art. 6(1)(b)) | 24 hours |
| Shared report snapshots (a result frozen behind an unguessable link) and their view counts | Sharing a result with people outside the account | Contract (Art. 6(1)(b)) | Until the link expires or is revoked, when the snapshot is deleted |
| What is left of a revoked or expired shared report (tool, checked domain, dates, view count; no snapshot) | The account's data export and reviewing reports of abusive links | Contract (Art. 6(1)(b)); abuse reviews legitimate interest (Art. 6(1)(f)) in preventing abuse | 30 days after the link was revoked or expired |
| Sign-in and email-change link tokens (a hash) and the address they were sent to | Signing in by email, confirming a new email address | Contract (Art. 6(1)(b)) | 1 day |
| A requested change of sign-in address (the new address and a hash of the link sent to it) | Changing the address only after the new address confirms it | Contract (Art. 6(1)(b)) | 1 hour to use the link; the request is deleted 1 day after it was made |
| A user's earlier email addresses after a change in Settings (old and new address, when) | Account security, so a change someone else made can be traced and undone | Legitimate interest (Art. 6(1)(f)) in securing accounts | 12 months after the change, or until the user is deleted in Settings if that comes first |
| Website sessions (a token hash, the browser's user agent, times) | Staying signed in, the sessions list in Settings | Contract (Art. 6(1)(b)) | 30 days after the session ended |
| Invitations (the invited address, a token hash) | Adding members to an account | Contract (Art. 6(1)(b)) | 30 days after the invitation expired or was revoked |
| The result of a charged call, kept under its request id | A retried request gets the same answer and is never charged twice | Contract (Art. 6(1)(b)) | 24 hours |
| Raw WHOIS text, scrubbed of contact data before it is kept | Showing the registry's own wording | Legitimate interest (Art. 6(1)(f)) in showing the registry's own record | At most 1 hour in the shared cache; up to 24 hours in the caller's own replay copy |
| Email headers and messages pasted into the header analyzer and DKIM verifier | Analysing what the visitor pasted | Contract (Art. 6(1)(b)); for visitors without an account, legitimate interest (Art. 6(1)(f)) in answering what they asked | Never stored, cached, logged or shared |
| Private keys made by the CSR generator | Making a certificate request | Not applicable (never received) | Never leave the browser |
| A keyed hash of the visitor's IP address (IPv6 by /64) with request counts | Free-check limits and abuse protection for anonymous visitors | Legitimate interest (Art. 6(1)(f)) in protecting the service | Under 48 hours |
| Edge and container logs (truncated IP addresses, paths without lookup targets, status, timing) | Operating and securing the service | Legitimate interest (Art. 6(1)(f)) in operating, securing and fixing the service | 14 days |
| Webhook URLs and secrets of alert channels | Delivering alerts | Contract (Art. 6(1)(b)) | Until the channel or the account is deleted |
| API keys (stored only as a keyed hash; only the first 12 characters are shown) | Authenticating API and MCP calls | Contract (Art. 6(1)(b)) | Revoked at once when the account is deleted, and their labels and creators erased; the first 12 characters and the hash stay against the account's internal id, like the usage records (until then, revoked keys stay listed as revoked) |
| Encrypted copies of our database, which holds everything in this table except PDF export files, server logs, our mailbox, the other backup copies, what we never store, and the short-lived data we keep only in our cache (counters, cached results and pages, replays, live events and error fingerprints) | Restoring the service after a failure, as part of keeping data secure | Legitimate interest (Art. 6(1)(f)) in being able to restore the service and its data | About 3 weeks (3 weekly full backups with their archived changes) |
| A copy of the encrypted backups in a second data centre | Surviving the loss of the server, as part of keeping data secure | Legitimate interest (Art. 6(1)(f)) in being able to restore the service if the server is lost | 60 days, then deleted by the storage's own rule |
| Not in use: an offline copy of the encrypted backups kept by the operator | A second copy under the operator's control | Legitimate interest (Art. 6(1)(f)) in keeping a copy of the backups under the operator's control | None while not in use; if set up, it mirrors the server's backups, deletions included, so about 3 weeks |
| Vulnerability reports (summary, details, an optional reply address; nothing about the sender) | Fixing security problems people report | Legitimate interest (Art. 6(1)(f)) in securing the service | Until reviewed, then 90 days |
| Email sent to hello@dnssuper.com, abuse@dnssuper.com or security@dnssuper.com and our replies (refund and withdrawal requests, privacy requests, complaints, abuse and security reports), with the sender's address | Answering and handling these requests, and defending legal claims | Contract (Art. 6(1)(b)) and legitimate interest (Art. 6(1)(f)) in handling requests and defending claims; privacy requests also legal obligation (Art. 6(1)(c)) | 3 years after the matter is closed |
| Error fingerprints (exception type and code frames; never messages, targets or user data) | Finding and fixing faults | Legitimate interest (Art. 6(1)(f)) in finding and fixing faults in the service | 15 days |
| Approximate counts of the distinct domains each account or visitor hash looks up in registration data | Spotting mass harvesting of registration data, which the registries' terms forbid | Legitimate interest (Art. 6(1)(f)) in preventing mass harvesting of registration data | 26 hours |
| Monitors (the target domain or URL, label, options, schedule, state, who created it) and their channel links | Watching what the account asked us to watch | Contract (Art. 6(1)(b)) | Until the monitor or the account is deleted |
| Hourly uptime and response-time figures per monitor | Building the daily uptime figures | Contract (Art. 6(1)(b)) | 8 days |
| Alert channels (name, kind, status and, for email, the account members who get the alerts, by user id) and members' opt-outs | Delivering alerts to the members, webhooks or Slack channels the account chose | Contract (Art. 6(1)(b)) | Until the channel or the account is deleted; an opt-out also goes with its user |
| Passkeys (credential id, public key, the name you gave it, transports, last use) | Signing in with a passkey | Contract (Art. 6(1)(b)) | Until the passkey or the user is deleted |
| White-label branding (company name, logo, footer text, who changed it) | Branded PDF exports | Contract (Art. 6(1)(b)) | Until removed or the account is deleted |
| Expiry calendar feeds (a token hash, who created it, times) | The account's private expiry calendar link | Contract (Art. 6(1)(b)) | Revoked when replaced or when the account is deleted; revoked rows (no checked domains) stay against the account's internal id |
| Reports that a shared link is abusive (a reason from a fixed list; nothing about the reporter) | Taking down abusive shared links | Legitimate interest (Art. 6(1)(f)) in preventing abuse | 90 days after the report, or earlier when the shared link itself is deleted (30 days after it expires or is revoked) |
| Tool results in the shared cache, and results cached per account (or per visitor hash, for checks without an account) for domain availability and non-root URL pages | Answering a repeated check quickly and cheaply | Contract (Art. 6(1)(b)) and legitimate interest (Art. 6(1)(f)) in answering repeated checks quickly and cheaply | The tool's cache lifetime (minutes to hours; partial results at most 60 s, errors never) |
| Live events of a check, a job or an account's activity (progress, results, and the tool and target of each new call) | Showing a check or job while it runs, and recovering its result after a dropped connection | Contract (Art. 6(1)(b)); for visitors without an account, legitimate interest (Art. 6(1)(f)) in answering what they asked | 10 minutes after the last event |
| Copies of the web pages and files our tools fetch from the websites you check | Fetching a page once when several tools or checks need it | Contract (Art. 6(1)(b)) and legitimate interest (Art. 6(1)(f)) in fetching each page no more often than needed | 5 minutes |
When you delete an account, we delete at once its monitors (with their history), alert channels, invitations, branding and PDF exports. We revoke its API keys and erase their labels, revoke its shared reports and delete their snapshots, cancel its unfinished jobs, and erase the account's email address and name. Any plan is set to end at the close of its current period and doesn't renew. Its members leave it, and a user who belongs to no other account is deleted with their sessions, passkeys and record of email changes. Its usage records lose the domains and addresses you checked.
The rest expires on its normal schedule: finished jobs and their rows 30 days after the job finished, stored results 7 days after the row ran, and the rest of a revoked shared report 30 days after the link was revoked or expired. Deleted data also stays in our encrypted backups until they expire, after about 3 weeks (3 weekly full backups with their archived changes) on our server and 60 days, then deleted by the storage's own rule in the off-site copy. We don't restore it into live use.
We keep some records against the account's internal id only, with no name or email address: usage records without the checked domains, a revoked key's first 12 characters and its hash, and, because accounting law requires it, the ledger, payments and Stripe ids for the period the retention table gives.
Your rights
In Settings you can download your own data, and an account's owner can download the account's data, once a day. You can also correct your name, delete your user, and, as an account's owner, delete the account. You can change your email address in Settings too: we send a link to the new address and a notice to the old one, and the address changes only when the link is used. You have 1 hour to use the link; the request is deleted 1 day after it was made. We keep a record of the change (the old and new address and when), so a change someone else made can be traced and undone, for 12 months after the change, or until the user is deleted in Settings if that comes first.
You have the right to access, correct and delete your personal data, to restrict or object to processing, and to data portability. Write to hello@dnssuper.com for anything Settings doesn't cover. We answer within one month. If a request is complex or one of many, we may take up to two more months, and we tell you so within the first month. We may ask you to show that the account or address is yours before we act. If a request is clearly unfounded or excessive, we may refuse it or charge a reasonable fee, as the law allows.
If you think we got something wrong, you can complain to the Lithuanian State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija), or to the authority where you live.
Changes
We date every version of this notice and keep the earlier ones. For changes that affect you, we tell the account's owner by email at least 30 days before they take effect, unless the law requires a change sooner.
| Version | Status | In force from | Last reviewed |
|---|---|---|---|
| 1.0 | Current | 19 November 2026 | 19 November 2026 |