Cookies & device storage

What this application stores

Supabase authentication uses first-party sb-…-auth-token cookies, which may be split into numbered chunks, and a temporary code-verifier during a requested sign-in flow. They maintain your session and secure authentication. They expire or refresh under the provider’s session settings; signing out clears the app session. Blocking them prevents signed-in features.

When you write a private chat, padvorn-unsent-<account>-<conversation> local storage preserves the draft you requested. It is cleared after sending, explicit removal, sign-out or account change, or when you clear site data. It is readable by anyone using the same unlocked browser profile, so use a private device. This is device storage even though it is not a cookie.

The app does not install analytics, marketing cookies, advertising pixels or third-party embeds. Fonts are served locally. We do not show a misleading consent banner for essential-only storage. Hosting/security providers may still process technical network data as described in Privacy; this is not a claim of zero data collection.

Control and future changes

Use your browser’s site-data controls to clear cookies and local storage. This signs you out and removes device drafts; it does not erase your server account or sent messages. Use Settings or a Privacy request for server data.

Optional analytics or marketing must stay off unless a suitable consent mechanism is added, with a genuine refusal option and withdrawal as easy as acceptance. This policy must be updated before adding optional tracking.