This local-edition notice describes the implemented data flow as of 3 October 2026. Operator contact details, provider retention terms and account-deletion procedures require confirmation before public release.
Accounts and saved games
Signing in uses an authentication cookie. Account records include login identifiers and profile information. Saved or imported games and connected chess-account credentials are handled by the existing account and game services. The application uses Turso for database services and retains compatibility code for Supabase.
Chess Chat
When you send a question, the server receives its text, recent conversation context and the selected position snapshot. It sends those inputs and verified chess evidence to the same configured Volcano Engine Ark service used by Coach to generate an explanation. Do not send sensitive personal information. Provider retention terms and the final production configuration must be confirmed for the production configuration before this notice is finalised.
Chat recovery uses sessionStorage in your browser tab, separated by account. Clear conversation removes the current conversation there, and signing out through this site clears Chat recovery records. Closing a tab normally ends its session storage, although browser session restoration may restore it. A pending sign-in draft is kept briefly in the same storage and is not placed in a shared URL.
The Chat request receipt stores a hashed request identifier, user identifier, time and status, without question or reply text. Receipts are cleaned after seven days when subsequent requests run. Usage and task logs record model, token, timing and accounting information. Chat is configured not to deduct credits. The current code does not automatically expire every account, usage or Coach trace record.
Coach, diagnostics and service providers
Coach can store run inputs and results for diagnostics. Vercel hosting, database services, the configured AI provider, connected chess services and email delivery services process data needed for their respective features. Sentry error and performance diagnostics may run when configured; the client disables default personal-information collection, which does not mean all diagnostic data is anonymous.
Cookies, analytics and advertising
Authentication cookies are needed for sign-in. Local browser preferences support features such as theme and consent settings. The previous automatic Microsoft Clarity loader is disabled in this edition while a consent and disclosure configuration is prepared. No AdSense script or advertising cookie is activated by this change.
If advertising is enabled later, this notice must identify the actual vendors and explain their cookies, choices and applicable consent controls. A preference stored by this site is not a substitute for a Google-certified consent management platform where one is required.
Access, correction and deletion
Clear browser conversation recovery from Chat or by clearing this site’s browser storage. That does not erase server-side account, usage, game or diagnostic records. A verified contact route and a tested server-side deletion process must be established before the production notice can promise a deletion procedure. See Contact for the currently available channel.