Your files stay yours.

ToolingTools is a set of everyday PDF, image, and video tools that run in your browser whenever possible. When a tool can work on your own device, your file never has to be uploaded. When a job is too heavy for a browser, we offer a temporary server option — and we tell you clearly when that happens.

We do not have accounts, we do not track you across the web, and we do not keep your files.

We serve the site ourselves: there is no third-party content delivery network, no third-party analytics, and no external content origins fetching our fonts, scripts, styles, or images.

✓ Runs on your device — no upload required

🔒 Secure server processing — temporary processing only

Every tool shows one of these two badges so you know what is actually happening before you start.

• "Runs on your device" means your browser does the work. No file is uploaded.
• "Secure server processing" means the job is done on our server because it is too heavy or unsupported in your browser. Your file is uploaded only for that job, processed in a locked-down worker, and deleted when the job finishes. "Secure" here refers to the sandboxed, temporary processing described below — it is not a guarantee about your device, your network, or the contents of the file.

If a tool can do the job on your device, it does. The server is the exception, not the default.

When you see the "Runs on your device" badge, everything happens inside your browser, on your computer. The tool reads the file you chose, does the work, and gives you the result. Nothing is uploaded.

What this means, exactly:

The ToolingTools service does not receive the file during Tier 0 processing.

That is the precise promise. It is about what our service receives. It is not a claim about your device, your browser, or your network — see "What we cannot control" below.

Where does the file go? It is not sent to our service. It is held in your browser's memory while the tool works and is never uploaded to our servers. When you close the tab or reset the tool, it is released from the page — though your browser or operating system may keep its own copies, as "What we cannot control" below explains.

Some jobs — the heavy ones — cannot run well in every browser. When you see the "Secure server processing" badge, your file is uploaded to our server so we can do the work. Here is exactly what happens to it:

• Your file is uploaded only to do the job you asked for.
• It is processed in a restricted, locked-down worker that cannot reach the internet.
• It is held only while the job runs — usually in memory, sometimes briefly in a temporary memory-based location when the job needs to jump around inside the file.
• It is deleted when the job finishes, when you cancel it, or if it times out. There is no permanent store, no database, and no upload folder keeping your file.
• We do not inspect the contents for any purpose beyond the job you asked for, and we keep no copy to look at later. The processing software reads the file only to perform that job — we do not read it for analytics, we do not build a profile from it, and we do not retain it.

A short, honest note: the server exists because some jobs are too heavy for some devices. It is a small, bounded fallback, and it is designed so nothing stays behind. If you would rather avoid it, use a tool that shows the "Runs on your device" badge.

We have reserved the design for a future "heavy compute" tier for jobs that need much more power than a small server can provide. It does not exist yet, and nothing is processed that way today. If we ever build it, this page will explain exactly what it does before it is switched on.

We never use session recording or heat-maps that replay what you did on the page.

We never use invasive analytics, advertising trackers, or third-party marketing pixels, and we do not hand your visit to a third-party content delivery network or an external asset origin.

We never fingerprint your browser or device to identify you.

We never build a profile of your behaviour or track you across other sites.

We never send your filenames, document titles, PDF text, image content, form values, video names, or recognised text to analytics or logs. Not even a part of it, and not even when something goes wrong.

We never keep your files. Tier 0 files stay on your device; Tier 1 files are deleted when the job finishes.

We never require an account, a password, or a sign-in to use the tools.

Being honest about the limits of a promise matters as much as making it. These things are outside our control, and we will not pretend otherwise:

Your device. Files you save live in your Downloads folder and on your disk. We cannot delete, encrypt, or manage them.

Screenshots and screen recording. Anything shown on your screen can be captured by your device.

Your browser and operating system. Your browser keeps its own history and caches, and your operating system may keep temporary files, swap, or crash reports. We cannot reach into those.

Your network. Your internet provider, your workplace proxy, or security software on your network can see network traffic. We cannot make a network-level promise.

Your backups and sync tools. If your device backs up or syncs files, that is outside our reach.

Other software on your device. Browser extensions and malicious software can read data on your machine. We cannot protect against software you have installed.

The infrastructure that serves the site. Static files are served from our own server, not from a third-party content delivery network, and we use no third-party analytics or external content origins. Our server — and the company that hosts it — still handles ordinary network information (like the address a request came from) as any web infrastructure does. We do not describe them as "zero logs", because that would not be true. They never receive your file's contents from us.

What we guarantee: when a tool shows "Runs on your device", the ToolingTools service does not receive the file during Tier 0 processing. When a tool shows "Secure server processing", your file is uploaded for that job only and is deleted when the job finishes; we do not read its contents and do not keep a copy.

What we do not guarantee: that nothing ever leaves your device in general (Tier 1 uploads your file); that your device, browser, network, backups, or other software keep nothing; that any file is free of malware; or that we are certified, audited, or approved by any authority. Our promise is about what our service receives and keeps — not about the rest of your digital life.

There is no account and no login, so there is no dashboard to manage. If you have a privacy question or want to exercise a data right, or if you need to report abuse or a takedown, use the contacts below.

Privacy and data requests: see the privacy page.

Abuse and takedown reports: see the acceptable-use and contact pages.

For the full technical detail — exactly what is received, how long anything exists, and every limitation — read the privacy model. It is written for engineers and says the same things this page says, in more detail.

This page is available in Arabic as well as English. The Arabic version is written as native Arabic copy by an Arabic writer — it is not a machine translation — so that the exact meaning of every promise is preserved. The English and Arabic copy express the same scope and neither adds nor weakens any claim.