Privacy Policy

How Sachess handles local analysis, multiplayer room data, cloud-book requests, and optional analytics.

Sachess requires no account and is designed to minimize data collection. This policy distinguishes features that stay in your browser from multiplayer, cloud-book, hosting, and optional analytics data that must be processed remotely.

Author: Sachess Editorial Team · Updated: 2026-06-25 · 0 Sources

Highlights

  • No account, email, password, or payment information is required.
  • Google Analytics is not loaded until you explicitly allow analytics, and you can change that choice later.
  • Local AI and photo recognition stay on your device; multiplayer and cloud-book features transmit only the data needed to provide them.

Steps

01

Local analysis and photo-to-FEN processing run in your browser.

02

Browser storage keeps preferences, saved game state, consent, room credentials, and cached public assets.

03

Multiplayer uses Cloudflare Workers and Durable Objects to operate rooms; cloud-book lookup sends the current FEN to ChessDB.

04

Optional GA4 loads only after consent and records normalized page usage without room codes or shared FEN data.

Details

Local Processing and Browser Storage

Pikafish AI analysis and photo-to-FEN recognition run locally in your browser. Sachess does not upload photos for recognition or require an account, email address, password, or payment information.

Sachess uses localStorage for settings such as theme, language, application preferences, saved game state, and analytics consent. Multiplayer credentials use sessionStorage. A service worker caches public application assets for performance and offline use.

  • Local analysis and photo recognition remain on the device.
  • Browser storage can be cleared through your browser settings.
  • Service-worker caches contain public site and engine assets, not account records.

Multiplayer Rooms and Cloud Book

When you create or join a multiplayer room, Cloudflare Workers and a room Durable Object process the room code, player credential, settings, FEN, move history, clocks, chat messages, draw or rematch state, and result until the room is cleaned up under the room-expiry rules. Anyone holding a valid room link or credential may be able to access that room, so do not place sensitive information in chat.

Cloudflare processes ordinary network information needed to deliver and protect the service. For room-creation abuse prevention, Sachess converts the connecting IP address to a one-way hash and temporarily stores creation timestamps, waiting-room reservations, cooldowns, and abuse blocks in a Durable Object. Frequent creators may be asked to complete Cloudflare Turnstile; the verification token is checked by the Worker and is not used as a player profile. If you open the cloud-book feature, the current FEN is sent to the ChessDB service to retrieve moves.

  • Multiplayer positions, moves, timers, and chat are server-processed temporarily.
  • Room credentials are stored in sessionStorage and should be treated as private links.
  • ChessDB receives a FEN only when you use cloud-book lookup.

Optional Google Analytics

Google Analytics 4 is optional. Sachess does not request the Google Analytics script or send analytics events until you select Allow analytics. If allowed, GA4 may process the normalized page path, page title, referrer, browser or device information, and approximate geography. Room codes and shared FEN query data are excluded from page paths.

Analytics storage is granted only after consent. Advertising storage, Google Signals, and ad-personalization signals remain disabled. Google states that GA4 does not log or store individual IP addresses. You can reopen Privacy settings to revoke consent; Sachess then disables analytics and removes accessible first-party GA cookies.

  • No analytics request before explicit consent.
  • One manual page view per normalized application route.
  • Consent is stored locally and can be changed at any time.

Service Providers and Your Choices

Cloudflare hosts and protects Sachess. Google provides analytics only after consent. ChessDB provides cloud-book results only when requested. These providers process data under their own terms and privacy policies.

You may use the core local-analysis features without analytics, clear site data in your browser, avoid multiplayer chat, and choose not to use cloud-book lookup. Declining analytics does not disable Sachess features.

  • Sachess does not sell personal information.
  • Analytics refusal does not reduce site functionality.
  • Clearing browser site data removes local preferences, consent, cached assets, and saved session credentials.

FAQ

Does Sachess require registration?

No. Sachess does not require an account, email address, password, or payment information.

Is game data uploaded?

Local AI analysis and photo recognition stay on your device. Multiplayer room state is temporarily processed by Cloudflare, and cloud-book lookup sends the current FEN to ChessDB when you request it.

Does Sachess use cookies?

Sachess uses browser storage for preferences and sessions. GA4 may set first-party analytics cookies only after you explicitly allow analytics.

Can I change my analytics choice?

Yes. Open Privacy settings at the bottom of the page. Revoking consent disables GA and removes accessible first-party GA cookies.

Which third parties process data?

Cloudflare provides hosting and multiplayer infrastructure, Google provides optional analytics after consent, and ChessDB receives FEN positions only for requested cloud-book lookups.

Sources

Related Pages