Cookies & browser storage

Authentication and access

Clerk uses cookies to maintain and check a signed-in session. These can include __client, __session, __client_uat and temporary handshake cookies; names and lifetimes vary with the configured environment. Blocking these can prevent sign-in. See Clerk’s cookie documentation.

A studio administrator’s read-only role preview uses the signed aiko_role_preview cookie. It expires after 30 minutes or when the preview is exited.

Drafts and preferences

The workspace uses local browser storage for drafts, selected references, briefs, preferences and the last selected project. These entries may persist until replaced or cleared. Tab-session storage can preserve pending-request receipts and export request identifiers. Browser drafts are distinct from setups or plans explicitly saved to the project.

On a shared device, sign out and clear this site’s cookies and storage before another person uses it. Clearing storage may erase unsaved drafts and require signing in again.

Optional tracking

AIKO has no advertising, session-replay or audience-analytics service installed, and no third-party video embeds. The showcase media and Inter font files are served by this site. Authentication and hosting services still receive operational requests. Clerk also documents optional SDK-usage telemetry for development environments in its telemetry notice; that is separate from recording staff sessions.

Questions

Read the privacy notice for production data and retention information, or follow the contact instructions to report an unexpected tracking request.