Privacy Compliance for Email Capture — CAN-SPAM, GDPR, and Not Getting Sued
This is the eat-your-vegetables article. Privacy compliance isn't exciting, it isn't glamorous, and it won't make you a dollar. But it keeps the dollars you've already made from being taken away by regulators, lawsuits, or platform bans. Here's what you actually need to do — no more, no less.
In the first Jurassic Park, Jeff Goldblum’s Ian Malcolm delivers the line that every toll operator should tattoo on their forearm: “Your scientists were so preoccupied with whether or not they could, they didn’t stop to think if they should.”
I thought about this line when an operator I’d been following got hit with a GDPR complaint from a single subscriber in Germany. One person. One complaint. The fine wasn’t catastrophic — the operator had a small list and the violation was technical, not malicious. But the legal fees to respond, the audit to prove compliance, and the three weeks of panic were far more expensive than the thirty minutes it would have taken to set things up correctly in the first place.
Privacy compliance is the spinach of operating a toll position. Nobody gets excited about CAN-SPAM. Nobody opens a beer to celebrate a properly configured DMARC record. Nobody high-fives over a compliant privacy policy.
But the operators who skip this step are building on sand. One complaint, one platform audit, one regulatory notice — and the infrastructure you spent months building can be frozen, fined, or shut down.
So let’s eat the vegetables. I’ll keep it short, specific, and actionable. No legalese. No “consult your attorney” hedging (though you should, eventually). Just the minimum viable compliance that keeps you operating without looking over your shoulder.
CAN-SPAM: the U.S. baseline
CAN-SPAM is the federal law governing commercial email in the United States. It’s been around since 2003, and despite its age, it remains the baseline compliance standard for any operator sending email to U.S. recipients.
What CAN-SPAM requires:
-
No misleading headers. Your “From,” “To,” and “Reply-To” fields must accurately identify who’s sending the email. If you’re sending on behalf of a partner, the “From” field should reflect that relationship — not impersonate someone the subscriber has never heard of.
-
No deceptive subject lines. The subject line must relate to the email’s content. “Re: Your account” on a promotional email violates CAN-SPAM. This seems obvious, but aggressive subject line testing can drift into deceptive territory.
-
Identify the email as an ad. If the email is commercial in nature — and any email containing affiliate links qualifies — it must be identifiable as advertising. This doesn’t require a giant “ADVERTISEMENT” banner. A clear mention of the commercial nature is sufficient.
-
Include your physical mailing address. Every commercial email must include a valid physical postal address. This can be a street address, a registered PO Box, or a registered commercial mail receiving agency address. No, you can’t skip this. Yes, you need a real address.
-
Include an unsubscribe mechanism. Every email must contain a clear, conspicuous way for the recipient to opt out of future emails. The unsubscribe must be processed within 10 business days.
-
Honor unsubscribes. Once someone unsubscribes, you cannot email them again. Period. Your email platform handles this automatically — but verify that your automation sequences also respect unsubscribes. A subscriber who unsubscribes on Monday should not receive Email 5 of your sequence on Wednesday because the automation didn’t check.
CAN-SPAM penalties: Up to $51,744 per email in violation. The FTC has the authority to impose fines, and while individual small operators rarely face enforcement, the penalties are severe enough to be existential.
The practical takeaway: If you use any reputable email platform (ConvertKit, ActiveCampaign, Mailchimp, Beehiiv), most CAN-SPAM requirements are baked into the platform — physical address in footer, automatic unsubscribe links, header accuracy. Your job is to not override these defaults and to ensure your content doesn’t violate the deceptive-header and deceptive-subject-line provisions.
GDPR: the European standard
GDPR applies to any email sent to a resident of the European Union or European Economic Area — regardless of where you’re based. If you have a single subscriber in Berlin, GDPR applies to your handling of their data.
GDPR is more demanding than CAN-SPAM. Where CAN-SPAM allows implied consent (you can email someone who gave you their address in a business context), GDPR requires explicit, informed, freely given consent.
What GDPR requires for email capture:
-
Explicit consent. The subscriber must actively opt in to receive emails. Pre-checked boxes don’t count. Implied consent from a purchase doesn’t count for marketing emails. The subscriber must take a deliberate action (checking an unchecked box, clicking a “subscribe” button) that clearly indicates they want to receive your emails.
-
Informed consent. At the moment of capture, the subscriber must know: who will send them emails, what kind of emails they’ll receive, and how their data will be used. This is typically handled through a brief disclosure near the email capture form, with a link to your full privacy policy.
-
Right to access. Any subscriber can request a copy of all data you hold about them. You must provide it within 30 days. In practice, this means you need to be able to export a subscriber’s data from your email platform — name, email, tags, behavioral data, transaction history — on request.
-
Right to erasure (“right to be forgotten”). Any subscriber can request that you delete all their data. Not just unsubscribe — delete. You must comply within 30 days. This means removing them from your email platform, your analytics, your CRM, and any other system where their data exists.
-
Data processing records. You must maintain records of what data you collect, why, how it’s stored, and who has access. For a toll operator, this is straightforward: you collect email addresses for the purpose of sending product recommendations, you store them in your email platform, and you (and possibly your team) have access.
-
Data breach notification. If subscriber data is compromised, you must notify affected subscribers and the relevant supervisory authority within 72 hours. This is unlikely for operators using reputable platforms, but the obligation exists.
GDPR penalties: Up to 4% of global annual revenue or EUR 20 million, whichever is higher. In practice, small operators face smaller fines — but the legal costs of responding to a complaint are substantial regardless.
The practical takeaway: Add an unchecked consent checkbox to your email capture forms for EU visitors. Link to a privacy policy. Be able to export and delete subscriber data on request. If you use geo-targeting, you can show the consent checkbox only to EU visitors; otherwise, show it to everyone (it’s the safer approach).
CCPA: the California standard
The California Consumer Privacy Act applies to businesses that collect personal information from California residents AND meet certain thresholds: over $25 million in annual revenue, data on 100,000+ consumers, or earning more than 50% of revenue from selling personal data.
Most solo toll operators don’t meet these thresholds. But if you’re approaching them — particularly the 100,000 consumer data threshold, which includes email subscribers — CCPA becomes relevant.
What CCPA requires (relevant to operators):
-
Right to know. California residents can request what personal information you’ve collected about them. Similar to GDPR’s right to access.
-
Right to delete. California residents can request deletion of their personal information. Similar to GDPR’s right to erasure.
-
Right to opt out of sale. If you “sell” personal information (which, under CCPA’s broad definition, can include sharing data with affiliate networks for commission purposes), you must provide a “Do Not Sell My Personal Information” link.
-
No discrimination. You can’t charge different prices or provide different service quality to consumers who exercise their CCPA rights.
The practical takeaway: If you’re below the thresholds, CCPA’s requirements are minimal. If you’re approaching them, add a “Do Not Sell” link to your privacy policy and ensure you can honor deletion requests. The GDPR infrastructure you built covers most CCPA requirements.
The privacy policy
You need one. It doesn’t need to be 12 pages of legalese. It needs to clearly communicate:
- What data you collect. Email address, name (if you collect it), behavioral data (opens, clicks), and any other data your email platform tracks.
- Why you collect it. To send product recommendations and commercial email.
- How you store it. In [your email platform], which maintains its own security and privacy standards.
- Who has access. You, and any team members with platform access.
- How subscribers can access, modify, or delete their data. An email address to contact for data requests.
- How you use cookies and tracking. If your landing pages use analytics, retargeting pixels, or affiliate tracking, disclose this.
Host the privacy policy on a page accessible from every landing page and every email footer. Update it when your data practices change.
Cookie banners: when you need one
If your landing pages use cookies — and they almost certainly do, since analytics tools, retargeting pixels, and affiliate tracking typically set cookies — you need a cookie banner for EU visitors.
The cookie banner must:
- Appear before non-essential cookies are set (analytics, tracking, retargeting)
- Allow the visitor to accept or reject non-essential cookies
- Not pre-check acceptance boxes
- Allow essential cookies (those required for the site to function) without consent
The practical approach: Use a lightweight cookie consent tool. There are free and low-cost options that handle the banner, consent logging, and cookie blocking for non-consenting visitors. Set it up once and forget about it.
If 100% of your traffic is U.S.-based, the cookie banner is less legally urgent — but it’s becoming best practice even for U.S.-only sites as state privacy laws proliferate.
The compliance checklist
Here’s the minimum viable compliance setup for a toll operator:
- Every email includes your physical mailing address (usually auto-inserted by your email platform)
- Every email includes a working unsubscribe link (auto-inserted by platform)
- Unsubscribe is honored within 10 business days (automatic if platform is configured correctly)
- Subject lines accurately reflect email content
- Email capture forms include consent language and privacy policy link
- For EU visitors: consent checkbox is unchecked by default
- Privacy policy is published and accessible from all landing pages and emails
- You can export a subscriber’s data within 30 days of request
- You can delete a subscriber’s data within 30 days of request
- Cookie banner is active on landing pages with non-essential cookies (for EU visitors)
- Automation sequences respect unsubscribes (test this manually)
Thirty minutes to set up. Five minutes to verify quarterly. The cost of non-compliance — in fines, legal fees, platform bans, and lost sleep — is orders of magnitude higher than the cost of compliance.
Ian Malcolm was right. Just because you can capture an email without a consent checkbox doesn’t mean you should. The dinosaurs in Jurassic Park eventually ate the people who cut corners. Regulators are slower, but they have longer memories.
More on building toll infrastructure?
This article covered one piece of the build dimension. The newsletter delivers a new install pattern every week.
Unsubscribe in one click. Useful operator material only. Promotions, sponsors, and partner links will be disclosed.