Slop ReaperYour feed, your choice.
Slop Reaper, published by Ameer Rayan, has one purpose: help you hide LinkedIn posts that Jev estimates were written by AI. This policy describes the extension and its included analysis service. Included analysis is active for approved test builds; public store release is pending.
What leaves Chrome
When filtering is on, the extension extracts eligible post text from your LinkedIn feed. For included checks, it sends that text to the publisher's service hosted on Vercel, which forwards it through OpenRouter to TypeSafe AI's Jev model. Included checks require your explicit agreement first.
We do not separately send your LinkedIn login, cookies, author profiles, comments, reactions, or browsing history. A post's text can itself contain names, links, or other personal information. Short posts are skipped and long text is bounded by the extension.
How we use it
Post text is used to return an authorship classification. Our service code does not intentionally save or log post text or model responses. Decisions are cached temporarily in the extension's service worker. There is no advertising or analytics code in the extension or this website.
Included requests also carry a random installation identifier. The hosting platform receives your network IP address. Our service converts the IP and installation identifier into daily salted hashes for fair-use limits. Redis stores these counters for up to 48 hours after their last update; aggregate monthly allowance counters expire 45 days after their last update. We do not intentionally store raw IP addresses in Redis. Hosting and model providers can process network or request data under their own policies.
What stays on your device
Your settings, consent choice, random installation identifier, running hidden count and fingerprints used to avoid counting a post twice are stored locally in this Chrome profile, not synced. Fingerprints are hashes, not saved post text. These local records remain until removed with the extension or its local data. Restoring a post does not reduce the lifetime count.
If you choose an advanced personal-key connection, your key is stored locally in Chrome and requests go directly to the selected Vercel AI Gateway or OpenRouter endpoint, then to Jev. Those requests use your provider account and billing. The publisher's included service does not receive that personal key. Local extension storage is not an encrypted vault.
Your controls
Turn Filtering off to stop new analysis requests. With included checks, choose Stop sharing post text in Connection settings to withdraw consent and cancel pending extension checks. Already transmitted requests cannot be recalled. You can reveal any hidden post. Uninstalling removes the extension's local data; already-created anonymous allowance counters expire automatically.
Providers and limited use
We do not sell data, use it for advertising, or use it to build a user profile. Use and transfer of information received from Chrome APIs will comply with the Chrome Web Store User Data Policy, including its Limited Use requirements.
External processing is covered by Vercel's privacy policy, OpenRouter's privacy policy, TypeSafe AI's privacy policy, and Upstash's privacy policy. We do not promise that every external provider offers zero retention.
Questions or problems
See Help for troubleshooting. For pre-release builds, contact the publisher who supplied the build. After publication, use the publisher contact shown on the Chrome Web Store listing. Do not include API keys or private post text in reports.