# Marion Flock Terms, Implementation, and Site Permissions Four produced records supply different kinds of evidence: vendor contract terms, generic installation guidance, Marion permission/permit records, and onboarding choices. A fifth is an Arkansas State Police LPR policy included in the Marion package. ## Vendor terms The 2023 terms say Customer Data belongs to the customer and is not sold, give Flock a license needed to provide services, and permit creation/use of anonymized data including `"training of machine learning algorithms"` (`Terms and Conditions - Flock info.pdf`, pp. 7-8). These are contract representations, not an audit of actual data practice. ## Generic implementation guidance The implementation guide prices existing-infrastructure, standard, and advanced installations at `$150`, `$650`, and `$1,900` per camera and allocates permitting, electrical, traffic-control, and exceptional site work between customer and installer (`Customer Imp. Guide - Flock.pdf`, pp. 7-12, 19-21). The guide is generic; no line is treated as proof that a particular cost or task applied at every Marion site. ## Site permissions and onboarding `Contracts - Agreements Flock.pdf` is primarily a 64-page collection of city/ARDOT permission letters, permit forms, engineering drawings, and third-party attachment/property licenses (pp. 1-64). It documents siting and coordination, not the commercial order history or current activation state. The onboarding deck records `"Camera Sharing: Yes"` and `"Public Announcement: Not going to do announcement at this time"` (`Flock safety info.pdf`, p. 8). These are captured onboarding choices, not a complete public-notice or sharing policy. ## Policy provenance `LPR USE - Flock.pdf` defines `"Member"` as a sworn Arkansas State Police officer and gives an effective date of 2024-07-01. It sets a maximum retention period `"not to exceed 150 days"` and includes ASP dissemination/reporting and hit-verification duties (pp. 1-4). The document's own text makes it an ASP policy; it is not attributed to Marion. ## Open questions - Marion's own adopted LPR policy and approval history. - Final permits, closeout, as-built, activation, and acceptance records for each Marion site. - Whether the onboarding sharing and public-announcement choices later changed.