Article

What Happens to My Data After Email Verification? A Stage-by-Stage Guide

By Unlimited Verifier Team ·

Flow diagram showing the seven stages of email verification data handling, from list upload through mailbox probe to retention and downloaded copies.

Summary

After you upload a list, the verifier checks each address via DNS and SMTP lookups, returns results, and keeps them for a published window (24 hours on Unlimited Verifier Free, 30 days on Pro). Upload, logs, backups and your own exports each persist on separate schedules, so the largest leftover risk is often the copies you download and forget.

After you upload a list, a verifier checks each address through DNS and SMTP lookups, returns the results to you, and then keeps those results for a set window: 24 hours on Unlimited Verifier's Free plan and 30 days on Pro.

That window covers only the results. The upload, server logs, backups and your own downloaded copies each persist on their own schedules, and most of the privacy risk sits in copies nobody tracks. This guide maps each one and shows how to limit what you send in the first place. For the wider picture, start with our email verification data privacy pillar. If you're asking whether uploading is safe at all, see is it safe to upload your list to a verifier.

Quick answer

What happens to my list, step by step, from upload to deletion?

Your file passes through seven stages, and the exposure differs at each one. Most privacy questions about verification are really questions about stage 4, the mailbox probe, and stage 7, your own copies.

Stage What touches your data Who can see it Your control
1. Upload The full CSV or Excel file The verifier's systems Which columns the file contains
2. Parsing and syntax Each address string The verifier's systems Removing unneeded fields beforehand
3. DNS and MX lookups Only the domain part (e.g., example.com) DNS resolvers on the path Little, since domains are public
4. SMTP mailbox probe Full address in an RCPT TO command The recipient's mail server and its logs Choice of verifier and how it probes
5. Classification Valid, Risky or Invalid labels, plus flags The verifier, then you Which results you export
6. Retention Results, logs, backups The verifier and its sub-processors Plan window and deletion requests
7. Your copies CSV, Excel or JSON exports You, and anyone you share with Storage, access and deletion

After verification, your contacts' data has more copies, not fewer: at the verifier, in your downloads, and in whatever sheet or CRM you re-import into. Track every copy, not just the vendor's. Whether verifiers keep the addresses you check at all is covered in whether verifiers store the emails you check.

Bottom line: Verification adds copies at several stages, so audit all of them, not only the vendor's storage.

Does verification send my contacts' addresses to their mail servers?

Yes. A mailbox check connects to the recipient domain's mail server, announces a sender, and issues RCPT TO: with the target address. The server accepts or rejects that recipient, and the client disconnects without sending a message. RFC 5321 defines these commands.

The recipient's server therefore sees the address and the IP address asking about it. Many mail servers log these connections, and some throttle or block repeated probing. That is why the probe is the one stage that reaches infrastructure you don't control.

Catch-all domains weaken the result. They accept RCPT TO for any local part, so the probe confirms the domain but not the individual mailbox. That is why catch-all results are usually labelled Risky. The catch-all email verification page explains how those results are handled.

Ask every verifier three questions:

  1. Which checks run under standard verification, and which under deep verification? A mailbox probe may run in only one tier.
  2. Which IP ranges does it probe from, and how often does it contact a given mail server?
  3. Does it respect server rejections and rate limits?

Those answers tell you more about exposure than a homepage privacy statement.

Bottom line: Judge a verifier on how it probes as well as how it stores data, because the probe is the step that reaches third-party servers.

How long does a verifier keep my data?

Unlimited Verifier states that results are kept for 24 hours on the Free plan and 30 days on Pro. Those figures cover results only. The upload, logs and backups have their own timelines, which the published windows don't address. For a deeper look, see how long verifiers keep uploaded lists.

Data Why it persists Question to ask A good answer
Uploaded file Needed to run the check When is the file deleted after processing? A stated period, in writing
Results Available for download What is the plan-level window? The stated window (24 hours Free, 30 days Pro)
Logs Debugging and security Do they contain full addresses, and for how long? Redacted or pseudonymised, with a stated period
Backups Disaster recovery When are deleted items purged from backups? A defined cycle after which data is overwritten
Sub-processors Hosting and infrastructure Who else processes the data? A named list, plus notice of changes

Plan choice shapes your exposure. On Free, results disappear after 24 hours, so you must download them within that window or re-run the check. On Pro, results remain for 30 days, so a copy sits on the vendor's side for longer. Neither figure says anything about the upload itself.

Bottom line: Use the published windows to compare plans, but get the upload, log and backup timelines in writing before you send customer data.

Is my data sold, shared or used for anything besides my check?

A verifier should use your list only to run your check. Whether it shares or reuses data is settled in a contract, not a marketing page. Unlimited Verifier's published facts don't cover sub-processors or reuse of uploaded data, so confirm both before you upload customer or employee addresses.

Under privacy law, a verifier that processes your list on your instructions is usually a processor, and you are the controller. GDPR Article 28 requires a written contract that limits processing to documented instructions, imposes confidentiality, and covers deletion or return of data at the end of the service. The CCPA's equivalent is the service provider, whose use of personal information is restricted to the contracted purpose. The California Attorney General's CCPA page is the place to start.

Put three questions to the vendor in writing:

  1. Do you use uploaded addresses to train or improve any model, or for any other purpose?
  2. Do you sell or share them with third parties, including data brokers?
  3. Who are your sub-processors, and how will I be told when they change?

A clear yes or no is a good answer. Vague language about "partners" is not.

Bottom line: The data processing agreement, not the homepage, decides whether your list is used only for your check.

Does GDPR or CCPA cover my verification data?

Yes, in most cases. Under GDPR, personal data is any information relating to an identified or identifiable person, which covers most email addresses (GDPR Article 4). The labels a verifier adds, such as disposable or catch-all, are derived personal data and deserve the same care as the address itself.

Two principles apply directly. Data minimisation limits you to what the purpose needs. Storage limitation means keeping data no longer than necessary. Together they explain why you should strip columns before upload and delete exports once you've used them.

Whether verifying an address without permission is lawful depends on your legal basis and jurisdiction, so read is verifying emails without permission legal before you start. Many controllers rely on legitimate interests for list hygiene, but you, not the vendor, must document the balancing test. The ICO publishes guidance that UK teams find useful. For the detailed analysis, read GDPR and email verification processing and CCPA compliance for email verification. Both sit within wider email verification compliance and hygiene practice.

Bottom line: Treat verification as personal-data processing, document your basis, and check that the vendor's contract matches your obligations.

Where is my data stored and processed?

Your data is stored wherever the verifier hosts it and wherever its sub-processors operate. Unlimited Verifier's published facts don't name a server location, so ask before you upload. For EU or UK personal data sent outside those regions, GDPR's Chapter V transfer mechanisms, such as adequacy decisions or standard contractual clauses, must be in place. See where verification servers are located for what to check.

Bottom line: Location is a contract and transfer question, so get the answer in writing rather than inferring it from a logo or domain name.

Can I delete my contacts' data after verification?

Yes, but deletion works in layers, and the vendor's delete button covers only one of them. Work through these steps in order:

  1. Delete the upload and results in your account if the interface allows it, and note the date.
  2. Wait out the published window for anything you can't delete directly: 24 hours on Free, 30 days on Pro.
  3. Delete your local copies: the original export, the input file, and every results file in downloads, shared drives and email attachments.
  4. Send a written erasure request for anything still held, including logs and backups. Under GDPR Article 17 you can request erasure, and under Article 12(3) the controller has one month to respond. Under the CCPA, businesses generally have 45 calendar days to respond to a consumer request, extendable once.
  5. Keep a record of what you deleted and when, so you can answer an audit or a data subject request.

Vendor deletion does not remove connection logs held by the recipients' mail servers, which sit outside the verifier's control. That is why minimising data before upload matters more than deleting it afterwards. The full process is in deleting your data from an email verifier.

Bottom line: Deletion covers your copies and the vendor's copies, and the vendor's copies require a written request, not just a button.

How do I minimise the data I send before verifying?

Send the verifier only the email address and a row identifier, then rejoin the results to your full records on your own machine. Syntax, domain, MX and mailbox checks need no other field, and names, phone numbers and postal addresses add nothing to them.

  1. Add a row_id column numbered 1 to N, and keep the mapping to your full records locally.
  2. Strip every other column, including names, phone numbers, postal addresses, dates of birth, IP addresses and notes.
  3. Deduplicate and remove known suppressions first. Fewer addresses means less exposure and less quota used.
  4. Don't hash addresses. Verification needs plain addresses to query DNS and probe mailboxes, so a hashed list can't be checked. The trade-off is explained in verifying hashed emails.

Prospect lists follow the same rule. Email verification for sales prospecting shows how to keep enrichment data out of the verification file. Teams running email verification for ecommerce and SaaS usually find the largest reduction here, because their CRM exports carry the most extra fields.

Bottom line: Upload a row ID and an email address, and nothing else.

Hands-on tutorial: verify a list with the least data exposed

This tutorial assumes a CSV export from your ESP or CRM and a spreadsheet app.

  1. Export the original list to CSV and store it where it already lives. Don't email it to anyone.
  2. Build a minimal input file. Add a row_id column numbered 1 to N, delete every column except row_id and the email column, and save the file as verify-input.csv.
  3. Remove duplicate addresses and check for header errors and blank rows.
  4. Choose a plan. Free covers 25 lists a month of up to 150 emails each. Pro covers lists of up to 25,000 emails each. Sign up to start.
  5. Upload the file on the Upload and verify a list page. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
  6. Read the three buckets. Valid addresses are safe for first sends. Invalid addresses should be suppressed. Risky addresses include catch-all domains, disposable addresses and role accounts, and should be held back.
  7. Download before the window closes. Free results last 24 hours and Pro results last 30 days. Export as CSV for the simplest rejoin.
  8. Rejoin locally by matching row_id back to your original records. Keep only the columns you need for sending.
  9. Re-import manually. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so upload Valid contacts as a new segment and add Invalid addresses to your ESP's suppression list.
  10. Delete the copies. Remove the input and results files from downloads and shared drives, then record the dates in your data log.
  11. Spot-check any single address that looks wrong with the free email checker.

Bottom line: The safest workflow is a stripped file, a fast download, a local rejoin and a documented delete.

Worked example: verifying a 60,000-contact list

This example is illustrative, but the arithmetic and plan limits are real.

Starting file. A B2B team exports 60,000 contacts with 14 columns each: 60,000 × 14 = 840,000 cells of personal data.

Minimised file. The team keeps only row_id and email: 60,000 × 2 = 120,000 cells.

Reduction. (840,000 − 120,000) ÷ 840,000 = 85.7% less personal data sent to the verifier.

Fit on Pro. Pro caps each list at 25,000 emails, so the file splits into 25,000 + 25,000 + 10,000 = 60,000 addresses. Standard verification is unlimited on every plan. Deep verification is capped at 25,000 a month, so the team can't deep-check all 60,000 in one month. It should deep-check the riskiest segment first and run the rest as standard. Check current email verification pricing before budgeting: Pro is $29 a month, or $25 a month billed annually, which comes to $300 a year.

Why Free doesn't fit. Free allows 25 lists of up to 150 emails each per month, so a month tops out at 25 × 150 = 3,750 emails, or 6.25% of this list. Splitting the whole file would take 60,000 ÷ 150 = 400 lists.

Retention timeline on Pro. The team verifies on 1 June and downloads on 2 June. The vendor's results window runs about 30 days, to roughly 1 July. The exported CSV on the team's drive persists until someone deletes it, so the data log records the verification, download and deletion dates.

Bottom line: Stripping the file removes 85.7% of the personal data from the transfer, and the 25,000-per-list cap means three files, each with a dated delete.

Which verification setup keeps the least data?

The three main setups differ mainly in where the data goes and who controls retention.

Setup Where addresses go Who controls retention Effort Best fit
Hosted web upload The verifier's systems Plan window plus written requests Lowest: upload, check, download Periodic list cleans
API calls via the email verification API The verifier's systems, in API requests Verifier policy, confirmed in writing Moderate: needs development work Checks at signup or in batch jobs
Self-hosted open-source engine Your own infrastructure You Highest: you run and maintain it Strict data-residency rules

The API route suits email verification API and automation workflows, but API access is a Pro feature, not part of Free. Pro includes 100,000 API emails a month, and each bulk request accepts up to 10,000 emails. A 60,000-address job therefore needs six requests. Pair the API with real-time email validation at signup so fewer bad addresses enter your database at all.

The open-source engine is on GitHub. Self-hosting keeps retention under your control, but if you run its mailbox checks, the probes come from your own IP address. Many cloud providers restrict outbound port 25 by default, and probing from a new IP can draw blocks or throttling. You also take on the maintenance.

For most teams cleaning a list once a quarter, hosted upload with a stripped file is the right default, and this is where Unlimited Verifier fits best. Standard verification is unlimited on every plan, a Pro list can hold up to 25,000 addresses in one file, and CSV, Excel and JSON exports keep the rejoin simple. For a wider comparison, see our guide to the best email verification tools and email list maintenance best practices.

Bottom line: Hosted upload is the lowest-effort option, the API suits automated flows on Pro, and self-hosting gives the most control at the highest operational cost.

Common mistakes that expose data or break verification

Bottom line: Most avoidable exposure comes from extra columns, untracked copies, and assumptions about what "deleted" covers.

How we compared (and limitations)

This guide is based on public documentation: the SMTP command definitions in RFC 5321, the GDPR and CCPA texts and regulator guidance, and the plan facts Unlimited Verifier publishes. We did not audit any vendor's infrastructure, test deletion behaviour, or check sub-processor lists. Retention windows and plan limits change, so confirm current terms before you upload.

Unlimited Verifier states retention of 24 hours for Free results and 30 days for Pro results. Those are the company's own published figures, not independent audits. Its published facts don't cover upload deletion timing, sub-processors or data location, so ask for those in writing.

Nothing here is legal advice. Your signed data processing agreement and your own privacy assessment govern your obligations.

Seven-stage data trace

Stage Action you can take
1. Upload Strip extra columns before upload
2. Parsing Remove invalid or duplicate rows first
3. DNS/MX Nothing needed; domains are public
4. SMTP probe Choose a verifier with clear probing terms
5. Classification Export only the statuses you need
6. Retention Confirm plan window and log/backup timelines in writing
7. Your copies Log each export, restrict access, delete when done

Frequently asked questions

Does email verification delete my list after checking?

Not automatically in a way that covers everything. Published retention on Unlimited Verifier covers results only: 24 hours on Free and 30 days on Pro. The upload, server logs and backups follow their own timelines, so ask the vendor for those in writing and request deletion where needed.

Does verifying an email send it a message?

No email is sent to the recipient. However, the verifier connects to the recipient's mail server and issues an SMTP RCPT TO command with the full address, so that server can log the lookup.

What data do DNS lookups expose?

DNS lookups only involve the domain part of each address, such as example.com, to find mail servers (MX records). Domains are public, so the exposure is low, though resolvers on the path can see which domains were queried.

Should I remove columns before uploading?

Yes. A file containing only a row ID and an email address removes most personal data a typical CRM export carries, such as names, phone numbers and notes. Less uploaded data means less to retain, back up and leak.

Are my downloaded verification results a privacy risk?

Often the largest one. Exported CSV or Excel files can sit in downloads folders, email attachments and shared drives long after the vendor's retention window closes. Track each copy, restrict access and delete files you no longer need.

Can I ask a verifier to delete my data?

Usually yes. Check the provider's privacy policy and contact its support or privacy channel to request deletion of uploads and results. Confirm whether logs and backups are covered and when they are purged.

Does verification affect GDPR obligations?

Email addresses are personal data under the GDPR, so sending them to a verifier is processing that should be covered by your privacy notice and a processor agreement. Consult your data protection officer or legal counsel for your specific situation.

Do verifiers share my list with third parties?

Verifiers may use sub-processors such as hosting and infrastructure providers. Review the vendor's sub-processor list and data processing terms to see who else can access your data.

Is it safer to verify in small batches?

Batching does not change the mailbox probe, but it limits how much data sits in any single upload and export at one time, which makes deletion and tracking simpler.

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 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.