DTNDailyToolNest

Privacy Policy & Data Protection

DailyToolNest is built around an uncompromising principle: you should never have to trust a third-party server with your private documents. We provide two distinct operating modes so you always know exactly where your data lives and how it is handled.

1. The Two Operating Modes

Sensitive Mode (Device-Only)

In Sensitive mode, your files are processed entirely inside your local web browser tab using WebAssembly (WASM). No document bytes, file names, or derived content are ever transmitted over the network to DailyToolNest or any third party.

Sensitive mode is hosted on an isolated static origin (device.dailytoolnest.com) governed by an ultra-strict Content Security Policy (CSP). Outbound network requests, analytics scripts, external font CDNs, and third-party trackers are blocked at the browser level.

Normal Mode (Ephemeral Server Processing)

When files are too large for browser memory limits, you can opt for Normal mode. In this mode:

  • Files are transmitted over encrypted TLS 1.3 connections directly to our German servers.
  • Files are encrypted at rest using AES-256-GCM prior to processing.
  • Each file is processed by a fresh process created for that job alone, inside a gVisor sandbox with no route to the internet.
  • Both the input file and the processed output are deleted the moment you close the page. If you download the result, they are deleted five minutes later — long enough to download again in the same sitting, and no longer. If you never download and never close the page, they are deleted fifteen minutes after processing finishes. Time spent waiting in the queue does not count, so a busy moment never deletes a file before it has been processed. A file that is never processed at all is deleted 24 hours after upload.
  • We never inspect, train AI models on, or sell your documents.

2. How to Verify Sensitive Mode (Step-by-Step)

You do not need to take our word for it. You can independently verify that zero document bytes leave your computer in Sensitive mode:

  1. Open Developer Tools: Press F12 or Ctrl+Shift+I (orCmd+Option+I on macOS) in your browser.
  2. Navigate to the Network tab: Click on the Network tab in DevTools. Ensure the recording indicator is red (active) and check the Preserve log box.
  3. Check the Origin: Ensure the URL begins with https://device.dailytoolnest.com (or in local development, the device origin).
  4. Process a Sensitive File: Select and process your document.
  5. Inspect Network Activity: Observe the Network log. No POST,PUT, or fetch requests carrying payload bytes will appear. The only requests are initial static assets (HTML, JavaScript, CSS, WASM binaries) loaded when opening the page.

For the full walkthrough — including how to check the enforced Content-Security-Policy header — see How to verify Sensitive mode.

3. Analytics & Telemetry

We do not use Google Analytics, advertising pixels, or any third-party analytics service. Nothing about your visit is shared with another company. We measure three things, all on our own servers, and all described in full below.

Visit counting (no cookie, no consent required)

On dailytoolnest.com we count how many distinct people visit each day. To do this without identifying anyone, your IP address and browser user-agent are combined with a secret that exists only in our server’s memory and is replaced every day at midnight UTC. The result is a one-way hash. We store only that hash, a broad device category (mobile, tablet or desktop) and a platform family (Android, iOS, Windows, macOS, Linux).

Your IP address is used to compute the hash and is then discarded — never written to disk, never logged. Because the daily secret is destroyed and never recorded, the hash we hold for today cannot be linked to the hash for the same person tomorrow, and it cannot be reversed back to an IP address. No cookie is set, so nothing follows you between sessions. This lets us answer “how many people visited on Tuesday” and makes it impossible for us to answer “did this person come back on Wednesday”.

Device and platform figures are kept in a separate table that has no visitor column at all — it holds nothing but a date, a category and a counter. The table that counts visitors holds nothing but a date and a hash. The two share no key, so there is no record anywhere of which visitor used which device, and none can be reconstructed by joining them. This is enforced by tests, not just by policy.

The device origin, device.dailytoolnest.com, does not do this and cannot do this. Its Content-Security-Policy sets connect-src ‘none’, which blocks every outbound request at the browser level. Sensitive mode remains entirely uncounted.

Processing times (no personal data)

When you use Normal mode, we record how long the job took — the wait for a free worker and the processing time — along with which tool ran, whether it succeeded, and a coarse size band such as “1–5 MB”. This is timing information about our own infrastructure. It contains no filename, no exact file size, no file content, and nothing linking a job to a person. Sensitive mode never reaches our servers, so it produces no such record.

Optional performance telemetry (explicit consent)

Separately, you may opt in to anonymous performance telemetry. When declined, zero telemetry requests are transmitted. When accepted, it records aggregate processing duration bands and generic browser categories — never IP addresses, filenames, or user identifiers.

Feedback

If you send feedback, we store your rating and your message. That table has no identity column at all, so a submission cannot be traced back to you even by us. If you want a reply, use the contact form instead — that one asks for an email address precisely because a reply is expected.

4. Data Subject Rights (GDPR / DSGVO)

DailyToolNest operates under European data protection standards (GDPR). In Sensitive mode, we are not a data processor because your data never touches our systems. In Normal mode, our ephemeral lifecycle erases the data when you close the page, and otherwise fifteen minutes after processing finishes, or 24 hours after upload if it is never processed.