4. Electronic Signature & Forensic Disclosure

1. Consent to Electronic Transactions 1.1 By using Waiver2.0, you explicitly consent to conduct all transactions, signings, and legal declarations electronically. 1.2 You acknowledge that your electronic signature, captured via the Platform, is recognised as a valid method of signing under applicable electronic transactions legislation in your jurisdiction, as specified in Section 2 below, subject to the conditions those laws set. 1.3 You further acknowledge that you have been provided with a clear opportunity to review all documents prior to signing, and that your signature represents a free, informed, and unambiguous act of will. 2. Jurisdiction-Specific Legal Framework for Electronic Signatures 2.1 🇦🇺 Australia — Electronic Transactions Act 1999 (Cth) & State/Territory Equivalents Your electronic signature is not denied legal effect only because it is electronic, under the Electronic Transactions Act 1999 (Cth) and the equivalent electronic transactions legislation of each Australian state and territory. The Act provides that a transaction is not invalid merely because it took place by means of one or more electronic communications. Waiver2.0's forensic signing process is designed with the Act's reliability requirements in mind, by capturing a server-recorded timestamp, IP address, and SHA-256 document hash as a means of identifying the signatory and indicating their intention in respect of the document; whether those requirements are met in a given case is for the court. 2.2 🇨🇦 Canada — Personal Information Protection and Electronic Documents Act (PIPEDA) & Provincial Electronic Commerce Acts Your electronic signature is not denied legal effect only because it is electronic, under applicable provincial electronic commerce legislation, including the Electronic Commerce Act 2000 (Ontario), the Electronic Transactions Act (British Columbia), and equivalent statutes in other provinces, and, where a federal law requires a signature, under PIPEDA (Part 2). Waiver2.0's forensic signing process provides a tamper-evident record of the signing event; it does not create a secure electronic signature as defined in PIPEDA. 2.3 🇺🇸 United States — ESIGN Act (15 U.S.C. § 7001 et seq.) & UETA Your electronic signature is not denied legal effect only because it is electronic, under the Electronic Signatures in Global and National Commerce Act (ESIGN Act) and the Uniform Electronic Transactions Act (UETA), as adopted in applicable states. Waiver2.0's forensic signing process is designed with the ESIGN Act requirements in mind by: (a) capturing the signatory's intent to sign electronically; (b) associating the electronic signature with the signed record; and (c) retaining the record in a form that is accessible to all parties. Whether the consumer disclosure requirements of the ESIGN Act (15 U.S.C. § 7001(c)) apply to a waiver, and whether they are met in a given case, is for the court. 3. Forensic Integrity & SHA-256 Hashing 3.1 Tamper-Evident Digital Seal: Waiver2.0 utilizes SHA-256 hashing algorithms to create a tamper-evident digital fingerprint of every signed document. This process runs on infrastructure Waiver2.0 operates. 3.2 Anti-Tampering Logic: Altering the sealed submission data after signing produces a mismatch with its recorded hash, which a verification of the record can detect (Audit Trail & Compliance Package, Section 4). The platform makes no determination as to the admissibility of a record that does not match, which remains a matter for the competent tribunal. The IP address and the server timestamp are recorded with the sealed record; the server timestamp is not an input to the hash chain, and for waivers submitted from 16 October 2026 neither is the IP address. 3.3 Timestamping: All signing events are timestamped using the Platform's own server clock at the moment the signing event is received (the "server timestamp"), independent of the user's device time. 4. The Tamper-Evident Audit Log 4.1 You agree that the Forensic Audit Log — which includes the SHA-256 document hash, IP address, and the server-recorded timestamp of the signing event — may be offered as evidence of the signing event; its admissibility and weight remain for the competent court or tribunal. 4.2 Waiver2.0 records the SHA-256 hash of each generated document with the waiver's record and makes it available for that waiver on request. Anyone holding a copy of the document can compute its SHA-256 hash and compare it with the recorded hash; a difference shows that the copy is not the document that was recorded. 4.3 The Forensic Audit Log is stored in a tamper-evident format: an alteration of the hashed content of a recorded entry is detectable by hash verification. The Platform's application has no database permission to delete log entries or to change their hashed content; the owner of the database table and a database superuser can change or delete them, and personal data is to be deleted at the end of its retention period (Section 6.1). 5. Admissibility of Electronic Records 5.1 You agree that the digital records, forensic logs, and PDF records generated by Waiver2.0 may be offered as evidence in legal proceedings, subject to the rules of evidence applicable in the relevant jurisdiction; their admissibility and weight remain for the competent court or tribunal. 5.2 You acknowledge that the signed record is sealed with a SHA-256 hash chain, so that a change to it after signing is detectable; the weight of that evidence in any challenge to the document's integrity remains for the competent court or tribunal. 5.3 Jurisdiction-Specific Admissibility Notes: 🇦🇺 Australia: Electronic records may be admitted as evidence under the Evidence Act 1995 (Cth) and equivalent state and territory evidence legislation, including under the business records exception and the provisions on electronic communications; whether the forensic audit log meets those requirements in a given case is for the court. 🇨🇦 Canada: Electronic records may be admitted under the Canada Evidence Act (s. 31.1–31.8) and applicable provincial evidence legislation, subject to proof of the integrity of the electronic records system; whether that proof is made in a given case is for the court. 🇺🇸 United States: Under the ESIGN Act and UETA, electronic records and signatures are not denied legal effect only because they are electronic; their admission as evidence, including under the Federal Rules of Evidence Rule 803(6) business records exception and the authentication requirements of Rule 901, is for the court. 5.4 By signing, you accept the use of an electronic signature for this agreement. This acceptance does not limit any right you have under applicable law; whether your signature is valid and enforceable in a given case is for the court. 6. Data Integrity & Storage 6.1 Waiver2.0 applies appropriate technical and organisational measures to the personal data associated with each signing event, stored on infrastructure located in the European Union, for the applicable retention period set out in the Privacy Policy (Section 5) — until the limitation period applicable to the Gym's jurisdiction expires, counted from the expiry of the waiver — after which it is permanently deleted. The cryptographic record of the signing event — the SHA-256 hash values, server timestamps, and chain position — is retained permanently, by design, and contains no personal data. 6.2 No third-party automation tool takes part in generating the document: it is generated, signed and stored on infrastructure Waiver2.0 operates on Railway (EU West, Amsterdam). From the date Waiver2.0 starts the archive copy set out in the Privacy Policy, Section 6.6, an encrypted copy is also kept with Scaleway SAS (Paris, France). 6.3 In the event that Waiver2.0 ceases operations, users will be given no less than 90 days' notice and provided with copies of all their forensic records prior to any system decommissioning. 7. User Obligations in Electronic Transactions 7.1 Users must ensure that the device and network used for signing are under their sole control at the time of the signing event. 7.2 Users must not permit any third party to complete a signing event on their behalf without explicit written authorization, which must itself be recorded in the forensic audit log. 7.3 Users must immediately notify Waiver2.0 at support@waiver2.com if they believe a signing event was completed without their knowledge or authorization. 7.4 An image of a signature drawn for an eyewitness entry of an Athlete's incident record (Privacy Policy, Section 2.9) is not a signing event of this Policy, and the Platform decides no legal effect of it: the record shows that the image was sent from the Athlete's account, not who drew it. This feature is not switched on at present. 8. Amendments & Versioning 8.1 This Policy is versioned and stored on the Platform. We will notify users of material amendments and, where required by law, seek consent again. 8.2 The version of this Policy is not recorded with a signing event (Audit Trail & Compliance Package, Section 8.2). 8.3 Last updated: 10 November 2026.