What it is
A cookie banner is one interface a site can use to inform visitors about optional storage or tracking and collect a decision. Applicable rules generally prescribe an outcome—such as information, prior consent or an effective opt-out—rather than one universal visual component. The appropriate interface therefore depends on the processing and jurisdiction.
A banner is a rendering concern; whether a pixel fires is an execution concern. Clear copy does not control a request unless the visitor’s decision is connected to each relevant loader, tag, embed or platform API.
What a defensible banner contains
- A plain statement of what optional technologies the site wants to use and why
- An accept control and a refuse control at the same level of prominence
- A route into per-category choices without having to accept first
- A link to the privacy notice
- A way to reopen the choice later, from any page
StrongPrivacy ships this shape by default: "Accept all", "Reject optional" and "Manage choices", with necessary technologies marked always active and the privacy link resolved from the property’s configured privacy URL.
The banner is not the enforcement
In StrongPrivacy the decision about whether a declared or managed optional technology may run is made by the engine, not the banner. Under an opt-in model its loader is not created until the mapped category is granted. Scripts, embeds and server-side integrations installed outside that managed path still require separate control and verification.
Check this on your own site
Load the page with a fresh profile, refuse everything, and look at the network panel. If a marketing host appears anyway, the banner is decorative and the problem is upstream of it.
Common questions
Is a cookie banner legally required?
Privacy and storage rules generally do not require one universal component called a “cookie banner.” They may require information, prior consent before non-exempt storage or access, or an effective opt-out. A banner is one way to provide those controls; whether it is needed depends on what the site does and which rules apply.
Can a banner say "by continuing to browse you agree"?
Not in a prior-consent jurisdiction. Continued browsing is not a clear affirmative action, and the Court of Justice has been explicit that inactivity cannot be consent. The default copy in StrongPrivacy never implies it.
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.
- ICO: guidance on storage and access technologies
Regulator guidance
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.