Your files are private

The short version

All 521 converters in this build run entirely inside your browser. Your file is read into your device's memory, converted there, and handed back to you. It is never sent to a server, because there is no server-side conversion in this deployment to send it to.

What FileTools360 stores

In your browser's localStorage, and nowhere else:

• Your theme choice — light, dark or system.
• Recently used converters — the converter's name and how many times you have used it. For example heic-to-jpg and a count. Never a file name, never file contents, never a thumbnail.
• Favourites — a list of converter slugs you have starred.
• Per-converter settings — so the quality slider stays where you left it.
• Your own totals — how many files you have converted in this browser and how many bytes they came to, for the counter above the footer. Two numbers. Never a file name, never a format, never anything about a particular file.

All of it stays in your browser. Clearing your site data removes it completely, and nothing is synced anywhere. You can clear it from your browser settings at any time.

The one thing that is sent

When a conversion finishes, two numbers are sent to this site: how many files were in that batch, and how many bytes the results came to. They are added to the site-wide total shown above the footer. That is the only request this site makes that is not fetching the page you asked for or the conversion engine that runs on it.

What it is not: it carries no file name, no file type, no identifier, no cookie and no address beyond the one every web request necessarily has. It is sent after the conversion has already finished, so it cannot slow anything down, and it is sent to this site only — the Content-Security-Policy forbids the page from connecting anywhere else, which is why the measurement on the converter page can promise that nothing left this site while your file was being converted.

Your file is not involved. The server has no way to receive one, and adding a counter did not change that.

What FileTools360 does not do

• It does not upload your files.
• It does not require an account, an email address, or any personal detail.
• It does not run advertising scripts, and nothing here is used to sell you anything.
• It sets one cookie, for Google Analytics, so we can see which converters people actually need. You can switch that off below, and switching it off stops the script being loaded at all rather than merely asking it to behave.
• It does not send anything about your files to the aggregate analytics described below — not names, not sizes, not contents, not even which converter you used.
• It does not use your files to train anything.
• It does not sell, share or retain your data, because it never receives it.

Analytics

FileTools360 measures how many people visit and how fast pages load, using Vercel Web Analytics and Vercel Speed Insights. Both are cookieless, and neither can see anything about the files you convert.

This deployment also uses Google Analytics. It records the pages you visit so we can see which converters people actually need, and it sets one cookie to recognise a returning browser. It is on by default; the switch below turns it off for this browser, and when it is off the Google script is never fetched at all.

Google Analytics cannot see your files. That is not a policy — a conversion happens in a Web Worker on your device, and the file is never part of any page view. What Google receives is the same kind of information any web page sends: a URL, a referrer, an approximate location and a device type.

What is collected:

• Page views — the page path, the referring site, your country, and coarse device information such as “mobile” or “Chrome on Windows”.
• Loading performance — how long a page took to become visible and interactive, reported as timings against the page path.

What is not collected:

• The Vercel measurements set no cookie and store no identifier. Google Analytics sets one, unless you have turned it off below.
• Repeat visits are counted using a hash derived from your request that is re-salted every day, so you cannot be followed from one day to the next, or across other websites.
• Nothing about a conversion is reported: not the file, its name, its size, its type, nor whether a conversion happened at all. The scripts run on the page; the conversion runs in a worker they never touch.

An honest note about how that is enforced. The Vercel scripts are served from this site's own origin, so they need no exception. Google Analytics does: the Content Security Policy on every page had to be widened to let the browser reach Google's servers. Your files are still never uploaded — they are converted in a worker and never leave your device — but with Google Analytics enabled, that is enforced by how the software is built rather than additionally by the browser refusing every outside connection. Everything except Google and this site is still blocked outright.

If you would rather not be counted, any content blocker stops both scripts, and the converters keep working normally.

Third-party requests

A converter page loads code and assets from this site's own origin, with Google Analytics as the single exception, and only once you have allowed it. That includes the WebAssembly engines — the FFmpeg core for video and audio, the WOFF2 compressor for fonts, the archive reader — and the fonts used in the interface, which are self-hosted at build time rather than requested from Google. The two analytics scripts above are also served from this origin, though the measurements they send are processed by Vercel, this site's host.

Two features fetch additional data, both from this site and both only when you use them:

• OCR downloads a language model the first time you run it, then caches it in your browser.
• PDF export of non-Latin text downloads a Unicode font so characters outside Latin-1 render correctly.

Passwords you type

The Unlock PDF tool asks for the document's password. That password is used in your browser to open the file and is never transmitted, logged or stored — not even in localStorage. FileTools360 does not attempt to crack, guess or bypass PDF encryption; you must already know the password.

Safety checks on the files you add

Because files are processed locally, the risk is to your own browser tab rather than to a shared server. FileTools360 still validates aggressively:

• Files are identified by their actual bytes, not their extension, so a renamed file is never handed to the wrong decoder — and you are shown a warning when the name and the contents disagree.
• Archive extraction refuses entries with absolute paths or .. segments, caps the number of entries, and stops when an archive expands far beyond a safe ratio — the signature of a decompression bomb.
• Every conversion has a size limit, checked before any work starts, so a file cannot silently exhaust your browser's memory.
• File names are stripped of directory separators, control characters and bidirectional override characters before being used for a download.

If server-side conversion is ever added

Some conversions genuinely need a server — legacy binary Office formats are the clearest example. Rather than quietly routing those through a server today, FileTools360 lists them as unsupported with a specific reason. If server-side processing is added later, it will be labelled on the converter itself, before you choose a file, so the distinction is never hidden.

Questions

This is an independent project rather than a commercial service, so there is no legal entity or registered data controller behind it. Everything above describes what the code in this build actually does. See Contact for details.