See what this browser remembers.

Current browser storage

The site uses three disclosed local-storage patterns: ae-motion after an explicit Full, Calm or Still selection; ae-city-inventory-{city} after a workstation inventory is completed; and ae-field-{city}-{date} after a dated workstation field is completed. These values remain in that browser until cleared. They are not cookies and are not sent to the site merely because they are stored.

The live chamber above looks only for names matching those allowlisted patterns. It does not read or display their values. Its Clear controls act in the current browser only. If storage is blocked, the chamber reports that state and leaves the operative text available.

Cookies visible to this page

The chamber can list cookie names made available to JavaScript on this origin. The browser provides the full JavaScript-visible cookie string; the inspection processes it only long enough to extract names, never renders or persists values and transmits nothing. It cannot see HttpOnly cookies, cookies on another domain or provider-side logs. A count of zero therefore means “none visible to this page”, not “no technology exists anywhere in the delivery chain”.

Analytics and campaign attribution

Cloudflare Web Analytics can load an aggregate measurement beacon only when the site is built with an analytics token. The Bidder can send bounded, allowlisted events through Cloudflare Zaraz only when that service is present: landing source, selected route opens, Reel play and quartile or completion milestones, sound-on, and contact-start or submit. The current public build does not present either optional route as active merely because support code exists.

Campaign labels are accepted only within short character and length limits. Form-field contents are excluded. If a technology requires consent in the actual configuration, a clear choice must be presented before it operates. A statutory exception is applied only when its exact conditions are met; calling a technology “analytics” does not create an exception by itself. Where a statistical or appearance exception is relied on, clear information and a simple, free objection remain necessary.

Provider, server and enquiry boundaries

Namecheap shared hosting currently receives ordinary request information needed to serve and protect the public site. The host may hold request/security records and the form’s pseudonymous temporary rate-limit file; those records are not browser storage. Optional Cloudflare analytics receives allowlisted events only if separately enabled.

Contact messages travel through same-origin PHP and the domain mail route and follow the enquiry-retention boundary in the Privacy notice. They are not written into browser local storage by the contact form.

External destinations

Source links open official or third-party sites. Those destinations set their own cookies, storage and terms. Direct links are preferred over silent embeds where the source can be inspected at its own canonical address.

Control and change

Browser settings can clear local storage and cookies. The chamber can remove the disclosed local keys on this origin, but it cannot clear provider records or storage belonging to another site. Any future advertising, cross-site profiling or new non-essential storage would require a fresh technical and legal assessment and an updated notice before use.