Your data rights

Manage your privacy choices and learn how GDPR rights apply to Falling Chess. Last updated: 6 September 2026.

Controls you can use now

1. Stop optional gameplay analytics: open the game, choose Options and switch “Anonymous analytics” off. Despite that label, consented event identifiers are pseudonymous. This stops future optional client events and purges queued optional events, not server-side PvP processing or past records.
2. Clear local progress: use your browser’s settings to delete site data for the game’s origin. This can erase scores, settings and installation identifiers. It does not remove public scores or information a server has received.
3. Keep identifying clues for a request: before clearing site data, note the game URL, approximate date and time, platform, and any relevant score and initials. You do not need to create an account to ask for help.

Open the game or read the storage explanation. Clicking a link or continuing to browse does not change your analytics preference.

Rights under GDPR

Where GDPR applies, you can ask the controller to:

• Provide access to personal data about you and explain its use.
• Correct inaccurate data or complete relevant incomplete data.
• Erase data when the legal conditions apply, or restrict its processing in the circumstances set out by GDPR.
• Provide a portable copy of data you supplied when automated processing relies on consent or a contract.
• Consider your objection to processing based on legitimate interests, taking your circumstances into account.

You can withdraw optional-analytics consent at any time. Withdrawal does not change the lawfulness of processing before withdrawal. These rights have conditions and exceptions, including protecting other people’s data and meeting legal obligations.

Making a request

When contacting the team, say that your message concerns Falling Chess privacy and describe the action you want. Include only the details needed to locate the relevant data. We do not have account or email-linked gameplay records, so initials or a timestamp may not identify a record uniquely. If we cannot locate your data, we should explain that and what additional information would help.

Do not email guest credentials, access tokens, passwords or identity documents with your initial request. The controller may seek proportionate verification if there are reasonable doubts about identity. Removing local identifiers can make later server-record matching difficult; it does not cancel your rights.

GDPR requires a response without undue delay and within one month. For complex or numerous requests, the controller can extend by up to two further months, explaining the extension within the first month. Requests are generally free; GDPR provides limited exceptions for manifestly unfounded or excessive requests.

Complaints

You can complain to a data-protection authority, including in the EU country where you live, work or believe an infringement occurred. You do not have to contact us first. GDPR also provides routes to a judicial remedy.

See the official GDPR text, including Articles 7, 11–22 and 77. For the data categories and unresolved launch requirements, read our privacy notice.