Cookie Policy

1. What is actually stored

For an ordinary visitor, two items:

• apex-consent (local storage) — holds the value accepted or declined, depending on which button you pressed on the cookie banner. Its only effect is to stop the banner reappearing on your next visit.
• apex-hero-complete (session storage) — records that you have already watched the car on the home page finish changing color, so returning to that page during the same visit does not make you scroll through the whole animation again. It is discarded when you close the tab.

If you open the demonstration content editor at /admin.html, four more items are written. All four are in session storage, so they are discarded the moment you close the tab — the demo resets itself for the next visitor. They are never created by simply browsing the site:

• apex-cms-content — the services, hours, gallery captions and other copy as edited in the editor.
• apex-inline-edits — text and media changes made with the on-page editing toolbar.
• apex-edbar-pos — where you dragged that toolbar, so it reopens in the same place.
• apex-admin-session — marks the tab as being in editing mode.

Everything above is stored on your device, never transmitted to any server, and never read by any third party. Only your cookie-banner answer uses local storage, which persists until you clear your browser's site data. Everything else uses session storage and is gone when the tab closes.

This means any change you make in the demonstration editor is yours alone, lives only in that tab, and cannot alter what anyone else sees.

None of these contain personal information. The four editor items hold website copy; the consent item holds a single yes-or-no answer.

2. What is not stored

• No analytics or measurement cookies
• No advertising, remarketing or conversion-tracking cookies
• No personalization or preference profiling
• No authentication cookies, because there is no authentication. The apex-admin-session marker described above is not a credential, is not checked against anything, and grants no access to any server
• No accounts, and no personal information of any kind
• No third-party cookies of any kind, because no third-party resource is loaded anywhere on this site

3. Why you are asked at all

Strictly, a single functional preference of this kind would not require consent under most cookie rules. The banner is included because this build demonstrates the pattern, and because declining is honored exactly as accepting is: neither choice changes what the site stores beyond the preference itself, and neither unlocks any tracking, because there is none to unlock.

4. Manage your preference

Your current choice: No choice recorded yet.

Clear my choice and ask again

If this button reports nothing, your browser may be blocking site data — in which case nothing was stored in the first place.

5. Browser controls

Every major browser lets you view and delete local storage and cookies per site, usually under privacy or site-settings. Clearing site data for this domain removes the preference above.

6. If this design goes live

A real deployment that adds analytics, advertising pixels, embedded maps or a chat widget would need this page rewritten to list each one, and would need consent obtained before those technologies load rather than after. See the Privacy Policy.