Every send's footer includes a {{unsubscribe_url}} merge tag pointing at a real hosted page — a one-click, account-wide unsubscribe plus a second form for correcting or deleting the recipient's data, routed to you as a support ticket rather than deleted automatically.
A compliant unsubscribe link isn't a mailto: address someone has to write in by hand — it's a page that actually does something the moment it's confirmed.
One click, suppressed everywhere
Confirming unsubscribe on the hosted page blocks that address across every project you send from, not just the campaign it came from — checked automatically before every future send, with a badge and a Resubscribe action visible in Contacts afterward.
Not a granular preference picker — yet
Unsubscribe today is account-wide and blanket: one suppression list per owner, not a per-topic opt-in/opt-out picker. A recipient who unsubscribes stops receiving everything from that account across every project, not just marketing emails from one of them.
Data requests become a ticket, not a delete button
The same hosted page's "Correct or delete your data" form submits as a badged Privacy request support ticket in your own inbox. A single click can't safely delete a contact row on its own — doing so could break response attribution, void an order's audit trail, or ignore a legal reason to retain the record — so that judgment call stays with you as the controller.
Transactional mail plays by different rules
A send marked type: "transactional" (via the Send API) bypasses unsubscribe-suppression, since a receipt still needs to reach someone who opted out of marketing — but it never bypasses bounce-suppression, which always applies.
Getting started
Keep the {{unsubscribe_url}} tag in your footer preset, and review Privacy & data controls for exporting or deleting your own account's data alongside handling recipient requests as they arrive in your ticket inbox.