1. Scope
This page explains technologies used by this independent guide. It does not describe cookies set by an external gambling operator or assume that another website follows the same practices.
The inventory concerns this guide's code. External sites, browser extensions and a hosting control panel have separate processing and storage. Follow their own policies when interacting with them.
2. Cookies and browser storage
Cookies can accompany server requests. Local storage remains associated with the browser's website origin. The inspected guide stores one notice-choice value; it is not an account or gambling preference.
The JavaScript uses the local-storage key dbbet_cookie_choice. The value records the notice choice and should not be confused with a server cookie, identity record or operator account setting.
3. Inspection result
The reviewed source does not load an analytics SDK, advertising pixel, external font service, embedded video or device-profiling script. This is a source inspection, not an assertion about every infrastructure log.
The HTML, CSS and JavaScript inventory concerns the delivered guide. A user's extensions, an external destination or the hosting provider can have separate behaviour that is not controlled by this notice.
4. Categories
The identified preference concerns notice dismissal. No analytics or advertising category is activated by the inspected source. A future change would require a new inventory and an appropriate choice mechanism.
Optional tracking must not be described as necessary merely because a banner contains an Accept button. Here, accepting or declining the notice does not enable a separate analytics or marketing script.
5. Technology inventory
| Technology | Provider | Purpose | Category | Validity | Consent required |
|---|---|---|---|---|---|
| dbbet_cookie_choice | This guide | Remember the notice choice | Notice preference | Until the user clears the website's browser storage | Set through the user's notice-choice action |
The inventory identifies the key, provider, purpose, category, duration and user action. If the implementation changes, the policy must change with it; an old description is not evidence of current behaviour.
6. User choice
Both acceptance and rejection leave the information accessible. Neither option switches on an analytics or advertising tracker in the inspected source.
The stored choice controls whether the notice returns. It is separate from any choices made on an external operator's website, where a different mechanism and policy may apply.
7. Changing a choice
Clear this website's local storage or site data in the browser settings to remove the preference. The notice can then appear again.
This guide has no separate consent-management panel. Browser site-data controls provide the removal route for the identified preference; clearing it does not close or modify an external gambling account.
8. External services
An external link opens another domain with its own terms, storage and privacy practices. Read those policies before entering personal information.
This guide's local preference does not grant consent on an external website. No account, deposit or document should be submitted merely because a link appears in an informational article.
9. Retention
The local-storage value has no automatic expiry in the inspected implementation. It remains until the user or browser clears it.
Hosting records and an external operator's retention periods are separate from this local-storage inventory. This guide cannot remove another provider's records through its own notice controls.
10. Rights and contact information
A public controller contact is not listed on this guide. No contact or KYC-upload form is provided. Users can inspect and remove the identified local preference through their browser's site-data settings.
For processing by an external operator or infrastructure provider, identify that recipient and consult its actual privacy and rights-request channels. This page does not provide a substitute contact or invent a data controller's identity.
11. Changes to technologies
If analytics, a consent manager or embedded services are added, the inventory, controls and privacy information need reassessment. A notice choice should not silently authorise a new purpose.
The policy must remain consistent with the delivered HTML, CSS and JavaScript. A label such as privacy-friendly does not prove an absence of processing; technical and hosting behaviour need their own assessment.