If your organization operates in Illinois, employs people in Illinois, or serves Illinois residents, there’s a good chance you have technology systems that touch biometric data. Sometimes it’s obvious, like a fingerprint time clock. Other times it’s hidden in the background, like a vendor-hosted access control platform, a call center tool that uses voice authentication, or a camera system that offers face matching features.
The Illinois Biometric Information Privacy Act (BIPA) is one of the most consequential biometric privacy laws in the country. It’s also one of the easiest to overlook because it lands at the intersection of legal, HR, physical security, and IT operations. In practice, BIPA compliance is not just a policy exercise. It’s a technology systems exercise.
This article is general information, not legal advice. BIPA exposure is highly fact-specific. A good next step is to review your specific use cases with legal counsel and then make sure your IT and security program can support the policies you put in place.
What BIPA considers “biometric identifiers” and “biometric information”
BIPA uses two related terms that matter for technology planning.
A biometric identifier includes a retina or iris scan, fingerprint, voiceprint, or scan of hand or face geometry. The statute also lists several exclusions, including items like photographs, written signatures, and certain health care-related information and imaging.
Biometric information is any information (regardless of how it’s captured, converted, stored, or shared) that is based on an individual’s biometric identifier and used to identify that person.
The practical takeaway is that “biometrics” is not limited to fingerprint readers. If a system is using biometric identifiers to identify a person, it can become a BIPA issue quickly.
The BIPA requirements that directly impact your systems and processes
BIPA is often summarized as “get consent and have a policy,” but the actual operational requirements are more detailed. The parts most likely to affect your day-to-day technology operations are in Section 15 of the Act.
Here are the core requirements that frequently show up in real-world business environments:
1) Publish a written retention and destruction policy
If you possess biometric identifiers or biometric information, BIPA requires you to develop a written policy (made available to the public) that includes a retention schedule and guidelines for permanently destroying biometric data when the original purpose is satisfied or within 3 years of the individual’s last interaction with the organization (whichever occurs first).
From a technology standpoint, this requirement forces uncomfortable but important questions:
- Where is biometric data stored today?
- Can you actually delete it on schedule?
- Is deletion happening in one system, or in multiple downstream systems (vendor platforms, integrations, exports, backups)?
- What is your “last interaction” trigger for employees, former employees, customers, and visitors?
2) Provide written notice and obtain a written release before collection
Before collecting or obtaining biometric identifiers or biometric information, BIPA requires that you inform the individual in writing that biometrics are being collected or stored, inform them in writing of the specific purpose and length of time for which the data is being collected/stored/used, and receive a written release.
This is where many organizations get into trouble with common tools like biometric time clocks and access control systems, especially when a vendor installs the system and “it just works” without the internal business implementing the matching notice and consent workflow.
3) Do not sell or profit from biometric data, and limit disclosures
BIPA prohibits selling, leasing, trading, or otherwise profiting from a person’s biometric identifiers or biometric information.
BIPA also restricts disclosure, redisclosure, or dissemination of biometrics unless certain conditions apply (for example, consent or other specific statutory exceptions).
This is one reason vendor management matters so much. A biometric vendor, subcontractor, or integrator can create legal and security risk if contracts, access, and data handling are not clearly controlled.
4) Protect biometric data using appropriate security practices
BIPA requires that a private entity store, transmit, and protect biometric identifiers and biometric information using a reasonable standard of care within its industry, and in a way that is the same as or more protective than how the organization protects other confidential and sensitive information.
In other words, BIPA is not only about consent. It is also about security.
The 2024 BIPA amendment: why it matters for compliance planning
BIPA enforcement and litigation has been a major issue for Illinois businesses for years, and Illinois made an important update in 2024.
Public Act 103-0769 (effective August 2, 2024) amended BIPA by changing Sections 10 and 20.
Two changes are especially relevant to day-to-day operations:
- “Written release” now explicitly includes an electronic signature (along with informed written consent and, in employment, a release executed as a condition of employment).
- The Act now treats repeated collection or repeated disclosure of the same biometric data from the same person (using the same method) as a single violation for purposes of recovery in certain scenarios under Sections 15(b) and 15(d).
This amendment does not eliminate the need for a real compliance program. It does, however, change how many organizations think about exposure, consent workflows, and what “repeat scans” mean when an employee clocks in every day.
The safest operational stance is still the same: treat biometric data as high-impact, document your process, and keep the technology aligned with the policy.
Common technology systems that can trigger BIPA obligations
Most BIPA problems start with a simple operational decision: “This will make the process faster.” That’s the entire appeal of biometrics.
Below are the most common systems we see that can bring BIPA into scope:
Biometric time clocks and workforce attendance systems
Fingerprint and hand geometry timekeeping systems are a classic BIPA trigger. They often involve:
- A biometric reader on-site
- A management console (sometimes cloud-hosted)
- An HR or payroll workflow that depends on the attendance records
- A vendor relationship that may include data hosting and support access
If you can’t clearly explain what biometric data is collected, where it’s stored, and how it gets destroyed on schedule, you’re likely relying on assumptions. That is a risky place to be.
Access control, door entry, and facility security platforms
Modern access control can include fingerprints, facial matching, or other biometric methods. In many buildings, access control also integrates with cameras, visitor management, and alarms.
This creates a BIPA plus cybersecurity issue: you are not only managing identity. You are also managing physical entry to facilities. If those systems are misconfigured, the impact is not limited to privacy.
Facial recognition features in camera systems
BIPA’s definition of biometric identifiers includes scans of face geometry, while excluding photographs.
This is one area where organizations need to be careful and specific. A standard security camera recording video is not the same thing as a system actively generating a face geometry template for identification purposes. Whether a particular feature set triggers BIPA can depend on how the system works and how you use it.
If your security camera environment offers facial recognition or face matching, it’s worth having a structured conversation with counsel and your IT/security team to confirm what is enabled, what is stored, and what is being shared.
Voice authentication in customer service or internal systems
Voiceprints are explicitly called out as a biometric identifier.
If you use voice authentication to verify callers (or if a vendor provides that for your organization), you may need BIPA-aligned notice, consent, retention, and security practices.
Mobile apps and “biometric login” features
Many apps allow users to log in with Face ID or fingerprint authentication on their phones. Whether that creates BIPA obligations depends on whether your organization (or your vendor) is collecting or possessing biometric identifiers/biometric information, or whether the phone’s operating system is simply being used to unlock a stored credential.
This is a good example of why BIPA is not just an HR issue. It is a technology architecture issue.
A practical BIPA technology checklist for Illinois businesses
BIPA compliance becomes manageable when you treat it like any other risk management program: inventory, controls, monitoring, documentation, and periodic review.
Here’s a practical approach that works well for many smaller and mid-sized organizations.
Step 1: Build a biometric system inventory
Start by listing every system that might involve biometrics:
- Time clocks and attendance systems
- Access control and door entry
- Visitor management kiosks
- Cameras with advanced analytics
- Authentication tools (including voice verification)
- Any vendor platforms that store biometric templates or identifiers
For each system, document:
- What biometric identifier is involved (fingerprint, voiceprint, face geometry, etc.)
- Where the biometric data is stored (on device, on server, in vendor cloud)
- Who has administrative access
- Which vendors or subcontractors can access or receive the data
- How deletion works in practice
- Whether the system is integrated with other tools (HR, payroll, facility platforms)
This inventory becomes the spine of your BIPA program because it links policy language to actual technology.
Step 2: Map the data flow, including vendors and integrations
BIPA risk often hides in the handoffs:
- Device to local controller
- Local controller to vendor cloud
- Vendor cloud to an HR/payroll system
- Vendor support staff access for troubleshooting
- Data exports for reporting or audits
Once you understand the data flow, you can enforce least privilege and reduce unnecessary sharing.
Step 3: Implement a consent workflow that matches the technology
If your consent process is paper-based but your system is deployed across multiple sites with frequent onboarding, you may have gaps.
The 2024 amendment clarifying that a written release can include an electronic signature makes it easier for many organizations to capture and track consent digitally, when appropriate.
The key is to ensure you can prove your workflow is consistent:
- Notice provided
- Purpose and retention explained
- Release captured before collection
- Release retained securely
- Release tied to the person and the system(s) involved
Step 4: Align retention and destruction with reality
BIPA requires a public written policy with retention and destruction guidelines, and the law ties destruction timing to the purpose being satisfied or within 3 years of last interaction (whichever comes first).
A policy is not enough if the system cannot execute it.
In practical terms, you need a deletion process that accounts for:
- The live biometric system
- Vendor-hosted storage
- Backups (including long retention backups)
- Exports and reports that contain biometric-related information
- Test environments (often overlooked)
Step 5: Secure biometric systems like high-value assets
BIPA requires protecting biometric data using a reasonable standard of care and at least as protectively as other sensitive information.
From an IT and cybersecurity perspective, that typically means:
- Strong authentication and MFA for admin portals
- Role-based access control so only authorized staff can access biometric administration
- Network segmentation for biometric devices (especially physical security systems)
- Encryption in transit and at rest where applicable
- Centralized logging and alerting for administrative access and unusual behavior
- Continuous monitoring for high-risk environments (often through a SOC)
- Secure patching and lifecycle management for devices and controllers
Also, remember that physical security and cybersecurity overlap here. A biometric reader on the network is still a networked device. If it’s poorly managed, it can become an entry point into the rest of the environment.
Step 6: Treat biometric vendors as a core part of your risk program
Even if a vendor hosts the biometric platform, your organization still owns the risk.
A basic vendor risk management approach for biometric systems usually includes:
- Contract language that clearly restricts use and sharing of biometric data
- Security requirements appropriate to the sensitivity of biometric information
- Breach notification obligations and response coordination expectations
- Clarity on subcontractors and where data is stored
- A documented process for periodic review and re-approval of the vendor
If you want to reduce risk further, consider a standard security addendum approach for key vendors so expectations are clear and consistent across partners.
Audits, assessments, and documentation: how to prove you take BIPA seriously
BIPA compliance is easier to defend when your organization has repeatable evidence of good practices.
For many businesses, that includes:
- A BIPA readiness review to confirm what systems are in scope
- Written policies and procedures aligned with actual system behavior
- Security assessments that validate controls (not just intentions)
- Periodic vulnerability and configuration reviews of connected devices
- Vendor documentation and contract records
- Incident response planning that includes biometric systems
Even if you’re not pursuing a formal certification, approaching BIPA like an audit-ready program helps. It keeps the program from drifting over time as vendors, systems, and workflows change.
How ChicagoTG supports BIPA-aligned technology and security programs
Chicago Technology Group (ChicagoTG) works with Chicago-area and Illinois organizations that want practical, enterprise-grade IT management and cybersecurity without turning compliance into a never-ending internal project.
For BIPA and biometric systems specifically, support commonly includes:
- Secure IT Support and Secure IT Management to keep systems maintained, patched, and governed
- Advanced Security services such as monitoring, detection, and response across critical systems
- Cyber Assurance Shield for ongoing compliance-as-a-service and cyber liability risk management
- vCSO services to help build the program structure, documentation, and reporting cadence
- Physical security services like cameras, access control, and environmental sensors, designed with security-first network architecture in mind
The goal is not to drown you in paperwork. The goal is to make sure your policies, vendors, and technology systems all line up so you can run the business confidently.
A simple next step if you use biometrics in Illinois
If your organization uses biometric time clocks, biometric access control, voice authentication, or any system that could involve biometric identifiers, it’s worth doing a structured review. You don’t need a massive project to start. You need clarity on what you have, where the data goes, and whether your controls and documentation match BIPA expectations.
If you’d like help scoping your biometric systems and building a right-sized plan to reduce risk, reach out to ChicagoTG. We’ll be happy to talk through your environment and outline practical next steps.





