Cookie notice

Last updated: 12 August 2026. How AdVault Craft uses cookies and similar storage on advaultcraft.life.

Cookie storage on advaultcraft.life is minimal by design: one consent record, optional functional permission for maps, optional analytics flag reserved for future use.

The consent cookie sg_studio_consent is JSON URL-encoded with keys essential, functional, analytics, ts and v. It is set with Path=/, SameSite=Lax and Secure on HTTPS connections.

localStorage key cookie_consent_v1 mirrors the cookie so choices survive browser settings that block cookies until cleared manually.

Reject all sets functional and analytics to false. Maps then show placeholders with a Load map button that sets functional true when clicked — documented in DELIVERY-QA for this build.

Customise lets you enable maps without analytics. Save choices overwrites prior consent and hides the banner until expiry or manual reset via browser data deletion.

Manage cookies on this page reopens the banner panel with toggles reflecting current values. Keyboard users can tab to buttons; focus rings are visible on both themes.

We do not use cookie walls or blocking modals. The banner is a bottom strip that does not prevent reading page content while visible.

Third-party cookies from Google may appear only after functional consent when a map iframe loads. Review Google privacy documentation for their retention practices.

Accept all enables functional maps and leaves analytics off by default in the current implementation. You may enable analytics separately in customise if we add tools later.

Clearing site data in your browser removes consent and restores the banner on next visit — expected behaviour, not an error.

Essential cookies cannot be disabled while using consent storage; without them the banner would reappear every page load and map preferences could not be remembered.

Functional toggle controls Google Maps iframes site-wide. Privacy notice describes map data processing; this page describes the technical switch only.

Analytics toggle is present for future tools; current build does not load third-party analytics scripts even when toggled on — documented here for transparency.

Cookie panel opens from Customise on the banner or Manage cookies on this page. Panel is not modal; page scroll remains available.

prefers-reduced-motion disables banner slide animations but not consent storage functionality.

Session testing checklist for QA: first visit banner visible; accept hides on reload; reject shows map placeholders; customise saves exact flags; manage reopens panel.

Cookie JSON schema version v1 allows future fields without breaking parsers; malformed cookies trigger banner display and are overwritten on next save.

Browser private mode may block localStorage; cookie still attempts to persist consent for the session path where supported.

Cross-page consistency: consent read on every page load from cookie first, then localStorage backup key cookie_consent_v1.

Contact [email protected] for cookie questions not answered here; include browser and choice made for faster diagnosis.

Cookie banner copy on this site differs from MarkBloom Wave banner sentences — consent mechanics share code, not marketing text.

Developers reviewing main.js should note defensive JSON parse on malformed consent cookies — banner reappears rather than throwing errors.

Map placeholder copy explains functional consent in plain English without legal cross-reference only — privacy notice holds PDPA detail.

Six-month retention aligns with prompt spec; DevTools may simulate expiry by editing cookie Max-Age during QA.

Essential flag is always true in saved JSON; customise panel shows essential locked on to meet consent audit expectations.