Why this policy exists
Cookies, pixels, local storage keys, and similar technologies (“cookies” here as shorthand) can identify browsers or devices. Under the ePrivacy Directive as implemented in Norwegian law, paired with GDPR transparency duties, we must explain what we store, why we store it, how long it lasts, and how you can object or revoke consent.
This Cookie Policy complements the Privacy Policy. Where a conflict arises, the more specific instrument prevails for the matter it addresses.
Controller contact
Brandoadesign.world
Vetrlidsallmenningen 11, 5014 Bergen, Norway
Email: ask@brandoadesign.world
What technologies we use
HTTP cookies are name-value pairs exchanged between browser and server. Local storage persists larger key-value records client-side until cleared. Session storage mirrors local storage but expires when the tab closes. Server-side logs are not cookies but may record IP metadata that this policy references where intertwined with cookie consent state.
Static demo notice: on this deployment, non-essential categories rely on localStorage key cookie_prefs to remember banner outcomes until you erase site data.
Cookie categories in depth
Strictly necessary
These enable core functions such as security hardening, network management, accessibility state persistence, load balancing signals, consent-string storage, and fraud heuristics. They do not require consent under ePrivacy implementations because they are essential to provide an explicitly requested service, but we still document them for completeness.
Functional (where activated)
Optional preference memories—like remembering that you expanded a long legal section—may be introduced later; they always respect your prior consent and expire on a defined schedule.
Analytics (optional)
If enabled, analytics technologies measure aggregate traffic characteristics such as landing pages, scroll depth proxies, and conversion funnel drop-offs. We configure pseudonymous identifiers where possible and shorten retention to the minimum compatible with statistical reliability.
Marketing (optional)
Enabling marketing cookies might allow attribution tags that connect ad clicks with on-site events. We only deploy such tools after explicit opt-in and supply an always-visible route to adjust preferences.
Illustrative inventory
| Name / key | Purpose | Category | Duration |
|---|---|---|---|
cookie_prefs |
Stores banner decisions | Necessary / consent artifact | Until cleared by user |
| Session identifiers | Secure checkout continuity once launched | Necessary during session | Session |
| Analytics ID (if consented) | Aggregated usage metrics | Analytics | Vendor default, ≤ 24 months |
How consent is captured and withdrawn
The first-layer banner offers Accept all, Reject non-essential, and granular Cookie settings. Saving granular preferences writes to local storage and closes the modal. Withdrawing consent is as simple as clearing site storage or re-opening settings when we expose a footer link in future iterations.
Browser-level control: blocking all cookies may impair checkout or consent recall. Use per-site exceptions where your software supports fine-grained controls.
Policy maintenance
When we adopt new vendors or tracking technologies, we update this inventory, bump the visible date, and, where legally compelled, seek renewed consent before activating non-exempt cookies.
Questions
Email ask@brandoadesign.world with the subject “Cookie inquiry” for clarifications or to report unexpected identifiers.