A Practical Runbook for Marketing Privacy Compliance
Privacy and email compliance often gets pushed off with the assumption that it requires a legal team and a big project to address properly. Most of the foundational requirements are achievable with a focused, systematic pass through your actual practices, even on a small team.
This isn't legal advice, and anything jurisdiction-specific should go through your own counsel, but here's a practical runbook for the core, well-established requirements most marketing teams need to have in place.
Vendors Covered in this Article
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Step one: inventory where personal data actually lives
Before fixing anything, list every system that holds customer or prospect personal data: your email platform, CRM, analytics tools, any forms collecting information, and ad platform audience lists built from your own data. Most teams find this list is longer than expected once they actually look, since data tends to spread into new tools over time without anyone tracking it centrally.
For each system, note what data it holds and roughly how it got there, whether that's a form submission, a purchase, or an imported list. This inventory is the foundation everything else in this runbook builds on, and skipping it tends to mean later steps miss a system nobody remembered was holding personal data.
How do you confirm your emails meet CAN-SPAM requirements?
The well-established requirements are straightforward to check: a working, honored unsubscribe mechanism in every commercial email, a real physical mailing address in the footer, accurate and non-deceptive subject lines and sender information, and unsubscribe requests actually processed within the required window rather than just accepted and ignored.
Audit your actual current email templates against this list directly, don't assume a platform you're using handles all of it automatically just because it's a reputable email tool. Confirm each requirement is genuinely met in what recipients actually receive, not just in the platform's general capability to support it.
Step three: check how consent is actually captured, not just assumed
For any list building outside of a direct customer relationship, confirm you can point to how and when someone actually consented to receive marketing communication, whether that's an opt-in checkbox, a clear disclosure at signup, or another documented mechanism, rather than assuming consent because someone's email ended up on a list somehow.
Where jurisdiction-specific rules apply, like GDPR's requirements for EU residents, this is exactly the point to involve your own counsel on the specifics rather than relying on general guidance, since requirements and enforcement genuinely vary by where your contacts are located.
How do you handle data subject requests?
Have a defined, documented process for handling a request from someone asking what data you hold on them, asking you to correct it, or asking you to delete it, even if you've never received one yet. Know which systems from your inventory would need to be checked or updated to fulfill each type of request, and roughly how long it would take.
A request handled ad hoc, scrambling to figure out where someone's data lives across five disconnected systems, takes much longer and is far more likely to miss something than one handled against a process you've already thought through and, ideally, tested once with a sample request.
Step five: keep evidence, and revisit the inventory periodically
Keep a simple record of consent mechanisms, unsubscribe processing, and any data subject requests you've handled, since being able to show your practices rather than just describe them matters if anything is ever questioned. This doesn't need to be elaborate, a maintained log is enough for most small teams.
Revisit the full data inventory roughly twice a year, since new tools and new lists tend to get added over time without anyone updating the original picture. An inventory that's accurate once and never rechecked drifts out of date in exactly the way that creates real risk later.
Assign this revisit to a specific person with a specific date, not a general intention to get to it eventually. A recurring task with an owner and a deadline actually happens; a loose plan to revisit something periodically tends to quietly slip for a year or more.
Work through the runbook in this order:
- Inventory every system holding personal data, including email, CRM, analytics, forms and ad audience lists, and note how the data got there.
- Check that every commercial email has a working unsubscribe, a physical mailing address, and accurate subject lines and sender information.
- Confirm you can show how and when each contact consented, instead of assuming consent because an address ended up on a list.
- Document a process for data subject requests, including which systems you would check and roughly how long fulfillment would take.
- Keep a simple log of consent, unsubscribes and requests handled, and revisit the inventory about twice a year.
What Good Looks Like
Good marketing privacy practice means you can produce, on short notice, a current inventory of where personal data lives and evidence of how consent and unsubscribe requests are actually handled.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
A tool like Vanta can help maintain a continuously updated inventory of systems holding personal data and generate the evidence trail this runbook asks you to keep by hand otherwise.
Drata is a reasonable alternative to Vanta for the same job, automating evidence collection around your data inventory and consent practices instead of maintaining a manual log.
Frequently Asked Questions
Do we need a lawyer to be compliant with basic email marketing rules?
The well-established requirements, like a working unsubscribe link and accurate sender information, are straightforward enough for a marketing team to audit and fix directly. Anything jurisdiction-specific, especially around consent requirements for regions like the EU, is worth a conversation with counsel rather than relying on general guidance, since the specifics genuinely vary by where your contacts are located.
What's the most common compliance gap small marketing teams have?
An incomplete picture of where personal data actually lives, since it tends to spread into new tools over time, forms, ad platform audiences, analytics, without anyone maintaining a central inventory. Without that inventory, even a team with genuinely good intentions can miss a system entirely when handling a data subject request or auditing consent.
How quickly do unsubscribe requests need to be honored?
CAN-SPAM requires you to honor unsubscribe requests within 10 business days, and continuing to email someone after that window is a violation, not just a courtesy issue. Confirm your actual email platform is processing unsubscribes promptly and completely, rather than assuming it handles this correctly by default.
What should we do if we've never received a data subject request and aren't sure our process would actually work?
Test it with a sample request before you need it for real, ideally by having someone internally submit one and timing how long it takes to fulfill using your actual current systems and inventory. Finding gaps during a low-stakes internal test is far better than finding them for the first time under a real deadline.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
SMS Marketing Compliance: The Questions to Answer Before You Send
Plain answers to the consent, opt-out, and record-keeping questions a marketing team needs to settle before sending its first text campaign.
Which Conversion Benchmarks Actually Apply to Your Funnel
A guide to reading conversion rate benchmarks correctly: which published numbers are close enough to compare against, and which ones will mislead you.
Why Marketing Privacy Compliance Breaks as Campaigns Multiply
The specific, mechanical ways GDPR and CAN-SPAM compliance quietly breaks down as a marketing team adds tools and campaigns, and what to fix at each point.
Deciding Whether Community-Led Growth Fits Your Product
A decision guide for whether an owned community will actually drive growth for your product, and what it takes to run one instead of just launching one.
A GDPR and CAN-SPAM Runbook for Teams Without In-House Counsel
A practical runbook for the marketing operations side of GDPR and CAN-SPAM compliance, plus when to bring in an actual attorney.
Keeping Your Creator Program's Disclosures and Data in Order
A practical checklist for creator and affiliate program compliance covering FTC disclosures, contract terms, evidence records and partner payment and tax data.