Privacy
Your files are processed in your browser. They are never transmitted to us, because there is nothing to transmit them to.
What we collect
No accounts. No cookies. No analytics script, no tracking pixel, no third-party embeds of any kind. There is no JavaScript on this site that reports anything about you to anywhere.
Our host records standard server logs — the page requested, an approximate region, a timestamp. We use those to know which pages people read. They contain nothing about the files you process, because the files never reach a server.
Feedback you choose to send
The suggestion box below a tool is optional. If you submit it, the tool name and the comment you wrote are sent to us by email so we can decide what to improve or build. Do not include a file, password, or other sensitive information in the comment. The feedback service accepts text only and cannot receive the file being processed by the tool.
To limit automated submissions, the service turns your IP address into a keyed, one-way value and keeps only recent delivery timestamps for a rolling 24-hour window. The raw IP address is not stored with the feedback or included in the email. Cloudflare delivers the email; no advertising or analytics service receives it.
Your files
Every tool on this site reads your file in the browser tab you have open. It is not uploaded, not queued, not scanned, and not stored. Close the tab and it is gone.
You do not have to take our word for this. Here is how to verify it yourself in about thirty seconds, using a tab your browser already has.
The same distinction is measured across 25 services in the Converter Privacy Index. CreatorValet is included under the same method and failure rules.
Tool processing exceptions
There is none today. Every tool on this site runs entirely in your browser, and you can confirm that on any of them without taking our word for it.
Some planned tools will need to fetch a public web address that you type in — checking a redirect, reading a sitemap, validating a link preview. Those necessarily involve a request. When the first one ships it will say so on its own page, this section will name it, and the date above will move.
The distinction is whose material it is. Fetching a public URL you supplied is not the same as uploading your private file. We keep no log of which addresses are fetched and store no part of the responses.
Fonts and code
Fonts, scripts and any WebAssembly modules are served from this domain. Nothing is loaded from a content delivery network belonging to someone else, which means no third party learns that you visited.
Changes
If this ever changes in a way that affects your files, it will be stated plainly here and on the affected tool, not buried in a revision note.
Last revised . A policy without a date is a policy you cannot check for movement — which is the first thing we look for when reading someone else's.