Cookie consent
Learn how the platform’s cookie consent service and JavaScript client publishes banner versions, category tracking groups, and records visitor consent.
The platform provides a consent service for cookies and the client package @probo/cookie-banner. Together, they publish a version banner, collect visitor choices and control the configured tracking resources.
System model
Section entitled “System Model”- A banner contains defaults, presentation settings, and translations.
- Categories Necessary and uncategorised categories have system behavior; custom categories can be added and rearranged.
- Tracker patterns identification of resources and cookies. tracking resources can be moved between categories.
- A published version is the configuration delivered to visitors.
- A consent record Stores the action, category choices, banner version, client context and timestamp to the platform.
Project changes do not change the configuration already displayed to visitors. Publish a new version after reviewing categories, translations, resources and standards.
Browser behavior
Section entitled “Browser behavior”The JavaScript client retrieves the published configuration from /api/cookie-banner/v1, resolves the language, regulation and appearance (presentation), reads the existing consent and plays the selected UI.
The package supports a ready-made banner and lower-level web components for customized interfaces. API Consent Manager exposes current choices and change events to other application codes.
Confidentiality and legal liability
Section “Privacy and Legal Responsibility”Geolocation, presentations (opt-in, opt-out and notification), global privacy control management, version history and consent records help teams implement a consent program. They do not determine which law applies, do not automatically classify each tracker or guarantee legal compliance. The site operator remains responsible for the tracker inventory, category purpose, copy, retain and legal review.