iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Short answer: Flock Safety’s current stated default is seven calendar days of retention, while Axon describes agency-defined retention and sharing that is off by default. A local Flock deployment can be stricter than the vendor’s network-wide capabilities, as Burbank’s policy illustrates. Motorola/Vigilant cannot be ranked reliably on retention or sharing from the available public material alone. The decisive documents are the customer contract, agency policy, configured settings, user list, sharing-network membership, and audit records—not the vendor name.
That distinction matters because an automated license plate reader (ALPR) is both a camera system and a searchable information system. A plate image can be connected to a vehicle description, a date and time, and a camera location. The privacy risk is therefore determined by the entire lifecycle: what is captured, who can query it, whether another agency can search it, how long it remains available, and whether misuse is detected and punished.
What an automated license plate reader system actually controls
An automated license plate reader (ALPR) photographs passing vehicles, converts the plate image into searchable characters, and associates the record with vehicle characteristics, a capture time, and a camera-location identifier. The result is not just a plate number: it is a time-and-place record that can be searched later by authorized users.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePrivacy therefore depends on the complete deployment. A vendor may offer role-based access, deletion timers, audit logs, and sharing switches, but the agency decides which features are enabled, which personnel receive accounts, which outside agencies can query the data, and how exceptions such as evidence holds are handled. State law, local policy, contract language, and actual audit practice can produce very different outcomes from the same platform.
#1 Best Overall
- Compatibility-- Only Work With ONWOTE TD Series NVR (PNT-808, PNA-8016-T, PNT-1232).
- LPR-- License Plate Recognition IP Network PoE Camera.
- 4MP Resolution-- 2592×1520 @30fps for sharp and fluid video.
- 1/1.8" Low-Light Image Sensor-- Ensuring clear images even in dim conditions.
- 8-32mm Motorized Varifocal Lens @F1.6 for adjustable field of view.
There are several separate control questions that are often collapsed into one:
- Collection: Which roads, facilities, or camera zones are covered, and what vehicle or location fields are stored with each image?
- Use: What official purposes justify a query, and are plate searches allowed for exploratory or personal reasons?
- Access: Which named employees, contractors, or partner agencies can log in or receive results?
- Retention: When is a record automatically deleted, and what exceptions preserve it?
- Oversight: Are searches logged, reviewed, and tied to consequences for misuse?
The comparisons below describe published vendor or agency statements. They are not independent tests of camera accuracy, optical-character-recognition performance, uptime, cybersecurity, crime reduction, or value for money.
Flock Safety: the current retention rule and its exceptions
Seven days is the stated standard
Flock’s current Evidence Policy states: “Flock’s standard retention period is seven (7) calendar days from the date of capture.” The policy says the customer agreement can specify a different period. It also says data is permanently deleted when the applicable retention period expires.
That makes seven days a stated default, not a universal promise for every installation. A contract, state requirement, local policy, or evidence-preservation process can change the effective period for a particular agency. The important distinction is between the vendor’s standard setting and the value configured for a specific customer.
Longer retention requires a documented basis
The same policy describes extensions of up to one year. When a longer period is not already required by law, the extension requires approval from an elected official or governing body under the conditions in the policy. A department should therefore be able to identify the applicable retention schedule, the approving authority, and the system setting that implements it.
Ask whether the period starts at capture or at a later event, whether a record can be placed on an evidence hold, and whether an exported copy remains in another case-management system. Automatic deletion in the ALPR platform does not necessarily answer what happens to copies lawfully retained elsewhere. The contract should also address deletion after termination, backups, and records preserved for litigation or a criminal case.
Recent change from a longer default
Flock announced platform changes in August 2026 that shortened its standard window from 30 days to seven days and required law-enforcement customers to implement an audit tool intended to flag abnormal searches by January 1. Because the announcement and the Evidence Policy are separate sources, confirm whether the audit tool is operational at the agency and what alerts, reviews, and disciplinary actions it produces after the stated deadline. The Associated Press reported the change in its August 2026 coverage.
A shorter default reduces routine availability of historical records, but it does not by itself control sharing, account privileges, or evidence holds. A department could have a seven-day setting and still permit broad real-time access, or it could use a longer legally required period with strong role and audit controls.
What Flock says it collects and who can search it
Flock’s Data Privacy & Protection page describes captured plate images, vehicle characteristics, timestamps, and camera-location identifiers. It says approved users receive role-based access and that “Every search is recorded and reviewable.” Those are descriptions of the vendor’s system; they do not independently establish that every customer has configured roles correctly or reviews every log.
For a real deployment, ask four separate questions:
- Which named employees and contractors have accounts?
- What searches may each role perform, and are case numbers or reasons required?
- Can another agency search directly, receive exported records, or only receive a response to a specific request?
- Who reviews logs, how often, and what happens after an improper search?
Also ask whether administrators can change retention or partner settings without a public vote, whether former employees are removed promptly, and whether a user can download a bulk result. These are implementation questions, not conclusions that follow from the Flock brand.
Axon’s published privacy posture is configured by the agency
Axon’s Data Privacy materials describe a different control model. Axon says the agency owns the data, “Nothing is shared by default,” and “Access happens only at your agency’s direction.” It also describes logically separated agency environments, least-privilege access managed by the agency, and configurable retention, auditing, and access controls.
No universal Axon retention duration is stated on that page. Consequently, “Axon keeps data for X days” is not a supported generalization. The relevant number is the period in the department’s contract and configuration, including any rules for evidence holds, exports, backups, and deletion verification.
Axon also says it does not create national databases or automatically enable sharing across agencies. That claim addresses the platform’s stated default architecture; an agency can still choose to share information through an approved workflow or participate in another data exchange. The contract, policy, and network settings determine what users can actually do.
For comparison purposes, Axon’s agency-ownership language should be read alongside practical questions: Does the agency have administrator rights? Can the vendor support team view records, and under what authorization? Are audit logs retained long enough to investigate an allegation? Does a data export preserve the same access restrictions? The published page describes controls, but the customer agreement determines obligations and remedies.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Flock, Axon, and Motorola/Vigilant: what can be compared
| Question | Flock Safety | Axon | Motorola/Vigilant |
|---|---|---|---|
| Retention | Standard stated period: seven calendar days. A customer agreement may differ; the policy describes extensions up to one year with approval in specified circumstances. | Agency-defined and configurable according to Axon’s published privacy materials; no universal duration is stated. | A complete current retention specification is not established by the available material; inspect the jurisdiction-specific contract and policy. |
| Access and audit | Flock describes approved role-based users and recorded, reviewable searches. Local policy determines practical restrictions. | Axon describes agency-directed access, least-privilege controls, and configurable auditing. | A current direct comparison of controls and logs is not established; obtain product and agency documentation. |
| Interagency sharing | Depends on the network and local settings. Burbank reports disabling interstate and nationwide lookup and limiting sharing to California law enforcement. | Axon says nothing is shared by default and automatic cross-agency national sharing is not enabled. | Confirm the exact product, subscription, database, and sharing-network terms in the contract and policy. |
| Oversight | Flock says searches are reviewable. Burbank documents training, reason requirements, and supervisory audits. | Axon describes agency-configurable audit controls. | Review log availability, audit cadence, responsible officials, and enforcement provisions. |
This is a governance comparison, not a performance ranking. The available sources do not support a reliable claim that one vendor’s cameras read plates more accurately, prevent more crime, or provide stronger cybersecurity than another’s.
Counts of agencies using a vendor are not a substitute for control specifications. A department can operate multiple systems, change products during a contract term, or subscribe to a particular database or sharing network that differs from another customer’s arrangement.
Rank #2
- LICENSE PLATE RECOGNITION CAMERA - Features 8mm - 32mm lens for an 15° - 40° Viewing Angle. F1.6 Max Aperture, 1/1.8" 4-Megapixel CMOS Image Sensor and License Plate Recognition Distance 26.25ft - 98.43ft. Supports recognizing vehicle type, vehicle color, and license plate details. Supports IVS, Tripwire & Intrusion as well as displaying vehicle plate, vehicle path & loitering detection.
- SMARTER SECURITY – Query and review license plate details professionally on a PC using a web browser. Works with most standard web browsers however for an optimal experience it is recommended to use Microsoft Edge in IE mode as the camera may require the use of a .exe plugin. Supports storage to a MicroSD Card (up to 256GB), PC/Windows only supports SFTP, IE mode in Microsoft Edge, Firefox, Chrome (limited query options).
- ACTIVE DETERRENTS – This outdoor POE IP LPR camera features a heavy-duty metal weatherproof IP67 housing as well as 4 IR LEDs for night vision up to 98 feet, includes red/blue warning LEDs which can be used as an active deterrent. Dual H.265/H.264 compression allows for maximum encryption with the latest technology as well as backwards compatibility with legacy platforms.
- SIMPLE, RELIABLE, SECURE – This Amcrest POE camera features a secure connection. At Amcrest, we want to ensure the safety of our customers, their loved ones, homes and businesses. Compatible with the following Amcrest AI NVR's for live view purposes only: B0C381YK91, B0CDHDHPR8, B0CBL8W9NY, B0D464HMBB, B0D47X8WJJ
Why a local Flock policy can be narrower than the platform
Burbank Police Department’s Flock Safety ALPR Information Guide and FAQ shows how a customer can impose additional limits. Burbank says personnel must have assigned roles and training; searches must have an official purpose and a case or reference number, or a recorded reason; and supervisors conduct audits. The department says interstate and nationwide lookup features are disabled and sharing is limited to California law enforcement.
The FAQ also records a concrete access incident. An audit found two searches by VA Police involving Burbank ALPR data in May 2025. Burbank then excluded VA Police from its sharing network. This is evidence about Burbank’s deployment and response, not proof that every Flock network has the same restrictions or that every agency performs equivalent audits.
Recommended Free Tools
The example illustrates why a privacy answer must distinguish capability from configuration. A system may technically support a broad lookup, while an agency disables it, limits the partner list, requires a case number, and reviews search logs. Conversely, a permissive policy can expose more data even when the vendor’s platform offers restrictive options.
When evaluating an incident like Burbank’s, ask what the audit actually covered, whether the searches were authorized at the time, how quickly access was removed, and whether affected people were notified. Those details reveal enforcement quality more clearly than a generic statement that searches are logged.
Adoption does not prove governance
The Virginia State Crime Commission’s 2026 report on its 2025 survey found that 137 of 159 responding agencies (86%) reported using Flock Safety. Axon was reported by 35 agencies and Motorola by 12. Agencies could report multiple vendors, so these counts overlap and are not market-share totals.
The same survey found that 112 of 159 agencies (70%) reported having an ALPR policy, 26 (16%) reported no policy, and 14 (9%) were implementing one. The report notes that displayed percentages do not total 100% because of rounding and nonresponse. The practical lesson is that buying a widely used platform and maintaining a written, enforced policy are separate questions.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →A records-based ACLU of Iowa report found Flock contracts at 27 of 43 responding Iowa agencies, Axon contracts at seven, and Motorola contracts at four. Those are sample-specific results from public-records requests, not national adoption or pricing data. Contract lengths, prices, and sharing language varied by agency.
Those Iowa records are useful for a procurement question: price and term are negotiated institutional details. They should not be converted into a supposed national price list or used to claim that every customer receives identical features. A requester should obtain the actual purchase order, renewal terms, implementation fees, support charges, and amendment history for the agency being evaluated.
What remains unknown about Motorola/Vigilant
The available material does not establish a complete, current Motorola/Vigilant specification for retention duration, query logging, sharing defaults, or customer-configurable controls. Virginia’s survey confirms that some agencies reported Motorola use, and the Iowa report discusses a limited set of Motorola contracts, but neither establishes one rule for every product, subscription, database, or jurisdiction.
Do not turn that evidence gap into a claim that Motorola/Vigilant is either more private or less private than Flock or Axon. A defensible comparison requires the specific agency’s contract, amendments, product name, database arrangement, policy, and configuration. The same caution applies when a department operates more than one ALPR product.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsAsk the agency to identify whether “Vigilant” refers to a particular camera, a local database, a national or regional exchange, or a service subscription. Then request the retention schedule, user and partner list, search-log fields, audit procedures, and deletion terms for that exact arrangement. Without those documents, a feature-by-feature ranking would overstate what is known.
How to investigate a department’s actual ALPR controls
For a city, county, campus, or state agency, request the following records. Compare them side by side rather than relying on a vendor label.
- Contract and amendments: identify the product, subscription term, ownership language, permitted uses, vendor access, breach duties, and termination or deletion obligations. Include schedules, exhibits, data-processing terms, and renewal amendments.
- Written use policy: look for authorized purposes, prohibited searches, case-number requirements, emergency exceptions, employee training, and sanctions for misuse. Check whether the policy applies equally to dispatchers, investigators, supervisors, contractors, and partner-agency users.
- Retention and deletion settings: obtain the configured number of days, evidence-hold rules, export and backup treatment, and proof that expired records are deleted. Ask who can alter the setting and whether changes are logged.
- Authorized-user and agency list: determine which employees, contractors, neighboring departments, state entities, or federal agencies can search or receive records. Request the date the list was last reviewed.
- Sharing-network settings: check whether interstate or nationwide lookup is enabled, whether partners can search directly, and whether the agency must approve each request. Distinguish a direct query from a manually shared report.
- Logs and audits: ask whether every search records the user, time, purpose, and result; who reviews logs; how often reviews occur; and what consequences follow an improper query. Ask whether abnormal-search alerts are generated and resolved.
- Transparency records: search for annual reports, public meeting materials, audit summaries, public-records responses, and documented incidents involving outside access.
When an agency refuses a request, ask for the legal basis and a segregable version with sensitive fields redacted. A retention schedule or partner-agency list may be more informative than a general privacy statement. Also check meeting minutes for approvals of longer retention, new sharing partners, or contract amendments; those decisions may not appear on the vendor’s website.
A useful audit exercise is to trace one record from capture through deletion. Identify where the original image and searchable metadata live, who first accessed it, whether it was shared or exported, whether an evidence hold was applied, which logs recorded each event, and when every copy was deleted. If an agency cannot answer those questions, it cannot demonstrate effective control merely by pointing to a privacy policy.
Questions that often produce misleading answers
“How long does Flock keep license plate data?”
The current stated standard is seven calendar days from capture, but the customer’s agreement can specify another period. The Evidence Policy describes extensions up to one year with approval under stated conditions. Ask for the local contract and configured rule, including evidence holds and exported copies.
“Can police departments share Flock data with other agencies?”
They can do so when the deployment’s network and policy permit it, but the scope is not uniform. Burbank says it disabled interstate and nationwide lookup and limited sharing to California law enforcement, while documenting and then ending VA Police access after two May 2025 searches. Other agencies may use different settings or networks.
“Is Flock different from Axon or Motorola/Vigilant?”
Flock publishes a seven-day standard and describes recorded, reviewable searches. Axon publishes agency ownership, sharing off by default, agency-directed access, and configurable retention. A complete current Motorola/Vigilant comparison is not supported by the available documentation. For all three, deployment records outrank brand-level assumptions.
Rank #3
- 𝐄𝐧𝐡𝐚𝐧𝐜𝐞𝐝 𝐃𝐮𝐚𝐥-𝐂𝐚𝐦𝐞𝐫𝐚 𝐂𝐥𝐚𝐫𝐢𝐭𝐲 𝐚𝐭 𝐔𝐩 𝐭𝐨 𝟒𝟎 𝐟𝐭 (𝟏𝟐 𝐦): Capture every event around your home in ultra-clear 3K resolution. Enjoy sharp, detailed visuals with 8× zoom to see what matters most.
- 𝐒𝐨𝐥𝐚𝐫-𝐏𝐨𝐰𝐞𝐫𝐞𝐝, 𝐈𝐧𝐬𝐭𝐚𝐥𝐥 𝐎𝐧𝐜𝐞 𝐚𝐧𝐝 𝐢𝐭 𝐑𝐮𝐧𝐬 𝐅𝐨𝐫𝐞𝐯𝐞𝐫: Experience constant peace of mind with this solar-powered security camera that's easy to set up and always on, thanks to its removable solar panel.
- 𝟑𝟔𝟎° 𝐆𝐮𝐚𝐫𝐝𝐢𝐚𝐧, 𝐍𝐨 𝐁𝐥𝐢𝐧𝐝 𝐒𝐩𝐨𝐭𝐬: Say goodbye to blind spots with full home coverage by installing the product vertically. Enjoy 360° Pan & Tilt Surveillance , check your front porch, monitor your backyard, and keep an eye on the driveway with ease.
- 𝐕𝐞𝐫𝐬𝐚𝐭𝐢𝐥𝐞 𝐈𝐧𝐬𝐭𝐚𝐥𝐥𝐚𝐭𝐢𝐨𝐧, 𝐄𝐟𝐟𝐨𝐫𝐭𝐥𝐞𝐬𝐬 𝐒𝐞𝐭𝐮𝐩: Experience the convenience of a 7-minute installation with its compact size and wire-free design.
- 𝐑𝐞𝐬𝐭 𝐚𝐬𝐬𝐮𝐫𝐞𝐝 𝐬𝐞𝐫𝐯𝐢𝐜𝐞: you can enjoy a worry-free experience, all backed by our professional customer service team.
“Does a seven-day setting mean no one can retrieve older data?”
Not necessarily. A longer contract setting, a legally required period, an approved extension, an evidence hold, or an exported copy may preserve information beyond the ordinary automatic-deletion window. The agency should explain each exception and identify where preserved records are stored.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
“If every search is logged, is misuse impossible?”
No. Logging creates an investigative record; it does not prevent an improper query. Ask whether supervisors review logs, whether abnormal searches trigger alerts, how quickly access is suspended, and what discipline or referral follows a violation.
“Are Virginia’s vendor counts national market shares?”
No. They cover 159 responding Virginia agencies, and agencies could report multiple vendors, so the counts overlap. The survey is evidence about that jurisdiction and its respondents, not the entire United States.
“Do Iowa contract prices tell me what my department will pay?”
No. The ACLU of Iowa report describes a limited public-records sample in which contract lengths, prices, and language varied. Obtain the target agency’s solicitation, contract, renewals, implementation charges, and support terms instead of treating those examples as a price list.
“Can a vendor’s default guarantee my local agency’s practice?”
No. Vendor pages describe platform capabilities or stated defaults. The local contract, policy, account assignments, sharing settings, and audit records determine how the system operates in practice.
Free tools Windows power users keep installed
One-click scans. No signup required.
Bottom line for privacy and control
Flock’s seven-day stated standard is a meaningful change from its former 30-day standard, but it is not the whole privacy story. Axon’s published defaults emphasize agency control and no sharing by default, while Burbank demonstrates that a Flock customer can impose narrower regional sharing and formal audit requirements. Motorola/Vigilant needs product- and contract-specific investigation before any ranking is credible.
The most reliable way to judge an ALPR system is to trace one record’s lifecycle: capture, search, sharing, retention, evidence hold, audit, and deletion. If a department cannot identify who may search, which agencies may receive data, how long records remain, and who reviews the logs, the vendor’s privacy language does not answer the governance question.
Frequently Asked Questions
Does Flock Safety always delete ALPR data after seven days?
No. Seven calendar days is Flock’s stated standard, but the customer agreement may set a different period, and the policy describes approved extensions of up to one year. Evidence holds, legal requirements, and exported copies can also affect what remains available.
Can police departments share Flock data with other agencies?
Sometimes. Sharing depends on the agency’s network membership, partner list, policy, and settings. Burbank says it disabled interstate and nationwide lookup and limited sharing to California law enforcement, then excluded VA Police after two May 2025 searches.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Does Axon have a universal retention period?
Axon’s published privacy page describes configurable, agency-defined retention but does not state one universal number of days. The department’s contract and configuration control the applicable period.
What remains known about Motorola/Vigilant retention?
The cited material does not establish a complete current specification. Obtain the exact product and subscription documents, contract, database arrangement, policy, retention rule, sharing settings, and audit procedures for the agency being evaluated.
Are Virginia’s vendor counts national market shares?
No. They cover 159 responding Virginia agencies, and agencies could report multiple vendors, so the counts overlap.
What should I request to verify an ALPR deployment?
Request the contract and amendments, written use policy, configured retention and deletion rules, authorized-user and agency list, sharing settings, search-log and audit procedures, evidence-hold rules, and transparency or incident records.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsDoes logging prevent an improper ALPR search?
No. Logging records the event. Effective oversight also requires routine review, abnormal-search alerts where implemented, prompt account suspension, and documented consequences for misuse.
Do Iowa contract prices predict a department’s ALPR cost?
No. The ACLU of Iowa report found different prices, contract lengths, and language among a limited sample. Local procurement records are needed for a reliable cost estimate.
The Bottom Line
Choose and evaluate ALPR systems by deployment, not brand. Verify the retention setting, evidence-hold process, authorized users, sharing partners, audit cadence, and deletion evidence in the agency’s own records. Flock’s seven-day standard and Axon’s stated agency-control model are useful starting points; neither replaces the contract and local policy.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
