Privacy
What the application keeps, why and for how long.
Revised:
Sessions and nicknames
To keep your seat at the table, the application stores a player ID, nickname, creation date, session-token hash, request-protection token and expiry. The essential session cookie lasts up to 30 days. Expired session records are removed by periodic cleanup.
There is no registration or password sign-in. You can change your nickname in Settings. Your session belongs to this browser and cannot be recovered by email. Any account records from an earlier version remain stored without a sign-in route or automatic deletion. A guest with no active session or linked match records is removed after 30 days by periodic cleanup.
Matches, ratings and replay
We keep participant IDs and nicknames, game type, start and finish times, score, result, bot level where applicable, and recorded dice and moves. These support history, ratings and game study. Replays are available to participants. There is no public nickname or ratings leaderboard. Saved results and replays do not yet have an automatic deletion date.
Active tables live in memory. Planned maintenance can wait for matches to finish, but a forced stop or failure can interrupt them. Computer evaluation concerns game positions and does not guarantee a win.
Studies and sharing
You can save notes, bookmarks and legal variations from a finished match. Studies are private to your browser session. Publishing creates a separate snapshot of the game and, if you select that option, notes for anyone with the link, using generic player names. Do not include personal information in notes you publish. You can revoke the link and delete the study. Revocation cannot remove copies already downloaded.
Analysis stores position estimates. Lessons use prepared positions and do not store your answers on the server. Public statistics use only anonymous daily totals, with small groups suppressed and counts rounded. They do not count unique people.
Chat and reports
The last 50 messages stay in table memory for up to 24 hours with their text, sender and time. Only the two participants who have not muted chat receive them. Ordinary chat is not written to the database.
A report stores the selected message and its time, sender, reporter, match and report time for operator review. Evidence remains for up to 30 days, capped at the newest 50,000 reports. A report is not disclosed to your opponent. The application does not promise automatic moderation or an immediate response.
Preferences and anonymous counts
Your chosen nickname, language, sound, volume, appearance, contrast and the anonymous-count choice stay in your browser until changed or site data is cleared. Interface assets can be cached.
Counts store daily totals by general page, game, mode, language and device category for up to 395 days. They contain no player identity, IP address, private link, text or full referring URL. They do not link visits together. Browser counts respect the choice below, Do Not Track and Global Privacy Control. Separate server operational totals, such as match completions and overload rejections, remain.
Security and access
Temporary counters in memory use hashed network addresses to limit abuse. They are not stored in the database. The operator and authorised server administrators can access application records and backups for operation, security and requests. Hosting infrastructure, access logs and backups are described separately below.
Your records and rights
The history and ratings download from the browser with your guest session contains your latest 50 matches and your ratings. It is not a complete personal-data export: full replays, study notes, legacy account details, sessions and reports are not included.
You can request access, correction, deletion, restriction, objection or portability where applicable. Use the details on the contact page. There is no complete automated player-data deletion workflow yet. Requests need safe identity verification. Never send a password, cookie or recovery code.
You can contact the Hellenic Data Protection Authority. The conditions for these rights are explained in official European guidance.
Operator and contact
- Operator
- The operator's identity has not been published.
- Public email
- No contact address has been published yet.
These details must be completed before public launch. Privacy requests cannot be submitted through this page until a contact address is published.
Hosting, access logs and backups
Hosting and logs
Hosting provider, server location, access-log fields, access permissions and retention have not been published. These deployment details need to be confirmed before public launch.
Backups
Backup location, retention and deletion procedure have not been published. Copies may retain records after they leave the live database; do not assume that live-record expiry also deletes older backups.
Advertising choices
Advertising is disabled for this deployment. No advertising or consent-provider scripts are loaded.