Browser storage and measurement
Necessary website behavior and optional measurement should be easy to tell apart.
At a glance
This local design does not use cookies, persistent storage, analytics, fingerprinting or a third-party measurement service. Its example interactions live only in the current page session.
What this design does
The HTML, styles and scripts load from the local preview server. Forms do not transmit their values. Example account changes and support conversations live in memory and reset on refresh. The prototype does not store experimental assignments, send analytics events or link website activity to an installed app.
Before production
The deployed website needs an inventory of cookies and equivalent storage/access technologies, with provider, purpose, duration and control. Necessary delivery, authentication and anti-abuse records must be distinguished from optional acquisition measurement. First-party hosting is not automatically exempt from disclosure or consent requirements.
Optional measurement is a choice
Downloads, local writing, Contact and security reporting must remain usable with optional measurement declined, blocked or unavailable. Where optional measurement is introduced, choices should be clear, unselected by default and easy to revisit. A control that turns off nothing is not added to this design.
Experiments and interpretation
Assignment is different from actual exposure. The four acquisition pages represent distinct audiences, while the team-story comparison is a separate test. Missing measurement is not a failed conversion. No note text, file paths, private search terms or agent prompts belong in acquisition events.