Privacy policy

What the extension reads, and what it keeps

Last updated: 17 September 2026

Chess Cheating Signals is a Chrome extension that shows badges on your opponent's card on chess.com. It has no backend. There is no server of ours anywhere in the path, so there is nothing for us to collect even if we wanted to.

The short version

Who is responsible

The extension is developed and published by an individual developer, not a company. Contact goes through GitHub issues, or by email at support@fbextractor.com. The full source is public, so every claim on this page can be checked against the code.

Requests the extension makes

All requests go directly from your browser to chess.com. They carry your normal chess.com session, exactly as the site's own pages do while you browse it — the extension does not log in for you and holds no credentials of its own.

Endpoint Why
www.chess.com/service/player-game-archive-v2/… The finished-game list the site's own pages use. This is the main source: result, time control, accuracy where chess.com has computed it, opening and the client the game was played from.
www.chess.com/member/<username> Read only when the player's public identifier is not already present on the page you are on. The extension parses the profile markup for that identifier and nothing else.
api.chess.com/pub/player/<username> chess.com's documented public API. Used as a fallback when the first endpoint is unavailable, and for the account creation date.

There are no other network destinations. The interface fonts ship inside the extension package, so rendering a badge contacts nobody.

What it reads about a player

Only what chess.com already shows about that player's finished games, and only for the player whose card is on screen — your opponent, or you:

The game in progress is never read. Live moves, chat, private messages, email addresses and payment details are outside what the extension requests and outside what these endpoints return.

What it stores, and where

What Where How long
Your settings: thresholds, time window, which badges to show chrome.storage.sync Until you change them or remove the extension
Public identifiers of players already looked up, to avoid re-fetching a profile chrome.storage.local Until you remove the extension or clear its data
The fetched game list for the card currently on screen Memory of the page 60 seconds, and gone when the tab closes

One honest detail about settings. They live in chrome.storage.sync, which is Chrome's own sync storage. If you have Chrome sync switched on, Chrome carries those settings between your own devices through your Google account, under Google's terms — not through us, and we never see them. If you would rather they stayed on one machine, turn extension sync off in Chrome's settings.

Permissions, and why each one exists

What the extension does not do

Removing your data

Removing the extension from Chrome deletes both storage areas with it. Settings that Chrome has synced are cleared through Chrome's own sync controls, in the same place as the rest of your synced browser data.

Children

The extension is not directed at children and collects nothing from anyone, of any age.

Changes to this policy

If what the extension reads or stores changes, this page changes with it in the same commit, and the date at the top moves. The history of this page is public in the repository.

About chess.com

This policy covers the extension only. chess.com is an independent service with its own privacy policy and terms, and this project is not affiliated with it in any way.