Maple Grove Police Department
2 audits on file. Next audit expected 2026, on the two-year cycle in Minn. Stat. § 13.824, subd. 6.
Auditor
Auditor type
Government consortium
Result
Compliant - no findings
Findings
None recorded
Audit depth
Substantive
Tested live system
Not stated
Retention found
60 days
Report pages
5
Conducted
May 24, 2024
What the audit said
No exceptions found across all seven itemized statute controls. Identical control-by-control testing table format to the Coon Rapids and St. Paul LOGIS audits: policy review, agency-provided screen prints (60-day retention confirmed), and staff interviews.
FinePrint notes
Auditor Blake Tyra, LOGIS Information Security Specialist. This is the 2024 audit cycle; a 2026 audit would be the next expected filing. Located via LRL mandated-reports search.
Auditor
Auditor type
Government consortium
Result
Compliant - no findings
Findings
None recorded
Audit depth
Substantive
Tested live system
Not stated
System / vendor
Other / Multiple
Devices / cameras
2
Retention found
60 days
Report pages
2
Conducted
April 17, 2018
What the audit said
Two-page checklist-style audit of Maple Grove PD's legacy Vigilant ALPR deployment — 2 squad-car units, no stationary cameras — finding the department "in compliance with MN Statue [sic] 13.824" across every evaluated area: policy implementation, role-based access controls, 60-day retention, data classification, authorized inter-agency sharing, public reporting without plate numbers, and BCA notification. No findings, exceptions, deficiencies, or recommendations of any kind are recorded, and the narrative contains no language admitting an unrecorded gap. Department staff "demonstrated how they created these reports" from the Vigilant administrative control panel and audit trail rather than the auditor querying the system independently — the same second-hand methodology flagged on the Crystal PD 2019 LOGIS audit — so Tested Live System is left false.
FinePrint notes
Located 2026-09-03 (weekly rotation) by checking doc numbers adjacent to the known LEADS batch 200648/200649/200650 — 200647 turned out to be a LOGIS audit of Maple Grove, not a LEADS one. Verified the PDF's own text names Maple Grove Police Department and cites Minn. Stat. 13.824 (ALPR, not BWC). Report dated 2018-04-17; no separate fieldwork date is given, so Audit Conducted Date carries the report date. Audit period is not stated in the report; the narrative notes only that the system was installed 2016-07-07 and the audit agreement was signed 2018-01-18 — period fields deliberately left empty rather than inferred. Filing Year left blank: the report was filed in LRL's 2020 mandated-reports folder (a ~2-year lag), and the select only offers 2024-2027 (same gap noted on the Moorhead 200648 row — a pre-2024 option is still worth adding). System recorded as Other / Multiple because the report names "Vigilant", which has no select option; Vigilant Solutions was acquired by Motorola Solutions in 2019. AUDITOR TRAIL — worth following: the auditor here is "Dimitrios Hilton, LOGIS Security Specialist" (printed "LOG IS"). The same Dimitrios Hilton signed the Crystal PD 2019 LOGIS audit and now signs MNSec audits as "Senior Auditor, Minnesota Security Consortium" (e.g. Orono PD 2025, doc 251707). One individual has produced clean-sheet ALPR audits under two different auditor entities across at least seven years; per-auditor stats on the site split his output between LOGIS and MNSec. Maple Grove's audit history is now 2018 (this row) and 2024 (doc 240824, LOGIS/Blake Tyra). No 2020 or 2022 filing has been located despite the biennial requirement — a staleness gap worth a targeted search or records request. Next expected filing: 2026.
Recorded findings appear in green because a finding is evidence the auditor actually examined the program. A report with nothing at all appears in red.
Every agency operating an ALPR in Minnesota must arrange an independent audit every two years under Minn. Stat. § 13.824, subd. 6.
← All agencies and auditors