Article
How to Check if an Email Verifier Is GDPR Compliant
By Unlimited Verifier Team ·

Summary
There is no GDPR certificate for email verifiers, so a privacy badge tells you little. To check compliance, confirm the vendor will sign an Article 28 Data Processing Agreement, then verify its sub-processors, transfer mechanisms, data storage location and retention and deletion terms in writing.To check whether an email verifier is GDPR compliant, confirm it will sign an Article 28 Data Processing Agreement (DPA) before you upload, and that its written terms state where data is stored, how long it is kept, and how it is deleted. No GDPR certificate exists for email verifiers, so a privacy page or "GDPR ready" badge answers none of these questions. This sits within email verification compliance and hygiene, and the wider picture is covered in our email verification data privacy pillar.
Quick answer
- There is no GDPR certificate for email verifiers. Judge a vendor on signed documents, sub-processor lists and transfer mechanisms, not on badges.
- The verifier is normally your processor. Under Article 28, you need a signed DPA before any real address is uploaded.
- Check retention for every data type. Unlimited Verifier states that results are kept 24 hours on Free and 30 days on Pro. Ask separately about uploads, logs and backups.
- Minimise what you send. An email column plus an internal ID cut the data fields leaving your systems by about 83% in the worked example below.
- Treat these as red flags: the vendor reuses your uploads for its own database, won't name its sub-processors, or can't name a transfer mechanism.
Is an email address personal data, and is verifying it "processing"?
Yes. An address like jane.doe@company.com identifies a person, so it is personal data under Article 4(1) of the GDPR. Role addresses such as info@ are harder to classify, and many compliance teams still treat them as personal data when they can be linked to someone in the organisation. Treat every address in your list that way.
Verification is processing under Article 4(2), which covers collecting, storing, consulting, using and transmitting data. The step most teams overlook is the SMTP mailbox check. To test a mailbox, the verifier passes the address to the recipient domain's mail server, as the SMTP protocol in RFC 5321 describes. That server belongs to a third party you have no contract with. Your DPA covers the verifier, not that disclosure, so record it in your processing documentation.
Verification also needs a lawful basis. Many teams rely on legitimate interests under Article 6(1)(f), but that requires a documented balancing test and is not automatic. Our guide on whether verifying emails without permission is legal covers the reasoning, and our breakdown of whether verification counts as processing under GDPR goes further.
Bottom line: Every uploaded address is personal data, and the SMTP probe creates a disclosure you need to account for.
Is there an official GDPR certificate for email verifiers?
No. Article 42 allows approved certification schemes, but none is a general certificate for email verifiers that you can look up. When a vendor says it is "GDPR compliant," treat that as a claim to verify with documents. A third-party privacy seal is a pointer to evidence, not a substitute for a DPA.
The useful evidence is documentary. Ask for the signed document, its date and its scope. The table below ranks common evidence by how much it proves.
| Evidence | What it proves | Weight | What to watch for |
|---|---|---|---|
| Signed DPA (Article 28) | Binding processing terms | Strong | An unsigned template, or no sub-processor annex |
| Dated sub-processor list with change notice | Who else touches your data | Strong | "Available on request" with no version date |
| Transfer mechanism (SCCs or DPF listing) | Legal basis for transfers outside the EEA | Strong when you can verify it | A Data Privacy Framework claim you cannot find on the official list |
| ISO/IEC 27001 certificate | A security management system exists | Medium | A certificate scope that excludes the verification service |
| SOC 2 report | Controls tested over a period | Medium | A readiness letter or bridge letter presented as a full report |
| Published privacy notice | What the vendor says it does | Weak alone | Silence on use of customer uploads for its own purposes |
| "GDPR compliant" badge | Nothing verifiable | None | No document behind it |
Bottom line: Replace "Are you GDPR compliant?" with "Send me your signed DPA, sub-processor list and transfer documentation."
Who is the controller and who is the processor?
You are the controller because you decide why the list is being checked: to clean your own database. The verifier is normally a processor acting on your instructions, as defined in Article 4(8). The European Data Protection Board publishes guidance on how to apply these concepts in practice.
The role can shift. Under Article 28(10), a processor that determines the purposes and means of processing is treated as a controller for that processing. The clearest example is a vendor that uses uploaded addresses to improve its own global dataset. That is a purpose of its own, and it needs its own lawful basis. If you run email verification for ecommerce and SaaS workflows, this is the point where a vendor's terms can quietly change your risk.
Bottom line: The verifier should be a processor for your uploads. Any use of your data for its own ends changes its legal role, and you need to know about it before you upload.
What must a verifier's Data Processing Agreement include?
Article 28(3) makes a written contract mandatory. It must set out the subject matter, duration, nature and purpose of processing, the types of personal data and categories of data subjects, and your rights as controller. The table below turns the mandatory elements into checks you can run on a real contract.
| Requirement | GDPR reference | What to verify in practice |
|---|---|---|
| Documented instructions, including on transfers | Art. 28(3)(a) | Vendor processes only on your instructions, and transfers only as instructed |
| Staff confidentiality | Art. 28(3)(b) | Everyone with access is bound by a confidentiality duty |
| Security measures | Art. 28(3)(c), Art. 32 | Encryption in transit and at rest, access controls, access logging |
| Sub-processor control | Art. 28(2), 28(4) | Named list, advance notice of changes, right to object |
| Help with data subject requests | Art. 28(3)(e) | Vendor assists you within a stated time |
| Help with breaches and assessments | Art. 28(3)(f) | Assistance with notification and impact assessments |
| Deletion or return at the end | Art. 28(3)(g) | Clear deletion timeline and written confirmation of erasure |
| Audit rights | Art. 28(3)(h) | You can request evidence of compliance |
Bottom line: If any row is missing from the contract, the DPA is incomplete, whatever the vendor's website says.
Where does the verifier store and transfer your data?
Transfers outside the EEA are governed by Articles 44 to 49. Adequacy decisions under Article 45 cover some countries. Otherwise the most common route is the Standard Contractual Clauses under Article 46. The European Commission publishes the SCCs, which were updated in 2021. For transfers to the United States, check whether the recipient is certified under the EU-US Data Privacy Framework on the official Data Privacy Framework website.
Hosting location is only part of the answer. Remote access from another country can also count as a transfer, and EDPB guidance generally treats it that way. A vendor that stores files in the EU but lets support staff view them from elsewhere still has a transfer to document. Ask three questions in writing:
- Which regions store uploaded files, results and logs, and from which countries is data accessed?
- Which sub-processors touch the data, including cloud hosts and logging or support tools?
- Which transfer mechanism covers each transfer?
Ask for the executed SCCs, not just a reference to them. Our explainer on where email verification servers are located covers how to read a vendor's infrastructure answers.
Bottom line: A vendor should be able to name every country that stores or accesses your addresses, and every sub-processor involved.
How long can an email verifier keep your data?
Storage limitation under Article 5(1)(e) says personal data should be kept no longer than necessary. For a verification job, the purpose ends once you have your results, so any longer retention needs a clear justification.
Unlimited Verifier publishes two windows, and both apply to results: 24 hours on the Free plan and 30 days on Pro. Those figures are a useful benchmark because they are specific. They don't settle the whole question, though. Ask for the periods for each data type separately, because a results window says nothing about the uploaded file, logs or backups.
| Data type | Question to ask | A good answer looks like |
|---|---|---|
| Uploaded file | How long after processing is it deleted? | A stated period, or deletion when the job completes |
| Results file | What is the retention window, per plan? | A number of hours or days, per plan |
| Application logs | Do logs contain addresses, and for how long? | Addresses masked, or a short named window |
| Backups | How long after deletion do backup copies persist? | A named period in days |
| Sub-processor copies | Do cloud or logging providers keep copies? | Named providers, bound by the same retention terms |
Worked example (Pro): You upload a 25,000-row list on 3 March, and results are generated that day. Pro's 30-day results window closes on 2 April. Your own policy says you delete local copies within 7 days of export, which means 10 March. Your deletion date is well inside the vendor's window. The window is a ceiling, not a target.
Worked example (Free): A 150-row list uploaded at 09:00 on 3 March has results held until 09:00 on 4 March under the 24-hour window. The Free plan's limit of 150 emails per list makes this a practical way to test your own deletion routine before you handle a real list.
The public FTC guidance on data security reinforces the same habit: keep data only as long as you need it. Our guides on whether email verifiers store the emails you check and how long verifiers keep uploaded lists cover the details.
Bottom line: Compare the vendor's windows with your own deletion schedule, and get an answer for backups as well.
Does the verifier use your addresses for its own purposes?
This is the question teams most often forget. A verifier that uses your uploads to improve its own dataset acts as a controller for that use, which needs its own lawful basis under Article 6. Ask it directly: "Do you use customer-submitted addresses to update your own database, train models or enrich other customers' results?"
If the answer is yes, ask which lawful basis the vendor relies on, whether you can opt out, and how the use appears in its privacy notice. If the answer is no, get it into the DPA. A sales call or a support email is not a contract. This matters most for teams doing email verification for sales prospecting, where cold lists are common and the vendor's terms are easy to skim past.
Bottom line: Ask a yes-or-no question about own-purpose use, and get the answer in the contract.
How do you check a verifier's security and breach handling?
Article 32 requires appropriate security. For a verifier, look for TLS on uploads and API calls, encryption at rest, role-based staff access, and logging of access to customer files.
Breach timing is the detail to pin down. A controller must notify its supervisory authority within 72 hours of becoming aware of a breach, under Article 33(1). A processor must notify the controller without undue delay, under Article 33(2). Ask the vendor to commit to a number of hours. We'd push for 24 hours, because a 72-hour processor deadline leaves you no time to meet your own 72-hour clock.
Unlimited Verifier's check engine is open source on GitHub, so your technical team can read what the checks do. That helps with a security review, but it doesn't show how the hosted service stores data. Ask for that separately, along with a current ISO/IEC 27001 certificate or SOC 2 report if the vendor holds one, and check the dates.
Bottom line: Security claims are only useful with a certificate, a date and a breach-notice commitment you can hold the vendor to.
Does GDPR apply if you're outside the EU?
GDPR applies if you are established in the EU, or if you offer goods or services to people in the EU or monitor their behaviour, under Article 3. If none of those applies, GDPR may not cover your list, but other laws probably do. For US-based senders, read our note on whether email verification is allowed under CCPA.
If GDPR does apply to you, a verifier located outside the EU does not remove the DPA requirement. The contract is still required, and the transfer question in the earlier section still applies. Ask whether the DPA is available on the Free plan. If it isn't, don't upload real customer addresses to a Free account, because the contract is the foundation of everything else in this checklist.
Bottom line: Work out whether GDPR applies to your list first, then apply the same DPA and transfer checks whatever the vendor's location.
How do you check a verifier in eight steps?
Work through these steps in order before you upload a real list.
- Confirm the vendor's role. Ask whether it acts as your processor and whether it uses your data for any purpose of its own.
- Get the DPA and check it against the table above. Do not upload until it is signed.
- Obtain the sub-processor list with a dated version, and confirm you will receive notice of changes.
- Record hosting regions and remote-access locations, plus the transfer mechanism for each.
- Get the retention periods for uploads, results, logs and backups, in writing.
- Test deletion. Send a written erasure request for a test file, and note how long confirmation takes. Our guide on deleting your data from an email verifier explains what to request.
- Review security evidence and the breach-notice commitment, in hours.
- Minimise the data you send, add the verifier to your record of processing under Article 30, and schedule re-checks as part of your email list maintenance best practices.
Then score the answers against the scorecard in the worked example below.
Bottom line: Steps 1 and 2 are gates. If either fails, you do not upload.
How do you run a privacy test on a verifier yourself?
This test takes roughly an hour, not counting the wait for a deletion reply. It uses addresses you control, so no third party's personal data is at risk.
- Create a test list of 20 addresses you own, including two deliberately misspelled ones.
- Strip the list to two columns: the email address and an internal ID such as
contact_id. Keep a mapping of ID to email in your own system, and match results back by email address rather than assuming the verifier returns your ID. - Read the vendor's privacy notice and DPA, and note the retention and transfer answers.
- Sign up for a free account. Standard verification is unlimited on every plan, including Free, so re-running this test costs nothing per email.
- Upload the file. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Read the three buckets: Valid, Risky and Invalid. A misspelled domain should usually come back Invalid. A misspelling at a catch-all domain may come back Risky, because catch-all domains accept any address. Our catch-all email verification page explains that bucket.
- Export the results as CSV, Excel or JSON, and check which fields come back.
- Delete your local copies of the export, then send a written erasure request covering the test data. Record the date and the reply.
- Spot-check single addresses with the free email checker when you need an individual result.
If you want to automate the workflow, the Pro plan includes API access, and you can create API keys from your account. Free accounts don't have API access. Treat email verification API and automation as processing too: API calls transmit personal data, so the same DPA and retention questions apply. If you're planning production use, compare email verification pricing against your list sizes. Pro is $29 a month, or $25 a month billed annually, and it handles lists of up to 25,000 emails each.
Bottom line: A small test shows how the workflow handles data before any real customer records are involved.
Worked example: scoring two verifiers against the checklist
Use a scorecard with ten checks: DPA signed, sub-processors listed, transfer mechanism stated, retention stated for each data type, deletion process with a timeline, no own-purpose use, breach notice in hours, security evidence, DSAR assistance, and audit rights. Score each check Pass = 1, Partial = 0.5, and Fail or Unknown = 0. This is our suggested scorecard, not an industry standard.
Apply a gate rule: if the DPA or transfer mechanism is not a clear Pass, you do not upload, whatever the total. The two hypothetical vendors below show why.
- Vendor A: 8 Pass, 2 Partial. Score = 8 + (2 × 0.5) = 9.0 / 10. Gate passed.
- Vendor B: 5 Pass, 2 Partial, 3 Unknown. Score = 5 + (2 × 0.5) = 6.0 / 10. The transfer mechanism is Unknown, so the gate fails and you do not upload, despite a respectable score.
The gate matters more than the total. A high score built on a missing transfer mechanism is still a compliance problem. If you are comparing options before this stage, our overview of the best email verification tools helps narrow the field, but the gate decides whether a vendor qualifies at all.
Data minimisation example: A 60,000-contact list with 12 columns sends 60,000 × 12 = 720,000 data fields. Sending only email and an internal ID sends 60,000 × 2 = 120,000 fields. The reduction is 1 − (120,000 ÷ 720,000) = 83%. Hashing is not a shortcut: our note on whether email verification works with hashed emails explains why hashed addresses generally remain personal data.
Bottom line: Use the gate to decide whether to upload, and the score to compare the vendors that pass it.
How we compared (and limitations)
This article is based on public documentation: the text of the GDPR, EDPB guidance, European Commission SCCs, the Data Privacy Framework list, and the facts we have published about Unlimited Verifier. We have not reviewed any vendor's contracts or audited any vendor's systems.
- Unlimited Verifier's retention windows (24 hours on Free, 30 days on Pro) are the company's stated figures for results. They do not cover uploads, logs or backups, so ask for those separately. Check current terms before you rely on them.
- Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, and it speaks to deliverability, not to how data is handled.
- Fines under Article 83 are capped at €10 million or 2% of worldwide annual turnover for breaches of obligations such as Article 28, and at €20 million or 4% for breaches of transfer rules under Articles 44 to 49. The higher figure applies.
This is not legal advice. Have counsel review any DPA before you sign it.
Bottom line: The checklist tells you what to ask. Only the signed documents answer it.
Common mistakes that fail GDPR checks
- Trusting a "GDPR compliant" badge with no signed DPA behind it.
- Uploading full CRM exports with names, phone numbers and notes. Minimisation is the easiest win.
- Assuming deletion from the dashboard covers backups. Ask for the backup window in writing.
- Forgetting your own exports. A downloaded CSV on a laptop or shared drive is your retention problem, not the vendor's.
- Ignoring the API. Calls transmit personal data under the same obligations as uploads.
- Treating signup checks as outside scope. If you validate addresses on a form, that is processing too, and it needs the same DPA.
- Using accuracy claims as a privacy signal. A 99.5% accuracy figure says nothing about storage or transfers.
- Skipping the Article 30 record. Add the verifier to your record of processing and note the SMTP probe disclosure.
- Assuming verification equals consent. Checking an address does not give you permission to email it. That is a separate question, covered in our guide on whether it is ethical to verify emails before cold outreach.
Bottom line: Many GDPR problems in list cleaning come from the process around the tool, such as exports, backups and ad hoc sharing, rather than from the verifier's checks.
Four-step GDPR check for email verifiers
- Contract first: Confirm a signed Article 28 DPA exists, is dated, and covers the verification service.
- Sub-processors: Get the current list, including any mail-server or hosting providers, and confirm notice of changes.
- Transfers: If data leaves the EEA, identify the mechanism (adequacy decision or SCCs under Article 46) and request the signed copy.
- Retention and deletion: Get written periods for uploads, logs, results and backups, plus the deletion process.
Red flags: reuse of your uploads for the vendor's own database, unnamed sub-processors, or no transfer mechanism when data leaves the EEA.
Frequently asked questions
Is there a GDPR certificate for email verifiers?
No. There is no general GDPR certificate for email verifiers that you can look up. Article 42 allows approved certification schemes, but none applies broadly to this sector. Treat any "GDPR compliant" claim as something to verify with signed documents, such as a DPA, sub-processor list and transfer documentation.
Does an email verifier need to sign a DPA?
Usually yes. When a verifier processes email addresses on your behalf, it normally acts as your processor under Article 28 of the GDPR. That requires a written contract, commonly called a Data Processing Agreement, before you upload any real addresses. Check that the DPA is signed, dated and covers the verification service.
What should I check in an email verifier's privacy policy?
Look for where data is stored, how long each data type is kept, how it is deleted and which sub-processors receive it. A privacy policy alone is not a contract, so cross-check its claims against the DPA. Ask for retention periods separately for uploads, logs, results and backups, since they often differ.
Does the SMTP check create a data transfer?
It can. An SMTP mailbox check passes the address to the recipient domain's mail server, which is a third party. Your DPA with the verifier does not cover that disclosure. Record it in your processing documentation and assess whether the lawful basis and transparency obligations still hold.
What are standard contractual clauses and when do they matter?
Standard Contractual Clauses (SCCs) are EU-approved contract terms used under Article 46 to support transfers of personal data outside the EEA. If your verifier or its sub-processors are based or hosted outside the EEA, ask which transfer mechanism applies, such as SCCs or an adequacy decision, and request the signed version.
Should a verifier be able to reuse my uploaded list?
A verifier should only use your data to provide the service you ordered. If its terms allow it to reuse uploads to build its own database or train models, that is a red flag. Such reuse usually needs a separate legal basis and must be disclosed, so ask for the exact wording and reject vague permissions.
Do I need a DPIA before using an email verifier?
Not always. A Data Protection Impact Assessment under Article 35 is required when processing is likely to result in high risk. Routine verification of business contact lists often does not meet that threshold, but document your reasoning. If you verify large volumes of personal data or use profiling-like scoring, assess whether a DPIA is needed.
How can I minimise data when using an email verifier?
Send only the email column, and where possible an internal ID rather than names or other fields. Remove addresses you no longer need, and set a deletion schedule for uploads and results. Data minimisation under Article 5(1)(c) reduces both your risk and the vendor's exposure in the event of a breach.
What should happen if the verifier suffers a data breach?
Your DPA should require the verifier to notify you without undue delay, so that you can meet your own deadline to report to the supervisory authority within 72 hours under Article 33. Check the notification window, the contact route and whether the verifier must help with your obligations to affected individuals.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.