How our tools keep your files private
Your files are not uploaded. The tool comes to your file, not the other way round. Here is what that means, how you can check it, and the small amount of data we do keep.
Last updated
The short version
- Files stay on your device. PDF, image, video, audio and text tools run inside your browser tab. We never receive your files.
- Numbers stay on your device. Calculators do the maths in your browser. We do not log what you type.
- We keep very little. Only what you choose to send us: a "Was this helpful?" vote, a comment, a contact message or an email address for alerts.
- Ads pay for the site. Google ads may use cookies, with your consent where the law requires it. Our own code sets no tracking cookies.
What happens when you add a file
When you open a tool such as Merge PDF or Compress Image, your browser downloads the tool's code from us, the same way it downloads any web page. After that, everything happens on your computer or phone:
- You choose a file. Your browser reads it into memory. It is not sent anywhere.
- The work runs in a Web Worker, a background thread inside your browser tab. That keeps the page responsive while a big PDF or photo is being processed.
- Heavy jobs (image compression, video conversion, text recognition, background removal) use WebAssembly. It lets your browser run fast, compiled code, the same kind of code desktop apps use, inside the safety of the tab.
- The result is built in memory and saved straight to your device when you press Download.
Because nothing is uploaded, there is no upload wait, no file size limit set by a server and no copy of your file on someone else's computer. The trade-off is that very large files depend on your device's memory, and an old phone is slower than a desktop.
Check it yourself
You do not have to take our word for it.
- Watch the network. Open your browser's developer tools (F12 on most computers), choose theNetwork tab and run a tool. You will see the tool's own code load, but no request that carries your file.
- Go offline. Open a tool and process one file, so its code is loaded. Then turn off Wi-Fi or mobile data and try another file. Most file tools keep working, which they could not do if they needed our server.
Things the tools do download
A few tools need extra building blocks the first time you use them. These are downloads to your device; nothing about your file goes the other way.
- AI models for the background remover come from public model hosts such as huggingface.co and cdn.jsdelivr.net. They can be tens of megabytes, so your browser keeps them for next time.
- Text recognition data for image to text and OCR: one language pack per language you pick.
- Tokenizer files for the LLM token counter.
What is kept in your browser
Some small things are saved in your own browser so the site remembers your choices. They never leave your device, and clearing your browser data removes them.
| What | Where | Why |
|---|---|---|
| Light or dark mode | Local storage | So the page opens in the colours you picked. |
| Recent and favorite tools | Local storage | So the tools you use most are one click away. |
| Tool settings (for example compression quality or currency) | Local storage | So you do not set them again each time. |
| Text in some text tools and invoice drafts | Local storage | So a refresh does not lose your work. Clear the box to remove it. |
| A file passed with "Continue with this file" | IndexedDB | Hands a result to the next tool. Deleted as soon as the next tool opens it, or after 10 minutes. |
| The site's own scripts and styles | Service worker cache | Makes repeat visits faster. It holds our code only, never your files or pages you viewed. |
Calculator "share" links put your inputs after the # in the link. Browsers never send that part of a link to a server, so the numbers only travel where you send the link.
What we store on our server
Our server stores only what you actively send us, in a Cloudflare D1 database:
- Feedback: when you answer "Was this tool helpful?", we save the tool's name, your yes or no, the page address, the time and any comment you choose to write. Nothing in it identifies you, and we use it to fix and improve tools.
- Contact messages: your name (optional), email address and message, so we can reply.
- Email alerts: your email address and the topics you chose, until you unsubscribe.
- Spam protection: to stop floods of fake votes and messages we count requests per visitor for a short time. We store a scrambled, one-way code made from your IP address, never the address itself, and the count expires on its own.
Cookies, analytics and ads
KazamTools is free because of advertising. Ads are shown by Google AdSense, and Google and its partners may use cookies to show and measure them. In the European Economic Area, the UK and Switzerland you are asked before advertising cookies are used, and you can change your mind later. Ads never see your files: they load around the tool, not inside it, and the tool never shares your data with them.
We count visits with Cloudflare Web Analytics, which sets no cookies and does not follow you across sites. Our own code sets no tracking cookies. Calculator widgets that other websites embed show no ads at all.
If a tool ever needs a server
Every file tool on the site today runs in your browser and says so in a badge under its title. If we ever add a tool that cannot work that way, its page will say so clearly with an amber "processed on our server" badge, files will travel over an encrypted connection and they will be deleted within one hour.
More detail
The legal details are in our privacy policy and cookie policy. To see how we build and test the tools, read our methodology. Questions? Contact us.