Fused Identity
Fused Identity. Continuous Proof.
Polyguard fuses configurable identity factors into a single cryptographic token — and re-verifies that identity at every interaction.
The Fusion Gap
Most organizations verify identity factors separately — a liveness check from one vendor, a document scan from another, device posture from a third, phone verification from a fourth. These checks happen at different times, on different systems, with no cryptographic binding between them.
This creates a structural vulnerability: collaborative attacks. One person passes the face check. Another provides the document. A third contributes a clean device. Each factor passes individually, but no single person satisfied all of them. When verification is fragmented, the fragments can come from different people.
Polyguard closes this gap by fusing all required factors simultaneously, on one device, in one session. The fusion itself is the security property.
How Fusion Works
Each factor is verified independently on-device, individually signed, and fused into a single cryptographic token — one artifact proving all required factors were confirmed by one person.
Independent Verification
Each configured factor is verified separately on-device. Person, Document, Device, Location, Phone Number — each executes independently. The failure of one does not compromise the results of another.
Individual Signing
Each factor produces its own signed attestation using a hardware-backed key in the device's secure enclave. Every attestation is independently verifiable.
Fusion
The individual attestations are bundled and signed together — a single cryptographic proof that all required factors were verified simultaneously, by one person, on one device. This fused token is the Trust Check result, and it feeds into the Transaction Affidavit for a litigation-ready record.
Available Factors
Businesses configure which factors to require. Each factor adds an independent dimension of identity assurance.
Person
Real-time facial recognition with 3D depth analysis confirms the person on camera matches their registered identity. On-device via Apple Vision and Google ML Kit, with anti-spoofing measures that detect masks, photos, and video replay.
Document
Government-issued ID verified through NFC cryptographic chip reading when available — the chip on a modern passport or national ID card contains a digitally signed data structure validated against the issuing country's public key infrastructure. For documents without NFC chips, Polyguard supports photographic document verification as a fallback.
Device
Hardware-backed attestation via Apple AppAttest and Google Play Integrity confirms the verification is running on a genuine, unmodified device. This is a hardware-level cryptographic challenge that cannot be spoofed by emulators, rooted devices, or modified applications.
Location
GPS geolocation combined with PG-Presence optical distance bounding. Geolocation confirms the general region. PG-Presence confirms the person is physically present at the device — not operating remotely through screen sharing, remote desktop, or a KVM switch.
Phone Number
Phone number verification via OTP confirms control of a known phone number. Fused alongside other factors, this binds a communication channel to the same verified identity — preventing SIM-swap attacks from being useful in isolation.
Additional factors can be added as verification requirements evolve.
Why Fusion Matters
Closes Collaborative Attacks
When all factors are verified simultaneously on one device, in one session, different people can't contribute different factors. The fusion is cryptographic — the signed bundle proves one person, one device, one moment.
Makes Comprehensive Verification Practical
If companies needed separate vendors for liveness, document scanning, device attestation, and location — most wouldn't implement all of them. A single integrated flow makes it practical to require every factor you need. Less friction for the company and the individual.
Self-Service Identity Lifecycle
New phone, renewed passport, new country — the individual sets up Polyguard on their new device and re-registers the required proofs without involving the company. A deterministic user ID from legal name and date of birth ensures continuity across devices and documents.
Identity That Persists
Traditional identity verification happens once — at signup, at onboarding, at the start of an engagement. After that single checkpoint, systems rely on session tokens and assumptions. The person behind the screen may change. The verification does not.
Polyguard re-verifies fused identity at every interaction. On-device biometric matching confirms the same person is present — which in turn relies on device attestation to prevent camera spoofing. The factors don't just fuse once; they reinforce each other continuously.
The person verified last week is confirmed to be the same person in today's meeting, tomorrow's transaction, next month's access request. Each Trust Check produces a fresh signed token — a new cryptographic proof of the same fused identity.
Initial Trust Check
Fused identity established
Every Interaction
Re-verified, fresh bundle
Continuous Confidence
Same person, proven
See Fused Identity in Action
Access the Polyguard sandbox and experience identity fusion firsthand.