Palm Springs CA PD

Transparency Portal

Last Updated: Thu Oct 03 2024
Overview
Palm Springs CA PD uses Flock Safety technology to capture objective evidence without compromising on individual privacy. Palm Springs CA PD utilizes retroactive search to solve crimes after they've occurred. Additionally, Palm Springs CA PD utilizes real time alerting of hotlist vehicles to capture wanted criminals. In an effort to ensure proper usage and guardrails are in place, they have made the below policies and usage statistics available to the public.
Policies
What's Detected
License Plates, Vehicles
What's Not Detected
Facial recognition, People, Gender, Race
Acceptable Use Policy
Data is used for law enforcement purposes only. Data is owned by Palm Springs CA PD and is never sold to 3rd parties.
Prohibited Uses
Immigration enforcement, traffic enforcement, harrassment or intimidation, usage based solely on a protected class (i.e. race, sex, religion), Personal use.
Access Policy
All system access requires a valid reason and is stored indefinitely.
Hotlist Policy
Hotlist hits are required to be human verified prior to action.
Usage
Data retention (in days)
30 days
Number of owned cameras
16
External organizations with access
Bakersfield CA PD, California Highway Patrol, Cathedral City CA PD, Citrus Heights CA PD, Contra Costa County CA SO, Desert Hot Springs CA PD, El Cajon CA PD, Fairfield CA PD, Flock City PD - Law Enforcement Sales Demo, Flock Safety - Community Safety Sales Demo, Fullerton CA PD, Garden Grove CA PD, Grover Beach CA PD, Hemet CA PD , Indio CA PD, Murrieta CA PD, Napa CA PD, NCRIC, Newport Beach PD CA, Oceanside CA PD, Placentia CA PD, Pleasanton CA PD, Riverside County CA SO, Santa Barbara County CA SO, Seal Beach CA PD , Upland CA PD , Vacaville CA PD, West Covina CA PD
Hotlists Alerted On
California SVS, NCMEC Amber Alert
Vehicles detected in the last 30 days
373,678
Hotlist hits in the last 30 days
2,316
Searches in the last 30 days
548
Public Search Audit
Additional Info
Full ALPR Policy Here (reference section Policy 430)