Cookie policy
What this site stores, and why.
This cookie policy covers the storage and access technologies used by the BaseLayer Digital site itself, what is treated as essential, what optional categories are currently inactive, and how consent choices can be changed later.
Policy scope
This policy is about storage on this site itself.
At the time of writing, this site does not use active analytics tags, advertising technology, or behavioural marketing scripts. The active persistent storage used by the site itself is the accessibility/runtime preference layer and the related consent-preference layer.
Essential runtime storage.
The current site stores accessibility and display settings chosen by the visitor, such as theme, contrast, text presentation, motion preferences, transparency settings, and related reading controls. This storage exists so the page can reopen in the same usable state on the next visit.
Why this is treated as essential
That preference store is treated as essential because it preserves a user-requested runtime experience rather than supporting advertising, analytics, or profiling. The preferences interface still shows that category openly, but it is not offered as an optional marketing-style toggle because the site depends on it to remember the accessibility settings the visitor deliberately chose.
Optional categories are currently off.
The consent interface includes optional categories for analytics and marketing so the consent model can expand cleanly later without silently changing how the site behaves. Those categories are currently inactive on this site and should remain off unless a future change introduces them properly and updates this policy at the same time.
- Analytics and measurement: not active on this site today.
- Marketing and third-party tracking: not active on this site today.
- Third-party builder or integration storage: may apply on separate client projects delivered on external platforms, but that storage belongs to those platforms and services rather than to this site itself.
Third-party delivery layers.
The live site is delivered through Cloudflare as a third-party infrastructure layer for hosting, content delivery, caching, and security. Where Cloudflare uses network-level or delivery-level technologies as part of serving the site, those should be understood as part of third-party infrastructure operation rather than as first-party advertising or profiling technology added by BaseLayer Digital.
Search engines may also crawl and cache public pages. That crawling activity is not treated as this site's own analytics or marketing layer. Search-engine indexing, caching, ranking, and snippet behaviour sit with the relevant search provider and are outside direct editorial control.
Changing your choices.
Once a visitor has made a choice in the consent layer, the site provides a cookie settings control in the footer so that choice can be reviewed and changed later. Essential runtime preferences remain visible in that interface but stay non-toggleable while the current implementation depends on them to preserve the experience the visitor actively requested.
If the site's storage model changes in a material way, this policy and the on-site consent controls should be updated at the same time rather than after the fact.
The legal wording matters. The live controls matter too.
See how the engine behaves on the page itself.
The engine page shows the runtime controls that make those stored accessibility preferences useful in practice.