{"resourceId":"flock-guardrails-7day-retention-mandatory-audit-20260813","versions":[{"version":"external-e286bed4e7a4284c4b6c3de1dc13f1b82deb6bb836efbf929603d911d5d47bb2","resource":{"id":"flock-guardrails-7day-retention-mandatory-audit-20260813","title":"Flock announces 7-day default ALPR retention recommendation, mandatory Audit Assistance, proactive lockouts and required case codes","organization":"Flock Safety","sector":"Policing / ALPR vendor controls","geography":"United States (vendor-wide customer base)","publishedAt":"Aug. 13, 2026","publicationDate":"2026-08-13","eventDate":null,"sourceName":"Flock Safety","sourceLabel":"Flock Updates Privacy, Accountability, Security, and Transparency Safeguards","sourceUrl":"https://www.flocksafety.com/blog/flock-guardrails-address-lpr-privacy-concerns-and-police-transparency","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["data-security","governance-procurement","infrastructure","operating-model"],"finding":"Flock's Aug. 13, 2026 blog says it is changing its recommended/default ALPR retention from 30 days to 7 days and adding Evidence Mode to preserve selected data for active investigations. It will require all law-enforcement customers to adopt Audit Assistance by year-end, add proactive lockout when activity meets abnormal-behavior criteria, and require case codes for all law-enforcement searches by year-end (after optional use since July 2025). The post cites Bishop Fox security testing and encourages Transparency Portals. Existing customers keep democratically approved retention unless they opt into 7-day. Newly relevant as cities exit or sue over misuse and retention length.","sledRelevance":"Documents the dominant ALPR vendor's control roadmap agencies can demand in contracts—even while treating claims as unverified until independently audited.","evidence":"Opened Flock's product blog. Vendor self-description; no independent measurement of misuse reduction or lockout efficacy in the post.","architectureImplications":"Shorter default retention, Evidence Mode cold storage, mandatory anomaly detection and case-code fields on search APIs.","governanceImplications":"Interpretation: Councils should verify whether their tenant has Audit Assistance, case codes and retention set to policy—not assume vendor defaults.","securityPrivacyImplications":"Proactive lockouts and MFA/Bishop Fox review claims aim at misuse and product security; effectiveness not measured here.","caveats":"Vendor marketing; customers may keep longer retention; no public metrics on lockouts or false positives.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: Flock is promising mandatory audit assistance, case codes, lockouts and a 7-day retention default after privacy backlash. Agencies should treat this as a contract checklist, not proof of safety. A bounded engagement is a tenant-configuration audit against the announced controls. The blog does not show reduced misuse rates.","engineering":"Engineering framing: confirm Audit Assistance enrollment, case-code enforcement, lockout rules, MFA and retention/Evidence Mode settings in the live tenant. Prerequisites include admin rights and local retention policy. Proof of value is exporting configuration and a week of searches all bearing case codes.","delivery":"Delivery framing: update local ALPR policy to the shorter retention if adopted, train admins on lockout review and Evidence Mode, and schedule year-end compliance checks. Ownership is the ALPR program admin. Risk: leaving longer legacy retention while assuming the new default applies."},"roleDetails":{"sales":{"customerProblem":"Agencies under ALPR scrutiny need verifiable vendor controls, not blog announcements alone.","stakeholders":["Police command","City council","Flock administrator","City auditor","Privacy counsel"],"discoveryQuestions":["Is Audit Assistance on for every user?","Are case codes mandatory in our tenant?","What retention is actually configured?","How are lockouts reviewed?"],"valueHypothesis":"Forcing announced controls into acceptance tests can close known misuse gaps; it does not guarantee constitutional compliance.","potentialEngagement":"Flock tenant control-verification and policy alignment sprint.","unsupportedClaims":["7-day retention ends mass-surveillance concerns","Mandatory Audit Assistance stops all abuse","Bishop Fox review implies no remaining vulnerabilities"]},"engineering":{"fit":"Current Flock customers needing to operationalize 2026 guardrail features.","architectureIntegration":"Enable Audit Assistance and case codes globally; configure retention/Evidence Mode; integrate admin alerts for lockouts.","prerequisites":["Org admin access","Written retention policy","On-call admin for lockouts"],"constraints":["Legacy retention may remain until opted down","Feature timing by end of year","Vendor-defined anomaly criteria"],"security":"MFA everywhere, review lockouts promptly and monitor Evidence Mode holdings.","proofOfValue":["Config export showing Audit Assistance required","Zero searches without case codes in sample week","Documented lockout response drill"]},"delivery":{"work":"Roll out mandatory features, retrain users and align local policy/transparency portal.","dependencies":["Flock feature release schedule","Council retention preference","Auditor"],"ownership":"Agency Flock administrator","skillsAdoption":"Supervisors learn to adjudicate Audit Assistance flags.","governanceCheckpoints":["Year-end mandatory-feature deadline","Quarterly config attestation","Transparency portal update"],"acceptanceCriteria":["Case codes required in production","Audit Assistance enabled for all LE users","Retention setting matches council policy"],"risks":["Assuming default 7-day without checking tenant","Alert fatigue on lockouts","Evidence Mode overused to recreate long retention"]}},"retrievedAt":"2026-10-29T01:05:00Z","enrichedAt":"2026-10-29T01:06:25Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Administrators must review Audit Assistance flags; investigators need Evidence Mode procedures for cases lasting beyond 7 days.","procurementImplications":"Interpretation: Write year-end mandatory features into SLAs and acceptance tests.","operatingModelImplications":"Operational owner: agency Flock administrator with city policy on retention.","sourceVerification":{"openedUrl":"https://www.flocksafety.com/blog/flock-guardrails-address-lpr-privacy-concerns-and-police-transparency","referenceExcerpt":"We will now require all law enforcement customers to adopt this feature by the end of this year.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}