Privacy • Digital Evidence • Cybersecurity • Disclosure
CCTV, Surveillance and Data Protection for Security Guards (Updated for 2027)
Last updated:
The federal Safeguards Rule addresses specified financial institutions and customer information. It does not set a general video retention schedule for every security company. 16 CFR Part 314.
CCTV systems now sit inside a wider surveillance environment that may include body-worn cameras, audio, access control, visitor systems, vehicle plate records, facial recognition, biometric credentials, cloud platforms and artificial-intelligence analytics. This hub explains how private security companies can authorize, operate, preserve, disclose and delete surveillance data without treating footage as an informal collection of video clips.
CCTV and surveillance compliance at a glance
Define the purpose first
Every camera, microphone, analytic and access log should have a documented security purpose, approved location and accountable owner.
Audio is a separate decision
A lawful video camera does not automatically make audio recording lawful. State communication and consent laws require separate review.
Preserve incidents promptly
Routine overwriting must stop for relevant footage, logs and metadata when an incident, complaint, claim, investigation or legal hold arises.
Access must be accountable
Live viewing, playback, export, sharing, redaction and deletion should be role-restricted, logged and auditable.
Critical rule: there is no single nationwide CCTV policy
Private-sector surveillance may be affected by federal consumer-protection principles, state privacy and communication laws, biometric statutes, employment rules, sector requirements, contract terms, litigation duties and local restrictions. A camera system that is acceptable at one site may require different notice, audio, retention, access or disclosure controls at another.
Guards and control-room operators should follow approved policy and escalate uncertain requests. They should not personally decide whether to activate covert recording, release footage, ignore a legal hold or use facial recognition.
This page provides general educational information and is not legal advice.
The U.S. CCTV and surveillance legal map
| Legal or governance layer | What it can affect | Security-company response |
|---|---|---|
| Federal consumer protection and data security | Whether privacy and security representations are truthful and whether reasonable safeguards protect personal information. | Collect only what is needed, restrict access, protect retained information and dispose of it securely. |
| State privacy laws | Notice, individual rights, sensitive data, service-provider contracts, targeted analytics, sale or sharing and security duties. | Identify the state, the people recorded, the business role and any applicable exemption before setting policy. |
| State audio and communication laws | Recording conversations, microphone use, telephone recording and confidential communications. | Treat audio as a separate legal feature and disable it unless specifically approved. |
| Biometric and facial-recognition laws | Face geometry, fingerprints, voiceprints, templates, enrollment, consent, disclosure and destruction. | Complete a biometric review before enabling identification or enrollment features. |
| Employment and labor rules | Workplace monitoring, employee notices, union agreements, discipline, discrimination and retaliation. | Coordinate surveillance policy with HR, labor counsel and collective-bargaining obligations. |
| Sector-specific federal law | Healthcare information, student records, financial customer information and regulated infrastructure. | Apply the client sector’s rules in addition to ordinary security procedures. |
| Contract and post orders | Ownership, permitted use, retention, exports, incident notification, vendor access and deletion. | Convert contractual requirements into practical post orders, system settings and audit checks. |
| Litigation and investigation duties | Preservation, legal holds, disclosure, authenticity and defensibility of digital evidence. | Stop ordinary deletion, preserve native records and document every transfer. |
What counts as surveillance data?
Fixed and mobile CCTV
- Indoor and outdoor cameras.
- Pan-tilt-zoom cameras.
- Thermal and low-light imaging.
- Vehicle and mobile patrol cameras.
- Drone surveillance footage.
Body-worn camera records
- Video and optional audio.
- Activation and deactivation logs.
- Officer or guard identifiers.
- Location and time metadata.
- Device and upload audit records.
Identity and entry records
- Badge swipes.
- Door events.
- Visitor registrations.
- Elevator and turnstile logs.
- Denied-access events.
Plate and gate information
- License plate images.
- Vehicle movements.
- Parking records.
- Driver or visitor details.
- Watchlist alerts.
Derived and inferred information
- Face or object matches.
- People counting.
- Behavioral alerts.
- Dwell-time analysis.
- Movement and association patterns.
System and audit information
- User login records.
- Playback and export history.
- Camera health and outage logs.
- Configuration changes.
- Vendor support sessions.
Metadata can be as important as the image
Time, date, camera identifier, user access, export history, system configuration and original file information may be needed to explain where footage came from and whether it has been altered.
Eight-stage surveillance-data lifecycle
Authorize
Define the purpose, legal review, owner, site, people affected and prohibited uses.
Configure
Approve camera views, audio status, analytics, network connections, storage and user roles.
Notify
Install appropriate signs, notices, employee information and body-camera activation warnings.
Collect
Record only for approved security, safety, investigative or operational purposes.
Protect
Restrict viewing, secure credentials, patch systems and monitor access and vendor activity.
Preserve
Export relevant native footage, metadata and logs when an incident or legal hold arises.
Disclose
Verify authority, redact where required, use secure transfer and log every release.
Delete
Apply the approved retention schedule and secure deletion after holds and obligations end.
Locations and uses requiring extra review
| Location or use | Primary concern | Required control |
|---|---|---|
| Entrances, lobbies and parking areas | Routine identification, movements and vehicle records. | Purpose-based camera placement, notice and documented retention. |
| Work areas and break rooms | Employee monitoring, labor relations and disproportionate observation. | HR and legal review, workforce notice and clear prohibited uses. |
| Restrooms, changing rooms and private treatment areas | Extreme expectation of privacy and serious legal exposure. | Do not install or activate surveillance without explicit, specialized legal authority and a documented exceptional basis. |
| Residential buildings and dormitories | Homes, bedrooms, visitors, minors and persistent tracking. | Strict field-of-view controls and no viewing into private living spaces. |
| Healthcare environments | Patients, treatment, screens, conversations and protected health information. | Coordinate with the privacy officer and apply HIPAA controls where applicable. |
| Schools and campuses | Minors, student records, discipline and law-enforcement-unit distinctions. | Apply FERPA analysis, school policy and education-sector disclosure procedures. |
| Audio-enabled cameras | Confidential communications and state consent requirements. | Separate written approval; audio should be off by default unless authorized. |
| Facial recognition or watchlists | Biometric law, accuracy, bias, false matches and high-impact decisions. | Legal approval, documented purpose, human verification and strict watchlist governance. |
| Training and marketing use | Secondary use beyond the original security purpose. | Use separate authorization, consent where required and effective anonymization or recreation. |
| Covert surveillance | Heightened privacy, employment, audio and evidentiary risk. | Executive and legal authorization with defined scope, duration and review. |
Audio recording and state communication laws
Microphones can transform an ordinary video-surveillance project into a communication-recording program. State laws differ on consent, confidential communications, telephone calls, in-person conversations, expectations of privacy and available exceptions.
| Audio situation | Risk | Operational rule |
|---|---|---|
| CCTV microphone enabled by default | Employees or visitors may be recorded without an approved purpose or sufficient consent. | Disable audio unless legal, HR and client approval is documented. |
| Body-worn camera audio | Activation may capture private conversations, homes, medical discussions or bystanders. | Use state-specific activation, notice, deactivation and restricted-location rules. |
| Control-room telephone recording | Telephone and communication laws may impose notice or consent requirements. | Use an approved recorded announcement and state-specific legal review. |
| Open microphone in a workplace | Continuous collection may be disproportionate and difficult to justify. | Use the least intrusive method and avoid continuous audio where video meets the purpose. |
| Emergency activation | An urgent security need does not automatically remove every legal restriction. | Follow the approved emergency policy and obtain prompt review after activation. |
California example
California Penal Code Section 632 restricts intentionally recording confidential communications without the consent of all parties, subject to its definitions and exceptions. It is one example of why a national CCTV policy cannot simply state that signage authorizes audio everywhere.
Notice, signage and transparency
| Notice layer | What it should explain | Where it belongs |
|---|---|---|
| Entrance signage | That video surveillance operates and who controls the system or where questions can be directed. | Before people enter the monitored area. |
| Audio-specific notice | That sound may be recorded where audio has been separately approved. | At the recorded location and within telephone or body-camera procedures. |
| Employee notice | Purposes, monitored areas, data use, retention, access and disciplinary limitations. | Handbooks, workplace notices, union communications and onboarding. |
| Detailed privacy notice | Data categories, purposes, disclosures, retention, rights and contact routes where applicable. | Client or company website, privacy portal or facility information point. |
| Body-camera activation statement | That recording is starting when policy and circumstances permit an announcement. | Spoken by the guard and documented in training. |
| Biometric notice and consent | Purpose, collection, storage, disclosure and destruction information required by applicable law. | Before enrollment or capture where required. |
Signage supports transparency, but it does not automatically cure an unlawful camera location, microphone, biometric system, secondary use or disclosure.
Retention schedules and secure deletion
There is no single routine CCTV retention period suitable for every U.S. security operation. The company should establish a written schedule based on the purpose, state, sector, contract, storage design, incident frequency, limitation periods and legal-hold process.
| Record category | Retention decision | Deletion control |
|---|---|---|
| Routine CCTV with no incident | Keep only for the documented operational period justified by the site risk and contract. | Automated overwrite with tested settings and authorized exceptions. |
| Incident footage | Preserve for the claim, investigation, prosecution, disciplinary process or legal hold. | No ordinary deletion until an authorized release from hold. |
| Body-worn camera footage | Use categories such as evidentiary, complaint-related, use-of-force, routine and test footage. | Category-based retention with supervisor review and audit history. |
| Access-control and visitor logs | Align with security investigations, contract requirements and applicable privacy rules. | Automated deletion or anonymization after the approved period. |
| Vehicle plate records | Base retention on the approved gate, parking or investigative purpose. | Prevent indefinite searchable movement histories without documented need. |
| Biometric templates | Follow state-specific notice, consent, retention and destruction requirements. | Document unenrollment and verified deletion from active systems and backups where required. |
| Export and access audit logs | Keep long enough to support security investigations, audits and contract accountability. | Protect logs from alteration by ordinary users. |
| Training or marketing copies | Do not retain merely because a clip appears useful or interesting. | Delete unless separately authorized, anonymized and documented. |
The defensible-retention test
The company should be able to explain what it keeps, why it keeps it, who approved the period, how legal holds override deletion and how records are securely destroyed when the purpose ends.
Incidents, legal holds and evidence preservation
When routine deletion should stop
- Serious injury or death.
- Use of force or detention.
- Theft, intrusion or property damage.
- Privacy or discrimination complaint.
- Employee grievance or discipline.
- Police, regulator, insurer or attorney request.
- Threatened or filed litigation.
What should be secured
- Original or native video exports.
- Relevant time before and after the event.
- Associated audio where lawfully collected.
- Access-control and alarm logs.
- User access and export records.
- Camera maps and system configuration.
- Incident reports and communications.
Preserve context and metadata
- Camera identifier and location.
- System date and time accuracy.
- Export method and file format.
- Person performing the export.
- Transfer dates and recipients.
- File-integrity records where available.
- Any conversion or redaction performed.
End the hold carefully
- Use written authorization.
- Confirm every related matter is closed.
- Check insurer and client requirements.
- Update the evidence register.
- Return records to the approved schedule.
- Document final deletion where required.
Do not preserve only the dramatic clip
The minutes before an incident, other camera angles, access records and guard communications may explain the sequence more accurately than a short exported clip.
Live viewing, playback and export controls
| Activity | Typical authorization | Required record |
|---|---|---|
| Routine live monitoring | Assigned control-room and operational personnel. | User identity, role and approved camera groups. |
| Playback after an incident | Supervisor, investigator or designated client representative. | Reason, date, cameras and user access log. |
| Exporting video or still images | Authorized supervisor, evidence officer or investigator. | Export form, file details, purpose, destination and custody record. |
| Downloading to removable media | Restricted evidence or IT personnel. | Approved encrypted media, serial number and handover log. |
| Remote viewing | Named users using approved devices and secure access. | Authentication, session and administrator logs. |
| Redaction or conversion | Trained evidence, legal or privacy personnel. | Preserve the original and document every edited derivative. |
| Deletion outside the schedule | Records owner, privacy, legal or designated senior manager. | Reason, scope, authority and confirmation that no hold applies. |
| Vendor technical access | Time-limited, approved and supervised support access. | Ticket, technician, systems accessed, actions and session termination. |
Shared usernames should not be used where the system can support individual accounts. An export log loses much of its value when several people appear under one generic control-room identity.
Police, court, client and individual requests
| Request | Immediate action | Do not |
|---|---|---|
| Informal police request | Preserve the footage, record the officer and route the request through approved policy. | Hand over unlogged footage from a personal device or messaging account. |
| Warrant, subpoena or court order | Send promptly to legal or the authorized records owner and preserve the full scope. | Interpret, narrow or ignore the document personally. |
| Emergency request | Apply the emergency-disclosure process and document the threat, requester and material released. | Use an emergency claim as a reason to bypass all accountability. |
| Client manager request | Confirm the person’s authority, business purpose and permitted access. | Assume every client employee may see or copy all recordings. |
| Employee or member-of-public request | Route to privacy, HR, legal or the client’s designated process. | Play footage at the security desk or release unredacted images casually. |
| Attorney or insurer request | Preserve records and coordinate an authorized, secure production. | Make admissions, alter files or send incomplete extracts without context. |
| Media or social-media request | Refer to the authorized communications representative. | Post, livestream, forward or sell surveillance material. |
School-video disclosure may require a separate FERPA decision
The U.S. Department of Education explains that some school photos and videos become education records when they directly relate to a student and are maintained by the school or a party acting for it. Records created and maintained by a school law-enforcement unit for a law-enforcement purpose may be treated differently.
Body-worn cameras for private security
Department of Justice body-worn camera resources are primarily designed for law enforcement, not private security. Their policy categories are still useful: capture, viewing, use, release, storage, security, training and audit should all be addressed before deployment.
| Policy area | Questions the company must answer |
|---|---|
| Who wears a camera? | Which posts, assignments and incidents justify deployment? |
| When is recording required? | What events require activation, permit discretion or prohibit recording? |
| How is notice given? | Must the guard announce activation, and when is an announcement unsafe or impractical? |
| When must recording stop? | How are private areas, medical care, confidential conversations and personal breaks handled? |
| Can a guard review footage? | May footage be viewed before an incident report, statement or interview? |
| Who uploads and categorizes footage? | How quickly, under which event category and with what incident reference? |
| How are malfunctions reported? | What must the guard do when the camera fails, loses power or does not upload? |
| How are complaints protected? | How does the company prevent deletion or selective recording after a complaint? |
| What discipline applies? | How are accidental failures distinguished from deliberate misuse? |
| Is audio enabled? | Which state law and contract analysis approved audio capture? |
Facial recognition and biometric access systems
Facial recognition
- Define enrollment and watchlist sources.
- Test accuracy in the real environment.
- Require human verification.
- Prohibit action based only on an automated match.
- Document false-match handling.
- Restrict secondary use.
Biometric access control
- Fingerprint or palm readers.
- Iris or retina systems.
- Voice authentication.
- Face-geometry templates.
- Enrollment and withdrawal.
- Retention and deletion.
| State example | Why it matters | Official source |
|---|---|---|
| Illinois | The Biometric Information Privacy Act regulates private entities’ collection, possession, disclosure, retention and destruction of covered biometric identifiers and information. | Illinois Biometric Information Privacy Act |
| Texas | Business and Commerce Code Chapter 503 addresses capture and commercial use of biometric identifiers. | Texas Business and Commerce Code Chapter 503 |
| Washington | Chapter 19.375 addresses enrollment, disclosure, safeguarding and retention of biometric identifiers, including specific treatment of security purposes. | Washington Chapter 19.375 RCW |
A normal photograph is not always the same as a biometric template
Legal definitions differ. A system that measures a face, voice, fingerprint or other biological characteristic to identify a specific person may create additional obligations beyond ordinary video storage.
Cybersecurity, remote access and cloud storage
NIST Cybersecurity Framework 2.0 organizes cybersecurity outcomes around six functions: Govern, Identify, Protect, Detect, Respond and Recover. A networked surveillance program should address all six rather than relying on strong passwords alone.
| NIST CSF function | Surveillance-system controls |
|---|---|
| Govern | Ownership, policies, supplier risk, legal requirements, approved architecture and accountability. |
| Identify | Inventory cameras, recorders, servers, cloud accounts, software, users, data flows and dependencies. |
| Protect | Unique accounts, multi-factor authentication, encryption, secure configuration, patching and segmentation. |
| Detect | Monitor failed logins, unusual exports, disabled cameras, administrator changes and vendor sessions. |
| Respond | Contain incidents, revoke access, preserve logs, notify stakeholders and coordinate forensics. |
| Recover | Restore services, validate configurations, recover evidence, review lessons and prevent recurrence. |
Minimum technical controls
Identity and access
- Individual user accounts.
- Multi-factor authentication.
- Role-based permissions.
- Prompt leaver removal.
- Quarterly access reviews.
- Privileged-access monitoring.
Devices and networks
- Change all default credentials.
- Maintain supported firmware.
- Segment camera networks.
- Restrict internet exposure.
- Control USB and removable media.
- Test secure backups.
Cloud and remote access
- Approved hosting locations.
- Encrypted data transfer.
- Time-limited vendor access.
- Session and export logs.
- Mobile-device controls.
- Contract-exit and data-return plan.
Supplier governance
- Security documentation.
- Vulnerability notifications.
- Patch and support commitments.
- Subprocessor disclosure.
- Breach-notification deadlines.
- Verified deletion after termination.
Sector-specific surveillance considerations
HIPAA and patient environments
Cameras may capture patients, treatment, screens or conversations. Where footage contains electronic protected health information and the company is acting for a covered entity, HIPAA security and business-associate requirements may apply.
FERPA and student video
A school video may become an education record when it directly relates to a student and is maintained by the school or a party acting for it. Law-enforcement-unit records can be treated differently.
Customer information safeguards
Financial institutions covered by the FTC Safeguards Rule must maintain an information-security program and oversee service providers that can access customer information.
Physical and cyber convergence
CCTV, access control and remote support may connect directly to high-value operational networks. Strong segmentation, identity, remote-access and supplier controls are essential.
Tenants, visitors and private spaces
Camera placement should avoid private living areas, unnecessary tracking and intrusive secondary uses. Lease, property and state privacy requirements should be reviewed.
Customers, staff and analytics
Face matching, plate records, employee monitoring, audio and behavioral analytics may require controls beyond ordinary theft-prevention video.
Lost devices, unauthorized access and data-breach response
Contain
Disable compromised accounts, remote sessions, links and exposed devices without destroying evidence.
Preserve
Protect logs, system images, access records, communications and the affected equipment.
Escalate
Notify management, IT, privacy, legal, the client, insurer and other designated responders.
Investigate
Determine what happened, which records were affected, who had access and whether data left the system.
Assess Notice
Identify applicable state, sector, contract, insurer and law-enforcement notification duties.
Communicate
Use accurate, approved information and avoid speculation, concealment or inconsistent statements.
Recover
Correct vulnerabilities, reset credentials, verify systems, retrain staff and update controls.
Do not switch off or wipe evidence casually
The FTC recommends securing affected operations, mobilizing the response team, preserving forensic evidence, reviewing logs and determining applicable notification duties. Obtain IT and forensic direction before actions that could destroy useful evidence.
Required CCTV and surveillance policy pack
| Document | Minimum content |
|---|---|
| Surveillance governance policy | Purpose, ownership, legal review, approved technologies, prohibited uses and accountability. |
| Camera and data inventory | Location, field of view, audio, analytics, storage, owner, retention and network connection. |
| Access-control matrix | Who may view live feeds, perform playback, export, redact, administer and delete. |
| Retention schedule | Record categories, default periods, hold overrides, deletion and approval responsibilities. |
| Incident preservation procedure | Triggers, scope, native export, metadata, chain of custody and legal-hold management. |
| Disclosure procedure | Police, subpoena, client, employee, public, insurer, attorney and emergency requests. |
| Body-worn camera policy | Activation, notice, restricted areas, review, upload, retention, complaints and discipline. |
| Audio-recording authorization | State analysis, locations, purpose, notices, consent mechanism and approved devices. |
| Biometric and facial-recognition assessment | Law, purpose, consent, watchlists, accuracy, human review, retention and deletion. |
| Vendor security schedule | Hosting, access, patching, incidents, subprocessors, exports, termination and deletion. |
| Breach-response plan | Contacts, containment, preservation, investigation, notification and recovery. |
| Training and audit plan | Role-specific training, access reviews, sample audits, malfunction checks and corrective action. |
Training, supervision and audit schedule
| Frequency | Recommended control |
|---|---|
| Every shift | Check critical cameras, recording health, time accuracy, alarms and unresolved faults. |
| Weekly | Review outages, failed uploads, evidence exports and open preservation requests. |
| Monthly | Sample user access, playback, exports, body-camera classification and vendor sessions. |
| Quarterly | Review user permissions, inactive accounts, administrator access and retention settings. |
| Annually | Review law, policy, camera placement, notices, suppliers, data flows, contracts and training. |
| After an incident | Review preservation speed, footage quality, access records, disclosure and lessons learned. |
| After a system change | Repeat privacy, cybersecurity, retention and acceptance testing before production use. |
Common CCTV and surveillance mistakes
| Mistake | Why it creates risk | Better control |
|---|---|---|
| Copying one retention period to every site | Purpose, sector, state, contract and incident needs differ. | Create category and site-specific schedules. |
| Assuming signage legalizes audio | State communication laws may require different consent or prohibit the recording. | Complete a separate audio review. |
| Using shared control-room logins | Access and export activity cannot be attributed reliably. | Use individual identities and role-based access. |
| Saving only a converted phone recording | Quality, metadata and authenticity may be lost. | Preserve the original native export and record all derivatives. |
| Waiting for a subpoena before preserving footage | Relevant records may be overwritten after a known incident or complaint. | Use early incident and legal-hold triggers. |
| Giving police an unlogged USB drive | The company loses custody, scope and disclosure records. | Use an approved evidence handover process. |
| Using footage for entertainment | It violates purpose limits and increases leak, harassment and dignity risks. | Limit viewing to legitimate operational duties. |
| Posting clips in private staff chats | Messaging apps create uncontrolled copies and secondary disclosure. | Use approved evidence and incident systems only. |
| Turning on facial recognition without review | Biometric law, accuracy, watchlists and discrimination risk may be overlooked. | Require formal legal, privacy and technical approval. |
| Allowing permanent vendor remote access | External accounts can become an invisible route into live feeds and stored footage. | Use approved, time-limited and logged support sessions. |
| Deleting footage after a complaint | It may destroy relevant evidence and undermine trust. | Apply an immediate preservation hold. |
Frequently asked questions
How long should a private security company keep CCTV footage?
There is no single nationwide period suitable for every system. Use a documented retention schedule based on the security purpose, state, sector, contract and legal-hold requirements. Routine footage should not be kept indefinitely merely because storage is inexpensive.
Is 30 days the standard U.S. CCTV retention period?
No. Some organizations use periods around that length, but it is not a universal federal standard. The correct period must be justified for the specific system and record category.
Does a CCTV sign allow audio recording?
Not automatically. Audio may be regulated by state communication and consent laws. It should be separately reviewed and approved.
Can guards watch CCTV when nothing is happening?
Guards may monitor cameras as part of assigned security duties. They should not use footage for entertainment, curiosity, harassment, personal interest or unrelated monitoring.
Can a guard export footage for the police?
Only through the approved disclosure and evidence procedure. The request, cameras, time range, export method, recipient and handover should be recorded.
Should footage be emailed to a client?
Use only an approved secure-transfer method. Confirm the client representative’s authority and record what was sent, why, when and by whom.
Can a guard record an incident on a personal phone?
Personal-device recording should generally be prohibited unless an emergency policy expressly allows it. Personal phones create serious access, security, retention, disclosure and authenticity problems.
When should a legal hold be applied?
Apply preservation promptly when footage may relate to a serious incident, complaint, injury, investigation, claim, regulator inquiry or anticipated litigation. Do not wait for the ordinary retention period to expire.
Can footage be edited before giving it to the police or a lawyer?
Preserve the original. Redacted or converted copies may sometimes be created for a permitted disclosure, but every derivative should be documented and traceable to the unchanged source.
Does HIPAA cover all hospital CCTV?
Not every hospital image is automatically protected health information. The content, purpose, location, parties and role of the organization matter. The healthcare privacy officer should decide how HIPAA applies.
Does FERPA cover every school surveillance video?
No. The Department of Education uses a context-specific analysis. A video may be an education record when it directly relates to a student and is maintained by the school or a party acting for it, subject to exclusions such as qualifying law-enforcement-unit records.
Can a company use CCTV footage for training?
Not automatically. Training is a secondary use. Use recreated scenarios or effectively anonymized material where possible and obtain privacy, legal and client approval before using identifiable footage.
What should happen when a CCTV laptop or phone is lost?
Treat it as a security incident. Revoke credentials, contain remote access, preserve logs, notify the response team, determine what information was accessible and assess state, sector, client and insurer notification duties.
Can facial recognition be enabled because the camera system already includes it?
No. Technical availability is not authorization. Facial recognition requires separate legal, privacy, accuracy, watchlist, retention, cybersecurity and human-review controls.
Official federal and state sources
- FTC Start with Security guide for businesses
- FTC guide to protecting personal information
- FTC data breach response guide
- NIST Privacy Framework
- NIST Cybersecurity Framework 2.0
- NIST: Digital Evidence Preservation
- NIST: CCTV Digital Video Exchange Standards
- CISA: Guide to Securing Remote Access Software
- Bureau of Justice Assistance: Body-Worn Camera Policy Resources
- Bureau of Justice Assistance: Body-Worn Camera Privacy
- U.S. Department of Education: Photos and Videos Under FERPA
- U.S. Department of Health and Human Services: HIPAA Security Rule
- FTC: Gramm-Leach-Bliley Safeguards Rule
- California Penal Code Section 632
- Illinois Biometric Information Privacy Act
- Texas Business and Commerce Code Chapter 503
- Washington Biometric Identifiers Law
State laws, privacy thresholds, sector requirements and local restrictions change. Verify the current official text for the state and site before approving a surveillance technology or policy.



