Your files are private

The short version

All 527 converters on this site 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 anywhere in FileTools360 to send it to.

What FileTools360 stores

Signed out, everything below lives in your browser's localStorage and nowhere else. Signing in adds a second copy of two of them to an account, which is described after the list.

• 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.
• 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.

Clearing your site data removes all of it from this device, at any time, from your browser settings.

What an account stores

An account exists so favourites survive a new device. It holds four things, and this is the complete list:

• Your email address, plus a display name and profile picture if the provider you signed in with supplied them.
• The slugs you starred — heic-to-jpg, and the date you starred it. These are held only against your account, never in this browser: sign out and they are gone from the screen, because they were never on this machine. That is deliberate — a star is a statement about you, not about the computer you happened to be sitting at, and leaving one behind on a shared machine is a small thing to leak but a needless one.
• A count per tool — which converter, how many files, and when. These rows are deleted after seven days by a job that runs nightly.
• A plan row, which currently says free for everyone.

What is not in it: no file, no file name, no file size, no thumbnail, no extracted text. A conversion runs on your device and the account never learns anything about it beyond which tool was opened and how many files went through it. Your browser stays the source of truth — the account is a copy, so signing out loses nothing and the site works identically without one.

Getting it deleted

Signing out and clearing your site data removes every local copy immediately, from your browser settings or from the controls on this page. The account copy is separate: the tool counts expire on their own after seven days, and your email address and starred slugs stay until the account is deleted.

Deleting an account that the in-app button cannot reach has to be done by hand, because doing it from the browser would mean shipping a key that can read and delete every other account. Write to admin@bloxleads.com.au from the address the account is registered to and it will be removed. Either way, an account holds what the list above describes and nothing more — no file, and nothing about any file.

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 to convert anything. Every tool works signed out, with no email address and no personal detail. Starring a tool is the one feature that asks you to sign in, because a favourite that cannot reach your other devices is not much of one.
• It shows advertising, supplied by Google AdSense, on the converter pages and the guides — never inside the workspace where you are converting something. The ads are chosen by Google, not by us, and Google sets its own cookies to do it. The switch below covers advertising as well as analytics, and it is worth being exact about what it does, because this is weaker than the analytics promise and rounding it up would be dishonest. Google's loader is on every page — Google requires it there to review the site at all — so turning ads off does not stop it loading. What it does is refuse consent for advertising storage and personalisation, so nothing about you is stored or profiled. One cookie survives that refusal and it is fair to name it: Google writes a short-lived cookie called test_cookie on doubleclick.net whose entire value is the words “CheckForPermission” — it exists to test whether cookies work at all and identifies nobody. You may still see an advert; it will be chosen from the page you are on rather than from anything remembered about you.
• 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 fetched at all rather than merely asking it to behave.
• It does not send anything about your files to the analytics described below — not names, not sizes, not contents, not a thumbnail, not a single byte. Which converter page you opened is a different matter: each one has its own address, so a page view records it like any other URL. That is the page, never the file on it.
• It does not use your files to train anything.
• It does not sell or share your files or your account details. Advertising is a separate matter and is described above: Google sees which page you are on, as any ad network does, and never sees anything about a file on it. What it retains is the short list above: your email address and your starred slugs for as long as the account exists, and tool counts for seven days. It never receives a file, so there is no file to retain.

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.

FileTools360 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 unless you turn it off. The switch below turns it off for this browser, permanently, and when it is off the Google script is never fetched — not loaded and told to behave, never requested. You can confirm that in your own network panel rather than taking this paragraph's word for it.

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. One honest detail: that policy is fixed when the site is built, so it is the same header for everyone. Turning analytics off stops the browser from ever asking Google for anything — which you can watch happen — but it does not narrow the header back down.

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

Bringing a file in from somewhere else

As well as choosing a file from your device, this site can take one from Google Drive and Dropbox. The conversion still happens on your device and the file still never reaches a FileTools360 server. What is different is that the file travels over the network from the service you picked, so this page has to be allowed to contact that service.

You sign in to those services in their own window, never on this site, and no password or lasting access token is stored here. Where an access token is needed to fetch the file it is held only for the length of the download and is never written to disk. Nothing about the file — its name, its size, its contents — is sent to this site or recorded anywhere by it.

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.

Who is responsible for this

FileTools360 is published by BloxLeads Pty Ltd, an Australian company registered at 1/285 Guildford Road, Guildford NSW 2161, Australia. It is the data controller for the small amount of information described above — which, to be clear about what that covers, is an email address and a list of starred tools if you make an account, and nothing whatsoever about the files you convert.

Privacy questions, access requests and complaints go to admin@bloxleads.com.au. Everything above describes what the code on this site actually does, and most of it you can verify in your own browser rather than taking on trust. See Contact for the rest.