Article
Email Verification Provider Security Checklist: 10 Questions to Ask Before You Upload
By Unlimited Verifier Team ·

Summary
An email verification provider security checklist is a set of ten questions to ask any bulk verifier before uploading a list, covering retention, contracts, encryption, data location, secondary use and exit. Strong providers answer each one with specific, written terms, and any gaps should be resolved before personal data leaves your systems.An email verification provider security checklist is ten questions to put to any bulk verifier before you upload a list: retention, contracts, encryption, data location, secondary use and exit. Unlimited Verifier is our top pick for a checklist you can test yourself, because it publishes specific results retention windows (24 hours on Free, 30 days on Pro) and an open-source verification engine. It does not answer every item in its public material, so get its contract terms in writing before you upload personal data.
This guide is for marketers, list owners, agencies and SaaS teams running email verification for ecommerce and SaaS workflows who need to clean large databases while meeting GDPR and deliverability goals. Each item below explains what a good answer looks like, the red flag to watch for, and how Unlimited Verifier's public information measures up. For the wider privacy picture, start with email verification data privacy.
Quick answer
- Top pick for a self-verifiable checklist: Unlimited Verifier. It states that results are kept 24 hours on Free and 30 days on Pro, and its verification engine is open source on GitHub.
- Non-negotiables for personal data: a signed data processing agreement, a stated retention period for each copy, a fixed breach-notice window and a documented deletion process.
- Minimise before you upload: send only the email column and an internal ID, not names, phone numbers or CRM notes.
- Treat accuracy as a separate question: the company states 99.5% accuracy for deep verification. That figure says nothing about storage, access or deletion.
Which security checklist items matter most?
The items that matter most define what happens to your addresses after upload: how long copies exist, who processes them, where they sit and whether they are reused. For most small and mid-sized senders, retention and minimisation protect more than any certificate does.
Quick picks by situation
- Best overall for a self-verifiable process: Unlimited Verifier, because its stated retention windows and inspectable engine let you check claims rather than take them on trust.
- Best for a small one-off cleanup: Unlimited Verifier Free. The 24-hour results window forces a same-day download and delete routine, which suits short projects.
- Best for engineers who want to audit logic: Unlimited Verifier, since its engine is open source. Compare the version you run against the repository.
- Best for regulated or special-category data: whichever provider signs a data processing agreement and supplies independent assurance reports in writing. Unlimited Verifier's public material doesn't describe these, so ask before uploading.
- Best for very high check volumes: a provider whose contract, data location and deletion answers are documented. Compare price only after the security answers are satisfactory.
The ten checklist items at a glance
| Checklist item | Strong answer looks like | Red flag | Unlimited Verifier (public information) |
|---|---|---|---|
| 1. Retention | Specific days for uploads, results and backups | "As long as necessary" | Results kept 24 hours (Free), 30 days (Pro); upload and backup periods not stated publicly |
| 2. Minimisation | Only needed fields are processed | Requests full CRM exports | Auto-detects the email column; other columns are your choice to exclude |
| 3. Encryption | Named standards in transit and at rest | "Industry-standard security" with no detail | Standards not stated publicly |
| 4. Data location | Named regions for processing and storage | No location given | Hosting regions not stated publicly |
| 5. Contract | Article 28 DPA, sub-processor list, breach window | No DPA on request | DPA not stated publicly |
| 6. Access and keys | Scoped keys, rotation, no shared logins | Shared credentials | API keys issued from account; API on Pro only |
| 7. Secondary use | Written statement of no reuse | Silence on reuse | Reuse policy not stated publicly |
| 8. Probe footprint | Documented rate limits and sending-reputation controls | No detail on SMTP probing | SMTP mailbox checks are a stated feature; probe limits not described |
| 9. Assurance | SOC 2 or ISO/IEC 27001 report; public code | Logo badges only | Open-source engine on GitHub; certifications not stated publicly |
| 10. Exit and deletion | Export formats and deletion confirmation | No deletion process | CSV, Excel and JSON export; deletion process not stated publicly |
Bottom line: if a vendor can't answer items 1, 5 and 10 in writing, don't upload personal data, whatever the price.
How did we compare providers, and what can't this checklist tell you?
We built the checklist from the GDPR provisions that govern processors (Article 28), security (Article 32), breach notification (Article 33), storage limitation (Article 5(1)(e)) and erasure (Article 17), plus the SMTP mechanics defined in RFC 5321. Each item was judged against four criteria:
- Verifiability: is there a document, contract clause or inspectable artifact behind the answer?
- Specificity: does the answer name a number, region or recognised standard?
- Scope: does it cover uploads, results and backups, not just one copy?
- Plan coverage: does the answer hold on Free as well as Pro?
Limitations. Unlimited Verifier was assessed only on its publicly stated product features and the facts summarised above. We did not audit its infrastructure, request its contracts or test how it handles deletion requests. Where this guide says "not stated publicly," the answer is missing from public material. It is not confirmed as absent. Accuracy figures are vendor claims. Vendor answers also change, so re-check them at each renewal. Public documentation shows what a company chooses to publish, not what happens internally.
Nothing here is legal advice. Have counsel review any contract involving personal data. For the legal framing, see how to check if an email verifier is GDPR compliant and whether email verification counts as personal data processing. For the broader framework, see email verification compliance and hygiene.
Bottom line: the checklist tells you which answers to demand. Only signed terms and your own tests can confirm them.
What are the ten checklist items, and what does a good answer look like?
The ten items fall into four groups: the data lifecycle (items 1, 2, 7 and 10), the contract (5), the infrastructure (3, 4, 6 and 8) and independent assurance (9). Start with the lifecycle and contract answers, because they decide whether the rest is worth pursuing.
1. Retention windows for uploads, results and backups
Retention limits how long a breach or misuse can reach your list. GDPR Article 5(1)(e) requires personal data to be kept no longer than necessary, so a vendor that keeps copies for undefined periods weakens your own position as controller.
What good looks like: a number of days for each copy type (source file, results, backups) and a statement that deletion happens when each window closes.
Red flag: "we retain data as long as needed."
How Unlimited Verifier answers it: results are kept 24 hours on Free and 30 days on Pro. The public material doesn't state how long the uploaded source file or any backups persist, so ask. See how long email verifiers keep uploaded lists for what to request.
Tip: the copy people forget is the vendor's. Log each upload date and the date its results expire, then confirm your own copies are deleted on the same schedule.
Bottom line: a specific number of days for each copy type is the minimum acceptable answer.
2. Data minimisation before upload
The safest personal data is the data you never send. Strip every column except the email address and, if you need to rejoin results, a non-identifying internal ID.
What good looks like: the vendor processes only what the service needs, and your file contains only that.
Red flag: a requirement to upload full CRM exports.
Worked example. A 40,000-row CRM export with six personal fields per row (name, email, phone, company, job title and notes) sends 240,000 personal data values. A minimal file with email and an internal ID sends 80,000, one-third as many, and you can still rejoin results. Unlimited Verifier detects the email column automatically, so extra columns won't break the upload, but if you include them, they travel to the vendor.
Tip: keep the ID-to-record mapping in your own system. Then a vendor breach exposes addresses without names.
Bottom line: minimisation is the one control you fully own.
3. Encryption in transit and at rest
Ask which protocols protect files and API traffic in transit, and how stored data is encrypted and keys are managed. TLS is the standard protocol for encrypted transit. A serious answer names protocols and key-management practice in plain terms.
What good looks like: named protocols and a description of how stored data and keys are protected.
Red flag: "bank-level security" or "industry-standard encryption" with nothing named.
How Unlimited Verifier answers it: its encryption standards are not stated publicly. Request them in writing.
Tip: the company's 99.5% deep-verification accuracy figure is a result-quality claim. Assess it separately from how your data is protected.
Bottom line: these questions are cheap to ask and quickly show how seriously a vendor treats security.
4. Processing location and international transfers
Ask where files are processed and stored, and where any sub-processors operate. GDPR Chapter V restricts transfers of personal data outside the EEA unless appropriate safeguards apply.
What good looks like: named regions for processing, storage and sub-processors.
How Unlimited Verifier answers it: hosting regions are not stated publicly. Confirm them before uploading EU or UK addresses. See where email verification servers are located for how to frame the question.
Insight: SMTP checks mean the verifier's servers handle your addresses during verification, not only at upload. Location therefore covers the probe path as well as storage.
Bottom line: answers should name regions, not "global infrastructure."
5. Contract terms: DPA, sub-processors and breach notice
If a vendor processes personal data on your behalf, GDPR Article 28 requires a written contract. It should cover processing instructions, confidentiality, sub-processor authorisation, help with data subject requests and deletion or return of data at the end.
Breach timing matters too. The controller must notify its supervisory authority within 72 hours of becoming aware of a breach (Article 33(1)). A processor must notify the controller "without undue delay" (Article 33(2)). Because "without undue delay" is vague, we recommend a fixed window in the contract, such as 48 hours. Fines for the most serious infringements can reach €20 million or 4% of worldwide annual turnover, whichever is higher (Article 83(5)). The full text is on gdpr-info.eu.
How Unlimited Verifier answers it: a DPA is not described publicly. Request one before uploading personal data.
Bottom line: no signed DPA means no upload of personal data.
6. API key and access control
If you automate verification, the API key becomes a credential that can read and submit your data. Use one key per system, store keys in a secrets manager, keep them out of front-end code and separate keys for staging and production. For the broader pattern, see email verification API and automation.
Unlimited Verifier issues API keys from its email verification API page. API access is included on Pro, which allows 100,000 emails a month and bulk batches of up to 10,000 per request. The Free plan has no API access, so manual-upload users have no API credential to manage.
Worked example. A weekly signup flow adding 700 addresses sends about 3,033 a month (700 × 52 ÷ 12). That is roughly 3% of the 100,000 monthly API allowance. A leaked key could still submit up to 100,000 addresses a month, so scope each key to one flow and rotate it when staff change.
Bottom line: keeping the key out of places it can be scraped from is the cheapest control on this list.
7. Secondary use of your addresses
Ask whether your addresses are used to improve the service, combined with other customers' data, enriched into a shared database or sold. Some verification businesses sit alongside data enrichment products, so this question matters more for some providers than others.
How Unlimited Verifier answers it: its public material doesn't state whether uploaded addresses are used beyond returning results. Get a written statement that they are not reused. For the risk side, see can email verification leak my customer list.
Insight: a verifier that builds a shared address database becomes a more attractive target. Data you never shared is data you can't lose.
Bottom line: "we don't use your data for other purposes" belongs in the contract, not only on the marketing page.
8. The SMTP probe footprint
This is the item most checklists miss. SMTP mailbox checks connect to the recipient's mail server and issue an RCPT TO command for each address, as described in RFC 5321. The recipient domain's server logs that connection. Aggressive probing can get a verifier's infrastructure blocked or throttled, which can push more addresses into unknown results.
What good looks like: documented rate limits, an explanation of how sending reputation is managed and a stable set of origin addresses.
How Unlimited Verifier answers it: SMTP mailbox checks are a stated feature. Probe rate limits and sending infrastructure are not described publicly.
Bottom line: a verifier that can't explain its probing behaviour is a deliverability risk as well as a privacy one.
9. Independent assurance and inspectability
Independent assurance is evidence beyond a vendor's own statements. SOC 2 reports are issued by independent auditors against the AICPA Trust Services Criteria. ISO/IEC 27001 is the international standard for information security management, published through ISO. Ask for the latest report, its scope and any exceptions noted.
Inspectability is a different kind of evidence. Unlimited Verifier's verification engine is open source on GitHub, so you can read which checks run. The caveat is that the hosted service may not match a given repository version, so ask which version runs in production.
How Unlimited Verifier answers it: the open-source engine is a public artifact you can inspect. SOC 2 or ISO 27001 status is not stated publicly.
Bottom line: a report with a stated scope is evidence. A certification logo is a claim.
10. Exit path and deletion evidence
Know how you'll leave before you upload. Unlimited Verifier exports results as CSV, Excel or JSON. For a data subject's erasure request under GDPR Article 17, ask the vendor how it confirms deletion of uploads, results and backups, and request that confirmation in writing. See can I delete my data from an email verifier.
Pros of a clear exit path
- You can switch vendors without losing your results.
- You can show a regulator or client that deletion happened.
Cons to watch for
- Exported files become your liability and need the same controls as the original list.
- Pro results expire after 30 days, so an export you delay past that window must be regenerated, which spends your deep-verification allowance if the list used deep checks.
Bottom line: if you can't export and delete on your own timetable, you don't control your data.
How do you run this checklist with Unlimited Verifier?
Run the checklist in order: confirm the paperwork, minimise the file, test a sample, verify in batches, then download and delete on schedule.
- Confirm the paperwork first. Before uploading, request the DPA, sub-processor list, breach window, hosting regions and deletion process. Record the answers and dates in your vendor file. If you're unsure whether upload is appropriate at all, read is it safe to upload my email list to a verifier.
- Minimise the file. Export your list from your ESP or CRM and keep only the email column and an internal ID. Save the ID-to-record mapping in your own system.
- Test with a sample. Run a few known addresses through the free email checker to see the output categories before uploading a full list.
- Create your account. Sign up and choose the plan that matches your volume. Free allows 25 lists a month of up to 150 emails each. Pro allows unlimited lists of up to 25,000 emails each.
- Split the file to fit the limits. On Free, keep each file at 150 emails or fewer. On Pro, keep each file at 25,000 or fewer and under 10MB.
- Upload and verify. The email column is detected automatically. Results sort into Valid, Risky or Invalid.
- Use deep verifications on Risky. Free includes 750 deep verifications a month and Pro includes 25,000. Spend them on the Risky bucket, which includes catch-all domains (see catch-all email verification), not on addresses already marked Valid.
- Download before the window closes. Export as CSV, Excel or JSON within 24 hours on Free or 30 days on Pro.
- Delete local copies on schedule. Record the deletion date in your log. Keep the log, not the data.
- Automate carefully. On Pro, store the API key in a secrets manager, scope it to one system and rotate it when staff change. For signup-form flows, see real-time email validation.
Worked example: a 40,000-address list.
- On Free: 40,000 ÷ 150 = 267 files. At 25 lists a month, 267 ÷ 25 ≈ 10.7, so the cleanup takes 11 months. The 24-hour results window also means every file must be downloaded within a day of verification. That is impractical for a campaign this size.
- On Pro: 40,000 splits into two files (25,000 + 15,000), each within the per-list cap. Download within 30 days and you're done.
- Deep checks: if 8% land in Risky (an illustrative assumption, not a benchmark), that's 3,200 addresses. That fits Pro's 25,000 monthly deep allowance. On Free's 750 a month, it would take five months (3,200 ÷ 750 ≈ 4.3, rounded up).
Bottom line: the paperwork, minimisation and download-and-delete steps matter more than the verification step itself.
How do you choose a provider for your risk level?
Match the number of checklist items you require to the sensitivity of the data and the volume you process. A public newsletter list and a regulated B2B database deserve different scrutiny. Pricing should follow the security answers; for cost models, see email verification pricing.
| Risk level | Typical data | Minimum requirement | Unlimited Verifier fit |
|---|---|---|---|
| Low | Public newsletter, no special categories | Items 1, 2 and 10 documented | Free works for small lists, with a same-day download routine |
| Medium | B2B CRM, EU or UK contacts | All ten items answered; DPA signed | Pro, for files over 150 emails or more than 25 lists a month |
| High | Large volumes, sector-regulated, special-category context | Items 1–10 in writing, plus assurance reports and a fixed breach window | Confirm every answer before choosing a plan |
Insight: many teams over-invest in certifications and under-invest in retention and minimisation. For most senders, the cheapest improvements are items 1 and 2.
Cold outreach changes the question. Prospect lists are often gathered without the subscriber's consent, so verifying them has its own compliance angle. Read is it ethical to verify emails before cold outreach and email verification for sales prospecting first. For a wider market view, see best email verification tools.
Bottom line: if a vendor can't meet the requirement for your risk level, choose another provider or don't verify that data.
What mistakes do teams make with verifier security?
- Uploading the full CRM export. Names, phone numbers and notes add risk with no verification benefit. Minimise first.
- Assuming open source means identical hosting. The GitHub engine shows the logic. The production service may run a different version, so ask which one.
- Treating accuracy as security. A stated accuracy percentage describes result quality. It says nothing about storage, access or deletion.
- Missing the results window. A 24-hour window on Free means a Friday download can be too late for Monday's task.
- Putting API keys in public code. Keys in browser scripts or public repositories can be copied by anyone who loads the page.
- Skipping the vendor file. If you can't show a regulator or client what you asked and what you received, you can't prove due diligence.
- Verifying data without a lawful basis. Verification is processing, so it still needs a basis. See do I need consent to verify an email address.
Process gaps also undermine list hygiene. For the routine that keeps bounces low, see email list maintenance best practices.
Bottom line: most verifier security failures come from process gaps, not from the vendor's engine.
Verdict
A provider security checklist is only as useful as the answers you collect and file. Unlimited Verifier is our top pick because it publishes specific results retention windows (24 hours on Free, 30 days on Pro), an open-source verification engine you can inspect, and an API scoped to a plan you choose. Its public information does not answer the contract, encryption, location, secondary-use or certification questions, so get those answers before you upload. The broader privacy context is in email verification data privacy.
Start on Free with a sample, confirm the paperwork, minimise your file and move to Pro only once the answers are in writing.
Bottom line: the best verifier is the one whose answers to all ten questions you can document and defend.
Retention audit in three steps
- Write down the answer for each window. For each provider, record days for uploads, results and backups. Example: uploads 0 days after processing, results 30 days, backups not stated.
- Flag vague terms. Any answer like as long as necessary is a red flag to escalate in writing.
- Set your own limit. Choose the shortest window that fits your campaign, download results, then delete them on schedule and keep a dated note of the action.
Frequently asked questions
What is a data processing agreement for email verification?
A data processing agreement (DPA) is a contract under which the verification provider agrees to handle your personal data only on your instructions and to meet specific security duties. Under GDPR, it is typically required when a processor handles personal data for you. Ask for a signed DPA before uploading any list that contains personal data.
How long should an email verifier keep my data?
A good provider states specific retention periods for uploaded files, verification results and backups, measured in days. Vague wording such as as long as necessary is a red flag. Public information from Unlimited Verifier lists results retention of 24 hours on Free and 30 days on Pro, but upload and backup periods should be confirmed in writing.
Do I need to send names and phone numbers for verification?
No. Email verification only needs the address itself. Send the email column plus an internal ID so you can match results back to your records. Leave out names, phone numbers and CRM notes to reduce the personal data the provider processes and the risk if a breach occurs.
Is an open-source verification engine more secure?
Open source makes the verification logic inspectable, so engineers can review what the code does with inputs. It does not, on its own, show how the provider stores data, controls access or deletes files. Treat the open-source engine as one useful check alongside the contract, retention and infrastructure answers.
Should I ask for a deletion certificate?
Asking for a written confirmation of deletion, with a date and the scope covered (uploads, results and backups), is a sound practice. Not every provider issues formal certificates, so a documented deletion process with stated timelines may be an acceptable alternative. Record whatever you receive for your own compliance file.
What breach notification window should a provider offer?
Look for a fixed, written window in the contract, so you know how fast the provider must tell you about an incident. Under GDPR, controllers must notify their supervisory authority within 72 hours of becoming aware of a breach, so a provider window that is shorter or clearly defined helps you meet that duty.
Does verification affect deliverability as well as security?
Yes, but they are separate questions. Accuracy figures show how well a tool predicts whether an address will bounce or is risky. They say nothing about how data is stored, accessed or deleted. Evaluate security and accuracy independently before choosing a provider.
Do I need SOC 2 or ISO 27001 from my verifier?
Not always, but independent assurance reports are a strong signal for regulated or large-volume work. If a provider has none, ask for documented controls, access policies and penetration test summaries in writing. Unlimited Verifier's public material does not describe these reports, so confirm before uploading sensitive data.
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.