BiasClear sends nothing you type.

• The rules run in the page.Your text is read by the rules inside the page, in your browser. It is never uploaded, and the page keeps no copy. Close the tab and it is gone.
• The page does not send it.No script on the page sends your text anywhere, and the code is public. Every page also carries a security policy that lets it load files only from this site and blocks the usual ways a script sends data to a server (fetch, XHR, beacons and WebSockets: connect-src 'none'). It cannot stop a page from navigating elsewhere; this site’s code never does. You can read the policy at the top of the page source. The site’s tests check that the page’s own scripts use none of these, and the counter on the checker lets you watch.

This site is hosted on GitHub Pages. Like most web hosts, GitHub keeps standard server logs of visits, including IP addresses, and says it stores them for security purposes. BiasClear does not see or control those logs. GitHub’s privacy statement says how GitHub handles them.

The logs record that a page was requested. They cannot hold what you paste, because the page never sends it.

Links to other sites, such as GitHub and the paper’s page, take you to those sites, which have their own policies. Pages here ask your browser not to tell them which page you came from.

On the checker, a counter under the text counts every request your browser reports once the page and its typefaces have loaded. Paste something and watch it stay at 0. Your browser’s developer tools show the same in the network panel. Browser extensions can make requests of their own, and the counter may show some of those too.

The whole site is open source. The code is on GitHub, so anyone can check what it does.

Write to hello@biasclear.com.

If anything on this page changes, the page changes with it, and the change is in the site’s public history on GitHub.