Legal & Technical Framework

waiver2.0 seals each signed waiver, records its SHA-256 hash in a tamper-evident chain, and keeps it unchanged. The waiver text follows the jurisdiction of the gym. waiver2.0 is an independent third-party record-keeper. It is not a party to the waiver, takes no side in any dispute, and does not certify facts. It records what was signed, when, and how — and preserves it unchanged.

Jurisdictions

Signing and record-keeping are designed with reference to the laws below. This is not a statement that any particular waiver is enforceable.

Australia

All states and territories.

Electronic signatures and records: Electronic Transactions Act 1999 (Cth) and the corresponding State and Territory electronic transactions laws.

Personal information: Privacy Act 1988 (Cth) and the Australian Privacy Principles.

United States

All 50 states and the District of Columbia.

Electronic signatures and records: ESIGN Act (15 U.S.C. § 7001 et seq.) and state electronic transactions laws, including the Uniform Electronic Transactions Act as enacted by individual states and, in New York, the Electronic Signatures and Records Act (N.Y. State Technology Law §§ 301–309).

Personal information: state privacy laws where they apply.

Canada

All provinces and territories except Quebec.

Electronic signatures and records: provincial and territorial electronic commerce legislation (e.g. Ontario Electronic Commerce Act, 2000).

Personal information: PIPEDA, and PIPA in Alberta and British Columbia.

How records are kept

✓ SHA-256 hash chain — each sealed record is hashed and chained; any later change is detectable
✓ Independent record-keeper — not a party to the waiver and does not certify facts
✓ Data protection — data hosted in the EU and processed under the GDPR

Media Capture Documentation

Part of Premium, which cannot be chosen at present; not offered at present. How its code records incident photos and video:

✓ Camera or file, as reported — photos and video are taken with the camera of the waiver2.0 incident page; each file is marked as taken with that camera or added with the file button, as the app reports it, which the server does not check
✓ Sealed when it reaches our server — each file is designed to be hashed (SHA-256) when it reaches our server and recorded with its own hash, tied to the athlete's signed waiver
✓ The server's time — the time recorded for each file is the server's time of receipt, not the device clock
✓ Checked against its seal — a file whose hash no longer matches the record is designed to be reported to the waiver2.0 operator for review; the platform makes no determination as to its admissibility, which remains a matter for the competent tribunal

The legal documents are published at athlete.waiver2.com/legal. Whether a waiver is enforceable is always for the court to decide; nothing on this site is legal advice.