Privacy Policy

When you focus a text box, comment field or editor on a page, the extension reads the text in that field so it can underline AI clichés. It does not read the rest of the page, other tabs, your browsing history, or your bookmarks.

Password fields are never read. Neither are search boxes, code editors (Monaco, CodeMirror, Ace), or any element marked data-slop-ignore.

In your browser. The full detection catalogue ships inside the extension, so finding a cliché involves no network request at all. You can confirm this in DevTools: type into any editor with the Network tab open and nothing is sent.

Only when you ask for it. Specifically:

• You click Smash the AI Slop or a whole-draft rewrite. The draft is sent to our API, rewritten, and returned. It is used for that request only.
• You click Open this draft in Studio. The draft is passed to the Studio tab through the extension's own storage. It is not put in the URL, so it does not reach browser history or server access logs.

Applying an individual suggestion, using Fix all, and everything the underlines do are local operations. They send nothing.

Google Docs paints text to a canvas, so the extension cannot read it from the page. It instead requests the document's own plain-text export from Google, using the session you are already signed into. That text is analysed in your browser and is not sent to us unless you request a rewrite.

Held in the extension's local storage and never transmitted:

• Your account email, plan, and API key, once you connect an account
• Words you chose to never flag again
• Sites you switched the extension off for
• Where you dragged the panel, and whether you have seen the first-run tips

Your password is never stored by the extension, and never passes through it when you use one-click connect.

For an account: your email address, a hashed password (scrypt, so we cannot read it), your API key, your plan, and a per-day count of rewrites for quota enforcement.

Drafts sent for rewriting are processed to produce the result and are not retained as a stored record. If a plan uses an external model provider, that provider processes the draft under its own terms.

No analytics, tracking pixels, session recording, fingerprinting, advertising identifiers, or third-party trackers. None are present in the extension or the site. We do not build a profile of you and we do not sell or share data with anyone.

The extension requests access to all sites because the editor you write in could be on any of them: LinkedIn, Gmail, your CMS, an internal tool. Requesting them individually would mean the extension simply failed to work wherever we had not thought of.

Because that access is broad, there is a per-site switch: open the extension on any page and turn Run on this site off. Nothing is read there afterwards. You can also disable underlining everywhere from the same panel.

Sign out in the extension to remove the account details held on your device. To delete your account and its server-side record, email privacy@removeaislop.com from the address on the account.

If this policy changes in a way that affects what we collect, the date above changes and the change is described in the product changelog.