Consent, double opt-in & unsubscribes

Consent is tracked per channel, per contact — a contact can happily receive your SMS while having unsubscribed from email. The platform enforces it at send time so no code path can accidentally message someone without a legal basis.

Recording consent

Consent is written automatically when contacts arrive through forms (with timestamp, source and IP), and can be set explicitly via POST /v1/consent when you import audiences you've collected elsewhere. Every change is kept as an auditable history, not just a current flag — when a regulator asks when and how someone consented, the answer is one API call away.

Double opt-in

With double opt-in enabled (per form or per list), a new signup gets a confirmation message and only counts as subscribed after clicking. Yes, you'll "lose" the fake and mistyped addresses — that's the point. Those addresses were future bounces and spam-trap hits that would have dragged down deliverability for everyone else on your list.

Unsubscribing — every door open

• Email: every marketing email carries a List-Unsubscribe header with one-click unsubscribe (RFC 8058) — Gmail and Yahoo require this at volume, and the platform adds it automatically — plus a visible link in the footer.
• SMS: reply STOP (and local variants). Intercepted and processed instantly, before anything reaches your Inbox.
• Hosted page: the unsubscribe link leads to a hosted confirmation page (GET /v1/account/unsubscribes/:token) where the contact can also choose to only leave certain topics — see Preference center.

The suppression list

Unsubscribed and bounced addresses land on the suppression list: sends to them are blocked platform-wide, whatever the source (API, campaign, journey). Manage it under Audience → Suppressions — you can bulk-import suppressions from a previous provider (POST /v1/account/unsubscribes/api/import) on day one, which is strongly recommended before your first campaign.