SlopScreen privacy policy

Last updated August 28, 2026.

The short version

When you click scan, the text of the pull request or issue you are looking at is sent over HTTPS to the SlopScreen scoring server, scored, and returned. It is not stored, not logged in full, and not shared. That is the whole product.

What is sent, and when

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.

What is kept

The scoring server keeps a per-day counter per meter id (deleted within 48 hours) and standard short-lived infrastructure logs. Scanned text is processed in memory and discarded. No database of scanned content exists.

Batch scans

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 SlopScreen's servers.

Payments

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 SlopScreen, and this policy will be updated first.

What SlopScreen never does

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.

Contact

Questions: Munzzyy1@proton.me