What Princeton Identity is
Princeton Identity builds biometric identity products centered on iris and facial recognition. Its published portfolio includes EyeAllow, several Access-series devices, and Identity Server software. Depending on the device and configuration, a workflow can combine biometrics with cards, mobile credentials, PINs, QR codes, or multiple authentication factors.
This category is different from general camera analytics. A security camera may classify activity or help investigate an incident. A biometric access system is used to establish that a person presenting at a controlled point matches an enrolled identity. That distinction raises the assurance level, but it also raises the importance of enrollment, privacy, fallback, accessibility, audit, and integration design.
Where biometric access fits
- High-assurance areas: the risk justifies stronger identity verification than possession of a card alone.
- Contactless workflows: the site needs fast identity verification without relying only on a touched reader or shared credential.
- Multi-factor entry: policy calls for a biometric plus a card, mobile credential, PIN, or other factor.
- Identity-sensitive operations: the organization can support controlled enrollment, documented consent or other lawful basis, and defined exception handling.
Biometrics are not automatically better for every opening. Standard card, mobile, or PIN credentials may be easier to administer and more proportionate for ordinary office doors. Emergency egress and life-safety requirements remain independent of authentication technology. Tec-Tel begins with the door risk and operating policy, then determines whether biometrics solve a real problem.
How Princeton Identity fits an access-control stack
The biometric device is one part of a complete system. The project still needs controllers, locks, door-position switches, request-to-exit devices, power, network, access rules, schedules, visitor handling, alarm behavior, and a physical access-control system. Princeton Identity publishes Identity Server integrations with multiple PACS platforms, but the specific version, licensing, data path, and support boundaries must be confirmed for each project.
Enrollment is equally important. The organization needs an approved process for creating, updating, suspending, and deleting identities. It also needs a fallback for people who cannot or should not use the biometric method, plus a recovery process for device, network, or server interruptions.
A responsible evaluation sequence
- Define the risk: document why a standard card or mobile credential is insufficient for the selected opening.
- Review policy and law: involve privacy, legal, labor, security, and accessibility stakeholders before collecting biometric data.
- Confirm the PACS path: validate the controller, access platform, directory, identity records, licensing, and audit behavior.
- Design enrollment and fallback: specify who enrolls users, where templates reside, how revocation works, and how exceptions enter.
- Pilot the full door: test authentication, denial, emergency egress, network loss, device failure, visitors, and help-desk procedures.
Questions to answer before purchase
- Which biometric mode and additional credential factors are required?
- Where are biometric templates stored, protected, retained, and deleted?
- Which PACS version and integration method will authorize the door?
- How are visitors, contractors, accessibility needs, and enrollment failures handled?
- What happens during power, network, identity-server, or device failure?
- Who owns privacy notices, consent where applicable, audit, and incident response?
Primary product sources
Review Princeton Identity's current product and capability overview and Identity Server data sheet. This page is technical planning information, not legal advice. Requirements for biometric information vary by jurisdiction and use case.