xPrint: Biometric Template Protection
XorIDA splits biometric templates across independent storage nodes. No single node holds a usable template. Supports fingerprint, face, iris, and voice modalities.
The Problem
Biometric templates stored in single databases are permanent breach targets. Unlike passwords, biometrics cannot be rotated after compromise.
When a password database is breached, users can change their passwords. When a biometric template database is breached, the damage is permanent. You cannot change your fingerprints, your iris pattern, or the geometry of your face. A biometric breach compromises the victim for life.
Centralized biometric databases at airports, banks, and government agencies store millions of templates at single points of failure. The OPM breach in 2015 exposed 5.6 million fingerprint records. Those fingerprints are still compromised today and will be forever. Traditional encryption does not solve this -- it simply moves the problem to key management.
The Old Way
The PRIVATE.ME Solution
XorIDA splits biometric templates across independent storage nodes. No single node holds a usable template. Matching happens in the split domain without ever reconstructing the full template.
Each biometric template is split into N shares distributed across independent storage nodes. During authentication, shares are collected and the match is performed on the reconstructed template in a secure enclave, then immediately discarded. No node ever holds a complete template at rest.
Because XorIDA is information-theoretic, a compromised node reveals zero information about the template. Unlike encrypted templates where a future quantum computer could decrypt, XorIDA shares are provably unrecoverable without the threshold number of shares -- today, tomorrow, and forever.
The New Way
How It Works
A secure enrollment and matching pipeline ensures biometric templates never exist in usable form at rest. Templates are split at enrollment and reconstructed ephemerally at match time.
Use Cases
Protect traveler biometric templates at airports with threshold-based storage. No single airport system holds usable templates. Boarding gate matching uses ephemeral reconstruction.
Border SecurityReplace single-database fingerprint and face authentication with split-template verification. Branch and ATM systems reconstruct templates ephemerally for each authentication.
KYC / AMLNational biometric ID systems can distribute templates across government data centers. No single data center breach exposes the entire population's biometrics.
National ScaleCorporate biometric access control with split-template storage. Employee fingerprints and face templates distributed across independent security nodes.
Physical SecurityIntegration
import { vaultTemplate, matchSecure } from '@private.me/biometricvault'; // Vault a fingerprint template across 3 nodes (2-of-3) const shares = await vaultTemplate(fingerprintTemplate, { n: 3, k: 2, modality: 'fingerprint' }); // Secure match with ephemeral reconstruction const match = await matchSecure(probeTemplate, { userId: 'user-12345', threshold: 0.95 }); // match.ok === true → identity verified
Security Properties
| Property | Mechanism | Guarantee |
|---|---|---|
| No Template at Rest | XorIDA K-of-N split at enrollment | No storage node holds a usable template |
| Ephemeral Match | Reconstruct-match-discard pipeline | Templates exist in memory only during matching |
| Multi-Modal | Modality-agnostic split architecture | Fingerprint, face, iris, voice all supported |
| Quantum Resistance | Information-theoretic security (GF(2)) | Permanent protection -- no future attack can break |
| Re-Split Without Re-Enroll | Threshold reconstruction + re-split | Rotate storage nodes without touching users |
Verifiable Data Protection
Every operation in this ACI produces a verifiable audit trail via xProve. HMAC-chained integrity proofs let auditors confirm that data was split, stored, and reconstructed correctly — without accessing the data itself.
Read the xProve white paper →
Ready to deploy xPrint?
Talk to Ren, our AI sales engineer, or book a live demo with our team.
Ship Proofs, Not Source
xPrint generates cryptographic proofs of correct execution without exposing proprietary algorithms. Verify integrity using zero-knowledge proofs — no source code required.
- Tier 1 HMAC (~0.7KB)
- Tier 2 Commit-Reveal (~0.5KB)
- Tier 3 IT-MAC (~0.3KB)
- Tier 4 KKW ZK (~0.4KB)
Use Cases
Deployment Options
SaaS Recommended
Fully managed infrastructure. Call our REST API, we handle scaling, updates, and operations.
- Zero infrastructure setup
- Automatic updates
- 99.9% uptime SLA
- Enterprise SLA available
SDK Integration
Embed directly in your application. Runs in your codebase with full programmatic control.
npm install @private.me/xprint- TypeScript/JavaScript SDK
- Full source access
- Enterprise support available
On-Premise Upon Request
Enterprise CLI for compliance, air-gap, or data residency requirements.
- Complete data sovereignty
- Air-gap capable deployment
- Custom SLA + dedicated support
- Professional services included
Enterprise On-Premise Deployment
While xPrint is primarily delivered as SaaS or SDK, we build dedicated on-premise infrastructure for customers with:
- Regulatory mandates — HIPAA, SOX, FedRAMP, CMMC requiring self-hosted processing
- Air-gapped environments — SCIF, classified networks, offline operations
- Data residency requirements — EU GDPR, China data laws, government mandates
- Custom integration needs — Embed in proprietary platforms, specialized workflows
Includes: Enterprise CLI, Docker/Kubernetes orchestration, RBAC, audit logging, and dedicated support.