Frequently Asked Questions

FaceLock relies on UR Code technology plus PKI signing. The biometric template, credential details, and cryptographic signatures all live inside the QR code itself, so there's no server to call. The FaceLock Reader app checks the signatures and runs the biometric match using the phone's own processor, which means verification works with zero connectivity.

Most digital credentials only prove a device or certificate is valid — they can't confirm the right person is holding it. FaceLock closes that gap by binding the credential to the holder's face, using FaceTec's 3D liveness detection, certified iBeta Level 1 and Level 2. The biometric template is sealed inside the credential itself, so verifying it means checking both the credential and the person standing in front of you.

FaceLock uses FaceTec's 3D liveness detection, certified iBeta Level 1 and Level 2, the standard for biometric accuracy and anti-spoofing testing. It tells a live person apart from a photo, video, mask, or other spoof attempt, and the 3D facial map holds up across lighting changes, aging, and minor shifts in appearance.

Timelines depend on how complex your organization and integrations are. A simple pilot can launch in 30-60 days. Full production rollouts usually take 90-180 days, covering stakeholder training, system integration, and process changes. Our implementation team handles project management, training, and technical support along the way.

FaceLock doesn't need special hardware. To issue credentials, you need the FaceLock Creator app on a standard iOS or Android device. To verify one, any relying party can use the free FaceLock Reader app on any smartphone with a camera — no proprietary readers or scanners to buy, which keeps this within reach for organizations with tight technology budgets.

Biometric templates are created once, at issuance, and sealed inside the credential. They don't get stored on a server or travel anywhere else. During verification, the match happens locally on the verifier's device, comparing the person in front of the camera to the template already in the credential. No biometric data is collected, stored, or transmitted as part of that process.

FaceLock typically lowers total cost of ownership by cutting expenses tied to traditional systems: help desk calls, fraud remediation, infrastructure upkeep, and manual verification overhead. Because verification works offline, you're not paying for network dependencies either. Exact pricing depends on deployment scale, but most organizations see ROI within 12-18 months from reduced fraud and lower operational costs.

For end users, FaceLock is simpler than most verification methods in use today. Scan, look, verify. No passwords, no app to download just to get verified, no account to create. The cryptography and biometric matching happen behind the scenes; what the person in front of the camera sees is a scan and their own face.

Fair point, and worth checking against what your current system actually verifies. Most systems confirm that a certificate or device is valid, not that the person presenting it is who they claim to be. That's the gap FaceLock closes: the credential itself carries the biometric check, so whoever is relying on it isn't just trusting a card or a login token, they're checking the person standing in front of them.

FaceLock collects nothing during verification: no accounts, no usage tracking, no biometric data sent anywhere. The template stays sealed inside the credential instead of living in a database. Compared to systems that log every verification attempt, FaceLock's verification step leaves no data trail behind.