1. What these technologies are
"Cookies" are small files stored by your browser. "Local storage" is a related browser mechanism for storing small amounts of data on your device. We use both for the limited purposes below. We do not use third-party advertising or cross-site tracking technologies at launch.
2. What we use, why, and for how long
| Name | Type | Purpose | Category | Duration |
|---|---|---|---|---|
NEXT_LOCALE | Cookie | Remembers your chosen language so the site displays in your locale | Functional | ~12 months |
cl_age_18 | Cookie (signed token) | Records that you affirmed you are 18+ so we don't show the age gate on every visit; lets you skip re-confirmation. Contains a signed, tamper-evident token (not your identity) | Strictly necessary (for lawful operation of an 18+ service) | 90 days by default; 12 months if you choose "remember for a year" |
| Authentication tokens | localStorage (not a cookie) | Keeps you signed in and authorizes requests to our API | Strictly necessary | Until you sign out, the session expires, or you clear browser storage |
| {{OPTIONAL: web-push subscription state (FCM)}} | localStorage / browser push registration | If you opt in to web push notifications | Functional (opt-in) | Until you disable notifications |
We may also use transient, strictly-necessary technologies required for security (e.g., abuse prevention) and for the basic functioning of pages.
3. Why some of these cannot be switched off
The age-affirmation token and authentication storage are strictly necessary: without them we cannot lawfully gate adult content or keep you securely signed in. They are not used for advertising or profiling.
4. How to control cookies and local storage
- You can clear or block cookies and local storage in your browser settings. Note that clearing the age-affirmation token will cause the age gate to appear again, and clearing authentication storage will sign you out.
- You can decline or revoke web-push notifications in your browser at any time.
- If we introduce any non-essential cookies or analytics in the future, we will present a consent mechanism where required and update this Policy first.
5. Changes and contact
We will update this Policy if our use of these technologies changes. Questions: privacy@charmloop.ai.