Skip to content

Proof of the legal texts

Every version of our Terms & Conditions, Privacy Policy and Accessibility statement is recorded daily and anchored in the Bitcoin blockchain. This page lists, for each text, the checksum, the block it is anchored in, and the files needed to check it.

The timestamps are measurements. "Recorded on" is the day we saw the text, not the day it took effect. The anchor proves an upper bound: the text existed no later than the time of the block.

Terms & Conditions

Current version

Awaiting confirmation
Date stated in the document
March 29, 2026
Checksum of the text
6230f0b095e20cfe89eb447ddc910ed8d3d3d6465ebb1c9fe3d765670dc5ad6c
Recorded on
August 24, 2026, 14:13 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Superseded on August 24, 2026, 14:13 UTC

Awaiting confirmation
Date stated in the document
March 29, 2026
Checksum of the text
c84ec6f282ade1c527ef387c30c3564c344167bb879152fd93d79a8e24b85044
Recorded on
August 24, 2026, 13:15 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Privacy Policy

Current version

Awaiting confirmation
Date stated in the document
March 29, 2026
Checksum of the text
d8703439cf699f98e01510cb208544438303c58805510f05755aa306c3900d20
Recorded on
August 24, 2026, 14:13 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Superseded on August 24, 2026, 14:13 UTC

Awaiting confirmation
Date stated in the document
March 29, 2026
Checksum of the text
cf9d4247f7c482a915da5d6684a478066974d03c3ba4ac45310724371c61104c
Recorded on
August 24, 2026, 13:15 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Accessibility

Current version

Awaiting confirmation
Date stated in the document
April 1, 2026
Checksum of the text
1a48beb18c8625d3f9fa12af0f1c19a63400a843e49f4744ecc49ad6eb721b2f
Recorded on
August 24, 2026, 14:13 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Superseded on August 24, 2026, 14:13 UTC

Awaiting confirmation
Date stated in the document
April 1, 2026
Checksum of the text
cf8e6fbaf6e09f2427740847dfe7daebb3823fa555c0224a3458ac8d8016eae5
Recorded on
August 24, 2026, 13:15 UTC
Bitcoin anchor
Awaiting confirmation

The checksum is already fixed and stamped. Confirmation by a Bitcoin block usually follows within a day, after which the block number appears here. The proof files below are already complete.

Proof files

Check it yourself

  1. Download the proof files of a version.
  2. Recompute the checksum with shasum -a 256 page.txt. The result must match the value above and appear in the manifest.
  3. Verify the timestamp with ots verify -f manifest.json manifest.json.ots from the opentimestamps-client package. Without your own Bitcoin node, look up the block in a public explorer and compare the Merkle root.

As of August 24, 2026, 14:13 UTC