A little more context.
The project, its limitations and where to find the work.
What is BioAuth?
BioAuth is a TED University CMPE 492 senior design project. Its research focus is a quality- and attack-aware engine that fuses one-to-one face verification, visual presentation attack detection and physiological evidence.
Does a pulse prove that a capture is live?
No. rPPG extracts pulse-related optical changes from facial video, but replayed or synthetic video can contain pulse-like patterns. The design treats physiology as one required evidence channel, alongside face, PAD and capture quality—not as independent proof of liveness or freshness.
What is the difference between REJECT and RETRY?
REJECT requires a reliable rejection reason, such as a qualified identity mismatch or strong attack evidence. RETRY means required evidence is missing, unreliable or inconclusive. Missing or unusable rPPG prevents acceptance but does not, by itself, prove an attack.
Is the public simulation the actual biometric engine?
No. The console is an earlier, illustrative scenario simulation with generated signals and scores. Its challenge-response logic is distinct from the current design report. It does not run face matching, PAD or real rPPG analysis, and it produces no measured research results.
Where can I find the reports and backlog?
The Reports page contains the four CMPE 491 reports, the CMPE 492 Low-Level Design Report v1 and planned deliveries. Each available PDF can be opened or downloaded. The Progress page contains semester milestones and the backlog publication archive; backlog files are still awaiting publication.
Is the project production-ready?
The project is in its design and implementation phase. Model thresholds, measured accuracy and runtime performance require validation. This site describes academic work and should not be used to authorize real transactions.
What is planned for biometric data?
The design keeps ordinary session frames transient, stores approved reference templates encrypted, and defines a separate temporary lifecycle for enrollment review evidence. These are planned system requirements. The public scenario simulation sends scenario settings, not camera frames, to its mock API.