Privacy policy

Invisibles browser extension and web app · last updated 23 August 2026

The short version

Invisibles collects nothing, stores nothing and transmits nothing. There is no server, no account, no analytics and no storage of any kind. The text you paste exists in the page while you are looking at it and is gone when you close it.

What data is collected

None. Nothing is gathered, retained, transmitted or sold. Invisibles never collects, transmits or sells:

How it works instead

You paste text into a box. The script scans that string for characters in its table, marks where they sit, and builds a cleaned copy. All of it happens in the page you have open, in your own browser, using ordinary JavaScript on a variable in memory. Nothing is written anywhere and nothing is sent anywhere.

Closing the tab is the whole of the deletion process, because there is nothing to delete.

Storage

None. Invisibles uses no localStorage, no sessionStorage, no chrome.storage, no cookies and no IndexedDB. This is checkable: the source is public and those APIs appear nowhere in it.

Permissions

The extension declares one UI permission: sidePanel. That permission lets Chrome open Invisibles beside the current tab when you click its toolbar icon. The extension declares no host_permissions, so it cannot read the pages you visit. It has no access to your tabs, history, cookies or files.

Chrome Web Store Limited Use

Invisibles' use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. The extension does not collect, transfer, sell or use Chrome API data for advertising, credit decisions or any purpose unrelated to its visible text-cleaning feature.

Network access

The text-processing code makes no network requests. It contains no remote code, no third-party libraries, no fonts loaded from elsewhere and no tracking scripts. The GitHub and Ko-fi links open those sites only after you click them; pasted text is never included in either navigation.

The same is true of the web app at cig13zs.github.io/invisibles, which is one HTML file and one script. GitHub serves that page and will see the request for it in the way any web server sees a request, which is covered by GitHub's privacy statement. Nothing you paste into the page is part of that.

Reporting a miss

There is a "Report a miss" link in the side panel, for when a hidden character slips past or something gets flagged that should have been left alone. It does nothing until you press it. When you do, it builds a short note, copies it to your clipboard and opens a pre-filled GitHub issue so you can read it, edit it and decide whether to submit it.

Your text is not in that note. It contains the code points that were flagged (for example "U+200B Zero-Width Space x3"), the length of what you pasted, and how many of those characters were non-ASCII. That is enough to add a missing rule and useless to anyone reading it as content. Nothing is gathered in the background and nothing is ever sent on its own.

Third parties

No data is shared with third parties, because none is collected. Invisibles is not affiliated with, endorsed by or connected to OpenAI or any other AI provider.

What it does not claim

Invisibles removes invisible characters. That is not the same as removing an AI watermark: the statistical patterns in word choice and sentence structure are a separate thing, and no character cleaner touches them. If a tool tells you otherwise, it is overselling.

Changes

If this policy changes, the updated version appears at this address and the date above changes. The source is public, so any change in behaviour is visible in the commit history.

Contact

Questions or reports: open an issue on GitHub.

← Back to Invisibles