How AiTools stays private by design

Privacy pages are easy to skim. This post is the short version of how AiTools is built so your files and tokens are not part of a conversion pipeline we operate.

Tools run in your tab

Formatters, converters, and generators execute with client-side code. When you merge PDFs or compress an image, the bytes are read in the browser and turned into a downloadable result there. We are not sitting in the middle as a processing API for those workflows.

What that does not cover

Hosting still serves the website (HTML, JS, CSS). Theme preference may live in local storage. If we add analytics or ads later, those are separate from tool payloads — and we will describe them on the Privacy Policy page. Tool inputs themselves are not uploaded to AiTools for conversion.

Practical advice

• Use JSON Formatter, PDF Merge, Image Compressor, Password Generator, and JWT Decoder when you want local handling.
• Close the tab or clear fields after working with secrets.
• Read About and Contact if you need to ask how a specific tool behaves.

Why we write this down

Trust compounds when the product matches the copy. Browser-first tools are our default because they are faster to reason about for everyday privacy — for you and for us.