Cookie & Local Storage Notice
Last updated: 30 July 2026 · Draft for legal review · Storage verified against the live site on 2026-07-30
sessiontwin.ai (landing page and app page, signed-out) on
30 July 2026, not just against the source code. Items that only appear once a user
signs in could not be enumerated without an account and are marked accordingly.
Summary
sessiontwin's own code sets no cookies and no browser storage.
On the live site we found no cookies at all and a single
localStorage item set by the hosting platform's analytics, plus a
monitoring beacon sent by the site's CDN (Cloudflare). There is no advertising or
cross-site tracking.
What is stored in your browser
| Name | Type | Set by | Purpose | Lifetime |
|---|---|---|---|---|
base44_analytics_session_id |
localStorage | Base44 (hosting platform) | A random session identifier used by Base44's platform analytics. | Persistent until you clear site data (no expiry on localStorage). |
| Base44 session / auth token | Set by the Base44 SDK on sign-in (cookie and/or storage) — not observed signed-out; to confirm signed-in | Base44 | Keeps you signed in so your missions are attached to you. | Duration of the session / per Base44 (to confirm). |
Network telemetry (not stored, but a data transfer)
| Request | To | Purpose |
|---|---|---|
POST /cdn-cgi/rum | Cloudflare (the site's CDN/edge) | Cloudflare Real User Monitoring — page-performance telemetry. Sent from the site's own domain. |
import @base44/sdk | esm.sh (CDN) | Loads the Base44 SDK in the browser; the request itself reveals your IP and user-agent to esm.sh. |
Do we need a consent banner?
None of the items above is an advertising or cross-site tracking cookie. Whether the Base44 analytics identifier and Cloudflare RUM require prior consent under the EU ePrivacy rules / Israeli law (they are arguably "analytics", which several regulators treat as requiring consent unless strictly necessary) is an open question for counsel. If consent is required, a banner offering a genuine reject option must be added before these are set.
Open questions for counsel
- Do the Base44 analytics identifier and Cloudflare RUM require prior consent (ePrivacy / Israeli law)? If so, implement a compliant consent mechanism.
- Enumerate the exact cookies/storage the Base44 SDK sets when a user is signed in (auth/session token: name, type, lifetime) and add them here.
- Confirm with Base44 what its platform analytics collects and its retention, and whether it can be disabled for our app.
- Confirm whether Cloudflare RUM can be disabled or is required, and add Cloudflare to the recipients/sub-processor list.