Cookies
Last updated: November 2026
lyfeIO uses a small set of first-party cookies to keep you signed in and protect your account, and two first-party identifiers to count visits and sign-ups. Nothing on this site or in the app comes from an advertising or analytics company. Questions: privacy@lyfeio.com.
Cookies we set
Session app_session
- Purpose: keeps you signed in after you log in.
- Duration: 14 days.
- Attributes: HttpOnly; SameSite=Lax; Secure (sent only over HTTPS); path
/.
CSRF app_csrf
- Purpose: lets the web app send a matching token with state-changing requests so other sites cannot submit forms on your behalf.
- Duration: 14 days (refreshed with your session).
- Attributes: readable by JavaScript (not HttpOnly); SameSite=Lax; Secure (sent only over HTTPS); path
/.
Google sign-up lyfe_google_signup
- Purpose: remembers your in-progress Google sign-up between the OAuth redirect and completing registration.
- Duration: 30 minutes.
- When: set only during the Google sign-up flow, not on every visit.
- Attributes: HttpOnly; SameSite=Lax; Secure (sent only over HTTPS); path
/.
These three are strictly necessary: the app does not work without them.
Measurement identifiers (first-party only)
We measure our own marketing and product ourselves. No data goes to any other company.
Campaign lyfeio_attr (cookie)
- Purpose: when you arrive from an ad or a link with campaign tags, or from another website, remembers the campaign tags, the referring site's host name and the page you landed on, so we can tell which channel brought a sign-up. Copied to your account when you sign up.
- When: set only if there is something to remember (campaign tags or an outside referrer); a direct visit sets nothing.
- Duration: 30 days.
- Attributes: readable by JavaScript; SameSite=Lax; Secure on HTTPS; path
/.
Browser identifier lyfeio_anon (localStorage, not a cookie)
- Purpose: a random identifier so we can count visits and sign-ups from the same browser once, and see the path from first visit to first atom.
- Duration: until you clear your browser's site data.
- Contains: a random string. Never your email, name or content.
Tab identifier lyfeio_sess (sessionStorage) and lyfe_funnel_pv_home (sessionStorage)
- Purpose: group the events of one browser tab, and count the home page visit once per tab.
- Duration: until you close the tab.
What is recorded with these identifiers: the event name (for example page view, sign-up started, first atom), the page path, the campaign tags, your plan tier, and counts. The events are sent only to our own server.
To stop this measurement, clear this site's data in your browser, or use a private window. We have no third-party switch because there is no third party.
On-device storage (not cookies)
Some layout and UI preferences are stored only in your browser, on your device; they are not sent to our servers.
- localStorage: chat panel layout (
lyfeio.agentPanel) and Atoms view preference (lyfe.atomsv2.view). - sessionStorage: whether you dismissed the login prompt above the chat button (
lyfeio.fabLoginPrompt.dismissed); counts for review rows you closed in the brain menu (keys starting withlyfe.comms.acked.);lyfeio_signup_checkout, which remembers your chosen plan between sign-up and returning from Stripe checkout and is then cleared;lyfeio_signup_marketing, which carries your product-email choice through a Google sign-up.
IP address and country
On every request we read your IP address once to work out your country, so we can show prices in your currency and apply regional behaviour. We use the free IP geolocation by DB-IP (IP to Country Lite database, licensed under CC BY 4.0), which runs on our own server; your address is not sent anywhere and is not stored for this purpose. Sign-in sessions store a hashed form of the IP address for security.
What we do not use
The app's content security policy allows network connections only to lyfeIO and our API origin. We do not load third-party analytics or ad scripts, such as Meta Pixel or Google Ads tags, on this site or in the app, and we do not set third-party cookies. Fonts are bundled with the site at build time (no runtime request to Google Fonts). Payments happen on Stripe's own pages, which set Stripe's cookies there under Stripe's policy.