Cookies & Browser Storage

Version 2026-09-17-beta-1 · Effective 2026-09-17

Support and privacy: support@agendity.com

September 19 update: optional public-page analytics is available only with your permission. The analytics notice and privacy choices update the earlier analytics inventory below.

This page describes the new character-platform foundation, not unrelated applications or a customer’s website. Browser storage keeps sign-in and draft recovery working. It does not replace saved records in the database.

Necessary cookies

• Sign-in cookies use the agendity-studio prefix. They authenticate sessions and support the sign-in flow. Sessions are configured for a rolling 14 days; temporary authentication cookies may expire sooner. Actual expiration is set in each cookie.
• Cookies named agendity-brief followed by an identifier bind a saved pre-login brief to the browser that submitted it. They expire after 24 hours. They contain a random access proof, not the prompt text.
• Authentication state and verification protections can use additional short-lived cookies managed by the authentication library. They protect a sign-in you initiate; they are not advertising identifiers.

These cookies are set as HttpOnly where used for authentication or brief access, SameSite=Lax, and Secure on HTTPS deployments. Local development uses HTTP and cannot claim HTTPS cookie security. Do not share browser profiles or sign-in links with untrusted people.

Draft recovery and preferences

Session storage under Agendity-prefixed keys can hold unsent prompt text, a pending save request and its identifiers. It helps recover from a network error or page reload. It can disappear when the tab/session is closed and is not a cross-device backup. Successfully saved work is stored in the database. A browser may restore session data according to its settings.

Interface preferences are saved with your account. Browser and operating-system reduced-motion settings also influence animation. Browser storage created by the separate development Lab or by a customer website is not described by this foundation’s inventory.

Optional tracking

This foundation does not load advertising pixels, session-replay analytics or non-essential analytics cookies. There is no “accept all” banner because no optional tracking category is enabled here. This does not waive any legal requirements: an updated inventory and applicable opt-in controls must precede adding optional tracking. Refusing optional tracking must be as easy as accepting it, with a later way to change the choice.

Your controls

Use your browser settings to inspect, block or remove cookies and session storage. Removing necessary cookies can sign you out or prevent automatic recovery of a pre-login brief. Removing local drafts does not erase already-saved server records. Logging out ends the current authenticated session; it is not account deletion. See the Privacy Policy for retention and request handling.

Google’s sign-in page and any future payment or customer-hosted page have their own cookie practices. The production inventory, precise library cookie names, retention and regional consent requirements must be checked again before launch.