Privacy notice

The claim we make

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

That is a statement about what our service receives. It is not a statement about your device, your browser or your network. When a tool needs the server (Tier 1), the file is uploaded for that job, processed, and deleted when the job ends.

What we receive

• Every visit: ordinary web request information — the address requested, headers needed to route the request, and a coarse network address — used to serve the site, secure it and limit abuse.
• Tier 1 only: the file and the settings you chose, for the length of the job.
• Always, in aggregate: counters and timings that contain no content and no free-form text, so we know the service is healthy.

What we do not receive

• The file itself during Tier 0 processing.
• File names, document titles, PDF text, image content, video names, recognised text or form values are never sent to analytics, metrics, traces, error messages or logs.
• No account, no sign-in, no identifying cookie, no device fingerprint. The identity used to limit abuse is temporary, kept in memory and cannot be reversed to a person or an address.
• Your content is never placed in a web address.

How long anything exists

• Tier 0 file: in your browser's memory only, until you close the tab, reset the tool or leave the page. It is never written to browser storage.
• Tier 1 file and result: in memory or a temporary memory-backed folder, for the life of the job only. They are removed when the job finishes, is cancelled, times out, or the connection drops. Results are not kept for later download.
• Rate-limit counters: in memory, for the length of the rolling window (a minute for the burst limit, a day for the daily quota). The network address itself is not stored.
• Operational counters and timings: for a bounded period, with no content in them.
• Web server access records: minimal and bounded, on our own server. We do not describe them as "zero logs"; the exact fields and period will be published when the server is deployed.
• Abuse reports and correspondence: only as long as the report requires, then deleted.

Who else is involved

Static files are served from our own server. There is no content delivery network and no other third-party service in the request path.

• Hosting provider: runs the machine. A hosting provider has infrastructure-level visibility, and we do not claim otherwise. We keep what exists to see to a minimum.
• Name resolution and certificates: ordinary infrastructure information, not a processor of your content.

Our own server handles ordinary request information to serve you; we do not call it "zero logs". Operational metrics are collected by software we run ourselves.

No tracking

We do not use analytics that follow you, advertising trackers, session recording, fingerprinting, or profiles. Operational counters cannot carry content or free text.

What we cannot control

Your device, browser, operating system, network, backups and other software are outside our control. The trust page lists these limits in full.

Your rights and how to reach us

There are no accounts, so there is no dashboard. To ask about your data, to ask for access, correction, deletion or objection, or to complain, write to the privacy address below. No account or JavaScript is needed.

Almost nothing about you is stored. The honest answer is usually that we hold no file content and no personal record: Tier 0 data is on your device and we cannot reach it, Tier 1 data is already gone, and the temporary rate-limit identity cannot be looked up for a person. Because we cannot verify who you are for data we do not keep, we can only confirm the retention described here. That is a limit of the design, not a refusal.

Abuse and takedown reports go to a separate address, listed on the contact page.