You didn't start an agencyto become a privacy desk.
ConsentCenter gives you one account across every client site, so consent stops being a bespoke build on every project.
- GDPR Article 28(10)
- GDPR Article 82(4)
- ePrivacy Directive Article 5(3)
Most agencies install a banner and call it compliance.
It isn't. It's decoration.
The trackers still fire before anyone clicks. There is still no record of what the visitor chose. And when it goes wrong, the client reads your name on the invoice and their own on the complaint.
Where this goes wrong first.
One setup per client, forever
Categories, regions, styling, tag rules — rebuilt from scratch on every project. Nothing you worked out on the last site carries to the next one, so the fifteenth build costs what the first one did.
You find out when they do
A client's marketing team adds a pixel on a Thursday and tells nobody. Without an inventory that re-scans the site, the first signal is a complaint — and it arrives as a question you cannot answer.
The request lands on you
A deletion request hits a client's info@ address and gets forwarded to your account manager. The GDPR clock is one month, extendable by two further months only for genuinely complex cases, and nobody started it.
What you are actually buying.
Stand up a new client site from a configuration you already trust.
Keep a per-client tracker inventory that updates as their site changes.
Give every privacy request a named owner and a visible deadline.
How it works
Template
Build the consent configuration once, with your categories, regions and styling.
Deploy
Apply it to each client property and adjust only what that client genuinely needs.
Report
Show each client what was captured, what changed, and which requests are open.
What the text actually says.
- GDPR Article 28(10)
- A processor that goes beyond the controller’s documented instructions and decides the purposes of processing itself is considered a controller for that processing.
- GDPR Article 82(4)
- Where more than one controller or processor is involved in the same processing, each can be held liable for the entire damage.
- ePrivacy Directive Article 5(3)
- Storing or accessing information on someone’s device requires their consent, unless it is strictly necessary to provide the service they asked for.
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
Discover trackers per client site and hold the optional ones until there is a choice.
View productUniversal Consent & Preference Management
Carry each client's marketing preferences into the tools their campaigns actually run on.
View productDSAR & Privacy Rights
Route client privacy requests through one workflow with owners and deadlines.
View product
Frequently asked questions
Yes. ConsentCenter is designed around separate properties under one account, so each client site keeps its own configuration, inventory and records while you work from a single place.
Yes. Appearance is configured per property, so a shared starting point does not force a shared look.
The client is the controller of their own visitors’ data, and that responsibility does not transfer to you or to ConsentCenter. What ConsentCenter provides is the configuration and the record of what happened, which is what a challenge actually asks for.
No. Most agencies start with Cookie Consent across client sites and add preference management or privacy requests as clients ask for them.
Bring us the agencies 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.