What changes at twenty sites
The configuration work per site is much the same. What changes is everything around it: knowing which installations are healthy, noticing when a client’s developer adds a pixel, and being able to show a client what you found without rebuilding the analysis from memory.
- Twenty-five properties on the Agency plan, each with its own configuration and its own evidence
- Two hundred scans a month across them, up to twenty-five pages per scan, on a daily schedule
- Thirty-six months of consent-record retention, which outlasts most client relationships
- Installation health surfaced from heartbeats rather than discovered when a client complains
The deliverable is the finding, not the banner
Clients do not pay for a cookie banner; they can get one free. They pay to be told what is on their site, what it means, and what to do about it. Evidence investigations turn a HAR capture into a reviewable artefact with written findings, and captures can be compared to show what changed between two dates.
That comparison is the thing that turns a one-off audit into a retainer: "here is what changed since last quarter, here is what your developer added in March, here is what it is doing".
When the client wants the work done, not the tool
Above the self-serve plans is a managed service sold through a written engagement. An assigned-specialist workflow and protected publication are available where the executed order form includes them; define the properties, review scope, approvers and service levels rather than relying on an unqualified website promise.
Common questions
Can each client have their own workspace?
Properties live inside a workspace, and the Agency plan covers twenty-five of them. Where a client needs their own workspace and their own billing, that is a separate arrangement worth discussing rather than working around.
What happens to the evidence when a client leaves?
Consent records are retained by plan (thirty-six months on Agency) and are exportable as CSV at any point. Export before you offboard, because the records belong to the relationship rather than to the tool.
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
- StrongPrivacy verification guide
Product documentation
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.