Privacy Policy

What this policy covers

This page describes what Bench does with information when you load a page or use a tool, and what it does not do. It covers the whole site: every tool page, this one, and the pages around them.

It is written by the person who built the site, about the site, and it is written to match what actually happens rather than what a policy template would like to be true.

There is nothing to sign up for

There is no account to create, no sign-up form, no login, and nowhere on the site that asks for your name or your email address. Nothing you do here is attached to a profile, because no profile exists: no visitor identifier, no session, no fingerprinting script.

Cookies, and the one preference the site keeps

The site does not set cookies. Not a session cookie, not an analytics cookie, not a consent cookie, because there is nothing to consent to. There is no cookie banner here for the same reason there is no cookie.

One thing is stored in your browser: whether you prefer the light or the dark theme. It is kept under the key bench-theme in your browser's local storage for this site. That is a preference your browser holds on your behalf, not a cookie. It is never sent to me, no other site can read it, and it exists so that a page does not flash the wrong colours while it loads.

To clear it, open your browser settings and clear site data for this site, or delete the entry in the Application (or Storage) panel of the developer tools, or run localStorage.removeItem('bench-theme') in the console. Removing it changes nothing except that the site goes back to following your system's light or dark preference.

What happens to what you type into a tool

Nothing you type, paste or drop into a tool is transmitted anywhere. Each tool is a script running in the page you already have open: an image is read from your disk into the tab, a password is drawn from the browser's own random source, a JSON document is parsed where it sits.

The pages are also built to run from a file on your own machine. Save a tool page and open it from disk and it still works, which is the most direct proof available that the work is happening in the page.

The typefaces, and the one request that leaves your browser

The site sets its text in three typefaces and loads them from Google Fonts. Your browser therefore makes a request to fonts.googleapis.com and then to fonts.gstatic.com for the font files. That request carries your IP address and your browser's user agent, and Google can see both. It is the only third-party request the site makes.

What I cannot tell you from here: whether the fonts were already in your browser's cache, what Google records, how long it keeps it, or what it is joined to. Those questions are answered by Google's own privacy policy. Anything I wrote down here would be a guess dressed as a fact.

If you would rather no such request went out, a content blocker that blocks fonts.googleapis.com and fonts.gstatic.com will stop it. The site carries on with the fallback typefaces already named in its stylesheet: it looks different and works the same.

Server logs

If you are reading this on the web rather than from a file, the machine serving these pages keeps an ordinary access log: the address the request came from, the time, the page asked for, the user agent your browser sent and whatever referrer came with it. That is how web servers work. It is not something the site switches on, and it is not something the site can switch off.

Those logs are readable by me. I use them to work out what broke when something broke, and for nothing else. How long they are kept is the hosting provider's decision, not mine, and I cannot tell you what it is. Open the same pages from your own disk and no log exists at all.

Advertising, cookies and consent

This site is free to use and is paid for by advertising. Advertising is served through Google, including Google AdSense. This is the only third-party content on the site, and it is the only thing described in this policy that sets a cookie.

Third-party vendors, Google included, use cookies to serve ads based on your prior visits to this site and to other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and other sites on the internet. Those cookies are set by Google, not by this site, and I cannot read them.

Where the law in your country requires it, a consent notice appears before any advertising cookie is set, and you can change or withdraw that choice at any time from the notice itself. You can also opt out of personalised advertising in Google's Ads Settings, and opt out of a third-party vendor's use of cookies for personalised advertising at aboutads.info. Turning personalised advertising off does not remove advertising from the site; it makes the advertising less relevant.

What advertising does not get is anything you put into a tool. No advertising script is given access to the text you type, the image you drop or the document you open, and none of it is ever sent anywhere for an ad to be chosen against it. The section below on what happens to your input still holds exactly as written.

If advertising is switched off

Advertising can be turned off, and there have been periods when the site carried none. When it is off, the paragraph above describes nothing that is happening: no advertising cookie is set, no advertising script is loaded, and the site sets no cookies of its own.

The rest of this policy is written so that it is true either way. Nothing in it depends on whether advertising is running, which is why the sections about accounts, tool input, typefaces and logs read the same in both states.

What this policy does not cover

This policy covers Bench and nothing else. If you follow a link from here to another site, that site's own policy applies from the moment you arrive, and I have no say in it. The same is true of anything you reach from a tool's output.

What the tools will and will not vouch for is a separate question from what happens to your data, and it is answered on the Disclaimer page.

Changes to this page

This policy was last updated in September 2026. When something in it changes, the date at the top of this page changes with it, and the change is written into the section it affects. Changes are noted on this page rather than left for you to spot.

Asking about privacy

If something here is unclear, or if you think it is wrong about what the site actually does, write to moanacrab7610@gmail.com and say so. The contact page explains what else that address is for.