Transaction Affidavits
Not Just Verification. Proof.
Cryptographically signed, non-repudiable records of every verification event. Built for legal admissibility, regulatory audits, and compliance reporting.
What Is a Transaction Affidavit
Every time Polyguard verifies identity in a digital transaction, the result is recorded as a Transaction Affidavit — a structured, cryptographically signed document that captures who was verified, how they were verified, and when. These records are generated automatically, stored immutably, and designed from the start for legal and regulatory use.
Inside a Transaction Affidavit
Based on real affidavit structure (record #20260225-171344-3432).
Custodian of Records Declaration
A sworn statement by the Custodian of Records under penalty of perjury, certifying the affidavit as a business record. Includes certification under NY CPLR § 3122-a, establishing the record was created automatically by Polyguard's systems in the regular course of business, without human intervention.
Verification Summary
Meeting context including platform (Zoom, Teams), meeting title, start and end timestamps, and a complete participant list. Each participant is identified by their Poly ID with entry and exit times recorded.
Required Proofs
The verification factors required for the transaction, organized by criticality:
High Certainty
NFC document verification or location match
Presence Verification
PG-Presence optical distance bounding
Document Proofing
Government ID with NFC chip validation
Hardware Attestation
Device integrity via AppAttest / Play Integrity
Location
GPS geolocation (region only, not precise coordinates)
Facial Biometrics
Real-time facial recognition with confidence score
Per-Participant Attestation
Each verified participant receives an individual attestation record with specific verification results:
| Field | Example Value |
|---|---|
| Platform User ID | zoom:user:abc123def456 |
| Biometric Confidence | 98.37% |
| Document Type | ePassport (NFC verified) |
| Issuing Country | CAN |
| PG-Presence Timing | 87.702ms |
| Geographic Region | CA-ON |
| Hardware Attestation Key ID | attest:hw:e7f2...a91c |
Zero Trust Footer
Every affidavit includes a reference to the JWKS public key endpoint at
polyguard.ai/.well-known/jwks.json
— enabling any party to independently verify every cryptographic signature in the document without contacting Polyguard.
Why Affidavits, Not Logs
Server logs record what happened. Transaction Affidavits prove it.
Business Records Exception
Transaction Affidavits are structured to qualify as business records under NY CPLR § 3122-a and the Federal Rules of Evidence (FRE 803(6)). They include a custodian certification, are created automatically in the regular course of business, and are generated contemporaneously with the events they record.
Cryptographically Signed
Every attestation within the affidavit is signed with hardware-backed cryptographic keys, and the PDF itself is digitally signed by Polyguard at generation. Both layers of signature prove the data has not been altered since creation and can be verified independently using the published JWKS public keys.
Immutable Storage
Affidavits are stored immutably. They cannot be modified, deleted, or backdated after creation. The combination of immutable storage and cryptographic signing establishes a chain of custody from the moment of verification.
No Human Intervention
Transaction Affidavits are generated automatically by Polyguard's systems without human involvement. This eliminates the risk of selective recording, post-hoc editing, or human error in documentation.
What They Do Not Contain
Privacy First extends to every record Polyguard produces.
No Raw Biometric Data
Biometric templates and facial recognition data never leave the device and are never included in any record.
No Recordings
Polyguard never captures images, audio, video, or transcripts from your meetings or calls.
No Precise GPS
Geographic region only (e.g., US-NY, CA-ON). Precise coordinates are never stored or transmitted.
No Unnecessary PII
Only data required to establish identity verification is included. The data minimization principle is applied to every field.
Use Cases
Transaction Affidavits serve as evidentiary records across legal, regulatory, and business contexts.
Employment Disputes
Prove who participated in interviews, onboarding sessions, and meetings. Establish that the person hired is the person who was verified — with cryptographic proof, not just login records.
Regulatory Audits
Provide auditors with independently verifiable proof of identity verification for SOC 2, ISO 27001, and other compliance frameworks. Affidavits are structured for direct inclusion in audit evidence packages.
Legal Proceedings
Transaction Affidavits qualify as business records under NY CPLR § 3122-a and FRE 803(6). Custodian certification, immutable storage, and cryptographic signatures establish chain of custody and authenticity.
Insurance Claims
Document identity verification for claims involving remote interactions. Provide insurers with non-repudiable proof that participants were verified at the time of the transaction.
Compliance Reporting
Generate reports showing verification coverage, compliance rates, and verification factor completion across teams, departments, or the entire organization.
Fraud Investigation
When an incident occurs, Transaction Affidavits provide a complete, tamper-proof record of every identity verification event — including exactly which factors were completed and when.
See a Sample Affidavit
Access the Polyguard sandbox and generate a real Transaction Affidavit from a test verification.