Privacy policy

Last updated: 2026-09-20

1. Who we are

Slop Alarm is a personal, non-commercial open-source project by Damian (@damienen) ("we", "us"). This policy covers the Slop Alarm Chrome extension and this website. Questions or requests: open an issue at GitHub issues.

2. The short version

Slop Alarm has no server and no account. The extension collects nothing and sends nothing to us. When you check text, it is sent from your browser directly to the AI provider you chose, TypeSafe or OpenRouter, using an API key you supply and control. We, the developer of Slop Alarm, receive no text, no URLs, no analytics, and no identifiers, because there is nothing on our side to receive them.

3. What stays on your device

The extension keeps the following only in this browser's local storage (chrome.storage.local), never on any server:

Your settings, such as whether auto-scan is on and whether highlighting is enabled.
The API key you paste in, for TypeSafe or OpenRouter.
Your list of sites excluded from auto-scan.
A cache of scores, keyed by a SHA-256 hash of the checked text, not the text itself.
Daily usage counters, used to enforce your auto-scan limit.

To erase any of this: use "Clear local data" in the extension's settings to wipe the cache and counters, remove your key from settings to stop it being used, or uninstall the extension to remove everything Chrome stored for it.

4. What leaves your browser

When you run a check, two things leave your browser: the text you asked to check, and your API key, sent as the request's authorization header. Both travel over HTTPS to the single provider you selected in settings, either TypeSafe (typesafe.ai) or OpenRouter (openrouter.ai). That provider then processes the request under its own terms and privacy policy, which we do not control. Review the provider's own policy before you paste in a key; we do not summarize or quote it here because it can change.

5. What is never sent anywhere

The page's URL or title.
Your browsing history.
Cookies.
The contents of forms you fill in, separate from any text you deliberately select or open for a check.

6. Auto-scan safeguards

Auto-scan is off by default and only runs after you turn it on and grant the extension permission to read page content. When it is on:

It skips any page that shows a password field or a payment card field.
It skips webmail, online document editors, and banking-style hosts by default.
It skips local and non-public addresses, such as localhost or a raw IP address.
It honors your own exclusion list, set in the extension's settings.
It has a daily limit, 100 checks by default, so it cannot run up a bill on its own.

7. This website

This website is a set of static pages. It sets no cookies and runs no analytics. The hosting provider may keep standard server logs, such as request timestamps and IP addresses, as part of its own infrastructure; we do not have a separate analytics or tracking layer on top of that.

8. Children

Slop Alarm is not directed at children under 13, and we do not knowingly collect data from them. Since the extension and this website collect no personal data on our end, there is no such data for us to hold or remove; a request about a child's use of the extension is best addressed by clearing local data or uninstalling on the device in question.

9. Your rights

Because we hold no personal data about you, there is nothing on our end for us to access, correct, export, or delete. Everything the extension stores lives in your own browser, under your own control, as described in section 3. If your request concerns data held by your chosen provider, such as request logs kept by TypeSafe or OpenRouter, that request goes to the provider directly, under its own privacy policy.

10. Chrome Web Store data disclosure

The extension's use of data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

11. Changes to this policy

If we make a material change to this policy, we will update the date at the top of this page and, for significant changes, note it in the extension's release notes.

12. Contact

Questions or requests: open an issue at GitHub issues.