Cookie & Storage Policy
Last updated 4 June 2026
This page explains the small amounts of data Quack stores in your browser. Most of it is strictly necessary to run the product. We also use one privacy-friendly, EU-hosted analytics tool, and only after you opt in. We never use advertising cookies or third-party ad trackers.
What we store, and why
- Sign-in session (Firebase Authentication) - kept in your browser so you stay signed in. Stored in IndexedDB.
- “lyva.play.session” - the session id, PIN, and nickname for the session you joined, so you can return to it.
- “quack.host.activeGame.…” - the live session a host is running, so a page refresh doesn’t strand your players (cleared when you close the tab).
- “quack.shared.seenAt” - when you last looked at decks shared with you, to show an unread badge.
- “quack.consent.v1” - your choice on this notice, so we don’t ask again.
- “quack.lang” - your chosen language, so the app stays in it.
All of the above are essential to provide features you asked for, so they don’t require consent - but we’re telling you about them anyway.
Analytics is optional
For analytics we use PostHog, hosted in the EU. It is off by default and loads only after you accept analytics in the consent banner. Decline, and nothing analytics-related is stored. It helps us see which features land so we can improve Quack; we don’t use it for advertising. You can change your choice any time: clear your browser storage to be asked again.
More information
For the full picture of how we handle personal data, see our Privacy Policy.