Prove the file never left your browser
Most tools claim “we don’t upload your data.” Privacy receipts make that claim verifiable — downloadable JSON generated with Web Crypto, not marketing copy.
Trust is not a screenshot
The problem
Developers paste JWTs, API keys, contracts, and customer data into random formatters. Sites say processing is local, but there is rarely proof an auditor can inspect. A compromised CDN and an honest operator look identical from the outside.
The proof
When you run a receipt-capable tool, the browser hashes available input/output metadata locally and offers a JSON receipt for download. No server round-trip. Share it with a client, reviewer, or teammate.
What a privacy receipt contains
Each receipt follows our JSON Schema. Hashes are SHA-256 via the Web Crypto API — never the raw file contents.
typeOneDevToolkit.ProcessingReceipt — the document kind.
toolWhich utility ran (JSON Formatter, PDF Compress, HMAC signer…).
processedAtISO timestamp captured in your browser.
privacyModeAlways client-side for these receipts.
statementHuman-readable assertion that no network upload occurred.
input / outputOptional file metadata with SHA-256 — never the raw payload.
{
"type": "OneDevToolkit.ProcessingReceipt",
"privacyMode": "client-side",
"tool": "hash-generator",
"processedAt": "2026-08-20T04:22:11.000Z"
}
How it works technically
Run a tool
Use a receipt-capable utility — hashes, JWT, PDF, webhook HMAC, and more.
Hash locally
The browser hashes available input/output metadata with Web Crypto.
Assemble JSON
A receipt is built on-device and offered for download — no upload.
Share & verify
Send the file to a reviewer. Check structure in Receipt Verifier.
Advanced users can export a PDF certificate. The JSON schema remains the canonical machine-readable format.
Try it in three minutes
Open a tool
Run a job
Use the receipt control in the workflow chrome after processing.
Verify JSON
Drop the file into Receipt Verifier.