Privacy Policy
Last updated: October 10, 2026
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
Chess IT Services GmbHHenry Rausch
Kritzmannstr. 12
39128 Magdeburg
Email: contact@chess-analytics.app
We have not appointed a data protection officer, as we are not legally required to do so.
2. Overview
Chess Analytics analyses chess games from chess.com and Lichess. We only process the personal data we need to run the service. We do not use analytics, tracking, advertising or third-party fonts, and we do not sell personal data. The only third-party script is Cloudflare's bot check on the registration and contact forms (see section 5). If you connect an AI assistant to your account, data is shared with it only on your instruction (see section 9).
3. Hosting and content delivery
Hosting (netcup)
The website and the application run on servers of netcup GmbH, Daimlerstraße 25, 76185 Karlsruhe, Germany, in data centres in Germany. netcup processes all data stored on and transmitted through these servers on our behalf. We have concluded a data processing agreement with netcup pursuant to Art. 28 GDPR.
Content delivery and security (Cloudflare)
All requests to our website and application pass through the network of Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). Cloudflare delivers the content, encrypts connections, and protects the service against attacks and abuse (e.g. denial-of-service attacks and bots). For this, Cloudflare processes connection data such as your IP address, the requested URL, date and time, browser type (user agent), and security-related information. Cloudflare may set technically necessary cookies to tell legitimate visitors from bots.
The legal basis is our legitimate interest in a secure and reliable service (Art. 6 (1) (f) GDPR); storing security cookies is strictly necessary for providing the service (§ 25 (2) No. 2 TDDDG). We have concluded a data processing agreement with Cloudflare. Data may be processed in the USA; Cloudflare is certified under the EU-U.S. Data Privacy Framework (Art. 45 GDPR) and has additionally agreed to the EU Standard Contractual Clauses.
Server logs
Our application does not log IP addresses. To protect accounts against password guessing, the IP address of failed sign-in attempts is kept in memory for up to 15 minutes and never written to disk (Art. 6 (1) (f) GDPR).
4. This website
The landing page sets no cookies. If you switch between the light and dark theme, your choice is saved in your browser's local storage (key theme) and is never sent to us (§ 25 (2) No. 2 TDDDG).
5. Your account
Registration and sign-in
To use the application you create an account with a username and password, or sign in with Lichess. We store your username, your password as a salted Argon2 hash (never in plain text), your plan (Free or Premium), and the date you registered. The legal basis is the performance of our contract with you (Art. 6 (1) (b) GDPR).
Bot protection on registration and the contact form (Cloudflare Turnstile)
To keep automated sign-ups and spam out, the registration form and the contact form load Cloudflare Turnstile from Cloudflare, Inc. (see section 3). It is only loaded when you open one of these forms. Turnstile checks in your browser whether you are a human, usually without you having to do anything, and processes your IP address and technical information about your browser and device for this. Turnstile does not set cookies for tracking and the data is not used for advertising. When you submit the form, we send the result token and your IP address to Cloudflare to verify it. The legal basis is our legitimate interest in protecting the service against abuse (Art. 6 (1) (f) GDPR); access to your device is strictly necessary for this security function (§ 25 (2) No. 2 TDDDG). Data may be processed in the USA; see section 3 for the safeguards.
Two-factor authentication and passkeys
If you turn on two-factor authentication, we store the secret for your authenticator app encrypted (AES-256-GCM), the last time step a code was used (so each code works only once), and hashed one-time recovery codes. If you add a passkey, your device creates a key pair; we store only the public key, a counter, the name you give it, and when it was created and last used — never your fingerprint, face or device PIN, which stay on your device. While you sign in or add a passkey, the server keeps the temporary sign-in challenge in memory for up to 5 minutes. The legal basis is the performance of our contract with you and the security of your account (Art. 6 (1) (b) and (f) GDPR).
Session cookie and local storage
When you sign in, we set a cookie named session that keeps you signed in for up to 30 days; we store only a hash of it. Signing in with Lichess briefly sets a cookie named lichess_oauth (10 minutes) to secure the sign-in flow, and if two-factor authentication is on, a cookie named pending_login (5 minutes) holds your sign-in until you enter the code. The application also saves display preferences (theme, sounds, filters, autoplay speed) in your browser's local storage; these are never sent to us. All of this is strictly necessary for the service you request (§ 25 (2) No. 2 TDDDG; Art. 6 (1) (b) GDPR).
6. chess.com and Lichess data
When you link a chess.com or Lichess username, we fetch your games from the public APIs of Chess.com, LLC and Lichess (lichess.org). These games are public on those sites and contain the usernames and ratings of you and your opponents, the moves, clock times, and the date. We store your linked usernames and the games you analyse; game lists are only kept in memory for a short time.
During onboarding and in Settings we also fetch your current ratings per time control from your public chess.com statistics and Lichess profile, including a FIDE rating you entered on chess.com, and store them with your coaching profile (section 8a).
If you connect your Lichess account, Lichess tells us your Lichess account ID and gives us an access token so we can download your games. We request no additional permissions. We store the token encrypted and only until you disconnect or delete your account, and then revoke it with Lichess.
Your games also contain your opponents' usernames and ratings. We process this public game data to analyse your games, based on our and your legitimate interest in game analysis (Art. 6 (1) (f) GDPR). For your own data, the legal basis is the performance of our contract with you (Art. 6 (1) (b) GDPR).
You can unlink chess.com or Lichess at any time in Settings.
7. Game analysis (Premium)
Games are analysed with the Stockfish chess engine on our own servers in Germany. Analysis results may be reused when another user analyses the same game.
Fair-play check. On request, we check how closely your opponent's moves in one of your analysed games matched the engine. If you choose to compare with their recent games, we fetch up to 20 of your opponent's recent public rated games (usernames, ratings, moves, clock times and dates) from the chess.com or Lichess public API and analyse them with Stockfish in the same way. These games are only used for your check: they are visible only to you, are not added to your game history, and are deleted when you remove the check or delete your account, unless another user has analysed the same game. The result is a statistical indication, not a finding that anyone cheated, and we do not share it with anyone. We process your opponent's public game data based on our and your legitimate interest in fair play (Art. 6 (1) (f) GDPR); only chess.com and Lichess can investigate a suspicion.
To set the reference values for this check ("typical play at a rating"), we analysed a sample of public rated games from the chess.com public API once and keep only aggregate statistics per rating band and time control, not the games or usernames (Art. 6 (1) (f) GDPR).
8. AI features
Our AI features (written game reports, move-by-move coaching, the review of your recent games, trend narratives, the Focus Report and its read-aloud audio, all Premium, and the level estimate during onboarding, for every user) use large language and speech models through OpenRouter, Inc., USA ("OpenRouter"), which forwards requests to the provider of the selected model. We use OpenRouter's EU in-region routing: requests are processed only by OpenRouter infrastructure and model providers within the European Union, and prompts and responses do not leave the EU.
For this we send facts about the game: the usernames and ratings of both players, the result, the opening, time control, selected moves, engine evaluations, and statistics. AI texts are also given your coaching profile (section 8a): your level, goal, preferred time control and wording. For the read-aloud audio we send the text of your Focus Report and the voice you chose. We never send your email address or your Chess Analytics account name. We only use zero data retention (ZDR) endpoints: neither OpenRouter nor the model providers store prompts or responses after processing a request, and they do not use them for training. We store the generated text with your analysis.
The legal basis is the performance of our contract with you (Art. 6 (1) (b) GDPR). Because OpenRouter is a US company, access to data from the USA cannot be ruled out entirely (e.g. for operations, support, or under US law); any such transfer is covered by the EU Standard Contractual Clauses (Art. 46 (2) (c) GDPR).
8a. Coaching profile and level estimate
When you first sign in, we ask a few optional questions: how strong you think you are, how many years you have played, an over-the-board (FIDE or national) rating, your main goal, the time control you care most about, and how simple the wording of your reports should be. To estimate your playing level, we send your answers and your current chess.com and Lichess ratings (section 6) to a model through OpenRouter as described above, without your username or account name. Without the model, the level is derived on our servers from your ratings or, if there are none, from your own assessment. You can skip the questions, change your level and wording in Settings at any time, or answer them again.
We store your answers, the estimated level, and the ratings used for it, and add your level, goal, time control and wording to the instructions for the AI texts we write for you. The legal basis is the performance of our contract with you (Art. 6 (1) (b) GDPR). The profile is deleted with your account.
9. Connecting AI assistants (MCP and OAuth)
You can connect an AI assistant such as ChatGPT (OpenAI), Claude (Anthropic) or another tool that supports the Model Context Protocol (MCP) to your Chess Analytics account. This is optional and off by default. The assistant connects to our MCP server at app.chess-analytics.app/mcp. You authorise it by signing in to your Chess Analytics account on our own consent page (including two-factor authentication or a passkey, if you use them), which shows the assistant's name and the permissions it asks for. Alternatively, you can create a personal access token in Settings and enter it into a tool yourself.
What the assistant receives
When you or the assistant call one of our tools, we return data from your account to the assistant, depending on the permission granted: your username, your plan (Free or Premium), your linked chess.com and Lichess usernames and whether a Lichess connection exists; your dashboard statistics, your game history and your analyses (moves, engine evaluations, move classifications, accuracy); your trend reports and AI game reviews. We never send your password, email address, two-factor secrets, passkeys or Lichess access token. With the permission to analyse, the assistant can also ask us to start the analysis of your games or to create an AI review, which is then processed as described in sections 7 and 8; these actions are limited to Premium accounts and are rate-limited per user. The assistant cannot change your account settings, plan or credentials.
Your choice of assistant
We do not share your data with OpenAI, Anthropic or any other assistant provider on our own initiative, and they are not our processors. Data only reaches an assistant because you chose to connect it and you (or the assistant acting on your request) call one of our tools. Which assistant you use, and under which account and settings, is entirely your decision. From then on, the data is processed by that provider under your own agreement with them and their privacy policy and terms (for example OpenAI, L.L.C. for ChatGPT or Anthropic, PBC for Claude), including where they process it and whether they store conversations or use them to improve their models. Please read the provider's policy before you connect an assistant. Our legal basis for returning your data to the assistant you connected is the performance of our contract with you, at your request (Art. 6 (1) (b) GDPR). You can stop this at any time by disconnecting the assistant in Settings.
What we store about connected assistants
- Access tokens and personal access tokens. We store only a hash of each token, never the token itself, together with its name, permissions, the assistant it was issued to, when it was created, when it expires and when it was last used. Personal access tokens expire after 30, 90 or 365 days, or never if you choose so. OAuth access tokens are valid for 1 hour.
- Refresh tokens (hashed) let the assistant obtain a new access token without asking you again. They are valid for 60 days and are replaced each time they are used, and are deleted when they expire.
- Authorisation data. A pending authorisation request is kept for 10 minutes, and an authorisation code for 60 seconds.
- Assistant registrations. Assistants register with us with their name and redirect addresses (or publish them in a metadata document, which we fetch from the assistant's own domain and keep for up to 7 days). Registrations that were never used to authorise an account are deleted after 30 days; cached metadata of unused assistants after 7 days.
Your controls
In Settings, under "Connected apps & tokens", you see every connected assistant and every personal access token with its last use, and can disconnect an assistant or delete a token at any time. Disconnecting immediately revokes its access and refresh tokens. All access tokens, personal access tokens and connected assistants of your account are also revoked automatically when you change or reset your password, and are deleted when you delete your account. Disconnecting does not delete data the assistant provider already received; for that, use the controls of that provider.
Logs
Our application does not log IP addresses (see section 3) and does not log the content of tool calls or the data returned. Technical server logs contain at most the request path, status and duration. Cloudflare processes the connection data of MCP requests as described in section 3.
Overview
| Data | Purpose | Recipients | Retention |
|---|---|---|---|
| Username, plan, linked chess.com / Lichess usernames | Show the assistant whose account it is connected to and what is available | The assistant you chose to connect, at your request | Held by us as in section 11; by the provider under its policy |
| Game history, dashboard statistics, analyses, trend reports, AI reviews | Answer your questions about your games in the assistant | The assistant you chose to connect, at your request | Held by us as in section 11; by the provider under its policy |
| Token hashes, permissions, assistant name, creation / expiry / last-use time | Authenticate and authorise the assistant; let you review and revoke it | None (netcup and Cloudflare as processors) | Access token 1 hour; refresh token 60 days; personal token until its expiry or deletion; all deleted on revocation, password change or account deletion |
| Requests for Premium analyses and AI reviews started by the assistant | Run the analysis or review you ask for | OpenRouter and its model providers for AI reviews (section 8) | As in sections 7, 8 and 11 |
10. Email
We only email an address after you confirmed it (double opt-in): when you enter an address and agree to receive emails there, we send a confirmation link to it, and only once you click it do we use the address. Until then we keep it as unconfirmed with the time you gave your consent; the link expires after 24 hours. We store when you gave consent and when you confirmed, to be able to show that you agreed.
We use your confirmed address to send you the trend reports you request or schedule, test emails you trigger, replies to your support requests and, if you ask for it, the Premium launch email. Emails are sent through Cloudflare's email service (Cloudflare, Inc., see above); they contain the report and the recipient address. The legal basis is the performance of our contract with you (Art. 6 (1) (b) GDPR) and, for the confirmation, your consent (Art. 6 (1) (a) GDPR). You can remove your email address in Settings at any time; we then stop sending emails.
Support requests
Contacting us through the Support page needs a confirmed email address, which we reply to. We store your message (topic, subject, text), that email address and your username with your account, and email the message to our support inbox through Cloudflare's email service. To keep track of the conversation, we also add the emails exchanged about your request (your replies and ours) to it. Replies to our support emails go to our support address, where Cloudflare's email routing passes them to our server (Cloudflare, Inc., see above); we store the new text of the reply (not the quoted history) and forward it to the other side. If you email the support address from your confirmed address without a ticket number, we open a new request for you. We use this only to answer your request. The legal basis is the performance of our contract with you (Art. 6 (1) (b) GDPR). You can see the whole conversation on the Support page. Open requests are closed automatically after 7 days without activity.
Contact form (without an account)
You can also write to us through the public contact page, signed in or not. We ask for your email address, a topic, a subject and your message, and optionally your name. We store them as a support request (without an account link if you are not signed in), email the message to our support inbox and send a confirmation to the address you gave; we do not add it to any mailing list. Because the address is not confirmed in advance, the confirmation email may reach someone who did not write to us; for this reason, and to keep out spam, the form uses Cloudflare Turnstile and limits how often it can be used per IP address and email address (counters kept in memory for up to one hour). Our replies, and your answers by email, are added to the request as described above. The legal basis is the performance of a contract or steps prior to entering into one at your request (Art. 6 (1) (b) GDPR), and our legitimate interest in answering enquiries and protecting the form against abuse (Art. 6 (1) (f) GDPR). Retention is the same as for other support requests (see section 11 for the periods). Without an account you cannot see the conversation on the Support page; to have it corrected or deleted, write to us.
Premium waitlist
If you join the Premium waitlist, we store with your account which features you want, what you are missing, the price range you chose and whether you want a single email to your confirmed address when Premium launches. All answers are optional. We use them to plan Premium and to give you the free days at launch; the launch email is sent through Cloudflare's email service. The legal basis is the performance of our contract with you (Art. 6 (1) (b) GDPR) and, for the launch email, your consent (Art. 6 (1) (a) GDPR), which you can withdraw at any time by editing or leaving the waitlist.
11. Retention
- Account data, linked usernames, coaching profile, analyses, reports and schedules: until you delete them or ask us to delete your account.
- Fair-play checks and the opponent games fetched for them: until you remove the check or delete your account.
- Session cookies: until you sign out, or 30 days after your last visit.
- Lichess access token: until you disconnect Lichess or delete your account.
- Two-factor secret and recovery codes: until you turn two-factor authentication off or delete your account.
- Passkeys: until you remove them or delete your account.
- Email address and consent records: until you remove the address or delete your account. Unconfirmed addresses: until you confirm, cancel or replace them; the confirmation link expires after 24 hours.
- Premium waitlist answers: until you leave the waitlist or delete your account, at the latest 6 months after Premium launches.
- Support messages (including those sent through the contact form without an account): 6 months after the request was closed, or earlier if you delete your account. Copies in our support inbox are also deleted within 6 months of the last message.
- Failed sign-in attempts: up to 15 minutes, in memory only.
- Connected AI assistants: OAuth access tokens 1 hour; refresh tokens 60 days (renewed on each use) or until you disconnect the assistant, change your password or delete your account; personal access tokens until they expire (30, 90 or 365 days, or never if you chose so), you delete them, you change your password or delete your account. Unused assistant registrations: 30 days; cached assistant metadata: 7 days; authorisation requests 10 minutes; authorisation codes 60 seconds.
You can delete your account at any time in Settings. This immediately deletes your account, sessions, linked usernames, Lichess connection, email address, support messages, waitlist answers, analyses, reports, schedules, AI reviews and fair-play checks, as well as stored games and engine results that no other user has analysed. Games and engine results that other users have also analysed are kept for them, but are no longer linked to you. If you cannot sign in, email us atcontact@chess-analytics.app and we will delete your account within 30 days. Data we must keep by law (e.g. invoices) is retained for the statutory period.
12. Your rights
You have the right to:
- access your personal data (Art. 15 GDPR),
- rectification (Art. 16 GDPR),
- erasure (Art. 17 GDPR),
- restriction of processing (Art. 18 GDPR),
- data portability (Art. 20 GDPR),
- object to processing based on Art. 6 (1) (f) GDPR on grounds relating to your particular situation (Art. 21 GDPR).
To exercise your rights, email contact@chess-analytics.app. You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the EU member state of your habitual residence, place of work, or the place of the alleged infringement.
13. Security
All connections are encrypted with TLS. Passwords are stored only as salted hashes, session tokens only as hashes, Lichess access tokens and two-factor secrets encrypted (AES-256-GCM), and recovery codes, OAuth tokens and personal access tokens only as hashes. You can protect your account with an authenticator app or a passkey.
14. Automated decision-making
We do not use automated decision-making or profiling within the meaning of Art. 22 GDPR. The level estimate (section 8a) only adjusts how your reports are written; it has no legal or similarly significant effect, and you can change it yourself.
15. Changes
We update this policy when the service or the law changes. The current version is always available on this page.