Your marketing site says one thing.Your product says another.
ConsentCenter ties the choice made on the website to the preference set inside the product, against one record.
- GDPR Article 7(3)
- GDPR Article 7(1)
- GDPR Article 28(2)
You have consent in two places that have never spoken.
Marketing captured a cookie choice. The product captured a preference toggle.
Nothing reconciles them. So "did this user opt out?" has two answers, and the pipeline ships whichever one it reached first.
Where this goes wrong first.
The handoff loses the choice
Someone rejects analytics anonymously, then signs up ten minutes later. The browser-level choice and the account are now two unrelated facts, and the account is the one your systems act on.
The toggle goes nowhere
You shipped a notifications screen in the product. It writes to your own database and stops there — the CRM, the email tool and the warehouse never hear about it and keep sending.
Proving it means an archaeology project
A customer asks what they agreed to and when. Answering means joining your app database, your tag manager and an export from a marketing tool, and the three disagree about the date.
What you are actually buying.
Keep website and in-product choices tied to one consistent consent record.
Push purpose-based preferences to CRM, marketing and identity systems.
Answer "what did this user choose, and when" from one place.
How it works
Capture
Collect region-aware cookie consent and purpose-specific product preferences.
Connect
Resolve each choice to the right person and send the update to the systems that act on it.
Prove
Keep the history that explains what changed, when, and through which experience.
What the text actually says.
- GDPR Article 7(3)
- Consent can be withdrawn at any time, and withdrawing it must be as easy as giving it.
- GDPR Article 7(1)
- The controller must be able to demonstrate that the person consented.
- GDPR Article 28(2)
- A processor cannot engage another processor without the controller’s prior written authorisation, specific or general.
Paraphrased for brevity and provided for orientation, not as legal advice. Which obligations apply to your organisation is a question for your own counsel, and ConsentCenter does not determine it for you.
The products that apply
Cookie Consent
Control trackers across the marketing site and the authenticated product.
View productUniversal Consent & Preference Management
Hold purpose-based choices once and keep the rest of the stack in step.
View productDSAR & Privacy Rights
Run access, deletion and correction requests through one accountable workflow.
View product
Frequently asked questions
ConsentCenter is designed to capture browser-level choices and to connect identified preferences to the appropriate person and purpose once identity is available.
No. Each product works on its own and can be connected to the others as your privacy programme grows.
That is exactly the handoff this is built for: the browser-level choice is recorded first, and ConsentCenter is designed to resolve it to the account once there is an identity to attach it to.
Bring us the saas companies version of this problem.
Show us the consent question you cannot currently answer — the choice that did not propagate, the record you could not reproduce — and we will walk through exactly how ConsentCenter handles it.