Privacy Policy

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

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

Author: Sachess Editorial Team · Updated: 2026-07-28 · 0 Sources

Highlights

  • No account, email, password, or payment information is required.
  • 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, 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.

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, and saved game state. 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.

Service Providers and Your Choices

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

You may clear site data in your browser, avoid multiplayer chat, and choose not to use cloud-book lookup.

  • Sachess does not sell personal information.
  • Clearing browser site data removes local preferences, 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.

Which third parties process data?

Cloudflare provides hosting and multiplayer infrastructure, and ChessDB receives FEN positions only for requested cloud-book lookups.

Sources

Related Pages