ChessEndings

Бесплатное приложение

СкачатьСкачать

Privacy Policy

Последнее обновление: 29 октября 2026 г.

Наши юридические документы публикуются на английском языке; английская версия имеет приоритет. Смотреть оригинал на английском

In short: we collect only what the product needs. Your email and training activity if you create an account; no account and no server-side training data if you train as a guest (guest progress stays in your browser). Payments are handled by Stripe, or by Apple/Google on mobile; we never see your card. We never sell your data. We do run one advertising measurement tool, Meta's, and it works only if you accept it, in the cookie banner or in the settings of the Android app. Refuse, or simply never answer, and nothing about you is sent to Meta. You can delete your account, with your profile and training data, from your account settings at any time (section 7 lists what is kept).

1. Data controller

The controller of your personal data under the EU General Data Protection Regulation (GDPR) and the French Data Protection Act is:

ANKT SERVICES

SASU (société par actions simplifiée unipersonnelle) with a share capital of EUR 100

SIREN: 843902156 · SIRET: 84390215600010 · RCS: Angers

EU VAT: FR78843902156

25 Rue Lenepveu, c/o WeForge

49100 Angers, France

President and publication director: Antoine Tamano

Email: support@chessendings.com

2. Data we collect

2.1 Account data

  • Email address, for sign-in and service emails. If you sign in with Google, we receive your email and basic profile (name, avatar) from Google; if you sign in with Apple in the iOS app, we receive the email address Apple shares with us (which can be an Apple relay address).
  • Display name, chosen by you, shown on leaderboards only if your profile is public.
  • Settings and preferences (language, training options, email and notification preferences).
  • Push token: if you allow notifications in a mobile app, the token that lets us send notifications to that device.

2.2 Training data

Your training activity: drills played, moves, results, mistakes and their explanations, ratings, XP, streaks, achievements, and journey progress.

2.3 Scan feature

If you use the scan feature, we store the public Lichess or Chess.com username you enter and fetch publicly available games for it from those platforms' public APIs. We never access private data on those platforms.

2.4 Payment data

Purchases on the website are processed by Stripe; we store your Stripe customer ID, plan, and payment status, never your card details. On mobile, purchases are processed by Apple or Google and managed through RevenueCat; we receive only a purchase receipt and subscription status, no payment details.

2.5 Technical data

Standard server logs (IP address, user agent, timestamps) collected by our hosting provider for security and debugging, and, where analytics is enabled, product usage events (see section 5).

2.6 Guests

You can train without an account. Guest training runs entirely in your browser: your progress and the daily drill counter are stored in your browser's local storage on your device and are not sent to our servers. No guest account or server-side profile is created.

4. How we use your data

  • Running the product: accounts, progress tracking, mistake explanations, achievements, quotas.
  • Leaderboards: your display name and ranking only, and only if your profile is public. You control this in your settings.
  • Emails and notifications: transactional emails (receipts, account notices) and, unless you turn them off, training emails and app notifications (onboarding tips, streak reminders, the weekly digest, a reminder when your free quota is back, a message if you have been away for a while) and messages about our own products (a reminder after an unfinished checkout, sometimes with a discount code, and, after you buy Pro, a discount code for our other chess apps). Every email other than transactional ones has an unsubscribe link, and each kind can be switched off in your account settings or, for notifications, in the app or your device settings.
  • Improving the service: aggregate usage analysis and debugging.
  • Security and compliance: preventing abuse, meeting legal obligations.

Our other chess apps (DarkSquares, ChessAtlas, ChessTactics) are published by the same company. To create the discount code for them after you buy Pro, our server sends your email address to theirs so that each can check whether you already own it; when you buy one of those apps, it sends us your address in the same way. The code is recorded with that address at Stripe, which redeems it.

We never sell your personal data. If you accept advertising measurement (advertising cookies in the banner, or the setting in the Android app), and only then, we share a hashed version of your email address with Meta so that an account creation or a purchase can be attributed to the advertisement that led to it. A hash is not reversible into your address, it is sent for that single purpose, and if you refuse or have not answered it is never sent at all.

5. Third-party processors

We share data with the providers below. Most of them (Supabase, Vercel, Resend, Expo, Web3Forms, PostHog, Sentry, RevenueCat, Cloudflare) process it on our behalf as processors, under data processing agreements. Stripe, Apple and Google (as app stores and sign-in providers) and Meta also process some of it as controllers for their own purposes, under their own privacy policies. Lichess, Chess.com and DiceBear only receive what a web request carries.

  • Supabase: authentication and database hosting.
  • Stripe: payment processing on the website (PCI-DSS certified); receives your email for receipts and billing.
  • Vercel: website hosting and content delivery (server logs).
  • Resend: delivery of our emails, and of support messages sent from inside the mobile apps.
  • Expo (mobile apps): delivery of push notifications to your device through Apple's and Google's notification services; receives your device's push token and the notification text.
  • Web3Forms: contact form delivery from this website; your email and message are transmitted to reach our support inbox.
  • Google and Apple: optional sign-in with Google (OAuth), or with Apple in the iOS app.
  • PostHog (hosted in the EU): product analytics on this website and in the mobile apps: the pages and screens you view and your training activity, under a random identifier kept in a cookie (website) or on the device (apps), linked to your account identifier and email address once you sign in. It also receives your IP address, from which it derives your approximate location, the error reports of this website, and, in the Android app, the campaign that led to the installation as reported by Google Play. It is never shared with an advertising network.
  • Sentry (mobile apps): crash reports and a sample of performance measurements, with the error details, your device model, its operating system and the app version; no email address or other identifying details are sent.
  • Meta (Facebook, Instagram): advertising measurement, and only after you agree to it (on this website, by accepting advertising cookies; in the Android app, in its settings). From this website it receives page views, account creations, purchases, and the fact that you finished your first training position together with how that attempt ended; from the Android app it receives purchases only, reported by our server rather than by the app. Account creations and purchases are each reported twice, once by your browser and once by our own server, so that a blocked or failed script does not lose them; the two carry the same identifier and Meta keeps one. Both carry a hashed form of your email address, and the copy our server sends also carries your IP address and the identification your browser sends with every request, so that we can tell which advertisements bring people here. Nothing is sent, from either place, if you refuse or have not answered. Your latest answer, given on this website or in the settings of the Android app, is the one that applies to your account. A purchase made in the App Store, on iPhone or iPad, is never reported to Meta.
  • Apple App Store / Google Play and RevenueCat (mobile apps): purchase processing and subscription status. The store handles your payment data directly; RevenueCat stores an app user identifier and purchase receipts, no email or card data.
  • Lichess: our servers, and your browser directly, query the Lichess tablebase API with chess positions only (a direct query also shows Lichess your IP address, like any web request). The scan feature fetches public games from the Lichess and Chess.com public APIs for the username you provide.
  • Cloudflare and DiceBear: your browser or app downloads the coach's audio files from our storage at Cloudflare, and avatar images from DiceBear (by default an avatar is drawn from your random account identifier); like any download, these requests show those providers your IP address.

6. International transfers

Some providers process data outside the European Economic Area (notably in the United States). Where they do, transfers are protected by the EU-US Data Privacy Framework or the European Commission's Standard Contractual Clauses. You can request details of these safeguards at support@chessendings.com.

7. Data retention

  • Account and training data: kept while your account exists. Deleting your account from your account settings (website or app) removes your profile, training data and push tokens immediately.
  • Product analytics: the events already recorded by PostHog are not erased automatically when you delete your account; ask us at support@chessendings.com and we delete them.
  • Billing records: kept for 10 years, as French accounting law requires. Purchase records are never edited retroactively; refunds are recorded as reversals.
  • Support messages: kept up to 3 years after resolution.
  • Server logs: kept for a short rolling window by our hosting provider.
  • Guest data: stored only in your browser; clear your browser storage to remove it.

8. Your rights

Under the GDPR you have the right to:

  • access your data and get a copy (Art. 15)
  • correct inaccurate data (Art. 16)
  • have your data erased (Art. 17); account deletion is self-service from your account settings
  • restrict processing (Art. 18)
  • receive your data in a portable, machine-readable format (Art. 20)
  • object to processing based on legitimate interests, and to any direct marketing (Art. 21)
  • withdraw consent at any time, without affecting prior processing

To exercise any of these rights, email support@chessendings.com. We respond within one month. You also have the right to lodge a complaint with a supervisory authority (see section 13).

9. Cookies and local storage

Three kinds of cookie. The functional ones need no permission and are set regardless: the authentication cookies that keep you signed in, and the ones remembering your language, your theme and your answer to this banner. The product-analytics cookie is set by PostHog, our analytics processor, on this website's own domain: it holds a random identifier so that the pages and training steps of one visit can be counted together (see PostHog above); it is never shared with an advertising network. The advertising ones exist only if you accept, and they let Meta recognise a browser that arrived from one of our advertisements. Most are Meta's own; one of them, the identifier of the advertisement you clicked, we write ourselves from the link you arrived on, so that it still exists when your browser blocks Meta's script. Until you accept, no Meta script is loaded and no advertising cookie exists. Your answer is kept for six months, after which we ask again; you can change it at any time from the link on this page, and withdrawing deletes those advertising cookies from your browser rather than merely stopping their use. We also use your browser's local storage for preferences and for guest training progress; that data stays on your device.

One entry does leave your device. So that we can tell which channels bring people to ChessEndings, local storage keeps a short record of your first visit: the site that referred you (the site name only, such as lichess.org, never the page you came from), the first page of ours you opened, any campaign tags in the link you followed, whether you arrived on a phone, a tablet or a computer, and the date of that first visit. That record is sent to our analytics processor when you arrive and again if you create an account, so that we can see how many people a channel brings and not only how many sign up. It is the same record either way. It contains no name, no address and nothing about what you read here, but it travels with the identifier your analytics profile is kept under, and once you have an account that profile is your account: it is your personal data and the rights in this policy apply to it. It is never used to advertise to you.

If, and only if, you accepted the advertising cookies above, the record also keeps the identifier of the advertisement you clicked (Meta's or Google's, taken from the link you arrived on). If you then create an account, the record is also sent to the processor that handles purchases made inside our mobile apps, so that a purchase there can be counted against the advertisement that led to it; without it those purchases are attributed to nobody. Refuse, or simply never answer, and no advertising identifier is kept and nothing is sent to that processor. The whole entry is discarded after 90 days, and clearing your browser storage removes it immediately. If you create an account, a copy of that record is also kept with the account on our own servers, so that a later purchase can be counted for the channel that brought you; that copy is deleted with the account.

10. Security

Data is encrypted in transit (TLS), authentication is handled by Supabase with hashed credentials, access to production data is restricted, and database access is enforced by row-level security. No system is perfectly secure, but we design the Service so that the server never trusts unverified client input and holds no more personal data than the product needs.

11. Children

The Service is not directed at children under thirteen (13) and we do not knowingly collect their data. Users under the age of digital consent in their country (fifteen (15) in France) need parental consent to use the Service with an account. If you believe a child provided us personal data, contact us at support@chessendings.com and we will delete it.

12. Changes to this policy

We may update this policy as the product or the law evolves. Material changes are announced by updating the date above and, if you have an account, by email or an in-product notice.

13. Contact and complaints

For any privacy question or to exercise your rights, write to support@chessendings.com or use the contact page.

ANKT SERVICES

SASU (société par actions simplifiée unipersonnelle) with a share capital of EUR 100

SIREN: 843902156 · SIRET: 84390215600010 · RCS: Angers

EU VAT: FR78843902156

25 Rue Lenepveu, c/o WeForge

49100 Angers, France

President and publication director: Antoine Tamano

Email: support@chessendings.com

If you are not satisfied with our response, you may lodge a complaint with the French supervisory authority: CNIL, 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France (www.cnil.fr), or with the authority of your country of residence.