Cookies and device storage — draft

1. Storage for requested features

The login cookie is __Host-frameparty_session on the secure deployment, or frameparty_session in the local configuration. Remembered login lasts up to 30 days; otherwise the browser cookie is session-based and the server credential lasts up to 12 hours. kacha_room remembers the current room for 30 days. frameparty_locale remembers an explicitly chosen language for 365 days. The cookie-preference record lasts 180 days. These records are used for the stated function, not as advertising permission.

2. Optional usage statistics

Usage measurement is disabled until you explicitly allow it. If allowed, the site records daily counts for fixed page categories and feature use, with account-based daily unique counts for signed-in users. It does not add a separate advertising identifier, but the account-linked counts are personal information. Daily records are normally trimmed to about 40 days when measurement runs.

You can refuse or withdraw permission in the cookie controls without losing basic account and room access. Global Privacy Control and Do Not Track signals keep optional measurement off, including when they conflict with an earlier choice. Security and operational records needed to protect the service are handled separately.

3. Local and session storage

Room dice and mini-game keys, kacha:v1:room:{id}:dice and :mini, save settings and game state; entries older than 30 days are rejected and removed when read. kacha-challenge keys store plans and pending offline actions, including room, account and participant references. They have no general automatic expiry; some confirmed deletion markers are pruned after 60 days using trusted server time.

frameparty-guide sessionStorage keys remember the current onboarding session. These device records are not all cookies and may survive until the browser clears them or the relevant feature removes them. Clearing pending challenge data can lose unsynchronised work. A future App permission must be requested separately; a website cookie choice does not authorise camera, microphone or location access.

4. Changing your choice

Use the page controls to save, refuse or withdraw optional measurement. Your preference applies to this browser; another browser or cleared storage may require a new choice. Withdrawal stops future optional recording and does not by itself delete previously recorded information. Browser settings can also remove or block storage, but blocking login or room storage may affect those requested functions.

Any new optional purpose or provider needs updated information and any fresh permission required by applicable law. This draft does not treat continued browsing, accepting service terms or closing a banner as permission for optional measurement. See the privacy notice for recipients, retention and account-rights limits.