Cookie policy

1. Necessary storage and essential tokens

The app stores learning progress in IndexedDB, settings and session information in browser storage, and app files in a service-worker cache. Local exercises remain usable offline after the download finishes. Guest and account profiles are separated on the same device. There are 0 marketing cookies, 0 tracking cookies, and 0 third-party advertising cookies.

• Sign-in tokens and session: sb-*-auth-token (Supabase authentication token) and ww_session (up to 30 days); ww_admin (up to 2 hours for a verified admin session). All security-critical cookies are protected against unauthorized access and sent only over HTTPS.
• Browser storage: ww_theme (appearance mode), ww_ui (interface language), ww_last_read_update (read release notes marker), ww_guest and session data such as ww_hero_rotation.
• Audio and learning copies: on this device without a general automatic expiry; audio is not embedded in the normal JSON backup.

2. Optional diagnostics

ww-telemetry-consent stores your choice. If you consent, the server may set ww_analytics: a random identifier for up to 30 days, limited to the diagnostics path. The interface does not send diagnostics events without consent. The privacy page explains the details and possible recipients.

3. Managing and removing data

You can remove site data through your browser. Back up learning progress and personal audio first. Removing browser data does not automatically delete your Supabase account, cloud snapshot, or previously transmitted diagnostics data. Self-service account deletion is not implemented; deletion requests can be sent by email to [email protected]. A dedicated control to withdraw diagnostics consent later is not available in settings.