Legal · version 1.0 · effective 20 July 2026
Cookies and Browser Storage Policy
Disciplio uses essential authentication storage and user-requested functional browser storage at launch, plus optional, consent-based PostHog product analytics and session-replay storage that stay off until you accept them. It has no advertising or marketing storage.
refresh-cookie
disciplio_refresh is a first-party, essential HttpOnly cookie. It stores a refresh-session token, is created on registration, login, or refresh, is unavailable to JavaScript, uses SameSite=Lax and Secure on HTTPS, has path /api/auth, and lasts up to 90 days. It is removed on logout and expires, is revoked, or is removed with account deletion. The cookie has no Domain attribute, so it is host-only for the API host.
local-storage
The app may use localStorage keys: disciplio-browser-storage-consent-v1 (essential record of your storage choice); disciplio-api-workspace-v1 (optional local workspace cache); disciplio-language-v1 (optional interface language); disciplio-welcome-draft-v1 (optional unfinished registration draft, seven days, never a password or legal-checkbox choice); disciplio-onboarding-guide-position-v1 and disciplio-onboarding-guide-collapsed-v1 (optional onboarding display preferences). These are first-party, JavaScript-accessible functional storage on app.disciplio.me, created when the relevant feature is used and removed when optional storage is rejected, cleared in the browser, or, for the draft, expires.
session-storage
The app may use sessionStorage keys: disciplio-goal-creation-drafts-v1 for temporary signed-in goal drafts (first-party, functional, JavaScript-accessible, deleted when the browser session ends, the draft is cleared, or optional storage is rejected) and disciplio-stale-chunk-reload-v1 for a one-time reload-recovery marker (essential technical storage, deleted after successful recovery or when the session ends).
control
You can accept or reject optional browser storage in the app and separately on the public landing page (disciplio.me), including PostHog analytics and session replay on either surface; each surface keeps its own consent choice. Rejecting on either surface removes its optional keys immediately, stops analytics capture and session recording, and clears PostHog's locally stored identifiers for that surface. Browser settings can also clear storage, which may remove preferences or sign you out. The public landing page does not set any non-essential cookies or browser storage beyond its own analytics-consent preference and, once accepted, PostHog's identifiers.
analytics
When you accept analytics on the app or the landing page, PostHog (an EU-hosted analytics processor) may set its own first-party localStorage/cookie identifiers (a device/distinct ID and a session ID), scoped to the shared disciplio.me domain, to support product analytics — page views and named events such as navigation clicks, language changes, and a successful contact-form submission — and consented session replay of navigation, clicks, and layout for usability review on either surface. We never send task, goal, or reflection text, AI prompts or output, contact-form name/email/message content, your name, or your email address to PostHog; session replay masks or fully blocks all such content and any input field, and the landing contact form is blocked entirely. Analytics and replay run only after you accept in the relevant banner — the app's storage-preferences banner or the landing page's analytics banner — and account holders with the Admin role are opted out of future capture and replay; historical admin activity is hidden by the PostHog exclusion filter rather than deleted. You can withdraw consent at any time from the relevant banner (reachable again from the app's account privacy settings or the landing page's footer/cookies page), which stops capture and recording immediately and clears PostHog's local identifiers for that surface. Data retention is configured in the PostHog project and is not set by application code.
not-used
Disciplio does not use IndexedDB, service workers, Workbox, Cache API application cache, advertising cookies, or marketing cookies. This release does not include Turnstile, CAPTCHA, or a Cloudflare challenge-cookie implementation in application code.
changes
If we introduce additional non-essential storage, we will update this policy and obtain any required consent before it is used.
contact
Questions about storage: privacy@disciplio.me. Effective date: 20 July 2026. Document version: 1.0. Reference language: English.