A lot of sites collect almost no personal data except one thing: an email address, typed into a signup form in exchange for a newsletter subscription or a downloadable lead magnet, a checklist, template, or short guide gated behind the same form. That looks like the simplest possible privacy policy to write. In practice it is one of the easier ones to get subtly wrong, because the generic privacy policy template most sites start from is written for a business collecting names, addresses, and payment details, and it says almost nothing about the three things an email-list privacy policy actually needs: how the opt-in itself works, who processes the list once someone subscribes, and how a subscriber gets out.
Single Opt-In vs. Double Opt-In, and Why the Policy Has to Say Which
Opt-in method is a privacy policy disclosure, not just an email marketing setting, because it is the mechanism by which consent is captured, and consent is the legal basis most sites rely on for sending marketing email at all. Single opt-in adds someone to the list the moment they submit the form: no confirmation step, no second click. Double opt-in sends a confirmation email first, and the subscription only becomes active once the recipient clicks a link in that email confirming they meant to sign up. The confirmation email itself is a transactional message, not a marketing one, so most sending platforms and most read of anti-spam law allow it to go out before any consent has been confirmed.
The gap between the two matters more under GDPR than under US law. GDPR requires consent to be freely given, specific, informed, and unambiguous, and a double opt-in confirmation click is the clearest evidence a business can produce that a real person, not a typo, a bot, or someone else filling in a stranger’s address, actually agreed to receive email. Regulators and email service providers increasingly treat double opt-in as the practical standard for EU-facing lists for exactly that reason: it is not a separate legal requirement spelled out by name in the GDPR text, but it is the version of “unambiguous consent” that is easiest to defend if a subscriber later disputes ever signing up.
Single opt-in vs double opt-in for a privacy policy
| Single opt-in | Double opt-in | |
|---|---|---|
| When list is active | Immediately on form submit | After confirmation link is clicked |
| Consent evidence | Form submission and timestamp only | Submission plus a confirmed click |
| GDPR fit | Workable but harder to defend | Closest to unambiguous consent |
| CAN-SPAM requirement | Not required either way | Not required either way |
| Common use | US-only lists, low-risk content | EU-facing lists, gated lead magnets |
Whichever method a site uses, the privacy policy should state it plainly, something like “when you subscribe, we send a confirmation email and your subscription becomes active once you click the link in it” for double opt-in, or “you are added to our list when you submit the signup form” for single opt-in. Leaving this out is not usually a legal violation on its own, but it is the kind of gap that turns an unhappy subscriber’s “I never signed up for this” into a dispute the business has no documented answer for.
Lead Magnets Collect More Than an Email Address, Sometimes
A newsletter signup form usually asks for one field. A lead magnet, a free guide, checklist, or template offered in exchange for an email address, sometimes asks for more: a first name, a company size, a job title, or an answer to a qualifying question before the download unlocks. Each additional field is additional personal data, and the privacy policy’s data-collection section needs to list what is actually gathered at the point of download, not just “we collect your email address when you sign up for our newsletter” copied from a template that assumed a one-field form.
The lead magnet delivery mechanism matters too. If the download triggers automatically after form submission, that is different, from a disclosure standpoint, than a delivery email sent after the fact, because the second path means the site is now also using the email address for a one-time transactional send in addition to whatever ongoing newsletter the person may or may not have also opted into. A common mistake is treating “downloaded the lead magnet” and “subscribed to the newsletter” as the same event when the sign-up form only asked once and the checkbox for the newsletter was pre-checked, or missing entirely. If the two are meant to be separate opt-ins, the form needs to ask separately, and the policy should describe both uses rather than collapsing them into one.
Naming the List Provider, Not Just Describing It
Almost every site running an email list is not storing subscriber data on its own server. It is handing that data to a third-party email service provider, Mailchimp, ConvertKit, ActiveCampaign, Klaviyo, or something similar, that stores the list, sends the campaigns, and tracks opens and clicks. Under GDPR that provider is a data processor acting on the business’s instructions, and the privacy policy’s third-party disclosure section should say so specifically enough that a reader can tell who actually has the data, not just that “we may share information with service providers” in the abstract.
A specific disclosure names the category of service, email marketing platform, and ideally the provider itself, and states what the provider does with the data: store the list, send campaigns, and in most cases track opens and link clicks for analytics the business itself sees in a dashboard. That last part is easy to leave out and worth including, because open and click tracking is itself a form of profiling the subscriber may not expect from a plain-text disclosure that only mentions “sending you emails.”
- We may share your information with third-party service providers
- We use tools to help manage our email list
- Your data may be processed by our partners
- Your email address and name are stored and sent through Mailchimp, our email service provider
- Mailchimp processes this data on our behalf and does not use it for its own marketing
- We use open and click tracking to see which emails you engage with
If the site also runs ads or shares subscriber data with an ad network for retargeting, that sharing has its own disclosure requirement separate from the list-provider one, and under CCPA and CPRA it can count as a “sale” or “share” of personal information even without money changing hands; see CCPA and CPRA Privacy Policy Requirements for what that adds to the policy for California subscribers. And if the signup form or lead magnet landing page sets tracking cookies or pixels of its own, separate from what the email itself does, that is a cookie-policy disclosure rather than an email one; see Cookie Policy vs. Privacy Policy for where that line falls.
Unsubscribe Rights: What the Policy Has to Promise, and Actually Keep
In the United States, the CAN-SPAM Act sets the floor for every marketing email, newsletter or otherwise: every message needs a clear and conspicuous way to opt out, that opt-out request has to be honored within 10 business days, and the business cannot charge a fee, require a login, or ask for anything beyond an email address to process it. CAN-SPAM does not require opt-in consent at all, which is why single opt-in is legal for US-only lists, but it is strict about the exit: once someone unsubscribes, sending them another marketing message afterward is a violation regardless of how they were added to the list in the first place.
GDPR adds a second layer for subscribers in the EU: the right to withdraw consent has to be as easy as it was to give in the first place. If subscribing took one click on a web form, requiring a subscriber to email support, wait for a manual reply, or navigate a multi-step account settings page to unsubscribe does not meet that standard. A one-click unsubscribe link in every marketing email, the same mechanism most email platforms build in by default, satisfies both CAN-SPAM’s 10-business-day requirement and GDPR’s ease-of-withdrawal requirement at once, which is why nearly every list provider makes it the default rather than an opt-in feature.
The privacy policy should state, plainly, that a subscriber can unsubscribe at any time using the link included in every email, and separately, that unsubscribing from the newsletter does not automatically delete the underlying subscriber record from the list provider’s system, an unsubscribed contact is often retained, suppressed from future sends, specifically so the business does not accidentally re-add and re-email someone who already opted out. If the site also lets subscribers request full deletion of their data rather than just suppression from sends, the policy should describe that as a separate, further step, since the two are legally and practically different: one stops emails, the other removes the record entirely. GDPR’s right to erasure covers the second kind of request for EU subscribers regardless of what the list provider’s default retention setting does; see GDPR Privacy Policy Requirements for how the erasure right applies beyond just the unsubscribe mechanism.
Putting the Clauses in Order
A privacy policy built around an email newsletter or lead magnet reads well when it follows the order a subscriber actually experiences the list: what happens when the form is submitted (single or double opt-in), what data is collected at that point (email address, and anything extra a lead magnet form asks for), who processes it after that (the list provider, named specifically), what tracking happens once someone is subscribed (open and click tracking, and any ad-network sharing), and how to get out (the unsubscribe link, the 10-business-day CAN-SPAM window, and whether suppression or full deletion is available on request).
None of these sections needs to be long. A newsletter-only site’s privacy policy can be genuinely short, since there is comparatively little data in play, but each of the five pieces above needs to be present and specific, because a generic template’s placeholder language, “we may collect information you provide” and “we use service providers to operate our business”, does not actually answer any of the questions a subscriber, or a regulator, would ask about a list built on an opt-in form. Our Privacy Policy generator builds the opt-in method, list-provider, and unsubscribe-rights sections from a short set of questions about how the signup form and email platform are actually set up, so the policy matches what the form does rather than a template written for a business collecting a different kind of data entirely.








