Potluck
Join

Potluck, Malta

Cookies & browser storage

Essential sign-in and requested storage, plus optional usage statistics controlled by your privacy preferences.

Updated 19 October 2026, Version 2026-10-19.4, Draft

Authentication cookies

Authentication uses first-party cookies named like sb-<project-ref>-auth-token, sometimes in numbered chunks, and temporary code-verifier cookies for authentication flows. These support requested sign-in and verification. They contain sensitive session information: never share them.

The current SSR library gives authentication cookies a maximum lifetime of up to 400 days, renewed or cleared by authentication flows; actual sessions can end earlier under authentication settings. Code verifiers are removed as their flow completes or expires. Check live session settings before publishing this draft. Blocking these cookies can sign you out or prevent account features working.

Browser storage

sessionStorage under exchange-draft:<review-id> keeps unsaved answers, summary, elapsed time, and revision in the review’s browser tab. Entries are removed on successful submission or when browser/tab storage is cleared; abandoned entries can remain until that tab’s session ends. Server drafts are separate.

The sample-notes feature uses localStorage under exchange-sample-notes when you choose to save on your device. Those notes remain until removed or browser storage is cleared; this does not submit them to members. Query caches use in-memory storage for the page session. With analytics consent and a configured EU PostHog project, sessionStorage named potluck_usage holds only a random tab identity until that browser session ends or analytics is disabled. The SDK can store an opt-out marker in localStorage to remember that it must not collect; that marker is not an account or analytics identity.

Your analytics choice

You can delete storage using browser settings. This removes that browser copy, not server accounts or submitted reviews. Use Settings → Privacy for account requests.

Malta’s rules can exempt storage strictly necessary for a requested service from cookie consent. PostHog analytics and experiment storage are optional and remain off until you opt in. Accept analytics and Reject analytics are available on the same layer. Ignoring the banner leaves analytics off; essential sign-in continues to work. Turning analytics off in Privacy preferences stops future tracking from that browser. We remove URL query strings and fragments, group app, review, message and member detail pages by screen, and exclude authentication and recovery URLs. We do not send account names, emails, app content, feedback or messages as event properties. Configured EU PostHog product analytics measures the fixed-label testing funnel and experiment variants after the same optional consent. Its sessionStorage supports consistent variants during a browser session; it does not identify your account. It does not automatically capture fields, clicks or recordings. Page views are recorded explicitly using the permitted screen labels and sanitized URLs. Vercel is used for hosting, not website analytics in this version. Any future non-essential tracking must be assessed and held back until valid consent where required, with accessible refusal and withdrawal controls. These Terms and this notice do not authorise future tracking.