Your files stay yours.

The page reads the file straight off your device using the browser’s file API. All the work — decoding, re-encoding, rebuilding a PDF, reading text off a scan — happens in the tab you are looking at. The finished file is created in memory and handed to your browser’s download manager.

You can check this yourself: open the network tab, run any tool, and watch. No request carries your file.

Two things are fetched, and both are program code rather than your data:

• The PDF engine and its font data, served from this domain, the first time you use a PDF tool.
• The text-recognition engine for OCR. The engine is served from this domain; the language model (about 15 MB for English) comes once from the public tessdata CDN and is then cached by your browser. The picture you are reading text from is never part of that request.

There is none. All 99 working tools run on your device. If a tool ever needs a server it will be labelled as such on its own page, the file will be deleted immediately after processing, and it will never be used to train anything.

Three things, and none of them are your files: a random account identifier in a cookie, how many operations that account has run, and the credit balance attached to it. An activity list records which tool was used and when — the tool’s name, not your filename.

If you buy credits, the payment happens inside the provider’s own window. FixIt never sees your card or UPI details; it receives a signed confirmation and an order reference, and that is what it stores.

You can use everything here without an account, and nothing above changes if you do. Signing in is optional and only exists so credits follow you between devices; it is handled by Clerk, who hold the email address or social login you sign in with. FixIt stores their user id against your account and nothing else about you.

When you set a password on a PDF, it is used to encrypt the file in your browser with AES-256. It is not transmitted or stored anywhere. If you lose it, the file cannot be opened again — not by you, and not by us.

Removing a password requires you to know it. FixIt will not guess, brute-force, or bypass a password on a document you cannot already open.

There is nothing to delete. Your files were never uploaded, so no copy exists to remove. Close the tab and the working copy in memory goes with it.

To clear the small amount that is stored — the account cookie, your usage counters and the activity list — clear this site’s data in your browser settings. That also gives up any unused credits, because the recovery code is the only thing linking them to you. Copy it from your account page first if you want to keep them.

This site carries Google AdSense, and its script runs on every page. That is how it is paid for. It is worth being exact about what that does and does not mean.

It does not see your files. Every tool runs in your browser; nothing you open is uploaded, so there is nothing about it for an advertiser to receive. The ad script cannot read what a tool is working on, and the security policy this site sets forbids any script from sending a file anywhere.

It does see that you visited. Google receives the page address, your IP address and the usual details a browser sends, and sets its own cookies to choose and measure adverts. What it collects, and how to control it, is governed by Google’s advertising policy, not by this one. A content blocker stops it, and the tools work exactly the same with it blocked.

• Store your files
• Require an account or email address
• Use anything you process to train a model
• Send your file to a third-party API
• Track what you upload

Because the work happens on your device, the limits are about what a browser tab can hold in memory — not about pushing you to upgrade:

• Up to 200 MB per file
• Up to 100 files at once, 500 MB in total
• A run is stopped if it goes 3 minutes without progress

A very large file on an older phone can still run out of memory. If that happens you get a plain message saying so, not a crash — and doing fewer files at a time usually fixes it.