Cookie & Storage Policy

Last updated: September 14, 2026 · LifeOS v1.0.0

Overview

This policy describes how LifeOS uses cookies and browser storage technologies today. It is intended to match the actual product behavior on lifeos.vision. This page does not claim legal compliance in any specific jurisdiction; operators and users should consult applicable local requirements.

What LifeOS Does Not Use

LifeOS currently does not use:

Advertising cookies or cross-site advertising trackers
Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, Microsoft Clarity, PostHog, Mixpanel, Amplitude, or similar analytics/marketing pixels
Browser fingerprinting for advertising or profiling
Third-party analytics JavaScript loaded on ordinary pages

If non-essential analytics or similar technologies are introduced in the future, LifeOS will update this policy and obtain consent where required before enabling them.

Essential Cookies

`lifeos_session` (strictly necessary)

LifeOS sets one first-party session cookie named lifeos_session to keep you signed in and to protect forms with CSRF tokens bound to your session.

Purpose: Authentication, session management, and security (CSRF protection).
Provider: LifeOS (first party).
Flags: HttpOnly, Secure on HTTPS deployments, SameSite=Lax.
Duration: According to your “Remember me” preference and LifeOS session lifetime policies (including absolute session expiry).
Consent: Required for the service to operate when you choose to stay signed in; not used for advertising.

LifeOS does not currently set separate non-essential preference or analytics cookies in the browser.

Browser Storage (First Party)

LifeOS also uses browser storage on your device for product functionality. These are not advertising trackers.

localStorage

Used to remember workspace and UI preferences between visits, for example:

Theme, language, accent color, and appearance settings
Notification, vibration, and do-not-disturb preferences
Volume levels and alert tone selections
Wallpaper path/blur/opacity cache keys
Onboarding completion flags (lifeos_onboarding_done)
Optional client-side error log entries you can view or clear in Settings (lifeos_error_log_v1, capped)

sessionStorage

Used for short-lived UI state within a browser tab, for example restoring planner section, scroll position, selected date, or open Settings panel after navigation or reload.

Cache Storage (Service Worker)

LifeOS registers a service worker for offline/PWA support. It caches static application assets (for example CSS, JavaScript bundles, icons) under a cache name such as lifeos-cache-v17. Protected user uploads and authenticated media are excluded from this cache.

Third-Party Payment Processing (Razorpay)

When you initiate a web payment on Plans or Support, LifeOS loads Razorpay checkout JavaScript from checkout.razorpay.com only at that moment (lazy loading). Razorpay may set its own cookies or use similar technologies to process your payment securely. LifeOS does not control Razorpay’s cookies. See Razorpay’s privacy policy for details. Payment scripts and cookies are used solely for checkout, not for LifeOS advertising.

Functional Media CDN (Mixkit)

LifeOS may fetch optional alarm/reminder sound files from assets.mixkit.co when you choose tones that use that library. This is functional media delivery, not advertising analytics.

Server-Side Operational Data

LifeOS servers may log operational and security information (for example request path, timestamp, IP address, and authenticated user ID where applicable) for reliability, abuse prevention, and support. These server logs are separate from browser cookies and are described further in the Privacy Policy.

Managing Cookies & Storage

You can sign out to end your session cookie, or clear site data in your browser settings.
Clearing browser storage may reset local preferences and onboarding flags.
Marketing email preferences are managed separately in Settings → Privacy and are not the same as cookie consent.

Changes

We may update this policy as LifeOS evolves. Material changes will be noted in Release Notes and by updating the effective date on this page.