Key takeaways
- BIPA lists voiceprints as biometric identifiers, and people can sue without showing harm beyond the violation itself[1][2].
- A call recording or transcript is not the same as a voiceprint; the risk starts when a tool measures a voice to tell who is speaking.
- Before any voiceprint: a public retention policy, written notice of purpose and term, and a written release[1].
- Ask every phone vendor in writing whether any feature creates voice templates, and get the answer into the contract.
Why an Illinois plumbing office should care
Illinois' Biometric Information Privacy Act is short, old and expensive. It names a voiceprint as a biometric identifier, alongside fingerprints, retina and iris scans and scans of hand or face geometry[1]. Anyone aggrieved by a violation can sue, and a prevailing plaintiff recovers $1,000 per negligent violation or $5,000 per intentional or reckless one, or actual damages if higher, plus attorneys' fees and expert costs[1].
The Illinois Supreme Court gave that right of action its bite in 2019. In Rosenbach v. Six Flags, it held that a person need not show any actual injury or adverse effect, beyond the violation of their rights under the Act, to seek liquidated damages[2]. A missing consent form is enough to start a case.
For most trades businesses the familiar BIPA exposure is the fingerprint or face-scan time clock for technicians. Voice is newer. It arrives quietly inside phone systems, call analytics and features that promise to recognize repeat callers or verify staff by voice. If your office is in Illinois, serves Illinois homes or employs people there, this is the part to understand before anything gets switched on.
Recording, transcript or voiceprint?
BIPA lists voiceprints but never defines the word[1]. Biometric information, the second category it protects, is information based on a biometric identifier that is used to identify an individual[1]. A sensible working reading, until a court says otherwise: a voiceprint is a measurement of someone's voice kept so a system can tell who is speaking. A recording of what they said, and a transcript of it, are not built for that job.
Other laws draw the line in different places, which is why the reading matters. Washington's biometric law lists voiceprints but expressly excludes audio recordings and data generated from them, and only the attorney general can enforce it[3]. The FTC goes the other way for its own purposes: its 2023 policy statement counts recordings of a person's voice, and data derived from them, as biometric information where the person could reasonably be identified[4]. BIPA sits between the two, with no audio exclusion and a private right to sue.
| What the phone tool does | What it creates | Where it sits under BIPA |
|---|---|---|
| Records calls for review | An audio file of the conversation | Not on BIPA's list; recording consent laws apply instead |
| Transcribes and summarizes calls | Text of what was said | Text, not a measurement of the voice |
| Recognizes repeat callers by voice | A stored voice template for each caller | Looks like a voiceprint used to identify someone: notice, release and retention rules |
| Verifies staff by spoken passphrase | An enrolled voiceprint for each employee | Voiceprint; written release from each employee first |
| Clones a voice for greetings | A model of one person's voice | Ask how the model is built and whether it can identify the speaker |
| Scores tone or sentiment | Scores for each call | Ask whether any template per speaker is kept |
Recording raises its own question: consent to record. Federal law allows a call to be recorded when one party consents[5], but some states require everyone on the call to agree. Those rules are covered in call recording consent rules for plumbing companies.
What BIPA requires before any voiceprint is taken
If a tool does create voiceprints, BIPA's duties fall on any private entity that collects, obtains or holds them[1]. That can be you as well as the vendor that built the feature. The duties come in a fixed order.
- A written policy, available to the public, with a retention schedule. Voiceprints must be permanently destroyed when the original purpose is satisfied or within 3 years of the person's last interaction with you, whichever comes first[1].
- Written notice to the person that a voiceprint is being collected or stored[1].
- Written notice of the specific purpose and of how long it will be collected, stored and used[1].
- A written release from the person, before collection starts[1].
- No selling, leasing, trading or otherwise profiting from it, and no disclosure without consent or a legal requirement[1].
- Protection at least as strong as you give other confidential information, such as account numbers and Social Security numbers[1].
Each is a separate obligation. A good privacy page does not replace a signed release, and a release does not excuse keeping the voiceprint of a customer who last called four years ago.
The public policy does not need to be long. One page on your website, linked from the hiring paperwork, can cover it. Here is an example outline for a shop whose only biometric is a fingerprint time clock for technicians:
- What we collect: fingerprint templates from the time clock, and no voice or face data from callers.
- Why: to record working hours accurately, and for no other purpose.
- How long: deleted when employment ends, and never later than 3 years after the person's last interaction with us[1].
- Who holds it: the time clock vendor, named, with a link to its own policy.
- Who sees it: nobody outside the vendor and the company unless the person consents or the law requires it[1].
- How it is protected: at least as carefully as Social Security numbers and bank details[1].
- Who to ask: the office manager's name and email address.
What the 2024 amendment changed, and what it did not
Public Act 103-769, effective August 2, 2024, made two changes that matter to small businesses. Collecting the same voiceprint from the same person by the same method, again and again, now counts as one violation with at most one recovery, and repeated disclosure to the same recipient counts once too[1]. And the written release can now be an electronic signature, defined much as federal law defines it[1]. Our guide to e-signatures on estimates and contracts covers what makes an electronic signature hold up.
The amendment did not touch the size of each recovery or the private right to sue. Exposure still grows with the number of people involved.
Source: Illinois General Assembly, 2026[1]
Show the data
| Type of violation | Liquidated damages |
|---|---|
| Negligent ($1,000 each) | $300,000 |
| Intentional or reckless ($5,000 each) | $1,500,000 |
Example: a busy residential shop hears from about 300 distinct repeat customers a year. If a caller-recognition feature quietly enrolled each of them without notice or a release, the liquidated damages ceiling would be $300,000 if the violation were negligent and $1.5 million if reckless[1], before attorneys' fees. The amendment stops the count multiplying with every call. It does not stop it multiplying with every caller.
Callers and employees are different problems
BIPA's consent must be in writing, and it must come first[1]. With employees that is manageable. In employment, a release signed as a condition of employment counts[1], so voice login for a phone system or a fingerprint time clock can be handled at hire with the rest of the onboarding paperwork. Describe the policy in the employee handbook and keep each signed release in the personnel file.
Callers are much harder. A homeowner with water coming through the ceiling has not read your retention policy, and a voice prompt is not written notice. BIPA's definition of an electronic signature does include an electronic sound adopted with intent to sign[1], but the notice of purpose and term still has to reach the person in writing before collection. For a plumbing company the realistic answer is simple: do not run voice identification on callers. Recognize repeat customers by phone number and service address instead, which your field software already does.
Questions to put to any phone vendor
The FTC has said it will judge a business's handling of biometric data partly on whether it assessed foreseeable harms before collecting it, avoided surprise collection, and evaluated the vendors that handle it[6]. That makes the vendor conversation part of the compliance work, not a formality. Put the same questions to every phone vendor, AssistCall included, and file the written answers with the contract.
Ask what is created
Does any feature create a voiceprint, speaker embedding or voice template used to identify or verify a person, for callers or for staff?
Ask about defaults
Is any such feature on by default, and can it be switched off for our account and confirmed in writing?
Ask about training
Are our recordings used to build speaker-recognition or voice-cloning models, for us or for anyone else?
Ask about storage
Where are recordings, transcripts and any templates stored, for how long, and how do we have them deleted?
Ask who else has access
Which subcontractors can reach call audio, and what do their contracts require of them?
Ask for it in the contract
Will you state in the agreement that no biometric identifiers are collected on our account without our written approval?
An SI Employee answering your line produces what most offices already rely on: a recording, a transcript and a summary of each call, emailed to the person you choose (what it does). In the 8-truck emergency-call example, every night call ends as exactly that, and nothing in the workflow needs a voiceprint. The questions above are how you confirm, for any product, that nothing beyond those records is being made. The wider checklist is in privacy questions to ask any AI phone vendor.
If you genuinely need a voice feature
- System
- Your team
01System
Vendor confirms the feature
Written answer: what template is created, where it is stored, how it is deleted.
02Your team
Policy published
Public schedule: destroy at the end of the purpose or 3 years after last contact.
03Your team
Written notice given
Each employee is told in writing what is collected, why and for how long.
04Your team
Release signed
A signed or e-signed release is on file before anyone enrolls.
05System
Enrollment
Templates are created only for employees with a release on file.
06System
Deleted on schedule
Templates are destroyed when someone leaves, and the vendor confirms deletion.
Example sequence for employees. For callers, the simpler and safer route is not to collect voiceprints at all.
Plan for the leaver as carefully as the joiner. The 3-year limit runs from the person's last interaction with you[1], but the purpose of a voice login ends the day an employee leaves, and BIPA's clock stops at whichever comes first. Add template deletion to the exit checklist next to returning the van keys and the tablet.
Stored templates are also data to protect. New York's breach notification law lists voice prints among the biometric data whose theft triggers a notice[7], so a template you never needed becomes a liability if it leaks. The notice side is covered in data breach notification rules for small firms.
Frequently asked questions
Does recording our calls violate BIPA?
A recording is not on BIPA's list of biometric identifiers[1], and consent to record is governed by wiretap and eavesdropping laws[5]. The BIPA question arises if the audio is used to build a template that identifies the speaker.
Our vendor collects the data. Isn't BIPA their problem?
BIPA's duties apply to any private entity that collects, obtains or holds biometric identifiers[1], which can include you and the vendor. Get the vendor's answers in writing and into the contract.
How long can we keep a voiceprint?
Until the original purpose is met or 3 years after the person's last interaction with you, whichever is sooner, under a written schedule that is available to the public[1].
Can a caller consent by saying yes?
The release can be an electronic signature, which includes an electronic sound adopted with intent to sign[1], but written notice of purpose and term must come first. On an inbound service call that is rarely practical.
Are fingerprint time clocks for techs covered by the same law?
Yes. Fingerprints are biometric identifiers too[1]. Use a public written policy, a release signed at hire, and confirm how the clock vendor stores and deletes templates.
References
Illinois General Assembly (2026). Biometric Information Privacy Act (740 ILCS 14) (opens in a new tab) โ
Supreme Court of Illinois (2019). Rosenbach v. Six Flags Entertainment Corp., 2019 IL 123186 (opens in a new tab) โ
Washington State Legislature (2026). Chapter 19.375 RCW: Biometric identifiers (opens in a new tab) โ
Federal Trade Commission (2023). Policy Statement of the Federal Trade Commission on Biometric Information and Section 5 of the Federal Trade Commission Act (opens in a new tab) โ
Legal Information Institute, Cornell Law School (U.S. Code) (2026). 18 U.S. Code ยง 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) โ
Federal Trade Commission (2023). FTC Warns About Misuses of Biometric Information and Harm to Consumers (opens in a new tab) โ
New York State Senate (2025). New York General Business Law Section 899-AA (opens in a new tab) โ