SB34 ALPR Data Sharing (Berkeley Police Department)
| Tracking # |
24-157 |
| Multi Request | SB34 ALPR Data Sharing |
| Submitted | Jan. 30, 2024 |
| Due | Feb. 9, 2024 |
| Est. Completion | April 26, 2024 |
MuckRock users can file, duplicate, track, and share public records requests like this one. Learn more.
Communications
From: Jennifer Pinsof
Dear Custodian of Records:
This letter constitutes a request under the California Public Records Act ("CPRA") from the Electronic Frontier Foundation, submitted with the assistance of MuckRock News.
We request the following records related to Automated License Plate Readers ("ALPRs") and your law enforcement agency ("Agency").
Part A - Information related to ALPR data sharing.
A1. The names of agencies and organizations with which the Agency shares ALPR data;
A2. The names of agencies and organizations from which the Agency receives ALPR data;
A3. The names of agencies and organizations with which the Agency shares “hot list” information;
A4. The names of agencies and organizations from which the Agency receives “hot list” information.
The information requested in items A1-A4 is readily available for extraction through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Data Sharing Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality.
Most agencies have encountered little difficulty in providing this information (see below). In a small number of cases, an agency has interpreted items A1-A4 as requesting the creation of a record that does not exist. We disagree: this data is maintained by your software, can be exported through software your agency has already purchased, and is therefore subject to CPRA.
However, should you disagree, you may alternatively produce the following records:
A5. All agreements, memoranda of understanding, requests, or other certifying documents that external agencies have signed to comply with Sec 1798.90.52(b) for accessing your agency's ALPR data. These documents are also often required under the "Releasing ALPR Data" subsection of a California law enforcement agency's SB 34 policy.
A6. All agreements, memoranda of understanding, requests, or other certifying documents that your agency has signed pursuant to Sec 1798.90.52(b) to access other agencies' ALPR data.
A7. All "records of access" required by Sec. 1798.90.52(a) for the periods January 1, 2021 until the date of processing this request.
Items A5-A7 are not necessary if your agency provides the information requested in items A1-A4. We feel that items A1-A4 are more focused and would require less labor from your agency to produce.
Part B - Information Related to Numbers of “Detections” (plate scans) and “Hits” (plate scans that matched to a hotlist)
B1. The aggregate number of "detections" collected during 2023.
B2. The aggregate number of “hits” during 2023.
B3. The aggregate number of "detections" from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period. For example, most Flock Safety systems may not have this data beyond 30 days.
B4. The aggregate number of “hits” from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period.
The information requested in items B1-B4 is readily available through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Hit Ratio Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality. As noted above, this information exists within your system and can be easily exported with existing software.
Please note that more than 80 California law enforcement agencies have provided the information requested in Parts A1-A4 and B1-B4 in previous years. For your reference we have included a table (attached) with the names of the agencies that have historically provided these records.
CPRA requires you to undertake reasonable efforts to locate responsive records and to work in good faith with requesters to respond to their request. See CYAC v. City of National City, 220 Cal.App.4th 1385, 1430 (2013). Thus under the CPRA you are obligated to conduct a reasonable search and cannot deny a request merely because it might generate a large volume of records.
We ask that you please respond to this request within 10 days either by providing all the requested records or by providing a written response setting forth the legal authority on which you rely in withholding or redacting any document, as well as stating when documents will be made available. Should you choose to withhold or reject this request, we ask that you provide an explanation of why your agency is responding differently compared to the many others that have complied with our request.
We also request that any records maintained in an electronic format be provided in that same format (such as a PDF, CSV or XLS file), to avoid copying costs.
However, should you be unable to do so, EFF will reimburse you for the direct costs of copying these records (if you elect to charge for copying) plus postage. If you anticipate that these costs will exceed $25.00, or that the time needed to copy the records will delay their release, please contact me so that I can arrange to inspect the documents or decide which documents I wish to have copied. Please also provide an invoice and a cost breakdown of the fee estimate. If the fees are less than $25.00, please copy and send the records and invoice as soon as possible, and we will promptly pay the required costs.
Thank you for your consideration of this request. If you have any questions or concerns, or if I can provide any clarification that will help identify responsive documents or focus this request, please do not hesitate to contact me at ALPR@eff.org.
Sincerely,
Jennifer Pinsof
Staff Attorney
Electronic Frontier Foundation
From: Berkeley Police Department
City of Berkeley
************************************************************************
Your record request #24-157 has been submitted successfully.
The due date for your request may be later than usual because the office is closed on:
* February 12: Lincoln's Birthday
************************************************************************
Reply to this email or sign in to contact City of Berkeley.<br><br>
<a href="https://cityofberkeleyca.nextrequest.com/settings?id=1272998">Change your email settings</a> | <a href="https://www.nextrequest.civicplus.help/hc/en-us/categories/17720084172567-Requesters">Visit our help center</a>
From: Berkeley Police Department
City of Berkeley
************************************************************************
A message was sent to you regarding record request #24-157:
This is in response to your February 4, 204 Public Records Act request for:
This letter constitutes a request under the California Public Records Act ("CPRA") from the Electronic Frontier Foundation, submitted with the assistance of MuckRock News.
We request the following records related to Automated License Plate Readers ("ALPRs") and your law enforcement agency ("Agency").
Part A - Information related to ALPR data sharing.
A1. The names of agencies and organizations with which the Agency shares ALPR data;
A2. The names of agencies and organizations from which the Agency receives ALPR data;
A3. The names of agencies and organizations with which the Agency shares “hot list” information;
A4. The names of agencies and organizations from which the Agency receives “hot list” information.
The information requested in items A1-A4 is readily available for extraction through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Data Sharing Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality.
Most agencies have encountered little difficulty in providing this information (see below). In a small number of cases, an agency has interpreted items A1-A4 as requesting the creation of a record that does not exist. We disagree: this data is maintained by your software, can be exported through software your agency has already purchased, and is therefore subject to CPRA.
However, should you disagree, you may alternatively produce the following records:
A5. All agreements, memoranda of understanding, requests, or other certifying documents that external agencies have signed to comply with Sec 1798.90.52(b) for accessing your agency's ALPR data. These documents are also often required under the "Releasing ALPR Data" subsection of a California law enforcement agency's SB 34 policy.
A6. All agreements, memoranda of understanding, requests, or other certifying documents that your agency has signed pursuant to Sec 1798.90.52(b) to access other agencies' ALPR data.
A7. All "records of access" required by Sec. 1798.90.52(a) for the periods January 1, 2021 until the date of processing this request.
Items A5-A7 are not necessary if your agency provides the information requested in items A1-A4. We feel that items A1-A4 are more focused and would require less labor from your agency to produce.
Part B - Information Related to Numbers of “Detections” (plate scans) and “Hits” (plate scans that matched to a hotlist)
B1. The aggregate number of "detections" collected during 2023.
B2. The aggregate number of “hits” during 2023.
B3. The aggregate number of "detections" from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period. For example, most Flock Safety systems may not have this data beyond 30 days.
B4. The aggregate number of “hits” from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period.
The information requested in items B1-B4 is readily available through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Hit Ratio Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality. As noted above, this information exists within your system and can be easily exported with existing software.
The City is extending the response period by fourteen additional calendar days to February 28, 2024 from February 14, 2024, based on the need to search for, collect, and appropriately examine a voluminous amount of separate and distinct records, and the need for consultation with two or more City departments or offices with substantial subject matter interest in the request. (Cal. Gov. Code § 7922.535(b)-(c) (formerly Gov. Code § 6253(c)).
Berkeley Records Bureau
************************************************************************
<em>Questions about your request?</em> Reply to this email or sign in to contact staff at City of Berkeley.<br><em>Technical support:</em> See our <a href="https://www.nextrequest.civicplus.help/hc/en-us/categories/17720084172567-Requesters">help page</a>
From: Berkeley Police Department
City of Berkeley
************************************************************************
A message was sent to you regarding record request #24-157:
This is in response to your February 4, 204 Public Records Act request for:
[This letter constitutes a request under the California Public Records Act ("CPRA") from the Electronic Frontier Foundation, submitted with the assistance of MuckRock News.
We request the following records related to Automated License Plate Readers ("ALPRs") and your law enforcement agency ("Agency").
Part A - Information related to ALPR data sharing.
A1. The names of agencies and organizations with which the Agency shares ALPR data;
A2. The names of agencies and organizations from which the Agency receives ALPR data;
A3. The names of agencies and organizations with which the Agency shares “hot list” information;
A4. The names of agencies and organizations from which the Agency receives “hot list” information.
The information requested in items A1-A4 is readily available for extraction through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Data Sharing Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality.
Most agencies have encountered little difficulty in providing this information (see below). In a small number of cases, an agency has interpreted items A1-A4 as requesting the creation of a record that does not exist. We disagree: this data is maintained by your software, can be exported through software your agency has already purchased, and is therefore subject to CPRA.
However, should you disagree, you may alternatively produce the following records:
A5. All agreements, memoranda of understanding, requests, or other certifying documents that external agencies have signed to comply with Sec 1798.90.52(b) for accessing your agency's ALPR data. These documents are also often required under the "Releasing ALPR Data" subsection of a California law enforcement agency's SB 34 policy.
A6. All agreements, memoranda of understanding, requests, or other certifying documents that your agency has signed pursuant to Sec 1798.90.52(b) to access other agencies' ALPR data.
A7. All "records of access" required by Sec. 1798.90.52(a) for the periods January 1, 2021 until the date of processing this request.
Items A5-A7 are not necessary if your agency provides the information requested in items A1-A4. We feel that items A1-A4 are more focused and would require less labor from your agency to produce.
Part B - Information Related to Numbers of “Detections” (plate scans) and “Hits” (plate scans that matched to a hotlist)
B1. The aggregate number of "detections" collected during 2023.
B2. The aggregate number of “hits” during 2023.
B3. The aggregate number of "detections" from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period. For example, most Flock Safety systems may not have this data beyond 30 days.
B4. The aggregate number of “hits” from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period.
The information requested in items B1-B4 is readily available through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Hit Ratio Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality. As noted above, this information exists within your system and can be easily exported with existing software.]
The City has identified documents which are responsive to your request. A partial production of those records can be found attached to this letter.
The City is in the process of compiling and reviewing additional documents and anticipates being able to produce additional responsive documents by March 28, 2024.
If you have any questions concerning your request, please feel free to contact me at kperez@berkeleyca.gov.
************************************************************************
<em>Questions about your request?</em> Reply to this email or sign in to contact staff at City of Berkeley.<br><em>Technical support:</em> See our <a href="https://www.nextrequest.civicplus.help/hc/en-us/categories/17720084172567-Requesters">help page</a>
From: Berkeley Police Department
City of Berkeley
************************************************************************
A document has been released to you for record request #24-157:
* Surveillance Use Policy-Fixed Automated License Plate Readers (ALPRs).pdf
Document links are valid for one month.
After April 16, you will need to sign in to view the document(s).
************************************************************************
<em>Questions about your request?</em> Reply to this email or sign in to contact staff at City of Berkeley.<br><em>Technical support:</em> See our <a href="https://www.nextrequest.civicplus.help/hc/en-us/categories/17720084172567-Requesters">help page</a>
From: Jennifer Pinsof
Hello —
Thank you for providing the requested policy. However, your reply did not contain the other responsive materials that I requested. These include the data sharing report with the requested list of agencies with which your department shares ALPR data and from which your agency receives ALPR information. Could you please provide this requested material as soon as possible? Please let us know if your agency has any questions.
Thank you for your time and help.
From: Muckrock Staff
To Whom It May Concern:
I'm following up on the following California Public Records Act request, copied below, and originally submitted on Feb. 4, 2024. You had previously indicated that it would be completed on March 28, 2024. I wanted to check on the status of my request, and to see if there was a new estimated completion date. You had assigned it reference number #24-157.
Thanks for your help, and let me know if further clarification is needed.
From: Berkeley Police Department
City of Berkeley
************************************************************************
A message was sent to you regarding record request #24-157:
This is in response to your February 4, 204 Public Records Act request for:
[This letter constitutes a request under the California Public Records Act ("CPRA") from the Electronic Frontier Foundation, submitted with the assistance of MuckRock News.
We request the following records related to Automated License Plate Readers ("ALPRs") and your law enforcement agency ("Agency").
Part A - Information related to ALPR data sharing.
A1. The names of agencies and organizations with which the Agency shares ALPR data;
A2. The names of agencies and organizations from which the Agency receives ALPR data;
A3. The names of agencies and organizations with which the Agency shares “hot list” information;
A4. The names of agencies and organizations from which the Agency receives “hot list” information.
The information requested in items A1-A4 is readily available for extraction through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Data Sharing Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality.
Most agencies have encountered little difficulty in providing this information (see below). In a small number of cases, an agency has interpreted items A1-A4 as requesting the creation of a record that does not exist. We disagree: this data is maintained by your software, can be exported through software your agency has already purchased, and is therefore subject to CPRA.
However, should you disagree, you may alternatively produce the following records:
A5. All agreements, memoranda of understanding, requests, or other certifying documents that external agencies have signed to comply with Sec 1798.90.52(b) for accessing your agency's ALPR data. These documents are also often required under the "Releasing ALPR Data" subsection of a California law enforcement agency's SB 34 policy.
A6. All agreements, memoranda of understanding, requests, or other certifying documents that your agency has signed pursuant to Sec 1798.90.52(b) to access other agencies' ALPR data.
A7. All "records of access" required by Sec. 1798.90.52(a) for the periods January 1, 2021 until the date of processing this request.
Items A5-A7 are not necessary if your agency provides the information requested in items A1-A4. We feel that items A1-A4 are more focused and would require less labor from your agency to produce.
Part B - Information Related to Numbers of “Detections” (plate scans) and “Hits” (plate scans that matched to a hotlist)
B1. The aggregate number of "detections" collected during 2023.
B2. The aggregate number of “hits” during 2023.
B3. The aggregate number of "detections" from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period. For example, most Flock Safety systems may not have this data beyond 30 days.
B4. The aggregate number of “hits” from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period.
The information requested in items B1-B4 is readily available through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Hit Ratio Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality. As noted above, this information exists within your system and can be easily exported with existing software.]
The City has identified documents which are responsive to your request. A partial production of those records can be found attached to this letter.
Here are some responses for some of your questions.
A1. We do not share information
A2. We receive information from Department of Justice (stolen vehicles)
A3. We do not share information
A4. We receive information from Department of Justice (stolen vehicles)
A5. We have uploaded Policy 422 and Policy 1305.
B1. Number of detections per our retention policy of 14 days (110019)
B2. Hits on stolen vehicles for the year of 2023 (366)
B3. Number of detections per our retention policy of 14 days (110019)
B4. Hits on stolen vehicles from January 1, 2024, to February 23, 2024 (62)
The City is in the process of compiling and reviewing additional documents and anticipates being able to produce additional responsive documents by April 18, 2024.
If you have any questions concerning your request, please feel free to contact me at kperez@berkeleyca.gov.
************************************************************************
<em>Questions about your request?</em> Reply to this email or sign in to contact staff at City of Berkeley.<br><em>Technical support:</em> See our <a href="https://www.nextrequest.civicplus.help/hc/en-us/categories/17720084172567-Requesters">help page</a>
From: Berkeley Police Department
City of Berkeley
************************************************************************
A document has been released to you for record request #24-157:
* Fixed Automated License Plate Readers (ALPRs).pdf
Document links are valid for one month.
After April 29, you will need to sign in to view the document(s).
************************************************************************
<em>Questions about your request?</em> Reply to this email or sign in to contact staff at City of Berkeley.<br><em>Technical support:</em> See our <a href="https://www.nextrequest.civicplus.help/hc/en-us/categories/17720084172567-Requesters">help page</a>
From: Berkeley Police Department
City of Berkeley
************************************************************************
A message was sent to you regarding record request #24-157:
This is in response to your February 4, 2024 Public Records Act request for:
[This letter constitutes a request under the California Public Records Act ("CPRA") from the Electronic Frontier Foundation, submitted with the assistance of MuckRock News.
We request the following records related to Automated License Plate Readers ("ALPRs") and your law enforcement agency ("Agency").
Part A - Information related to ALPR data sharing.
A1. The names of agencies and organizations with which the Agency shares ALPR data;
A2. The names of agencies and organizations from which the Agency receives ALPR data;
A3. The names of agencies and organizations with which the Agency shares “hot list” information;
A4. The names of agencies and organizations from which the Agency receives “hot list” information.
The information requested in items A1-A4 is readily available for extraction through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Data Sharing Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality.
Most agencies have encountered little difficulty in providing this information (see below). In a small number of cases, an agency has interpreted items A1-A4 as requesting the creation of a record that does not exist. We disagree: this data is maintained by your software, can be exported through software your agency has already purchased, and is therefore subject to CPRA.
However, should you disagree, you may alternatively produce the following records:
A5. All agreements, memoranda of understanding, requests, or other certifying documents that external agencies have signed to comply with Sec 1798.90.52(b) for accessing your agency's ALPR data. These documents are also often required under the "Releasing ALPR Data" subsection of a California law enforcement agency's SB 34 policy.
A6. All agreements, memoranda of understanding, requests, or other certifying documents that your agency has signed pursuant to Sec 1798.90.52(b) to access other agencies' ALPR data.
A7. All "records of access" required by Sec. 1798.90.52(a) for the periods January 1, 2021 until the date of processing this request.
Items A5-A7 are not necessary if your agency provides the information requested in items A1-A4. We feel that items A1-A4 are more focused and would require less labor from your agency to produce.
Part B - Information Related to Numbers of “Detections” (plate scans) and “Hits” (plate scans that matched to a hotlist)
B1. The aggregate number of "detections" collected during 2023.
B2. The aggregate number of “hits” during 2023.
B3. The aggregate number of "detections" from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period. For example, most Flock Safety systems may not have this data beyond 30 days.
B4. The aggregate number of “hits” from January 1, 2024 until the date this request is processed. If your agency has a retention period shorter than 1 year, please provide whatever data is available based on your retention period.
The information requested in items B1-B4 is readily available through the ALPR software you use. For example, with Vigilant Solutions/Motorola Solutions, this data can be exported easily using the Hit Ratio Report function. With Flock Safety, this information is available through the transparency portal function. Other software, such as BOSS, has similar functionality. As noted above, this information exists within your system and can be easily exported with existing software.]
The City is continuing its search and anticipates completing its review and being able to provide additional responsive documents if any by April 26, 2024.
If you have any questions concerning your request, please feel free to contact me at kperez@berkeleyca.gov.
************************************************************************
<em>Questions about your request?</em> Reply to this email or sign in to contact staff at City of Berkeley.<br><em>Technical support:</em> See our <a href="https://www.nextrequest.civicplus.help/hc/en-us/categories/17720084172567-Requesters">help page</a>
Files
pages