Loading
Because consent usually lives in the marketing tool. When someone objects, the answer has to be assembled from three systems, and the one that is missing is the one that sent the email.
Consent is held per contact per purpose — marketing, product updates, research — each with the date it was given or withdrawn and the form or conversation it came from.
Consent state sits on the contact record itself, so every product reads the same values. Withdrawal takes effect immediately everywhere, and the full history of changes is kept.
A contact objects to marketing email. Their record shows consent given through a pricing-page form in March, a preference change in August, and the three sequences that stopped the moment it changed.
It records and enforces what you have configured. Which lawful basis applies to your business, and how long you may keep a record, are decisions for you and your advisers.
Sequences check it before sending, Growth excludes non-consenting contacts from campaigns, segments can filter on it, and the audit trail keeps every change with its actor.
Yes. Enrolment is checked at send, not only at enrolment.
Yes, via import or API, with the source recorded so it is not indistinguishable from a form fill.
Yes. Erasure removes personal data while keeping the anonymised financial record Books is required to hold.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.