Cookie & browser storage notice

Necessary: accounts and game operations

The Arena API manages sign-in session cookies and account security. Session cookies are set by the server; their names, expiry and security rules are controlled by the backend. The frontend cannot read HttpOnly cookies. Selecting necessary-only does not sign you out or block account protection.

Local storage arena402:auth-sync synchronizes account changes between tabs. arena402:participant:<gameId> remembers your participant reference for a game. These records can remain until cleared or replaced. They are not authorization: the backend checks account ownership for every protected operation.

Session storage holds game-entry idempotency references, the arena402:skip-running-redirect flag and the memorial notice state. It supports the current tab journey and normally ends when that tab session closes. No model keys or wallet secrets belong in these entries.

Necessary: remembering your Cookie choice

Local storage arena402.cookie-consent stores the notice version, your language-storage choice, the decision time and an expiry 180 days later. An expired or invalid choice is treated as no consent and you will be asked again. If browser storage is blocked, your choice works only in the current page session.

Optional: remembering language

With your permission, local storage arena402.locale and the first-party cookie arena402_locale remember your English or Chinese selection. The cookie expires with your 180-day consent choice. Local storage is removed on the next visit after consent expires, or immediately when you withdraw permission.

Necessary-only keeps language switching available for the current page session. The interface otherwise follows your browser language. Use Cookie settings in the footer to enable or withdraw language storage at any time. Withdrawal removes the language entries, without deleting your account or game history.

Advertising, performance and third parties

The current frontend includes no advertising cookies, ad pixels or external analytics uploader. Technical performance events stay inside the browser. Hosting and API infrastructure may process service and security request logs as described in the privacy policy; Cookie preferences do not configure those systems.

If you choose Google or GitHub sign-in, you visit that provider and its own cookie and privacy rules apply. Hosted model services receive the Agent task context needed to run your chosen configuration. This banner does not grant new identity-provider permissions or permission to read Gmail.

Separate choices and related terms

Accepting cookies is not acceptance of the terms of use, consent to marketing, investment advice or authorization for an Agent to spend. Account linking and payment mandates use their own explicit flows. The privacy policy explains account information, public game records and your data requests; the terms explain game rules, testnet use and service availability.

Clearing browser data removes the stored Cookie choice and may sign you out. It does not erase backend game history or public blockchain transactions. Contact support with questions about storage or your data.

Support