What is local processing?

Local processing means the work happens inside your browser tab using JavaScript. The file you select is never uploaded to a server. When you close the tab, the data is gone -- because it was never anywhere else.

How is this different from end-to-end encryption?

End-to-end encryption still sends your file to a server in encrypted form. Local processing doesn't send anything at all. There is no server in the loop.

Why does it matter for lawyers, doctors, or accountants?

Professional confidentiality, HIPAA, attorney-client privilege, and many other compliance regimes are violated the moment a sensitive document is uploaded to a third-party server, even if it is later deleted. Browser-only tools avoid the violation entirely.

How can I verify this myself?

Open Chrome or Firefox DevTools (F12), switch to the Network tab, then use any tool on this site. You will see zero outbound requests carrying your file. The tool runs entirely in your tab.

60-second read

Why browser-only processing is different

Most "free" privacy and PDF tools online send your file to a server, do the work there, and ask you to trust them. Today's Tasks doesn't have a server in the loop. Here's what that means — and how to verify it yourself.

1. How most cloud PDF / privacy tools work

📄

Your file

↗

☁️

Their server
file copied here

↓

⚙️

Processing
on their machines

↩

📄

Result back
trust they delete it

Even reputable tools advertise that they "automatically delete files after 2 hours". You're being asked to trust that promise. For most documents that's fine. For a contract, a medical record, a tax return, or a confidential settlement — it shouldn't be.

2. How Today's Tasks tools work

📄

Your file
stays on your device

→

🖥️

Your browser tab
processes it locally

→

📄

Result
stays on your device

No server in the loop. 0 bytes uploaded.

Every privacy tool on this site is built with browser-native JavaScript (and where needed, WebAssembly). The file you pick is read by your browser, processed by your browser, and the result is written back to your browser. No network request ever carries your file.

3. Who needs browser-only processing?

Legal

Lawyers & paralegals

Attorney-client privilege is broken the moment a draft contract is uploaded to a third-party server.

Health

Doctors & clinics

HIPAA, GDPR, and patient confidentiality apply even when a tool promises 2-hour deletion.

Finance

Accountants & auditors

Client tax returns, bank statements, and ledgers don't belong on a free tool's servers, ever.

Press

Journalists & activists

Source documents, leaked materials, and case files require zero-server handling — not "we'll delete it later".

4. Verify it yourself in 60 seconds

Open a Today's Tasks tool — try Document Redactor or Password Generator.
Open DevTools. Press F12 (or ⌘⌥I on Mac), then click the Network tab. Reload the page to start clean.
Use the tool. Type, paste, generate, redact — whatever the tool does. Now look at the Network panel.
Count outbound requests carrying your input. You'll find: zero. The only network requests are for the page itself, the CSS, and (where applicable) an anonymous k-hash lookup for breach checks.

You can do this test on any tool on this site, any time. We don't get to fake the Network panel.