# Flock Safety Evidence Policy > *Audited source extract. The dossier was used only as a lead; the underlying source was independently acquired and checked on 2026-07-20.* ## Source metadata - **Publisher:** Flock Safety - **Original dossier URL:** https://www.flocksafety.com/legal/flock-evidence-policy - **Resolved/canonical URL used:** https://www.flocksafety.com/legal/flock-evidence-policy - **Publication date:** not stated / not independently established - **Underlying event or version:** not separately stated - **Archived:** 2026-07-20, from unauthenticated public access; no cookies, tokens, or login state retained - **Wayback snapshot:** save failed on 2026-07-20 after the archive service returned HTTP 403; retry pending ## Verification verdict **supported with narrower wording** — The policy states a 30-day default, hard deletion after the applicable period, customer-specific exceptions, and up-to-one-year extended retention with governing approval. These are Flock policy representations, not proof that a tenant's settings or deletion jobs conformed. ## Claim boundary This source is authoritative only within the source class and limitations stated above. ## Extract **Extracted-text lines 239-243:** > Please see the below processes for requesting evidence from Flock. > Evidence Certification Requests > Flock’s Standard Retention Period: > Flock’s standard retention period is thirty (30) calendar days from the date of capture. This standard retention period applies to all customer data, unless otherwise specified in the individual customer’s agreement. > Non-LPR Evidence: **Extracted-text lines 327-331:** > Flock builds our in-house, proprietary machine learning technology which is capable of identifying types of vehicles, license plate information, and various other objective vehicle characteristics (e.g. roof rack). Flock maintains a high standard of quality check and validates every machine learning model with a large, diverse dataset of vehicles, ensuring that our accuracy is inline with industry standards. > How does data security work? > The license plate data is securely captured, transmitted to the cloud, stored for thirty (30) days, and then permanently deleted. The data and footage is encrypted throughout its entire lifecycle. All data is securely stored with AES256 encryption with our cloud provider, Amazon Web Services. On the camera itself, data is only stored temporarily until it is uploaded to the cloud, at which point it is removed automatically from the local camera. This means the data is secure from when it is on the Flock camera to when it is transferred to the cloud, using a secure connection to Flock servers. While stored in the cloud, all data (both footage and metadata) is fully encrypted at rest. Flock defaults to permanently deleting all data after thirty (30) days on a rolling basis unless otherwise required by law or the individual customer agreement. Data collected, stored, and processed on devices and within Flock Safety’s cloud platforms are secured in accordance with Flock’s adoption of policies, procedures, and security controls necessary to identify, protect, detect, respond, and recover from cybersecurity events which can be found on our website > Flock Safety Trust Center > . **Extracted-text lines 332-336:** > What is Flock’s Retention Period/ How is the Retention Period decided? > Flock Safety’s default data retention period for data collected by license plate readers is thirty (30) days, after which data is  hard deleted from the cloud. We believe thirty days provides strong protection for community privacy while still enabling the provision of sufficient evidence in the majority of cases. There are also administrative benefits for our customers by retaining and storing less data. > Flock will respect existing LPR retention laws and regulations that differ from 30 days. If a customer wishes to impose a longer retention period that is not already required by its jurisdiction’s laws, Flock will offer an extended retention for up to one year, but shall require the agency to first obtain approval from an elected official and/or a governing body > . > This allows the decision to be made transparently and with the support of the community. **Wayback failure**: The bounded Save Page Now pass stopped after the archive service returned HTTP 403 on the first request. This source was not individually retried; retry pending. ## Notes - Tier: 2 — vendor primary/self-description; authoritative only for the vendor's own claims. - The excerpt is bounded to the claims audited here; consult the preserved original for full context. - Cited by: see `citing_pages:` frontmatter; populated after wiki integration.