Fury Song · Legal Register

Terms & Privacy — version history

Every version of our Terms of Use and Privacy Policy, with the dates it was in force and the SHA-256 digest of its canonical text. If you accepted our Terms, the acceptance record we hold names a version and a digest listed here. This page lets you confirm what that document said.

What this page proves, and what it doesn't

A digest published on the same server as the document it describes cannot, on its own, prove that we haven't changed both. If you only ever check our copy against our number, you have verified nothing about us.

It is useful in two specific ways. First, if you kept your own copy of a document, you can hash it and confirm it matches a registered version — that check does not depend on trusting us, and it is the one the tool below performs. Second, the chain head at the foot of this page is published to an external location we do not control, on a schedule; anyone comparing today's head against a previously anchored one can tell whether this register has been rewritten.

Terms of Use

1 version on record

  1. Version 1.2

    In force
    Effective
    Superseded
    —
    SHA-256 of canonical text
    f64f2fdc181c597d74872b64731745bd124766482f6971703be99fdd1bdb3a33
    Chain entry
    237e0cdf43960b7e10330ca02b589116e3371d249d491ac83689d7dc7cb07c12
    What changedFirst published version of the current Terms.

Privacy Policy

1 version on record

  1. Version 1.0

    In force
    Effective
    Superseded
    —
    SHA-256 of canonical text
    07f1fd617f9084b1ba09c7b148faa5404f0763b78b5013a76693966f004c6297
    Chain entry
    1b3ff06ed0cc90939df17c8e199c09667dd4c7d9b4ed19fd23a066047ef9dc68
    What changedFirst published version.

Register generated . Chain head 1b3ff06ed0cc90939df17c8e199c09667dd4c7d9b4ed19fd23a066047ef9dc68. Machine-readable copy: /legal/manifest.json.

Verify a document you hold

Select the file you saved. It is hashed in your browser and never uploaded. If the digest matches a registered version, that version is marked in the register above.

or drag it here · SHA-256 computed locally

Or hash it yourself

shasum -a 256 terms-v1.2.txt
# or
openssl dgst -sha256 terms-v1.2.txt

Digests are computed over the canonical .txt file: UTF-8, no byte order mark, LF line endings, one trailing newline. The HTML rendering of a version is provided for reading and is not the hashed artifact.

Chain head

1b3ff06ed0cc90939df17c8e199c09667dd4c7d9b4ed19fd23a066047ef9dc68

Each register entry carries the digest of the entry before it, so an entry cannot be altered or inserted without changing every digest after it. The value above is the head of that chain. It has not yet been anchored to an external location, so at present it demonstrates internal consistency only — it does not constrain us. When anchoring begins, where and when will be recorded here.