This data processing agreement ("DPA") forms part of the agreement under the terms of service between the customer ("you") and MB IO Sprendimai, Perkūnkiemio g. 19, LT-12120 Vilnius, Lithuania, company code 307100077 ("we"). It applies when you use DNS Super for a trade, business or profession and have us process personal data for which you are the controller, under Article 28 of the GDPR. It takes effect when you accept the terms and lasts as long as they apply to you. It doesn't apply to people who use DNS Super only for themselves.
If the terms and this DPA disagree about processing personal data, this DPA applies. The limits and exclusions of liability in the terms apply to this DPA too.
Roles
We are your processor for personal data inside what you give us to process: the domains, URLs, IP addresses and networks you check or monitor and what we find about them, the email headers and messages you paste, your monitors and alert channels, your shared reports, PDF exports and branding, and the people you invite. Annex 1 describes this processing.
We are the controller of our own records about you and your account's members: user accounts and sign-in, sessions and passkeys, usage and billing records, and security and abuse records. The privacy notice explains how we handle them.
Through Stripe Managed Payments, Stripe sells our credits and plans to you as merchant of record. Stripe is an independent controller of the payment data it collects under its own terms. It is not our subprocessor.
Your instructions
We process personal data only on your documented instructions. The terms, this DPA and how you use and set up DNS Super (checks, monitors, alerts, bulk jobs, exports and shares) are your complete instructions. Any other instruction needs our written agreement, and we may charge for it. If EU or Member State law requires us to process personal data in another way, we tell you first, unless that law forbids it. If we think an instruction breaks the law, we tell you at once, and we may decline to follow it.
Your responsibilities
You make sure you may lawfully have us process the personal data you give us: that you have a legal basis for it and have told the people concerned what the law requires. Don't give us special categories of personal data or data about criminal convictions.
You compensate us for third-party claims, fines and reasonable costs, including legal fees, that arise because you had no right to have us process personal data, or because an instruction you gave broke the law, as the indemnity in the terms describes. This doesn't apply to the extent we caused the loss.
Confidentiality
Everyone who can reach personal data on our behalf is bound to keep it confidential.
Subprocessors
You authorise the subprocessors listed as in use in the subprocessor table on our subprocessors page. We tell you about a new or replaced subprocessor by email to the account's owner at least 30 days before it starts, and we update the subprocessors page.
You may object in writing within those 30 days on reasonable data protection grounds. If we can't meet your objection, your remedy is to stop using DNS Super and close the account before the change takes effect.
If we must replace a subprocessor urgently, for example because it stops its service or to keep DNS Super running or secure, we may make the change with shorter notice or at once. We then tell you as soon as we can, by email to the account's owner. You may object within 30 days of that email on the same grounds, and your remedy is the same: to stop using DNS Super and close the account.
Each subprocessor is bound by a contract with data protection obligations that meet Article 28 of the GDPR.
If a subprocessor fails to meet its data protection obligations, we remain liable to you for its performance as we are for our own, within the limits of liability in the terms as far as the law allows.
Security
We take the technical and organisational measures in Annex 2 and keep them up to date. We may change them, as long as the overall level of protection doesn't fall.
Personal data breaches
We tell you about a personal data breach that affects personal data we process for you without undue delay, and at the latest within 48 hours of becoming aware of it. We write to the account's owner by email with what we know and what we are doing about it, and send more as we learn it. Telling you about a breach is not an admission of fault or liability.
Helping you
Taking into account what we process and the information we have, we help you answer requests from data subjects and meet your duties on security, breach notifications, impact assessments and prior consultation. Settings and the API cover most requests: you can export your data and delete monitors, channels, shares, members and the account yourself. If a data subject contacts us about personal data we process for you, we refer them to you. Help beyond what Settings and the API offer may be charged at a reasonable cost, which we agree with you first.
Audits
We make available the information needed to show that we meet Article 28 of the GDPR: this DPA, the security measures in Annex 2 and written answers to your reasonable questions about them.
If that information isn't enough to show that we meet this DPA, or a supervisory authority requires it, you may have the systems we use to process your personal data inspected, on these conditions:
- The inspection is done by an independent auditor whom we reasonably accept and who is bound to keep what they learn confidential.
- It happens at most once in any 12 months, unless a supervisory authority requires more or a personal data breach affecting your data calls for it.
- You give us at least 30 days' written notice and a plan of what the inspection covers.
- It takes place during business hours in Lithuania and doesn't disrupt the service.
- It gives no access to other customers' data, or to information whose disclosure would weaken the security of the service.
- Our hosting provider's data centres are covered by that provider's own certifications and audit reports, which we pass on where we may.
- You pay the costs of the inspection, including your auditor's and our reasonable time spent on it, and you give us a copy of the report.
A supervisory authority may always audit us as the law allows.
Transfers
We host in the European Economic Area, and our subprocessors process personal data there. We transfer personal data outside it only on your instructions, or to a subprocessor added through the notice above, and only under a safeguard the GDPR recognises, such as the EU standard contractual clauses.
Liability
Our liability under this DPA and the terms together is subject to the limits and exclusions of liability in the terms. This doesn't limit liability that the law doesn't allow to be limited, such as liability for intent or gross negligence, or either party's liability to data subjects or supervisory authorities under the GDPR.
End of the agreement: return and deletion
This DPA ends when the terms stop applying to you: when you delete the account, or when we close it as the terms allow.
The return of your data is the account export in Settings, together with the results of your jobs and your PDF exports, which you can download from the dashboard. Download what you want to keep before you delete the account. The export leaves out share snapshots, branding, pending invitations, the recipients and webhook addresses of alert channels, monitor run snapshots and the detail of what changed in each monitor event. While an account is suspended, or before we close it, its owner can ask us at hello@dnssuper.com for the account export, and we send it to them.
If we close an account at once as the terms allow, we first suspend it and keep its data for 30 days. During those 30 days its owner can ask us at hello@dnssuper.com for the account export, and we send it to them. We delete the account when the 30 days end. Once an account is deleted, its data can't be returned.
Suspending an account deletes nothing: its data is kept on the normal schedule. When an account is deleted, by you or by us, its monitors, alert channels, invitations, branding and exports are deleted at once, its shares are revoked and their snapshots deleted, its user accounts go with it unless the users belong to another account, and its usage history loses the domains and addresses you checked. What remains expires on its normal schedule: jobs 30 days after the job finished, stored results 7 days after the row ran, the rest of a revoked shared report 30 days after the link was revoked or expired, copies of charged results kept so a retried request isn't charged twice after 24 hours, and cached results and live progress streams within minutes or hours. Deleted data stays in our encrypted backups until they expire, 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.
Where the law requires us to keep records, such as accounting records, we keep them against the account's pseudonymous id, as our own records. The retention table on the privacy notice lists every period.
Law and courts
This DPA is governed by the law of the Republic of Lithuania. The courts of Vilnius, Lithuania, have exclusive jurisdiction over any dispute about it.
Annex 1: details of processing
Subject matter and duration
We provide DNS Super to you as the terms describe. We process personal data for as long as the terms apply to you, and then until the periods in "End of the agreement" above run out.
Nature and purpose
We receive what you check, monitor or paste, contact the systems that hold the answer (DNS servers, domain registries, domain registrars when a registry refers us to them, the regional internet registries, 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), compare what we find with earlier runs, store results, send alerts by email or webhook, build PDF exports and shared reports, and delete all of it on schedule. We do this only to give you the checks, monitors, alerts, bulk jobs, exports and shares you ask for.
Types of personal data
- What you check or monitor. Domain names, URLs, IP addresses and networks, which can identify a person, and what public sources say about them, such as DNS records, registration data, certificates and website content.
- What you paste. Email headers and messages pasted into the email header analyzer and the DKIM verifier, which can hold names, addresses and message content. They are processed in memory only, for the length of the request, and never stored, cached, logged or shared.
- People you add. Email addresses of people you invite, and the names you give alert channels. Email alerts go only to your account's members.
- Alert channels. Webhook URLs and secrets, kept encrypted.
- Branding. The company name, logo and footer text you set for PDF exports, which can name a person.
Categories of data subjects
- Your account's members and the people you invite.
- People reached through your webhook or Slack alert channels, where those identify a person.
- People whose personal data appears in the domains, URLs, addresses, records, websites, headers or messages you check, monitor or paste, such as domain holders, website operators, and the senders and recipients of email.
- People named in your branding.
Annex 2: security measures
- Hosting and network. Servers in EU data centres; a firewall that admits only web traffic and administrator SSH from allow-listed addresses; containers that drop every Linux capability they don't need and can't gain new privileges, most running as unprivileged users with read-only file systems; the database on an internal network with no internet access.
- Encryption. HTTPS everywhere with HSTS; database backups encrypted before they leave PostgreSQL; alert channel secrets encrypted with a key kept outside the database.
- Access. Sign-in by email link or passkey; API keys stored only as keyed hashes; separate database roles for the application and for migrations, with the least privileges each needs.
- Data minimisation. Anonymous visitors counted by a keyed hash of their address, never the address; pasted email content never stored; logs without the domains you check; no third-party scripts, analytics or trackers.
- Resilience. Continuous archiving of database changes, nightly backups, an encrypted off-site copy in a second data centre and a monthly restore test.
- Outbound requests. Every request our servers make for you goes through a fetcher that refuses private and internal addresses.
| Version | Status | In force from | Last reviewed |
|---|---|---|---|
| 1.0 | Current | 19 November 2026 | 19 November 2026 |