Privacy receipts

Prove the file never left your browser

Many online tools say they do not upload your data. A privacy receipt gives you something you can keep and check: a JSON file, built in your browser with the Web Crypto API, that records which tool ran, when it ran, and SHA-256 hashes of what went in and came out.

Open Receipt Verifier Read the spec
Why this exists

Trust is not a screenshot

The problem

Developers paste JWTs, API keys, contracts, and customer data into whichever formatter shows up first in search. Many sites say processing is local, but they rarely leave anything a reviewer can inspect afterward. From the outside, a site that works locally and one that quietly uploads can look the same. That is why we recommend decoding JWTs with a local tool rather than a cloud debugger.

The record

When you run a receipt-capable tool, the browser hashes the available input and output metadata locally and offers a JSON receipt for download, with no server round-trip. You can share it with a client, reviewer, or teammate. A receipt is a record, not a guarantee, because the same page that did the work also writes it. For an independent check, open your browser's developer tools, watch the Network tab while the tool runs, and confirm no request carries your file.

Open schema

What a privacy receipt contains

Each receipt follows our JSON Schema. Hashes are SHA-256, computed with the Web Crypto API. The receipt never contains the raw file contents.

type

OneDevToolkit.ProcessingReceipt, the document kind.

tool

Which utility ran (JSON Formatter, PDF Compress, HMAC signer…).

processedAt

ISO timestamp captured in your browser.

privacyMode

Always client-side for these receipts.

statement

Human-readable assertion that no network upload occurred.

input / output

Optional file metadata with a SHA-256 hash, never the raw payload.

{
  "type": "OneDevToolkit.ProcessingReceipt",
  "privacyMode": "client-side",
  "tool": "hash-generator",
  "processedAt": "2026-08-20T04:22:11.000Z"
}
Pipeline

How it works technically

1

Run a tool

Use a receipt-capable utility, such as the hash, JWT, PDF, or webhook HMAC tools.

2

Hash locally

The browser hashes available input/output metadata with Web Crypto.

3

Assemble JSON

The receipt is built on your device and offered for download. Nothing is uploaded.

4

Share & verify

Send the file to a reviewer, who can check its structure in the Receipt Verifier.

You can also export a PDF certificate for people who prefer a document, but the JSON file is the canonical, machine-readable format. To create a receipt by hand for a job done elsewhere, use the Privacy Receipt Builder.

Hands-on

Try it in a few minutes

Open a tool

Start with the Hash Generator, the Webhook HMAC Signer, or Compress PDF. Our post on compressing a PDF privately walks through that last one.

Run a job

Process your input, then use the receipt option in the tool's workflow bar to download the JSON file.

Verify JSON

Drop the file into Receipt Verifier.

Keep a record of your private jobs

An open spec, hashes computed in your browser, and a JSON file you can download and share. Made for developers who handle secrets in everyday tools.

Full specification Compliance pack