Last updated: October 18, 2026

Privacy Policy

ChessExpert is currently free to use. This policy covers its website, browser extension and iOS or Android apps.

At a glance

  • Guest activity and cloud records can be linked to a profile ID.
  • Photos are stored for recognition and history.
  • Optional analytics needs your consent; chess features work without it.
  • Data requests are handled manually. Contact us or use the request form below.

1. Contact us

For privacy questions or requests, email support@chessexpert.io.

2. Profiles and Google sign-in

Firebase gives every profile an ID, including guests without email. Even as a guest, your activity and records can be linked to this ID; guest use is not anonymous. Optional Google sign-in on the website uses your profile ID and email. Your name and photo are not required, though Firebase Authentication may receive or keep basic Google profile information. Connecting an unused Google account keeps the guest ID. Website Google sign-in does not automatically merge separate app or extension profiles.

After you agree to the Terms and acknowledge this policy at sign-in, we record your final Google profile ID, document versions, statement and time. This is separate from analytics consent.

An existing Google account can open after an empty-profile check. Otherwise, choose a merge or continue without merging. A merge stores the profile association and progress for completion or retry. It copies the initial supported study set and transfers selected history without overwriting Google study material or deleting the source account and retained study records. Later guest records stay with the guest; interrupted transfers may need a same-account retry. PDFs, device-local progress, separate native profiles, pairing and privacy requests are excluded.

Without merging, cloud guest records are not added to Google and access on this device may be lost. This choice is available only when no merge is underway. Finish uploads and merges in other tabs before switching.

3. Images, documents and study data

Screenshots, photos, video frames, board regions, PDFs and cropped diagrams may be uploaded and stored, even with local recognition. Mobile apps may use camera or gallery images you choose; extensions may capture a page, region or video frame when you request it. Records may include source URLs, video timing, FEN, orientation, settings, status, timestamps and profile ID.

Photos are stored for recognition, history and related features, not published in a public gallery. Database recognition and saved-study records are restricted to their owner or authorized administrators. PDF download rules allow the owner and authorized administrators. Avoid confidential or unrelated personal details.

We store positions, notes, tags, collections, source references, solutions and exercise progress with your profile. Opening requests, feedback and support messages may be kept to respond or investigate.

4. Optional analytics and browser storage

Web and embedded extension pages start Google/Firebase Analytics only after Accept analytics. Rejecting it leaves chess features available; earlier activity is not backfilled. Analytics can link your Firebase ID and profile records to navigation, captures, training, errors, source URLs, exercise IDs and moves, device/browser, language and approximate location. It is not anonymous.

Use Privacy settings to accept, reject or withdraw consent in this browser. Withdrawal stops future collection, not earlier data or accepted requests in flight, and does not undo valid earlier consent. Unavailable storage keeps analytics off in that tab.

Rejection does not automatically remove existing analytics cookies. Clear them in your browser. Clearing the saved choice prompts us to ask again; clearing site data can also sign you out or remove local preferences and progress.

Authentication, preferences, caches, local progress, uploads and cloud study records are separate from analytics. Mobile WebViews do not load web analytics; updated native apps deactivate it. Older apps may collect until updated; updating does not erase earlier data.

5. Why we process data

  • Requested recognition, analysis and saved-study features: to perform our service contract.
  • Optional analytics: your consent, which you can refuse or withdraw.
  • Statutory privacy requests and applicable complaints: our legal obligations. Message and reply email are used for replies, ownership checks and necessary handling evidence.
  • Sign-in agreement records: our necessary legitimate interest in documenting your Terms agreement and Privacy acknowledgement, unless your rights and interests override it.
  • Security and support: our necessary legitimate interests, unless your rights and interests override them.

6. Retention and deletion

Data does not expire automatically after a fixed period. We are introducing manual reviews to decide when it is no longer needed and can be removed or reduced. Legal requirements or disputes may require us to keep some records longer:

  • Profiles and study: continuing access and use.
  • Images, PDFs and history: recognition, support and study; not every history record needs its original.
  • Logs and provider copies: technical, security or reporting needs and provider settings.
  • Merge originals and copies: completion and recovery; minimal ownership mappings can prevent duplicate transfers or wrong access.
  • Sign-in acknowledgements: continuing need for version and choice evidence, legal obligations or justified disputes.
  • Rights requests and private notes: response evidence, follow-up or disputes.

Deleting a position does not automatically delete its upload or exercise; deleting a collection leaves its contents. Clearing storage, signing out, starting a new guest or uninstalling an app or extension does not by itself delete cloud records and may remove profile access. Display limits are not retention periods. There is no single self-service export or erasure of all account data.

7. Your rights and manual requests

Where applicable, request access, correction, erasure, restriction or portability, object to processing, or withdraw consent. Email support@chessexpert.io or submit a data request for this browser’s existing profile.

The form needs a message and reply email; it records request type, profile ID, time and a private reference. Keep it. Email is for handling, not marketing; email or reference alone is not ownership proof. The form identifies only the current browser profile. For an app or extension using another profile, a lost session or another device, email the platform, material details and any available reference; a new guest cannot identify the old profile. Never send passwords or tokens. We may ask for proportionate ownership evidence, not routinely an identity-document copy.

All handling is manual. Private status and notes track progress; Completed does not prove erasure. Submission does not automatically email, export or delete data.

We reply without undue delay, normally within one month. Complex or numerous requests may need two additional months; we notify you with reasons within the first month. You may complain to a data protection authority.

8. Changes to this Privacy Policy

We may update this policy and publish a revised version with its date here. Please review it periodically.

Using ChessExpert. Read the current policy. If you disagree, contact us or stop using ChessExpert. Your continued use of ChessExpert after changes to this policy are published will be considered acceptance of those changes. We explain any new purpose before processing and seek consent where required.