Cookie and Storage Disclosure

Version 1.0.0. Effective August 4, 2026.

This is the full inventory referred to in section 10 of our Privacy Policy. It lists every cookie clearlabel receives and everything the app stores in your browser.

1. The short version

We set no cookies of our own and we use no advertising cookies. The only cookies involved come from the two services that sign you in and take payment. Most of what we store lives in your browser's local storage rather than in cookies, it stays on your device, and clearing site data in your browser removes all of it.

2. Cookies

clearlabel does not set any first-party cookies. These are set by third-party software we use:

__session, __client_uat (Clerk): Keeps you signed in. Without these you would be signed out on every page load, so they are strictly necessary and there is no version of the account experience that works without them
__stripe_mid, __stripe_sid (Stripe): Payment fraud prevention. Set only on the checkout page, when Stripe.js loads there. No other page loads Stripe, so if you never open checkout these are never set

3. Browser storage

Local storage persists until you clear it. Session storage is emptied when you close the tab, and is marked below where it applies. None of this is sent to advertisers, and none of it is readable by other websites.

Your settings and preferences. Choices you have made about how the app looks and behaves. They stay until you clear them.

claire-theme (light or dark)
cl-advanced-mode (whether advanced surfaces are unlocked)
cl-dashboard-order (the order of your home modules)
claire-text-scale, claire-rail, claire-dock-layout, claire-depth (Claire layout and reading size)
claire-voice, claire-volume, claire-rate, claire-endpoint-ms (spoken reply settings)
cl-smart-parsing (your opt-out of assisted log parsing)
location_consent (whether you allowed coarse location)
claire-log-consent (your Claire logging choice)

Things you have dismissed or finished. So the app does not ask you the same thing twice.

cl-onboarding-banner-dismissed
cl-notification-ask-dismissed
gdpr_consent_hidden
cl-notif-ledger (which notifications you have already seen)
clarity-progress-v1 (lessons you have completed)

Health-related storage. This is the group worth reading closely. These keys hold, or imply, information about your body. They are stored on your device and are cleared when you clear site data.

ob-setup-draft-v3 (session only) holds your half-finished onboarding: dietary restrictions and sensitivity levels, so closing the tab mid-setup does not lose them
dismissed_pattern_... names an ingredient and a symptom, because the key records which pattern card you dismissed. The key itself therefore implies a suspected trigger
cl-locked-ask (session only) holds a question you typed to Claire before hitting a paywall, so it survives the upgrade round trip
claire-pantry-v1, claire-events-v1, claire-places-v1, claire-profile-v2 hold recent items, activity and profile Claire keeps on-device
claire-activity-region-v1 holds a coarse region, not a precise location

Making the app work. Short-lived plumbing with no meaning outside the app.

cl-was-signed-in (avoids a flash of the signed-out splash)
cl-active-profile (which family profile you are viewing)
cl-product-recents:... (your recent product picks, per profile)
cl-ref-code (a referral code from a share link, cleared once used)
cl_map_focus_v1:... (a cached map centre so the community map does not re-geocode)
cl:profileChangedAt (a timestamp that tells other parts of the page to refresh)
cl-ask-consumed (session only, stops a question re-firing on reload)
claire-feedback-v1 (feedback you gave on Claire replies)

4. What we do not use

No advertising or marketing cookies.
No cross-site tracking, and no third-party ad networks.
No session recording or screen replay.
No product analytics today. Our analytics tooling is present in the code but has no key configured, so it sends nothing. If that changes, this page changes with it, and the tooling is built so that it cannot receive free text or the contents of a page address.

5. How to clear it

Clearing cookies and site data for this site in your browser settings removes everything on this page. Signing out clears the sign-in cookies. Deleting your account from Settings removes what we hold on our servers, which is a separate thing from the on-device storage listed here; section 6 of the Privacy Policy covers that.

Blocking storage entirely will sign you out and reset your preferences on every visit, but the app will still work.

6. Contact

privacy@clearlabel.ai

Framework Films, LLC, doing business as clearlabel