UD Policy Attestation
Pro · Free during betaCreate a tamper-evident record proving an employee read and understood a specific version of a policy. The policy hash and attestation are bundled together — making it impossible to claim a different policy version was attested to.
Built for compliance requirements
Article 5(2) requires demonstrable compliance. Policy attestation records are your evidence.
Section 302 certifications require auditable records of who reviewed which policy version.
Clause 7.2 requires competence and awareness evidence. Attestation records satisfy this.
Prove new employees acknowledged the employee handbook, data protection, and code of conduct.
How UD Policy Attestation differs
Email acknowledgments are easily disputed. LMS systems are expensive overkill for attestation. UD bundles the policy hash with the attestation in one tamper-evident record.
No tamper evidence. Employee can claim they saw a different version. Easily disputed in a hearing.
Expensive, complex, and designed for course delivery — not attestation. $10,000–50,000/year for simple acknowledgment.
Signing only. Does not capture which version of the policy was signed, or hash-verify the document.
Policy hash + attestation record in one tamper-evident .udz bundle. Disputes require breaking SHA-256.