We use one cookie.

The card above is the whole list. PHPSESSID is a standard PHP session cookie — the same kind of cookie that countless sites have used to keep people signed in since the 1990s.

It contains a random session identifier and nothing else. The identifier is meaningless on its own; the actual session data — which account you're logged into, when the session started — lives on our server, keyed by that identifier. The cookie never travels off lifelayers.net, never goes to anyone else, and isn't readable by JavaScript on the page (the HttpOnly flag enforces that).

Under EU ePrivacy and UK PECR, session cookies that exist solely to make a service work fall into the "strictly necessary" category, which doesn't require consent. That's why you don't see a banner asking your permission — we'd only be asking permission for something the rules already say is fine to set.

This is the longer list. Categories you'll find on most other social-network cookies policies that you won't find here:

We also don't use localStorage, sessionStorage, or IndexedDB to store anything beyond what's needed for the in-page experience to work (UI preferences like dark-mode choice, draft text in editors, that kind of thing — same-origin only, never sent anywhere).

You can browse lifelayers.net with cookies completely disabled. The map, public layers, and read-only browsing all work without a session.

What you lose by blocking cookies:

• You can't sign in — the session cookie is what keeps you signed in across page loads.
• Anything that requires being signed in — posting, messaging, friends, the feed — won't work.

You can block cookies for a specific site or globally in any modern browser. Browser-vendor documentation is the most reliable reference:

• Chrome
• Firefox
• Safari
• Edge

The Android and iOS apps don't use HTTP cookies in the browser sense. They keep you signed in with a secure authentication token stored in the platform's secure storage — Keychain on iOS, EncryptedSharedPreferences on Android. The token is sent to our server on each API call to identify the session.

Same principle as the web: minimal, first-party, only used to keep you signed in. No third-party SDKs phone home from the app for advertising or analytics purposes.

If we ever start using additional cookies — we don't intend to, but if anything changes — this page will be updated first, before the new cookie is set. Material changes will be announced in the app or by email. The "Last updated" date at the top of the page is the source of truth for when it last changed.

Questions about this policy go to [email protected]. For everything else, the contact page lists every other channel.

Operator: SynaVora FZ-LLC, Dubai, United Arab Emirates.