Last updated August 30, 2026.
When you click scan, the text of the pull request or issue you are looking at is sent over HTTPS to the Tellcheck for GitHub scoring server, scored, and returned. It is not stored, not logged in full, and not shared. That is the whole product.
The text does leave your browser. Scoring happens on a server, not on your device, so that part is a "can't" given how the detector works today. Everything below, about what the server does and does not do with that text once it arrives, is a "won't": read the code in this repo and check it.
Nothing is sent anywhere until you click a scan button, or turn on auto-scan in the
options (it ships off). A scan sends: the visible text of the PR or issue (code blocks
removed), and a random meter id like 7f3a... used to count your daily free
scans. The meter id is generated on your device, is not tied to your name, GitHub
account, email, or anything else, and a new one is generated every day, so scans on
different days cannot be connected to each other.
The scoring server keeps a per-day counter per meter id and, as a coarse backstop against a rotated meter id, a per-day counter per source IP address; both are deleted within 48 hours. It also keeps standard short-lived infrastructure logs (Cloudflare's). Scanned text is processed in memory and discarded. No database of scanned content exists. There is no server-side "paid" flag either; the worker does not read or trust any client-asserted payment claim, because nothing today can verify one.
Scanning a repo's open PRs calls GitHub's public API from your browser. If you add a
GitHub token in the options, it is stored only on your device and sent only to
api.github.com. It never touches Tellcheck's servers.
The extension's manifest requests exactly one permission: storage, used
to hold your settings, the daily meter id, and the last scan result on your device. It
does not request access to your browsing history or any site other than
github.com, where its content script runs. You can read the manifest and
every line of background.js yourself; nothing here is asserted without the
source to back it.
The current version has no payment features. If a paid tier is added later, payments would be handled by ExtensionPay and Stripe; your payment details would go to Stripe, not to Tellcheck, and this policy will be updated first.
No browsing history collection, no analytics or tracking pixels, no selling or sharing of data, no reading pages other than the GitHub page you scan.
Questions: Munzzyy1@proton.me