The problem is not the banner
Large organisations may have multiple consent implementations configured by different teams. The audit question is whether each property has a current, evidenced inventory and can reproduce what a particular visitor was shown and chose.
That is a verification and evidence problem. Scheduled browser scans across properties, configuration versions that decisions point back to, and investigations from real captures when something specific needs explaining.
The managed service
The managed service is sold through a written engagement rather than self-serve checkout. The public package describes an assigned specialist, reviewed publication and agreed capacity; those commitments apply only when they appear in the executed order form or service description, with named owners and measurable response and review terms.
- Everything in Agency, with capacity agreed per engagement
- A named specialist and review scope, when included in the executed engagement
- Evidence investigations from your own HAR captures, with written findings
- Protected publication when the engagement enables the specialist approval gate
- Periodic written reviews at the cadence stated in the executed engagement
Reviewed publication is the part that matters at scale
The risk at forty properties is not that nobody knows what to do. It is that a well-meaning change goes live on a Friday and nobody notices for a month. A review gate makes that a process rather than a hope.
Common questions
Can we get a data processing agreement?
A draft DPA and draft subprocessor disclosure are published for review. They currently identify the intended controller/processor allocation, but the legal entity, execution details, transfer mechanism and incomplete vendor fields must be confirmed in an executed agreement before they can be relied on as contractual commitments.
How do we migrate from an existing platform?
One property at a time, with a clean cutover rather than an overlap. The migration guide covers the specific failure mode: two consent systems running at once, producing states that contradict each other.
Sources and verification
Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.
- StrongPrivacy product capabilities
Product documentation
Checked
- Regulation (EU) 2016/679 (GDPR)
Legislation
Checked
See what your own site is loading
A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.