filetity

Privacy

All 70 tools run inside your browser tab. Your file is read from your disk into memory on your own machine, worked on there, and handed back. It is never uploaded, because there is no server here to upload it to.

The short version

  • No account, because there is no account system.
  • No cookies. Checked on the live site on 6 September 2026: document.cookie is empty.
  • Your files are never sent anywhere, and nor are their names.
  • Nothing you convert is stored, by us or by anyone.

What does leave your browser

Three scripts count usage. None of them receives a file, a file name, or anything you typed. A page that says only “we use analytics” is asking to be taken on trust, and this site’s whole argument is that you should not have to, so here they are by name.

PostHogEU servers (eu.i.posthog.com)
A page view, and one event when a tool finishes: the tool's name, how long the work took, the input size in bytes and which options you chose.
Session replay, autocapture, heatmaps, surveys and console recording are all switched off in our code. Nothing records your screen, your clicks or your file names.
DataSlowA server we run ourselves
The same completion event, with the tool's name only. It is here so the north-star number does not depend on a single vendor.
No profile, no cross-site identity, nothing about the file.
CloudflareThe network in front of this site
Page load timings, injected by Cloudflare rather than added by us. Standard web performance data.
No cookie, and nothing about what you did on the page.

What is kept in your browser

Nothing here leaves your device, and clearing site data removes all of it.

filetity-theme
Whether you chose light or dark. Ours, and the only thing we store on purpose.
ph_… and _dataslow
A random id each analytics script gives your browser so two visits are not counted as two people. Not a name, not an email, not linked to anything.
The service worker cache
A copy of the pages and engines you have already used, which is what lets the tools keep working with the network off.

A correction, on the record

On 6 September 2026 we read this site’s own network traffic and found PostHog session replay switched on in the project settings. Replay records the text on a page, and a tool page shows the name of the file you opened. So file names were reaching PostHog. No file content ever did, and the processing was local throughout, but the names were more than anyone reading “processed locally” would expect to give away.

It is off, along with autocapture, heatmaps, surveys and console recording, and it is off in the code rather than only in a dashboard so it cannot quietly come back. This paragraph stays because a privacy page that only lists good news is not evidence of anything.

Check it yourself

Open your browser’s network tab, drop a file on any tool, and watch. The engine downloads once if that tool needs one, and after that the request list stops moving while the work happens. The full walkthrough is here, including what a file actually does step by step, and we ran the same test on four other PDF sites.

Asking us something

Write to support@filetity.com. There is no account to delete and no file of yours to remove, so most requests of that shape have nothing to act on, which is the intended result rather than an evasion.

Last checked 6 September 2026.