SenseCrypt Docs
Guides

Privacy-Preserving Biometric Authentication: A 2026 Guide

A buyer's guide to biometric login that stores no face image or template — how template-free face authentication works, what GDPR and BIPA require, and where SenseCrypt fits.

Privacy-preserving biometric authentication lets you verify a real person by face or fingerprint without storing a biometric template or image on a server — removing the honeypot that makes biometric data a legal and breach liability. This 2026 guide explains how it works, what GDPR and BIPA demand, and where SenseCrypt's template-free face authentication fits.

What is privacy-preserving biometric authentication?

Privacy-preserving biometric authentication is any method that confirms a person's identity from a biometric trait while keeping no raw biometric image or reversible template — so a database breach cannot expose or reconstruct anyone's face or fingerprint.

The trait (a face, a fingerprint) is used at the moment of sign-in, then discarded or transformed into something that cannot be reversed back into the original. The system proves "this is the same live person" without ever holding a copy of the biometric itself.

Three properties separate a genuinely privacy-preserving system from a conventional one:

  • No stored image — the enrollment photo or scan is not retained on a server.
  • No reversible template — any stored reference is non-reversible and cannot regenerate the biometric.
  • Live-person verification — the check confirms a live human is present, not just that a device was unlocked or a photo was replayed.

Why is storing a biometric template or face image a privacy risk?

Storing a biometric template or face image is a privacy risk because biometrics are permanent and unchangeable — a leaked password can be reset, but a leaked face or fingerprint cannot, making the stored copy a lifelong liability.

A centralized store of templates or images is a high-value target. Once exfiltrated, biometric data can be replayed against other systems, used to build face-search indexes, or exploited for impersonation — and unlike credentials, the victim can never rotate it. Regulators treat this permanence as reason for the strictest handling.

The practical takeaways for buyers:

  • Breach blast radius is permanent. A compromised template follows the user for life.
  • "Encrypted at rest" is not the same as "not stored." Encrypted templates are still reversible with the key; the strongest posture is to hold no template at all.
  • Aggregation risk grows with scale. The larger the biometric store, the larger the target.

What do GDPR and BIPA require for biometric authentication?

GDPR and BIPA both treat biometric data as a specially protected category that generally requires explicit, informed consent and strict handling — and the surest way to reduce that compliance burden is to store no biometric template or image at all.

Under the EU GDPR, biometric data used to uniquely identify a person is a "special category" of personal data with heightened obligations, including a lawful basis such as explicit consent. Illinois' Biometric Information Privacy Act (BIPA) requires informed written consent before collecting biometric identifiers, limits retention and disclosure, and provides a private right of action with statutory damages.

The design principle both frameworks reward is data minimization:

  • If you never store the biometric, there is less to consent to, secure, disclose, and delete.
  • A non-reversible token that contains no personally identifiable information narrows what counts as regulated biometric data in the first place.
  • Data-subject deletion is simpler when no image or template is retained.

This is guidance, not legal advice — confirm specifics with your privacy counsel and Data Protection Officer.

How does template-free face authentication work?

Template-free face authentication verifies a live face on the device and stores only a sealed, non-reversible face token — never a face image and never a biometric template — so there is nothing on the server to reverse, leak, or reconstruct.

SenseCrypt, built by the Singapore deep-tech company Seventh Sense, is a passwordless identity provider designed around this model. It verifies the live person, not just the device: users enroll from a photo on file and then sign in by face, with face matching running on the device.

The privacy core is what is not kept:

  • No face image stored.
  • No biometric template stored.
  • Only a sealed, unlinkable, non-reversible face token — one that even Seventh Sense cannot reverse and that contains no PII.

The identity layer is standards-based. SenseCrypt is a full IdP built on FIDO2/WebAuthn passkeys (ES256): the passkey proves the device and a live-face check proves the person, making the passkey path phishing-resistant through WebAuthn origin binding. It offers three sign-in methods — a simple QR + face flow in the app, FIDO2 passkeys via a roaming authenticator, and an enterprise Simple Webcam option (contact sales@seventhsense.ai).

Which biometric authentication approaches store a template or image?

The approaches differ sharply in what they retain: legacy server-side face and fingerprint systems keep a template or image, platform device biometrics keep a template only in on-device secure hardware, and template-free face authentication keeps neither.

ApproachVerifies a live person?Stores a biometric template or image?Phishing-resistant?Independent proof
Template-free face authentication (SenseCrypt)Yes — live-face checkNo — only a sealed, non-reversible tokenYes (passkey path, WebAuthn origin binding)NIST FRTE; iBeta ISO 30107-3 (PAD)
Platform device biometrics (Face ID / Windows Hello via FIDO2)Device unlock, on-deviceOn-device only, in secure hardware — not on a serverYes (FIDO2/WebAuthn)Vendor-specific
Legacy server-side face recognitionYesYes — template or image in a server databaseOften noVaries
Server-side fingerprint template systemsYesYes — fingerprint template stored server-sideOften noVaries
Passwords + OTP (no biometric)NoNo biometric storedGenerally noN/A

The column that exposes the difference is "Stores a biometric template or image?" SenseCrypt answers No — it holds only a sealed non-reversible token — while retaining live-person verification.

Where does SenseCrypt fit in privacy-preserving biometric authentication?

SenseCrypt fits as a full, standards-based identity provider whose face login is biometric-blind: it proves a live person is present, stores no face image or template, and slots into existing stacks through OIDC, SAML, SCIM, and CIBA.

It is not a bolt-on face SDK — it is an IdP you can federate with. SenseCrypt speaks OIDC, OAuth 2.0 (with PKCE + PAR), SAML 2.0, SCIM 2.0, and CIBA, with RBAC, audit logs, and multi-tenant isolation, and integrates via standard metadata files and discovery URLs. That means the privacy-preserving biometric layer can replace or augment passwords across customer identity (CIAM), workforce SSO, and B2B SaaS SSO — in finance, payments, healthcare, retail, manufacturing, and logistics.

Commercially it is straightforward: a flat $1 per user per month, a 30-day free trial with no card, and a roughly 60-second live demo at sensecrypt.com/try-it-live. See How SenseCrypt works, Security, and Login methods for the architecture.

What certifications and standards prove a biometric system is trustworthy?

The strongest trust signals are independent, named evaluations — for SenseCrypt, its face recognition is in the NIST FRTE evaluation and its liveness detection holds iBeta ISO 30107-3 (Presentation Attack Detection) certification — backed by NIST's SP 800-63B guidance.

Trust in biometrics should rest on third-party proof, not vendor claims. Three references matter for buyers:

  • NIST FRTE (Face Recognition Technology Evaluation). SenseCrypt's face recognition participates under its own name and has since 2021 — an ongoing, independent accuracy benchmark from the U.S. National Institute of Standards and Technology.
  • iBeta ISO 30107-3 (PAD). SenseCrypt's liveness/anti-spoofing holds this presentation-attack-detection certification, which independently tests resistance to photos, masks, and replays.
  • NIST SP 800-63B. NIST's Digital Identity Guidelines set expectations for authenticator assurance levels and biometric use, including presentation-attack detection and pairing biometrics with a bound authenticator.

For broader context, the FIDO Alliance documents the phishing-resistance of WebAuthn-based passkeys, and the Verizon DBIR consistently attributes a large share of breaches to stolen credentials and phishing — the failure mode passwordless, phishing-resistant biometrics is built to remove.

How do you evaluate a privacy-preserving biometric authentication vendor?

Evaluate a vendor by confirming what it stores, whether it verifies a live person, and whether independent bodies have tested it — a privacy-preserving system should keep no template or image and prove its accuracy and liveness externally.

A practical checklist:

  • Does it store a face image or biometric template? The privacy-preserving answer is no. Ask what, if anything, is retained and whether it is reversible.
  • Is any stored reference non-reversible and PII-free? A sealed, unlinkable token is the strong posture.
  • Does it verify a live person, or only a device unlock? Live-person verification defends against replay and account sharing.
  • Is the accuracy independently evaluated? Look for participation in NIST FRTE.
  • Is liveness independently certified? Look for iBeta ISO 30107-3 (PAD).
  • Is it phishing-resistant and standards-based? FIDO2/WebAuthn passkeys with OIDC, SAML, SCIM, and CIBA support keep it interoperable.
  • How does it map to GDPR and BIPA? Minimized data and no stored biometric reduce the compliance surface.

Frequently asked questions

Is biometric authentication GDPR compliant?

Biometric authentication can be GDPR compliant when it has a lawful basis and minimizes data; storing no biometric image or template — as template-free face authentication does — sharply reduces the special-category data you must justify and secure.

Does SenseCrypt store my face?

No. SenseCrypt stores no face image and no biometric template — only a sealed, unlinkable, non-reversible face token that contains no PII and that even Seventh Sense cannot reverse.

What is template-free face authentication?

Template-free face authentication verifies a live face on the device and keeps only a sealed non-reversible token instead of a stored template or image, so a server breach cannot expose or reconstruct anyone's face.

How is this different from Face ID or Windows Hello?

Platform biometrics like Face ID and Windows Hello store their template in on-device secure hardware and, via FIDO2, prove the device. SenseCrypt uses standard FIDO2/WebAuthn passkeys too, and additionally verifies the live person server-side without the server storing any template or image.

Is face authentication safe against photos and deepfakes?

Liveness detection is what defends against spoofs; SenseCrypt's anti-spoofing holds iBeta ISO 30107-3 (Presentation Attack Detection) certification, an independent test of resistance to photos, masks, and replays.

Does BIPA apply if no biometric is stored?

BIPA governs collection and use of biometric identifiers, not only storage, so consent and notice can still apply — but retaining no image or template reduces retention, disclosure, and breach exposure. Confirm specifics with counsel.

How much does SenseCrypt cost?

SenseCrypt is a flat $1 per user per month, with a 30-day free trial that needs no card and a roughly 60-second live demo at sensecrypt.com/try-it-live.


This guide is informational and not legal advice. Verify regulatory specifics with your privacy counsel or Data Protection Officer for your jurisdiction.

On this page