Trust the math, not the server.

The current version of every record on PublishingPolicy.org has a receipt anyone can re-check, so what a policy says can be checked against the record, not memory.

What is a Cryptographic Hash?

When a version of a policy becomes official, our system takes its exact text and runs it through a standard mathematical algorithm called SHA-256. This generates a unique string of characters—a mathematical fingerprint of the document.

A receipt anyone can check

If a publisher were to secretly change even a single comma in their policy, the SHA-256 math would output a completely different fingerprint. This means when an audience questions their standards, the publisher has the mathematical receipts to show the text they published, unchanged.

Independent Verification

A standard URL relies on trusting a central server. A receipt lets anyone check a copy for themselves: run the SHA-256 math on your own computer and compare the result with the fingerprint on the record.

How to Verify a Receipt Yourself

You don't need any special software to re-check a policy's fingerprint. You can use standard tools built into your computer to independently verify the math.

  1. 1. Download the Cryptographic Receipt

    On the policy's record, open the Cryptographic Receipt and choose Download JSON (.json). This file contains the exact, byte-for-byte data that was hashed: the policy's name, its sector and its text. This prevents copy-paste formatting errors.

  2. 2. Run the SHA-256 algorithm

    Open your computer's terminal (no special software required).
    On Mac/Linux: shasum -a 256 receipt.json
    On Windows: CertUtil -hashfile receipt.json SHA256

  3. 3. Compare the output to the public ledger

    Look at the resulting string of characters. It should perfectly match the hash recorded on the policy's public timeline for that date. If it matches, the text you have is the text that was recorded, unaltered.