GDPR-Compliant Unsubscribe & Data Request Pages

Respecting your readers' choices is built into every email. The footer links to a hosted page where a reader unsubscribes in one click, keeps only the topics they want, or asks you to correct or delete their data. Requests arrive as tickets, and the contact's profile exports or erases everything you hold on them, across every list.

Subject

Weekend sale — 20% off

Every email's footer links to a hosted page where a reader unsubscribes in one click, keeps only the topics they want, or asks you to correct or delete their data. Requests arrive as tickets, and each contact's profile exports or erases everything you hold on them.

A compliant unsubscribe is a page that acts the moment the reader confirms, and a data request deserves an answer you can give in minutes.

One click, or just one topic

Keep the {{unsubscribe_url}} tag in your footer: the Footer preset has it. Confirming on the hosted page stops that address across every email you send, checked before each send, with an unsubscribed badge in Contacts. See Unsubscribe & suppression.

To let readers choose, name a few mail topics under Settings, such as "Product updates", "Promotions" or a weekly digest, and assign each email to one. Its page then shows a checkbox per topic, so a reader can drop promotions and keep the updates they value.

Every contacts import asks how the people in it agreed to hear from you, and saves the answer on each contact with who gave it and when. Contacts imported as a purchased or prospect list are kept off your sends. On signup forms and in emails, a form's consent checkbox records each reader's opt-in on their contact. See The consent question.

Data requests arrive as tickets

Below the unsubscribe link, the hosted page offers Correct or delete your data. The request arrives in your inbox as a Privacy request ticket, with what the reader asked for.

Export or erase in two clicks

The account owner opens the contact's profile and uses the Privacy requests card:

  • Export their data downloads one file with everything your account holds about the person: their rows in every list, consent records, answers, bookings, deals, orders and tickets.
  • Erase this contact deletes all of it, across every list. Their unsubscribe record stays, so a later import never emails them again, and orders keep their amounts for your accounts with the buyer's details removed.

Each action is recorded in your data-access log. Reply in the ticket to confirm. See Exporting or erasing one Recipient's data.

Transactional mail reaches everyone

Receipts and account notices sent through the Send API with type: "transactional" reach readers who unsubscribed from marketing. Addresses that bounced are skipped for every kind of email.

Getting started

Keep {{unsubscribe_url}} in your footer, add mail topics under Settings for topic choices, answer the consent question on each import, and handle requests from the contact's Privacy requests card.

A typical build-and-send sequence

  1. 1

    Keep the unsubscribe link in your footer

    The Footer preset's {{unsubscribe_url}} tag links each reader to their own hosted page.

  2. 2

    Add mail topics

    Name topics under Settings, such as Product updates or Promotions, and assign each email to one so readers choose what they keep.

  3. 3

    Record consent

    Answer the consent question on every import, and add a consent checkbox to your signup forms.

  4. 4

    Answer requests

    Data requests arrive as Privacy request tickets. Export or erase the person from their contact profile, then reply in the ticket.

Frequently asked questions

Can readers keep some topics and drop others?

Yes. Name a few mail topics under Settings and assign each email to one. That email's unsubscribe page then shows a checkbox per topic, so a reader can drop promotions and keep product updates.

What happens when a reader asks to delete their data?

The request arrives as a Privacy request ticket, and you decide as the data controller. Erase this contact, on the contact's profile, then deletes their data across every list in one step and keeps their unsubscribe record, so they're never emailed again.

Do transactional emails reach readers who unsubscribed?

Yes. Receipts and notices sent through the Send API as type transactional reach readers who unsubscribed from marketing. Addresses that bounced are skipped for every kind of email.

How are bounced addresses handled?

Like an unsubscribe: the address is kept off future sends and shows a bounced badge in Contacts. A mailbox your relay refuses as unknown is suppressed at once, and sending from your own verified domain also reports later bounces and complaints.

Can a reader come back after unsubscribing?

Yes. Once the reader tells you they want your emails again, click Resubscribe next to their address in Contacts.

Build this in the studio

Start on the free plan — every interactive block and the full fallback engine are included on every tier.