Compliance / Consent

A durable record of who can be contacted—and why.

Subscription changes are recorded with contact, channel, action, source, and time, then enforced before messages enter a send route.

✓START, STOP, and HELP events

✓Import, widget, API, and inbound sources

✓Cross-channel suppression

✓CSV and JSON exports

One contact-level decision

Consent is not split into disconnected provider lists; the workspace sees one current state with its event history.

Campaigns and automated sends re-check eligibility before dispatch so stale audience selections cannot bypass an opt-out.

Export the ledger when a carrier, client, or regulator needs the supporting history.

Ready to operate