What OmniWebTools stores, what it never collects, and where your data goes.
Short version: the tools run entirely in your browser. Whatever you paste, type or drop into OmniWebTools stays on your device, and we cannot see it. An account and an API are there if you want them, and neither is needed to use any tool.
Nothing you enter into a tool. The processing happens in JavaScript on your own machine, so your input is never transmitted to us and never stored on a server. Using the tools takes no account, and we never ask for your name, email or payment details to use the site.
The only thing we collect is anonymous usage statistics: which pages are opened and which tools get used, never what you do with them (see Usage statistics below). If you choose to create an account or call the API, see Accounts and the API; those are the only parts of OmniWebTools that hold anything of yours on a server.
The webcam and microphone tests ask for access only when you press their start button, and your browser shows its own prompt first. The picture and sound go from your device to the page and nowhere else: nothing is recorded to a server, a recording you make to hear yourself back stays in memory and is gone when you leave the page, and the camera or microphone switches off when you stop the test or close the tool.
Files work the same way. Photos you compress, convert or clean, HEIC images you convert and PDFs you merge, split or rearrange are read and written by your own browser. They are never uploaded, never added to your recent inputs, and the results are files your browser saves for you.
A few things are saved in your own browser's local storage so the site remembers your setup between visits. They stay on your device and are readable only by this site:
Nothing else in that list is sent anywhere, ever. Clearing your browser's site data for this domain removes all of it (signing you out in the process), and nothing is recoverable afterwards, including by us, since we never had a copy.
Some tools encode your input into the page URL so a link reproduces what you were looking at. That encoding happens in your browser and the link is only shared if you copy it and send it to someone. Be aware that a URL containing sensitive input is as sensitive as the input itself, so treat it the way you would treat the data.
The page talks to a single outside service. It sees the request itself, which carries your IP address, your user agent and the page you requested it from. But it never sees anything you type into a tool, because your input is never part of those requests:
There is no advertising and no third-party cookies.
Everything else is served from this site: every tool's own code, React (the library the interface is built with), and the larger libraries a few tools load on demand, such as the QR encoder, the SQL formatter, the PDF libraries and the HEIC decoder.
To learn which tools are useful, the page reports anonymous usage statistics to our own server (api.architep.com). There are only two kinds of report:
Each report carries the page address and the address you came from, both with any query stripped, and your browser's user agent string. It sets no cookie, stores nothing on your device, carries no identifier, and never includes anything you type into a tool. The statistics are used only as totals, never to identify or follow anyone.
Everything above describes the site as you meet it: signed out, working locally, with nothing of yours leaving the page. That is how OmniWebTools works by default and how most people use it.
Two things are available for people who want them, both optional. They work differently from the local tools, so it is worth being exact about the difference:
The API keeps none of what you send it. Your input and the result are processed in memory and dropped the moment the response goes back: there is no log of request bodies, no copy retained for debugging, and nothing left for anyone to retrieve later. The single thing recorded against a key is how many requests it has made, which is enough to enforce rate limits and the fair usage policy, and nothing beyond that.
Neither is required for anything. Not signing in, and never calling the API, leaves the site exactly as the rest of this policy describes it.
OmniWebTools sets no cookies: not for the tools, not for your preferences, not for signing in and not for statistics. Everything the site remembers uses local storage, which, unlike a cookie, is not attached to requests automatically and never rides along with a page load.
Signing in is cookieless and sessionless. Your account is held by a token kept in local storage, which the page sends only on the API calls you make. There is no session on our side to track you with, nothing that follows you between pages, and nothing that expires out from under you. Signing out, or clearing your site data, deletes an deauthorizes the token and that is the whole of it.
The site is a general-purpose collection of tools and is not directed at children. Since we collect no personal data from anyone, we hold none from children either.
Material changes to this policy (anything that alters what leaves your browser) are called out on the site rather than quietly edited in.
Questions about this policy: [email protected].