Privacy & Compliance

Receipt Verifier

All tools

Paste a privacy receipt and see whether its basic structure checks out.

How it works

Four simple steps

1

Paste the receipt

Add the JSON from a downloaded receipt file.

2

Run the check

Type, tool and timestamp fields are inspected.

3

Read the result

See the valid flag and any listed issues.

4

Compare hashes

Recompute the file SHA-256 separately for proof of identity.

Receipt Verifier

About Receipt Verifier

A colleague attached a privacy receipt to a ticket to show a contract PDF was compressed locally. Before you file it, you want to confirm the JSON is a real receipt and not a truncated or edited copy with key fields missing. Receipt Verifier runs that structural check.

Paste the receipt JSON and click Run. The tool parses it and checks three things: a type field whose value contains the word receipt in lowercase, a tool identifier in either tool or toolSlug, and a timestamp in either processedAt or timestamp. The output is JSON with valid set to true or false, an issues array naming anything missing, and the parsed receipt echoed back. Invalid JSON produces a parse error in the status line.

This is a structure check, not a cryptographic one. It does not verify signatures or recompute hashes, and it cannot prove where a file was processed. When a receipt includes an output.sha256 value, the stronger check is to hash the file you received with File Checksum and compare the two strings. If they differ, the file is not the one the receipt describes. Note also that the type check is case-sensitive, so a type spelled only with a capital R is reported as unexpected.

The guide to privacy receipts explains what each field means and what a receipt can and cannot show. To create a simple receipt by hand, use the Privacy Receipt Builder. Verification runs on the pasted text in your browser.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

No. A receipt is a statement generated in the page, and this tool only checks that its required fields are present. It shows the receipt is well formed, not that the claim inside it is true.

The check looks for the lowercase word receipt inside the type value. A type such as ProcessingReceipt with a capital R does not match, so the tool lists it as an unexpected type even if the rest of the receipt is complete.

The tool works with pasted text. Open the JSON file in any text editor, copy its contents and paste them into the input box.

View more FAQs

Related tools

View all

PII Detector

Scan text for emails, phones, and card-like patterns locally.

Open

On-Device NER Redactor

Redact PII with regex plus optional on-device NER - nothing uploaded.

Open

SBOM Privacy Studio

Inspect CycloneDX/SPDX SBOMs locally with optional OSV package lookups.

Open

Image OCR

Extract text from images with Tesseract.js in your browser.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools