Unanswered or partially answered requests
- 1
Pre-Feb. 25, 2025 access, use, training, certification, subscriptions, participation, and related records. Partially answered Signed MOU; complete account entitlement/history; training certificates; user-role history; terms applicable after April 1, 2024; complete search/audit records; any invoices or agreements for 2023-24 access. Produce the signed MOU, account/role/export records, certifications, and the complete terms governing 2023-24 access. - 2
Source of pre-Feb. 25, 2025 access, including agreements, sponsorships, pilots, partnerships, or another-agency access. Partially answered The actual MOU; exact free-plan or Community Tier terms; list of networks actually accepted and accessible; any sponsoring/partner agreement; basis for continued searches after April 1, 2024. Identify each access source, date, account tier, accepted network, and governing agreement. - 3
Records explaining 2023-24 Flock use and how access existed before the March 2025 service agreement. Partially answered A coherent explanation of the free/MOU/Community Tier lifecycle; what data/cameras were searchable; Board/County Administration notice; all prior records specifically identified. Provide a written record index and all agreements/terms explaining the 2023-24 access. - 4
All ACSO-Flock communications and attachments from Jan. 1, 2023 to present. Partially answered / completeness unclear Referenced but absent attachments, including signed MOU, Board packet/resolution, deployment maps, some project/proposal and training materials; search methodology and custodians. Supplement missing attachments and identify custodians, search terms, date completed, and any excluded systems/accounts. - 5
Every agency authorized to access ACSO ALPR data, date granted, and access type. Partially answered Grant dates; active vs pending/invited/revoked status; exact permission type; users/roles; alert access; audit of actual use. Export the full sharing configuration with dates, status, permissions, and revocations. - 6
Every agency or organization whose ALPR data ACSO personnel may access. Partially answered Acceptance/activation date; active vs offered/pending status; role assignment; exact search/alert/video privileges; revocations; actual use. Produce accepted/active share exports and role/network assignment history. - 7
Installation date, activation date, and operational status of each current camera location. Partially answered Two of ten contracted cameras/locations; distinct activation dates; serial/device IDs; current live/offline status; relocation history. Provide a ten-device inventory with location, install, activation, current status, and relocation history. - 8
All grant/funding applications, awards, agreements, reimbursements, reports, correspondence, and related ALPR funding records. Partially answered Complete applications, award letters, grant agreements, approvals, reimbursement requests, accounting ledgers, partner agreements, and correspondence tying each dollar to cameras/services. Produce the complete grant and accounting files by funding source and fiscal year. - 9
Specific grant sources referenced in the Feb. 25, 2025 Board item. Partially answered The complete Board-referenced grant source documentation and reconciliation to the $45,500 first-year invoice. Provide a source-by-source funding reconciliation and the underlying award/approval records. - 11
Whether any federal agency, task force, contractor, employee account, or indirect federal access existed. No responsive records claimed / unresolved Search description; indirect access through fusion centers, joint task forces, shared state/local accounts, contractors, or downstream sharing; account-domain review. Describe the search and produce or confirm records for direct and indirect federal/task-force/contractor access, including NCRIC. - 12
All agencies/entities/users that accessed, queried, received alerts, or otherwise used ACSO data. Partially answered / material withholding Non-investigatory fields from access/search logs; dates, agency/user identity, action type, result count, role, alert delivery; withholding log and segregability explanation. Produce segregated non-investigatory metadata and identify withheld record categories and fields. - 13
Policies, audits, compliance reviews, or reports about outside sharing and Civil Code compliance. Partially answered / mostly unanswered ALPR-specific sharing procedures, periodic reviews, Civil Code compliance assessments, approvals, misuse checks, and audit findings. Identify and produce ALPR-specific compliance/audit records or confirm none exist after a documented search. - 14
The policy referenced in the Sept. 13, 2023 email, including drafts, prior versions, approvals, and memoranda. Unanswered Sept. 2023 draft; revision history; Lexipol workflow/metadata; approval/adoption record; implementation memo; prior versions. Produce drafts, version history, approvals, or confirm none were retained and describe the search. - 15
Audits, compliance/policy reviews, misuse/discipline/administrative reviews, or corrective actions since Jan. 2023. Partially answered / mostly unanswered Confirmation whether misuse or corrective-action records exist; segregated non-identifying/aggregate portions; audit-review reports; policy review records. State whether each category exists and produce segregable non-personnel portions or a category-specific withholding description. - 16
All categories of data captured, processed, stored, retained, or available through Flock. Partially answered A system-specific data dictionary; enabled/licensed fields; storage locations; retention by category; distinction between ACSO cameras and shared networks. Produce enabled-feature configuration, data dictionary, and contract/order-form mapping. - 17
Whether Vehicle Fingerprint is used and what characteristics are captured/searchable. Partially answered Feature-enabled status for ACSO; exact characteristics; retention; audit of use; distinction between marketing claims and active configuration. Provide configuration screenshots/export and current feature list. - 18
Image resolution, dimensions, format, and quality. No responsive records claimed Search details; any vendor spec, sample export metadata, procurement specification, or camera configuration. Confirm custodians/systems searched and request the technical specification from Flock if held by ACSO. - 19
Screenshots, manuals, training, or records showing the user view of reads, alerts, searches, or history. Partially answered Locally retained manuals, webinar decks/recordings, help-center exports, user training attachments, sample reports, and any screenshots embedded in Board/training materials. Produce archived copies of materials relied upon or identify why they were not retained. - 20
Whether system captures cropped plates, full vehicles, multiple/front/rear/side images, or combinations. Partially answered Camera orientation, number of images per detection, plate crop versus context image, front/rear capability, and sample metadata. Produce deployed-camera specifications and configuration records. - 21
Whether any available device can capture/process audio, detections, video, clips, continuous video, still images, or other media. Partially answered Enabled access to shared video/audio networks; whether users had roles for VMS/live/historical/download; device-level capability/configuration. Produce role/network configuration for non-LPR shared products and clarify whether ACSO users can access them. - 22
Whether audio/video/non-ALPR functions are enabled, licensed, subscribed to, or available under ACSO agreement. Partially answered / unclear Exact enabled permissions and accepted networks; whether any ACSO user can access live/historical video, downloads, audio detections, or alerts. Provide an export of roles, networks, and product permissions for all ACSO users. - 23
How images are generated: stills, video extraction, buffered video, or another method. Partially answered Technical specifications or vendor correspondence held by ACSO; camera configuration and firmware documentation. Produce any held technical materials or identify the search and confirm none are retained. - 24
Materials requested/reviewed/relied upon about image capture, Vehicle Fingerprint, video, audio, and collected data. Partially answered Missing attachments/linked resources; preserved demos/recordings; Board packet FAQ/privacy materials; evidence of what ACSO actually relied on. Produce archived copies of referenced materials and identify which were used for policy/procurement decisions. - 25
Copies of records responsive to the immediately preceding technical-materials item. Unanswered / treated as unclear Clarification communication and complete copies of all item-24 records. Confirm item 25 was intended to request copies of item-24 records and supplement any omitted materials. - 26
Category-by-category retention periods, storage locations, and whether retained by Flock, ACSO, or both. Partially answered Retention for searches, alerts, hotlists, audit logs, metadata, exports, flags, downloaded images, evidence, shared video/audio; storage locations and deletion rules. Provide a retention schedule/data map for every requested category. - 27
Explain conflict between 30-day Flock retention and Policy 473.5 minimum one-year server storage, including downloads/exports/local storage. Unanswered / major unresolved conflict Meaning of “the server”; policy revision or implementation decision; download/export/flag procedures; local storage; category-specific retention; evidence/case file rules. Produce all policy drafts/revisions and a written, record-supported reconciliation of the two retention rules. - 28
All ALPR vendors/products researched, considered, compared, demonstrated, or discussed before choosing Flock. Partially answered / claimed research not substantiated Identity of the claimed second company; communications, demos, quotes, notes, product comparisons, and search methodology for other vendors. Identify every vendor considered and produce all related records, or state that no comparative research records exist. - 29
Criteria, factors, requirements, or standards used to compare ALPR vendors/products. Unanswered Requirements list, scoring, procurement criteria, privacy/data-sharing/retention standards, technical requirements, cost comparison. Produce evaluation criteria or confirm none were documented. - 30
Reports, studies, analyses, notes, charts, scoring, recommendations, or records about vendor evaluation/selection. Unanswered All evaluation/selection work product and internal notes; records held by Sheriff, GSA, County Administration, County Counsel, IT, purchasing. Search all relevant custodians and produce the evaluation records or state none exist. - 31
All ACSO-Flock communications and attachments Jan. 2023-Mar. 31, 2025. Partially answered / completeness unclear Missing signed MOU, maps, Board packet/resolution, project attachment, recordings, and other referenced attachments; custodian/search detail. Supplement missing attachments and provide a production index tied to custodians and date range. - 32
All ACSO communications with any other ALPR vendor/provider/reseller/consultant from Jan. 2023-Mar. 31, 2025. Unanswered / materially incomplete Emails and attachments with Vigilant/Motorola or any other vendor; procurement/reseller correspondence; records explaining the quote and renewal decision. Produce the communications or confirm after a documented search that none exist. - 33
RFIs/RFPs/RFQs, vendor responses, proposals, quotes, demos, literature, pricing, or marketing from ALPR vendors. Partially answered Any formal solicitation, competing quote/proposal, demo material, reseller response, and procurement file. Confirm whether a solicitation occurred and produce all vendor responses. - 34
Meetings, demos, presentations, webinars, trainings, or discussions with ALPR vendors, including date, attendees, vendor, subject. Partially answered Attendance records, meeting notes, recordings, agendas, and any non-Flock vendor meetings. Produce attendance/notes/recordings and identify canceled versus held events. - 35
Why Flock was selected over competitors, including recommendations, approvals, comparisons, or justification. Unanswered Decision memo; recommendation; comparative price/features; procurement justification; final decision-maker and approval chain. Produce the agency’s selection rationale and decision records, or confirm the choice was not documented. - 36
Privacy, civil-liberties, constitutional, surveillance, retention, sharing, accuracy, reliability, or misuse concerns considered during selection. Partially answered / mostly unanswered County Counsel/IT/privacy review; accuracy/error analysis; data-sharing risk assessment; misuse controls; constitutional analysis; public-impact assessment. Produce all issue analyses and identify whether County Counsel or Administration reviewed them. - 37
Communications/reports/recommendations to Sheriff, Undersheriff, command staff, County Administration, County Counsel, or Board about selecting Flock. Partially answered Complete internal decision chain; County Administration, GSA/purchasing, County Counsel and Board communications/attachments; recommendation and approval record. Search all named custodians and produce the internal recommendation/approval file and missing Board attachments.
Referenced but not produced
- Mutually signed July 2023 Flock MOU and all applicable free-plan/Community Tier terms.
Pre-contract access Mutually signed July 2023 Flock MOU and all applicable free-plan/Community Tier terms. Email chain expressly says the MOU was signed and mutually completed and would grant system/search access. 1, 2, 3, 4, 31 - Complete account, user-role, network-assignment, entitlement and access-history exports for 2023-2025.
Pre-contract access Complete account, user-role, network-assignment, entitlement and access-history exports for 2023-2025. Administrative audit and sharing emails show accounts and roles existed, but scope/status is not reported. 1, 2, 3, 5, 6, 11, 12 - Search Tool certifications, training completion records, and training-file records for users instructed to certify.
Training Search Tool certifications, training completion records, and training-file records for users instructed to certify. Emails instructed personnel to complete certification and submit certificates. 1, 3, 15, 19 - August 2023 deployment maps and the generated 16-camera quote.
Planning/procurement August 2023 deployment maps and the generated 16-camera quote. Aug. 31 email links to two maps and says a quote was generated. 4, 31, 33, 34 - Board letter/resolution attachment circulated Feb. 19, 2025 and the FAQs/Privacy Commitment added to the packet.
Board approval Board letter/resolution attachment circulated Feb. 19, 2025 and the FAQs/Privacy Commitment added to the packet. The email chain refers to attachments/resources, but the EML has no attachment. 4, 24, 31, 36, 37 - Project/proposal attachment referenced in the Jan. 14, 2025 “Re: The New Guy!” chain.
Planning/procurement Project/proposal attachment referenced in the Jan. 14, 2025 “Re: The New Guy!” chain. Message refers to a project/proposal, but no attachment was preserved. 4, 31, 33, 37 - Training resources/recordings referenced in 2025 training communications.
Training Training resources/recordings referenced in 2025 training communications. Emails reference recordings and resources; several exist only as external links. 4, 19, 24, 34 - September 2023 ALPR policy draft, prior versions, approval/adoption records, and implementation memoranda.
Policy September 2023 ALPR policy draft, prior versions, approval/adoption records, and implementation memoranda. The earlier email said the policy was being prepared/pushed out; current final policy does not show development history. 14, 15, 27, 36 - Policy/procedure defining “the server,” downloads, exports, flags, local storage, evidence retention, deletion and purging.
Retention Policy/procedure defining “the server,” downloads, exports, flags, local storage, evidence retention, deletion and purging. Policy and Sheriff response refer to one-year server storage and longer retention after flag/download, but no implementation record explains either. 26, 27 - Search/access audit logs with segregable non-investigatory fields.
Search/audit Search/access audit logs with segregable non-investigatory fields. Item 12 requested actual access/use; only admin audit and monthly totals were supplied. 10, 12, 15 - Sharing dates, active/pending/accepted/revoked status, exact permissions, user-role assignments and actual-use logs.
Sharing Sharing dates, active/pending/accepted/revoked status, exact permissions, user-role assignments and actual-use logs. Both sharing CSVs omit these fields; pending-share email shows multiple permission types exist. 5, 6, 11, 12, 13, 21, 22 - Communications, quotes, demos, evaluation criteria, comparison documents, recommendations and decision records concerning any competitor.
Vendor selection Communications, quotes, demos, evaluation criteria, comparison documents, recommendations and decision records concerning any competitor. Sheriff previously described extensive research/another company, but the production does not substantiate it. 28-36 - Communications with Vigilant/Motorola or another ALPR vendor during Jan. 2023-Mar. 2025.
Vendor selection Communications with Vigilant/Motorola or another ALPR vendor during Jan. 2023-Mar. 2025. A Vigilant renewal quote exists, but no corresponding communication thread was produced. 32, 33, 34, 35 - Complete inventory for all ten contracted cameras, including activation/current status and relocation history.
Installation Complete inventory for all ten contracted cameras, including activation/current status and relocation history. Install sheet has eight entries and deployment reports refer to ten devices. 7 - Complete grant applications, award letters, grant agreements, reimbursement requests, approvals, accounting records and partner agreements.
Funding Complete grant applications, award letters, grant agreements, reimbursement requests, approvals, accounting records and partner agreements. The production contains fragments and amounts but not complete funding files. 8, 9 - Record-category withholding log, segregability explanation, custodians, search locations, search terms, and date range for categories claimed absent or withheld.
Withholding/search Record-category withholding log, segregability explanation, custodians, search locations, search terms, and date range for categories claimed absent or withheld. The response uses general exemptions and “no records” statements without a detailed production/withholding index. 4, 11-15, 18, 25, 31-37
Contradictions and unexplained issues
- Claimed extensive competitor research is not substantiated
The production is dominated by Flock communications. Historical Vigilant POs and one 2023 renewal quote show an existing subscription, but no comparison, competing proposal, scoring, demo notes, criteria, or selection memorandum. What was the second company and where are the records of the claimed research? 28-36 - Operational use preceded formal camera approval
Accounts were created in August 2023 and monthly search totals begin that month; the Board item occurred February 25, 2025 and County-camera installs began in May 2025. What legal/contractual/account-tier basis supported 2023-24 searches, and what data/cameras were accessible? 1-3, 10, 31 - Free access change versus continued searches
Flock said broad free access would end April 1, 2024 and Community Tier would limit access; ACSO nevertheless recorded searches throughout 2024. Did ACSO become a paying customer, retain direct shares, use private cameras in jurisdiction, or use another arrangement? 1-3, 6, 10 - 30-day retention versus one-year policy
Flock default is 30 days; Captain Martin noted the policy said one year and asked to make necessary changes; no resolution was produced. Was policy 473.5 changed, ignored, or applied only to downloaded/local data? What is “the server”? 26-27 - Sharing statement is narrower than the records
Outgoing report is California-oriented, while incoming report includes at least 30 clearly out-of-state organizations and networks labeled Condor, Raven, PTZ and VMS. Which incoming shares were accepted, assigned to roles, searchable, or actually used; and was any access indirect through federal/fusion/task-force structures? 5-6, 11-13, 21-22 - Agency list is not actual-use evidence
Sheriff cites agency privileges and an administrative audit, but neither shows which outside users accessed/searched/received alerts from ACSO data. What segregable access-log metadata exists and what exactly was withheld? 12, 15 - Ten-camera contract versus eight install entries
Contract/deployment materials describe ten cameras; install sheet contains eight dated rows. Where are the remaining two devices, and what are the activation/current statuses of all ten? 7 - Generic IT policy treated as responsive ALPR compliance material
document.pdf is a general County IT policy, not an ALPR-specific sharing or Civil Code compliance audit. Do ALPR-specific compliance reviews, sharing procedures or audits exist? 13, 15 - Invitations, configured sharing and actual access are conflated
Invitation emails require an admin to add networks to roles; pending-share email shows requests can remain pending; reports do not state accepted/active status. Which invitations were accepted, which networks were role-assigned, and who used them? 2, 5, 6, 12 - Product capability versus purchased/enabled product is not separated
Flock marketing describes Nova, Condor, Raven, live video and other products; current order records show Falcon LPR/FlockOS-related services. Which non-LPR products, if any, were enabled through sharing or purchased by ACSO? 16-24