Privacy Policy
In short: Repertoire has no server and no user accounts. It does not collect, receive or sell your personal data, and it has no analytics, advertising or tracking. Your repertoires, games and settings stay in your own browser. If you choose to connect Google Drive, they are also stored in a folder in your own Drive.
Who runs this app
Repertoire (zeddyfree-art.github.io/chess) is a free, open-source web app published by zeddyfree-art on GitHub. The source code is at github.com/zeddyfree-art/chess. In this policy “we” means the publisher of the app.
What is stored, and where
| Data | Where |
|---|---|
| Your players (names, colours, ratings), repertoires, notes, engine flags, the last gap and engine check results, and training progress | In your browser (IndexedDB) on the device you use; with Google Drive connected, also in your Drive. Nothing is sent to us. |
| Settings and preferences (last tab, practice game options, and similar) | In your browser (localStorage). |
| Lichess login token and username, if you connect Lichess | In your browser only. |
| Google access token (valid about one hour), the connected account’s email address or name, and sync bookkeeping, if you connect Google Drive | In your browser only. |
| Cached Lichess database answers and the Maia model, if you use them | In your browser (IndexedDB). |
| Games you import (from Lichess or a PGN file), their analysis, and your Lichess username and the names you use in PGN files, if you enter them | In your browser (IndexedDB); with Google Drive connected, also in your Drive. |
| Sync files and backups, if you connect Google Drive | In a folder called “Repertoire app” in your own Google Drive (subfolders “Sync” and “Backups”). |
We cannot see any of this. There is no database on our side to hold it.
Who the app talks to
Your browser connects to these services directly. The connections are only made when the feature is used.
- GitHub hosts the app (GitHub Pages). Like any web host, GitHub receives technical data such as your IP address and browser type when you load the site, under GitHub’s privacy statement. We do not receive that data. The human-like opponent model may also be downloaded from
raw.githubusercontent.com. - Lichess (
lichess.org,explorer.lichess.org): to show what is played in the Opening Explorer and to fetch engine evaluations, the app sends chess positions (as FEN text) and your chosen rating and time-control filters. If you log in with Lichess, your access token is sent with those requests. The login itself happens on lichess.org; the app never sees your Lichess password and requests no permissions. See the Lichess privacy policy. Positions are sent even when you are not logged in, for engine evaluations. When you fetch your games, the app sends the Lichess username you entered and your period and time-control choices to the Lichess games export; your games are public on Lichess, so this needs no login. - Google (
accounts.google.com,www.googleapis.com): only if you choose “Connect Google Drive”. Before you do, the app makes no request to Google. See Google’s privacy policy.
The chess engine (Stockfish) and the human-like opponent (Maia) run entirely on your device; the positions you analyse or play are not sent anywhere for that.
Google Drive
If you connect Google Drive, the app asks for one permission: https://www.googleapis.com/auth/drive.file. It lets the app create and access only the files it created itself. It cannot see your other files.
- What we use it for: to keep two JSON files in sync between your devices (one with your players, repertoires and training progress, one with your imported games and their analysis), and to store dated backups: one a day of the first (the newest 30 are kept) and one a week of the games (the newest 8). The app also reads the email address or name of the connected Google account, to show you which account is connected.
- What we do not do: the data is not sent to us or to anyone else, not read by people, not used for advertising, profiling or analytics, and not sold or shared.
- The app’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Cookies and tracking
The app sets no cookies and includes no analytics, advertising or tracking code. It stores data in your browser as described above. When you sign in on the Lichess or Google pages, those services may set their own cookies under their own policies.
Your choices and how to delete your data
- Local data: clear this site’s data in your browser settings, or delete players and repertoires in the app (Settings). You can download a backup file first.
- Google Drive: click “Disconnect” in Settings, then delete the “Repertoire app” folder in your Drive. You can also revoke access at myaccount.google.com/permissions.
- Lichess: click “Disconnect” in Settings (this also revokes the token), or manage tokens at lichess.org/account/security.
- Maia model: Settings → “Remove from this device”.
Children
The app is for chess players of all ages, and parents may set it up for their children. We do not collect any personal information from anyone, including children. Anything entered (such as a player’s first name) stays on that device or in that person’s own Drive.
Changes to this policy
If the app changes in a way that affects your privacy, this page is updated and the date above changes. Earlier versions are in the public change history.
Contact
Questions or requests: please open an issue at github.com/zeddyfree-art/chess/issues.