Article
Is Email Verification Allowed Under the CCPA? What Businesses Need to Know
By Unlimited Verifier Team ·

Summary
Email verification is permitted under the CCPA, which regulates how personal information is handled rather than banning address checks. It is compliant when the verifier acts as a service provider under a written contract, the purpose is disclosed in your privacy notice, and you minimize the data you send.Yes. The California Consumer Privacy Act (CCPA) does not prohibit email verification, but it treats every email address as personal information, so verifying one is permitted when a service-provider contract, a disclosed purpose and a deletion process are in place.
Whether a specific verification is compliant depends on three things: how the vendor is contracted, what your privacy notice says, and how much data you send. This is a practitioner's reading of the statute and California regulator materials, not legal advice, so have counsel confirm it for your situation. For the wider picture, start with our pillar on email verification data privacy.
Quick answer
- Verification is permitted. The CCPA regulates how personal information is handled. It does not ban checking whether addresses work.
- Check scope first. The CCPA, as amended by the CPRA, applies to for-profit businesses doing business in California that have annual gross revenue above $25 million (inflation-adjusted), that buy, sell or share the personal information of 100,000 or more Californians or households, or that earn half or more of revenue from selling or sharing personal information.
- Lock the vendor down. Use a written service-provider contract that bars the verifier from selling your data or keeping and reusing it for its own purposes.
- Disclose and minimize. Name verification in your privacy notice, and upload only the email column plus a row ID you generate.
- Plan for deletions. Respond to consumer requests within 45 calendar days, and pass deletions to every vendor that holds the record.
Does the CCPA treat email addresses as personal information?
Yes. The CCPA defines personal information as information that identifies, relates to, or is reasonably capable of being linked to a particular consumer or household, and it lists email address among its identifiers (Cal. Civ. Code §1798.140(v)). A "consumer" is a California resident (§1798.140(i)), so the test is where the person lives, not where your company is based. The statute text is available on California's official legislative site.
Two points catch list owners out. First, the exemptions for business-to-business contacts and employee data expired on January 1, 2023. A sales lead at a company is now covered the same way a shopper is. Second, role addresses such as info@ are less clearly personal, because they may not point to one natural person. Jane.doe@acme.com plainly does. Treat every address as personal information. Over-protecting a role inbox costs you almost nothing.
Bottom line: Assume every email address you hold for a California resident is personal information, including B2B contacts.
Is email verification allowed as a business purpose under the CCPA?
Generally yes, but only when the verifier acts as your service provider. The statute covers services performed on the business's behalf, including "verifying customer information" (§1798.140(e)(5)). Checking whether an address is deliverable fits that description closely.
The line is contractual and behavioral. A vendor qualifies as a service provider under a written contract that prohibits it from selling or sharing the data, from retaining or using it outside the direct business relationship, and from combining it with other data except as the law permits (§1798.140(ag)). The California Privacy Protection Agency's regulations add further required contract terms (Cal. Code Regs., tit. 11, §7051).
Two consequences follow:
- A compliant disclosure is not a sale. The statute's definition of "sale" requires disclosure for monetary or other valuable consideration. A service provider acting under a compliant contract falls outside it, so your vendor fee doesn't turn verification into a sale.
- Opt-outs don't automatically block verification. A consumer who opts out of sale or sharing hasn't stopped you from processing their data as a service provider's client. A deletion request is different, and it does require action.
The practitioner's catch is in the fine print. Many verification providers say they use results to improve models or reputation data. If your contract lets the vendor keep or reuse your list for its own product, a regulator can argue the vendor is a third party, and sharing your list may count as a sale. That would trigger opt-out rights you probably haven't built. Read the data-use and retention clauses, not the marketing page.
Verification also can't fix provenance. If you bought the list, the seller was required to give notice at collection. Confirming that addresses bounce doesn't supply that notice after the fact.
Bottom line: Verification is a permitted service function only when the vendor is contractually bound to act solely on your instructions.
What does the CCPA require before you verify a list?
Verification is processing, so the same core duties apply as to any other use of personal information. Treat this table as the checklist for your email verification compliance and hygiene program.
| Obligation | Where it sits | What it means for verification |
|---|---|---|
| Notice at collection | §1798.100(a) | Disclose categories and purposes at collection. Verification should be a disclosed purpose or a compatible one. |
| Purpose limitation and data minimization | §1798.100(c) | Processing must be "reasonably necessary and proportionate." Send the email column only. |
| Service-provider contract | §1798.100(d), §1798.140(ag) | Written terms that bar sale, retention and reuse outside your instructions. |
| Privacy policy disclosure | §1798.130(a)(5) | Name the verification vendor category in your policy. |
| Deletion and vendor notice | §1798.105 | Notify service providers holding the record so they delete it. |
| Response deadline | §1798.130(a)(2) | Respond within 45 calendar days, with one 45-day extension if you notify the consumer. |
Penalties are set in §1798.155: up to $2,500 per violation, or $7,500 per intentional violation. The California Privacy Protection Agency adjusts these for inflation, so current figures are higher. Check the California Attorney General's CCPA page and the CPPA's site for current amounts. Separately, §1798.150 lets consumers sue after certain data breaches, with statutory damages of $100 to $750 per consumer per incident.
For scale only: if a regulator treated each of 10,000 unnotified records as a separate $2,500 violation, the base-rate exposure would be $25 million. Fines depend on the facts, so treat that as a hypothetical, not a prediction.
Bottom line: A disclosed purpose, a service-provider contract and a minimized upload cover most of what applies to verification.
Which of your lists can you verify under the CCPA?
The scenario decides the answer, so check this table before you upload anything.
| Scenario | Verify? | Conditions |
|---|---|---|
| Opted-in customers, privacy notice updated | Yes | Service-provider contract and a minimized upload |
| B2B prospects from your own web forms | Yes | Your notice at collection should cover business contacts. See email verification for sales prospecting. |
| Purchased list with seller CCPA notice and contract terms | Yes, once documented | Get the seller's provenance documents before verifying |
| Purchased list with no provenance | Not yet | Resolve sourcing first. Verifying it extends an undocumented data flow. |
| Scraped addresses with no notice | Don't start here | Get legal advice. Verification adds to the record of an unlawful collection. |
| Role addresses (info@, sales@) | Yes | Low risk. Treat them as personal information anyway. |
| Hashed addresses only | Depends | A hash you can't match back to an address is a different analysis. See does email verification work with hashed emails. |
| Employee addresses | Yes | The employee-data exemption ended in 2023. |
Whether verifying cold lists is ethical is a separate question from whether it is allowed. We cover that in is it ethical to verify emails before cold outreach. The CCPA is an opt-out framework for sale and sharing. It does not set a general opt-in rule for marketing email. Sending rules come from other laws, including CAN-SPAM, which the FTC's compliance guide explains.
Bottom line: The fastest way to fail is to verify a list whose origin you can't document.
What's the compliant process for verifying a list?
Follow these seven steps in order. Each one creates a record you can show a regulator or a customer.
- Document the source. Record where each list came from and what notice the person received at collection. Why: Provenance is the first question any reviewer asks, and you can't answer it from memory.
- Update your privacy notice. Add verification to your service-provider categories and purposes before the first upload. Why: A notice written after the fact looks like a rationalization.
- Sign a service-provider agreement. Confirm written terms that bar the verifier from selling, retaining or reusing your data. If a vendor won't sign, that answers the question. Why: The contract is what makes the vendor a service provider at all.
- Minimize the file. Send only the email column and a row ID you generated. Leave names, phone numbers and purchase history in your own system. Why: Data you never send can't be breached or retained by the vendor.
- Verify and sort. Sort results into Valid, Risky and Invalid, and keep the counts. Why: Counts are the evidence that the work happened and what it found.
- Set a retention rule. Delete downloaded result files on a fixed schedule that matches the vendor's retention window. Why: Your local copies sit outside the vendor's controls, so they need their own clock.
- Suppress and route. Keep a minimal suppression record for Invalid addresses so they aren't re-imported. Route deletion and opt-out requests to every vendor that holds the record. Why: Without suppression, deleted people get re-added in the next import.
Bottom line: Each step creates evidence. Regulators look for documented decisions, not good intentions.
Which verification method fits a CCPA program best?
The method you choose changes who processes the data and what contract you need.
| Method | Who processes the addresses | Contract you need | Retention control | Best fit |
|---|---|---|---|---|
| Hosted bulk upload (CSV or Excel) | Third-party vendor | Service-provider terms | Set by the vendor. Unlimited Verifier keeps results 24 hours on Free and 30 days on Pro. | Batch cleaning of existing lists |
| Email verification API and automation called from your systems | Third-party vendor | Same terms. You choose which fields leave your systems. | Vendor-set. You can avoid storing responses. | Signup forms and real-time checks; see real-time email validation |
| Self-hosted open-source engine | You | None for the check itself | Full control | Teams with engineering capacity who want no vendor in the data flow |
Self-hosting removes the third-party disclosure, but it makes you responsible for SMTP probe behavior, sending IP reputation, rate limits and security. Mail providers can rate-limit or block probing from a single IP, so budget for that. Unlimited Verifier publishes its verification engine on GitHub. Review the code and its licence yourself before relying on it.
The hosted route is faster to run. Pro includes API access for 100,000 emails a month, and bulk API requests accept up to 10,000 emails each. You can create API keys once your account is set up. For where the data physically sits, see where email verification servers are located. For how long vendors keep uploads, see how long email verifiers keep uploaded lists.
Bottom line: Hosted upload is often the simplest CCPA-compliant route, provided the contract and retention terms hold up.
How do you run a verification in Unlimited Verifier?
This walkthrough uses the hosted upload route. It takes about as long as the upload itself.
- Strip the export to two columns. Create a row ID (1 to N) and keep the email address. Going from eight fields to two means 75% fewer fields leave your systems.
- Check the limits. Each file can be up to 10MB. On Free, lists are capped at 150 emails each and 25 lists a month, so a Free month covers at most 3,750 addresses. Pro lists can hold up to 25,000 emails each. Split larger files to fit.
- Sign up for a free account. Free covers the first batches, and you can upgrade when a list outgrows it.
- Upload and verify a list. The email column is detected automatically. If detection fails, rename the header to "email."
- Review the three buckets. Valid addresses are safe to send to. Invalid addresses should be suppressed. Risky results include catch-all domains, disposable addresses and role accounts. The catch-all verification guide explains how to handle catch-all results.
- Export as CSV, Excel or JSON. Confirm the export keeps your row ID before you rely on it to rejoin records.
- Re-import only Valid contacts into your ESP as a segment, and add Invalid addresses to its suppression list.
- Calendar the deletion. Results stay on the platform for 24 hours on Free and 30 days on Pro. Delete your own local copies on your schedule, because the platform's window doesn't cover them.
To spot-check a single address, such as a key account that comes back Risky, use the free email checker.
Bottom line: Strip, verify, split by the plan cap, re-import Valid addresses only, and delete your copies on schedule.
What does a 48,000-contact verification look like under the CCPA?
Take a SaaS company with 48,000 contacts in an eight-column export: email, first name, last name, company, phone, plan, last login and monthly recurring revenue. The arithmetic below uses Pro's real limits. The result percentages are hypothetical.
- Minimize. Eight fields become two, so six fields never leave the company. At roughly 35 bytes per row (an estimate), the file is about 1.7MB, well under the 10MB cap.
- Split by list size. Pro allows lists of up to 25,000 emails each. 48,000 needs two uploads: 25,000 and 23,000.
- Plan the deep checks. Pro includes 25,000 deep verifications a month. Deep-checking all 48,000 would exceed that by 23,000. Instead, deep-check 9,600 flagged or high-value contacts, which leaves 15,400 of the monthly allowance for later (25,000 − 9,600 = 15,400).
- Standard checks. Standard verification is unlimited on every plan, so all 48,000 addresses are checked.
- Cost. One month of Pro is $29, or $25 a month on annual billing. For this run, that is about $0.60 per 1,000 addresses at $29 ($29 ÷ 48) and about $0.52 at $25. See email verification pricing for how plans compare. A SaaS company with a list this size usually runs verification on a schedule rather than once.
- Hypothetical results. Valid: 39,840 (83%). Risky: 5,280 (11%). Invalid: 2,880 (6%). The buckets sum to 48,000.
- Actions. Import the 39,840 Valid contacts as a segment. Hold the 5,280 Risky contacts. Suppress the 2,880 Invalid contacts.
Bottom line: The defensible version of this project is smaller, documented and traceable: two columns, a signed contract and a dated deletion.
How do you handle a deletion request that covers verification data?
Suppose a consumer asks for deletion on March 3 (a non-leap year). Your response plan looks like this:
- By March 3: Log the request and verify the requester's identity.
- By March 10: Delete the contact from your CRM and ESP. Send a deletion instruction to every vendor holding the record.
- By March 30: If a vendor still holds a February 28 upload, its 30-day Pro window closes on this date. Get written confirmation of deletion before then.
- By April 17: Send the final response. That is 45 days after March 3 (28 days to March 31, plus 17 into April).
You may keep a minimal record so the person isn't re-imported and mailed again. Keep only the email address and a deletion flag, and document why you kept it.
Bottom line: A deletion covers your copies and your vendors' copies, so keep a log of both.
What about GDPR and other state privacy laws?
The CCPA is one of several regimes. The GDPR applies to people in the EU, and more than a dozen US states now have their own comprehensive privacy laws, with different scopes and thresholds. Our guides on whether email verification is processing personal data under GDPR and how to check if an email verifier is GDPR compliant cover the stricter European side. For whether checking addresses without the owner's permission is legal, see is verifying emails without permission legal.
Bottom line: If you contact people in more than one jurisdiction, apply the strictest rule you face to your verification workflow.
What are the most common CCPA mistakes with email verification?
- Assuming verification is exempt because it "just checks." It is processing, so it needs a disclosed purpose and a contract.
- Uploading the full CRM export. Names, phone numbers and purchase history add risk without improving the check.
- Accepting standard click-through terms that let the vendor reuse your data for its own product. Check for a "service improvement" clause in particular.
- Verifying a bought list before checking its provenance. You may be cleaning data you should not hold.
- Keeping downloaded result files indefinitely on a shared drive. They sit outside both the vendor's retention window and yours.
- Forgetting vendors in deletion workflows. Your CRM is only one copy.
- Treating a Valid result as consent. A deliverable address isn't an opted-in one. See email list maintenance best practices.
- Believing hashing equals anonymization. A hash that can be matched back to an address is still personal information.
- Leaving the privacy notice unchanged after you add a vendor.
- Assuming you're too small to matter. Check the thresholds, and remember that other state laws may still apply.
For security concerns about the upload itself, see is it safe to upload my email list to a verifier and can email verification leak my customer list. To remove data from a vendor, see can I delete my data from an email verifier.
Bottom line: Problems with verification tend to come from missing paperwork, not from the check itself.
How we compared (and limitations)
This article is based on public documentation: the CCPA text in Civil Code §1798.100 et seq., the California Attorney General's and CPPA's published materials, and the FTC's CAN-SPAM guidance. We have not tested any regulator's enforcement position or any vendor's contract in practice.
Sources and practitioners read some points differently. Commentators disagree on whether a role address like info@ counts as personal information, and on how far a vendor's "service improvement" clause can reach before it makes the vendor a third party. We recommend treating role addresses as personal information and treating any reuse right as disqualifying until counsel clears it. Penalty amounts are statutory and change with inflation adjustments, so check the current figures before you rely on them.
Unlimited Verifier's plan limits and retention windows come from the company's published information. The company states 99.5% accuracy for deep verification. That is its own figure, not an independent benchmark. The 48,000-contact percentages are illustrative.
For vendor comparisons on contract terms, retention and deletion support, see our guide to the best email verification tools.
Bottom line: Check the vendor's paperwork as carefully as you check your list.
Compliant verification checklist
- Confirm CCPA scope: revenue, consumer volume, or revenue from selling or sharing data.
- Sign a written service-provider contract that bars sale, sharing, retention, and outside reuse.
- Update your privacy notice to name email verification as a purpose.
- Upload only the email column plus an internal row ID.
- Map every vendor that holds the record so deletion requests reach all of them.
- Respond to verifiable consumer requests within 45 calendar days, extendable once.
- Have counsel review the setup for your specific facts.
Frequently asked questions
Does the CCPA ban sending emails to check if they are valid?
No. The CCPA does not prohibit checking whether email addresses are deliverable. It regulates how personal information is collected, used, shared and deleted. Verification is generally permitted when the vendor acts as a service provider under a compliant written contract and your privacy notice discloses the activity.
Is a hashed email address still personal information under the CCPA?
Generally yes. Hashing an email address is a form of pseudonymization, and pseudonymized data that can still be linked to a consumer is typically treated as personal information. Do not assume hashing removes CCPA obligations. Treat hashed identifiers with the same contract, disclosure and deletion controls you apply to plain addresses.
Do I need opt-in consent before verifying a customer's email under the CCPA?
Generally no. The CCPA is primarily an opt-out and notice regime rather than an opt-in one for most processing. You must provide a notice at collection that covers the categories of personal information and purposes, and honor opt-out rights for sale or sharing. Confirm specific obligations with counsel, especially for sensitive data.
Does verification count as selling or sharing personal information?
It can, if the vendor is not a proper service provider. Sale involves disclosure for monetary or other valuable consideration, and sharing involves cross-context behavioral advertising. A verifier bound by a compliant service-provider contract that bars its own reuse of the data is generally not treated as a third party receiving a sale or share.
What must a service-provider contract include for email verification?
At minimum, it should prohibit the vendor from selling or sharing the data, from retaining or using it outside the direct business relationship, and from combining it with other personal information except as permitted. It should also require the vendor to comply with the CCPA, support deletion requests, and notify you if it can no longer meet its obligations.
How long do I have to respond to a deletion request tied to verified emails?
You generally have 45 calendar days to respond to a verifiable consumer request. The period can be extended once by up to 45 additional days if you notify the consumer. You must also pass deletion requests to service providers and contractors that hold the record so they can comply.
Does the CCPA apply to B2B email lists?
Yes. The exemptions for business-to-business contacts and employee data expired on January 1, 2023. A business contact at another company who is a California resident is a consumer under the CCPA, so their email address is personal information with the same protections as a consumer's.
Should I send the full contact record to an email verifier?
No. Data minimization suggests uploading only the email column and a row ID you generate internally. Sending names, phone numbers or other fields that the verification does not need increases your exposure and the scope of what your vendor must protect and delete.
What are the penalties for CCPA violations involving email data?
The CCPA allows the California Attorney General and the California Privacy Protection Agency to enforce violations through administrative fines and civil penalties. The statute sets higher amounts for intentional violations and for violations involving minors. Amounts are subject to inflation adjustment, so check current figures in the statute and official regulator materials.
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.