Five biometrics. One smartphone. Zero specialized hardware.
Iris, palm, ear, voice, PPG pulse, and selfie liveness โ six signals spanning something you are and point in time. Device attestation and geofencing extend to 4 factors.
No IR scanners, no vein sensors, no fingerprint readers. Uses the cameras and microphone already in every modern phone.
Compromise one signal, learn nothing about the others. An attacker must defeat 3+ unrelated modalities simultaneously.
Auth broker pattern โ no rip-and-replace. Compatible with existing SSO, ICAM, CAC/PIV, and zero trust frameworks.
Front camera
30% weight
Rear camera
30% weight
Microphone
25% weight
Front camera
15% weight
Rear camera
Liveness gate
All processing on-device. Raw biometric data never leaves the phone.
Phase-structure encoding from visible-light capture.
Placeholder UI โ drop in a real app screenshot at signals/iris.png before presenting.
Texture and line structure from contactless palm imaging.
Placeholder UI โ replace with signals/palm.png when ready.
Speaker embedding with time-bound digit challenge.
Placeholder UI โ replace with signals/voice.png when ready.
Cartilage geometry from profile capture.
Placeholder UI โ replace with signals/ear.png when ready.
Pulse-based liveness via camera; vetoes non-living presentation.
Placeholder UI โ replace with signals/vitals.png when ready.
Active liveness challenges (e.g., blink, motion) per session.
Placeholder UI โ replace with signals/presentation.png when ready.
Random blink + head turn challenges. Must respond in real time within a timeout window.
Defeats: photos, masks, screen replays
Detects cardiac blood pulse through fingertip. Vetoes entire authentication if no live pulse.
Defeats: all non-living artifacts
Time-bounded rotating 6-digit code (30s window). User must speak the current code live.
Defeats: pre-recorded audio replay
All liveness gates must pass. A perfect biometric match is rejected if liveness fails.
Fusion requires weighted majority of factors to pass AND all liveness gates to pass.
Figures derived from internal benchmarking under controlled conditions with a limited test population. Combined FAR computed from per-factor independence assumptions. Not NIST Biometric Evaluation Program results. Independent validation scoped for pilot phase.
Security through factor independence, not hardware specialization.
BioTone never stores biometric templates or key material.
On-premises or customer-controlled. Holds Key Part 1.
Azure, AWS, Oracle, or Google โ customer's choice. Holds Key Part 2.
Enrolled phone's secure enclave (Keychain/Keystore). Holds Key Part 3.
No single party โ including BioTone โ can reconstruct a template or authenticate on behalf of a user.
Architecture designed for alignment with federal identity and biometric standards. Formal validation scoped during pilot engagement.
AES-256-GCM for all biometric template data and disaggregated key parts. Each key part independently encrypted at its storage location.
TLS 1.3 for all API communication. Certificate pinning on mobile clients. No biometric data transmitted โ only assertion tokens.
Hardware-backed storage: iOS Secure Enclave (Keychain) and Android TEE (Keystore). Key Part 3 never leaves hardware security boundary.
Uses FIPS 140-2 validated cryptographic libraries (Apple CryptoKit, Android Keystore). Full FIPS 140-3 module validation scoped for pilot phase. Architecture supports CNSA Suite 2.0 cipher selection for NSS environments.
Entra ID (live today)
Okta + Ping (near-term)
Standard OIDC / SAML
Complementary factor alongside physical credentials
Offline-capable with cached credentials
Customer deploys our server software on their infrastructure. Data and liability stay with the customer.
Session confidence decays over time. Multi-signal architecture enables tiered re-verification from passive to active.
Policy-configurable per security context. SCIF, enterprise, and tactical edge each get the cadence their threat model requires.
Customer-hosted backend on government or corporate infrastructure. Full data sovereignty.
Azure Gov, AWS GovCloud, or customer-specified environment at IL5. FedRAMP High / GCC High on roadmap.
On-device verification with locally cached credentials. Trades disaggregation for offline capability. Policy-controlled session limits. Syncs when connected.
Device enrollment binds identity to a specific phone. Re-enrollment required for device change.
Timeline from PoC to pilot is driven by customer requirements. We move at your pace.
Five biometrics. One smartphone. Zero specialized hardware.
CEO, BioTone Corporation
CTO, Engineering Lead
Confidential โ shared for evaluation purposes