What data is processed and how to exercise your rights
Last updated: 16 de agosto de 2026
1. Data controller
- Responsible: Santiago García Jiménez
- Contact: chesscorpus@gmail.com
- Country: Spain
Chesscorpus is a personal project financed in part through advertising. It publishes public chess-game results for documentary, statistical and study purposes.
2. Data and sources
Published records may include player names, game details, results, tournaments, dates, ratings and public FIDE information. They come from public broadcasts and databases, including Lichess Broadcasts, Ajedrez Data, Figshare, Chess-Results and public FIDE sources.
Player records are displayed only after an interactive search inside /database/players. Chesscorpus does not publish an individual web address for each player; former personal routes return 410 Gone. This safeguard is especially important because public tournament records can include minors. Removal requests concerning a minor are handled without requiring justification and with priority.
Optional user accounts may store a public username, a private email address (for password recovery only), a password hash and salt, account creation time, and tactics progress. Public profile pages at /u/username show the username and aggregate tactics statistics, never the email. A signed session cookie (__Host-cc_session, HttpOnly, Secure, up to 90 days) is set when you sign in. To request account deletion, contact chesscorpus@gmail.com.
Google AdSense is loaded only after the visitor accepts the advertising-consent notice. If accepted, Google may process advertising identifiers and cookies according to its own policies. The chess-game data published by Chesscorpus is not sent to advertisers for targeting.
4. Your rights
To request access, correction, deletion, restriction or objection regarding a published record or account, contact chesscorpus@gmail.com. You may also complain to the Spanish Data Protection Agency.
5. Hosting
The site is hosted by Cloudflare, which processes technical request data to deliver and protect the service. Flags may be loaded from flagcdn.com. Password-recovery emails may be sent through Resend when configured.