Privacy policy

Files are never uploaded. Every tool processes them inside your browser — video through a WebAssembly build of FFmpeg, images through your browser's own codecs — and the result is produced on your device. No copy is transmitted to us or to anyone else, and we could not access one if we wanted to.

Because nothing is uploaded, there is no retention period to state: we hold no files at any point, and there is nothing for us to delete on request.

You can verify this rather than take our word for it. Open your browser's network panel during a conversion, or disconnect from the internet once the page has loaded — the tools keep working. In the network panel you will see one small request when a tool opens and another when a run finishes: those are the usage counts described below, and they carry the name of the tool and nothing from your file.

The "recently used" list on the home page is kept in your browser's local storage. It contains tool names and the time you used them, and nothing else — no file names, no file sizes, no content. It is never transmitted anywhere, and the Clear button on the home page deletes it immediately.

Your light or dark theme preference is stored the same way, for the same reason: so the page does not flash the wrong colour on your next visit.

The feedback form is the one part of this site that sends anything to a server, and it sends only what you type into it. If you submit it we store your message, the category you picked, the tool page you sent it from, the language you were reading in, your browser's user agent string and the time — in our own database, on our own server.

The email address is optional. Given, it is stored with the message and used only to reply to you; left blank, the message reaches us with nothing that identifies you.

Your IP address is not stored with a submission. To stop a single source flooding the form we store a salted, one-way hash of it instead, which cannot be turned back into an address.

Nothing about any file you have processed is included — not its name, size, type or contents. The form has no access to them.

Messages are kept for as long as they are useful for deciding what to build, and you can ask for yours to be deleted by writing to [email protected].

When you open a tool and when a run finishes, the page sends a short message to our server saying which tool it was, which language you were reading in, and whether it was an open or a finish. Nothing else is sent. It is the only automatic request this site makes about what you are doing.

This exists because every tool runs inside your browser, which means we otherwise have no way of knowing that anything on this site works. Comparing how often a tool is opened with how often a run actually completes is how a tool that is broken or confusing becomes visible — the alternative is waiting for someone to write in, and almost nobody does.

What is stored is a running total, not a record of your visit. Each message adds one to a counter for that day, that tool, that language and the country your request came from; there is no row that represents you, no identifier, no session, and no way to put your opens and finishes back together into a sequence.

Nothing about your file is included — not its name, size, type, contents or how long it took. The code that sends these counts is never given the file.

Your IP address is not stored. It is hashed with a secret salt only long enough to stop one source flooding the endpoint, and then discarded; the country is derived at the network edge before that.

No cookie is set, nothing is read from your device, and none of this is shared with anyone or combined with the advertising described below.

This site is funded by advertising through Google AdSense. Google serves those ads and, in doing so, may set or read cookies and similar identifiers on your device to measure performance, limit repetition and — where you have allowed it — personalise what you are shown.

This is the only third-party code on the site. Google's use of your data is governed by its own policies, which you can read at policies.google.com/technologies/partner-sites. You can review and change your advertising settings at any time at adssettings.google.com, and opt out of personalised advertising there.

Advertising cookies are not connected to your files in any way. Google receives the usual information any website's ad code receives — such as your IP address, browser and the page being viewed — but never the content you process, because that content is never sent anywhere.

If you are in the European Economic Area, the United Kingdom or Switzerland, you are asked for consent before non-essential cookies are set, and you can change or withdraw that choice at any time.

The web server records ordinary access logs — IP address, timestamp, requested URL, browser user agent — as essentially every web server does. These are used to keep the site running and to investigate abuse, and they are not combined with anything else or used to build a profile.

Traffic reaches the site through Cloudflare, which also processes this connection information in order to route and protect the request.

Because we hold no account and no file, there is very little personal data of yours for us to produce, correct or erase. Where the law gives you rights over what we do hold — chiefly server logs — you can exercise them, and you can ask what those logs contain, by writing to [email protected].

If this policy changes materially, the date at the top of this page changes with it.