PII Detector
Scan text for emails, phones, and card-like patterns locally.
OpenWrite a short JSON note recording which tool you used, for what, and that it ran in the browser.
Use the slug from the tool URL, such as json-formatter.
Type a short verb such as format or redact.
The receipt updates live with a timestamp.
Copy it or download privacy-receipt.json.
Your team's data handling checklist asks you to record when customer files were processed locally rather than sent to a third-party service. A sentence in a ticket is easy to lose. Privacy Receipt Builder produces a small, consistent JSON record you can attach instead.
Type the tool slug (for example pdf-compress) and a short action (for example compress), and the receipt updates as you type. It contains a version number, the site name, a generation timestamp, the tool and action you entered, a processing value of client-side, an uploaded flag set to false, and a note stating that no tool input is included. Copy it or download it as privacy-receipt.json.
This receipt is self-declared. It records what you typed and does not hash any file or inspect what happened in another tab, so it is evidence of your note, not of the processing itself. Several tools on the site have a Receipt button that creates a richer receipt automatically, including SHA-256 hashes of input and output files where they apply. Use those when they are available, and keep this builder for tools that do not have one or for manual records. Your organization's policies, not this file, decide what counts as adequate documentation.
The privacy receipts guide covers the full receipt format. To check a file against a hash later, use File Checksum, and Receipt Verifier checks the structure of tool-generated receipts. The receipt is generated in your browser and is not stored.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Built-in receipts are created by the tool that did the work and can include file names, sizes and SHA-256 hashes. This builder only records the slug and action you type, so it carries less evidence.
No. It contains only the tool slug, the action text, a timestamp and fixed fields. Avoid typing sensitive details into the action field, because whatever you type there is included.
Not in the builder. Compute a hash with File Checksum and add it to the downloaded JSON in a text editor, or use a tool with a built-in Receipt button that hashes files automatically.