The full inventory of cookies and localStorage entries used by the CascadeLights relay, plus the browser-side controls for managing them. The relay uses two entries; both are listed below in plain English with a retention window and a purpose.
This page lists every cookie and every localStorage entry that CascadeLights uses, along with what the entry is for, when it expires, and how to clear it. The relay is small; the inventory is small. We have not tried to pad this page; the goal is to be readable in two minutes.
The relay uses only one category of cookie: strictly necessary. The two entries are required for the age gate and the cookie-consent banner to work consistently across page navigations. The relay does not set analytics cookies, advertising cookies, or any third-party cookies of any kind.
| NAME | CATEGORY | PURPOSE | EXPIRY |
|---|---|---|---|
| cascadelights_age_ok | Strictly necessary | Records that the visitor confirmed they are 18 or older. Avoids re-prompting on every page navigation. | 180 days |
| cascadelights_ck_choice | Strictly necessary | Records the visitor's choice on the cookie banner (accept or decline). Avoids re-prompting on every page. | 180 days |
That is the entire inventory. There are no analytics cookies, no advertising cookies, and no third-party cookies on the relay. The two entries above are also written to localStorage as a parallel mirror so that previewing the relay via file:// still respects your earlier choice across pages.
The two entries above are written twice: once as a browser cookie and once as a localStorage key. This pattern matters when the relay is opened from a local file (a download, a USB stick, a preview environment) where browsers treat each file:// URL as a separate origin and refuse to share cookies between pages. The localStorage mirror is the survivor in that case. On a real domain (HTTPS), the cookie does the work and the localStorage entry sits as a backup.
If you would like to change your cookie choice after the banner has been dismissed, clear the two entries from the browser's storage settings. The next visit will re-prompt the banner with both options visible. We do not provide a floating “reopen” pill on the page itself because the relay is small and the banner is the right size only on first contact.
Each browser provides its own controls for managing cookies and localStorage:
Each browser also has a global “clear browsing data” control that wipes everything in one tap. That option works as well; it just clears more than the relay's entries.
Third-party cookies are off by default. The relay does not load any third-party tag manager, advertising pixel, or behavioural-tracking SDK. Google Fonts (used for the type families) does not set a cookie of its own; it is served as a content delivery request. The relay deliberately stays inside this small footprint and we have no plans to expand it.
To withdraw consent at any time, clear the two entries listed in section 2 from the browser's storage settings. The relay will then re-prompt the banner on your next visit and the new choice will be respected for 180 days. There is no “reach the studio to opt out” step; consent is entirely controlled in your browser.
If the cookie inventory changes in any way (a new strictly-necessary entry, a removed entry, a different retention window), we will update the “last updated” line at the bottom of this page and re-prompt the cookie banner so you can review the new inventory before it applies to your visit.
For any cookie question, write to [email protected]. The inbox is read by Ana from the studio.
Last updated: 2026-05-05.