A former Savannah Police Department officer lost her job in August 2026 after investigators confirmed she had handed her department-issued Flock Safety login to her husband, a federal U.S. Immigration and Customs Enforcement agent who had no license-plate-reader access of his own. The case, first detailed by The Verge, has reignited a fight that has simmered across the country for two years: who actually controls the flood of license-plate data that Flock Safety’s automated cameras collect, and what happens when the answer is “nobody is really checking.”
The officer, Amber Harpe, was terminated after an internal audit found 983 entries attributed to her account between January and July 2026, spanning six states and touching 97 license plates, according to WCAX. Her husband, Tyler Harpe, is identified in investigative records as an ICE agent who did not hold an independent Flock Safety account through the Department of Homeland Security. The story lands squarely in a software-and-data-governance problem that extends well beyond one Georgia police department: credential-sharing, access logging, and the gap between what a vendor’s platform can technically audit and what an agency actually enforces.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Happened in Savannah
According to the reporting, Tyler Harpe asked his wife for access to her Flock Safety credentials so he could run license plates tied to ICE “target packages,” cases where arrest warrants had already been developed. Amber Harpe gave him her username and password rather than requesting that ICE obtain its own authorized account. Over the following months, searches run through her login racked up 983 entries across six states, a volume that eventually drew the attention of Savannah Police Department’s internal affairs process.
Both Harpes told investigators the searches were tied to ICE enforcement targets and framed the access as serving a legitimate law-enforcement purpose. That framing did not satisfy the department. Savannah Police Department determined that sharing login credentials violated its internal policy regardless of the stated purpose behind the searches, and it terminated Harpe’s employment in August. The Georgia Bureau of Investigation reviewed the matter and did not file criminal charges against her, according to Gizmodo, leaving the consequence confined to a policy violation and a firing rather than a prosecution.
ICE has said it is reviewing the matter internally because of its agent’s direct involvement, though no outcome of that review has been made public. Savannah Police Department has been explicit that it does not have a data-sharing arrangement with ICE and that an outside agency’s investigative interest does not, on its own, authorize access to the department’s surveillance systems.
The Flock Safety Platform: What It Tracks and Who Can See It
Flock Safety sells automated license-plate-reader (ALPR) camera networks to thousands of local police departments, homeowners associations, and private businesses across the United States. Cameras log every plate that passes, timestamp and geolocate the read, and feed that data into a searchable database that participating agencies can query. The pitch to departments is straightforward: faster location of stolen vehicles, Amber Alert subjects, and warrant targets, without the manual legwork of pulling traffic-camera footage.
The system’s value, though, depends entirely on access controls that sit on top of a shared database spanning agencies with very different missions. A query run through a city police department’s account can surface a vehicle’s movement history across neighboring jurisdictions and states, since many agencies opt into regional data-sharing networks. That design is what made Amber Harpe’s single login so consequential: her Savannah Police Department credentials did not just unlock Savannah’s own data, they exposed whatever regional and cross-state feeds her account was entitled to search, now effectively in the hands of a federal agent operating outside any audited channel.
Flock Safety’s own audit logs reportedly made this case discoverable in the first place, which is the detail vendors point to when defending the platform. The logs recorded who searched what, when, and attributed every one of the 983 queries to Harpe’s account; they could not, however, tell investigators that the person physically typing in plate numbers was not her. That distinction, a system that logs access accurately but cannot verify the identity of the human at the keyboard, is the structural weakness regulators and departments are now being forced to confront.
By the Numbers: The Audit Trail
| Metric | Figure | Source |
|---|---|---|
| Total flagged searches on Harpe’s account | 983 entries | WCAX |
| Time window covered by the audit | January–July 2026 | WCAX |
| States touched by the searches | 6 states | WCAX |
| Distinct license plates searched | 97 plates | Gizmodo |
| Criminal charges filed against Amber Harpe | 0 | Gizmodo |
| Independent DHS/ICE Flock Safety account held by Tyler Harpe | None confirmed | The Verge |
Why This Isn’t an Isolated Incident
The Savannah case fits a pattern that has followed Flock Safety and comparable ALPR vendors since local agencies began adopting the cameras at scale in the early 2020s. Audits in multiple states have previously found police departments running searches on behalf of out-of-state agencies pursuing cases that would be illegal under their own state’s law, most notably around abortion-related travel and immigration enforcement, long before this specific credential-sharing episode. The common thread is not a single bad actor, it’s a platform built for data sharing between agencies that assumed good-faith use would substitute for technical restriction.
Savannah Police Department’s own statement acknowledges this gap directly. The department said unauthorized access to police technology by anyone is a breach of its policy and of public trust, and that an outside law-enforcement agency’s investigative purpose does not, by itself, authorize access to the department’s system. That is a policy statement, not a technical control. Nothing in the Flock Safety platform itself stopped Tyler Harpe from using his wife’s credentials; the system only recorded that it happened and later let auditors reconstruct the trail.
The broader implication for any department running shared surveillance infrastructure is that logging is not the same as enforcement. A platform can produce a perfect record of 983 searches and still fail to prevent a single one of them if there’s no multi-factor authentication, no device-binding, and no real-time anomaly detection flagging a sudden spike in queries tied to immigration-enforcement targets rather than the department’s own caseload.
Expert and Official Reaction
Tyler Harpe described his reasoning to investigators in blunt terms, explaining that he asked his wife for her Flock login because his team had already built target packages on people with active arrest warrants and wanted an easier way to locate them while out in the field, a point reported by WCAX. When an investigator reportedly expressed surprise that ICE lacked its own Flock Safety access, Amber Harpe’s response, recounted by Gizmodo, was that “no one really wants to work with them, sir.”
In her own appeal of the termination, Harpe framed the violation narrowly: she said the violation occurred because she gave her husband, a certified law-enforcement officer with the Department of Homeland Security, access to her Flock account, a characterization also reported by Gizmodo. Savannah Police Department’s position, meanwhile, has been that the nature of the requesting agency does not change the underlying policy violation. The department said unauthorized access to police technology by anyone is a breach of its policy and of public trust, and that an outside agency’s investigative purpose does not, by itself, authorize access to its system, according to a statement cited by WJCL.
Market Impact: Flock Safety’s Growing Scrutiny Problem
Flock Safety has built a multibillion-dollar valuation on the premise that ALPR networks are a low-friction public-safety tool that departments can deploy quickly. Every incident like Savannah’s adds friction to that pitch. City councils in several jurisdictions have already paused or scrutinized Flock Safety contracts over data-sharing concerns, and a story involving a literal credential handoff to an ICE agent, playing out in a city that explicitly says it does not share data with ICE, is the kind of headline that accelerates those council-level reviews.
For Flock Safety and rival vendors chasing the same municipal contracts, the commercial risk isn’t that the technology fails, it’s that procurement officers start demanding contractual guarantees around access control, mandatory multi-factor authentication, and automatic flagging of unusual query patterns before signing renewal contracts. Vendors that can point to hardened access controls, rather than just detailed audit logs after the fact, have a real competitive opening here.
Competitive Landscape: How ALPR Platforms Compare on Access Control
| Capability | Typical municipal ALPR deployment (Flock Safety-style) | Hardened enterprise security baseline |
|---|---|---|
| Authentication | Single username/password per officer account | Mandatory multi-factor authentication |
| Credential sharing detection | Not systematically flagged in real time | Device-binding and anomaly alerts on login |
| Cross-agency query visibility | Regional data-sharing opt-ins, broad default visibility | Scoped, purpose-limited query permissions |
| Audit trail | Logs searches after the fact, as seen in this case | Real-time query review plus after-the-fact logging |
| Policy enforcement | Relies on department-level discipline, not platform controls | Technical controls back up written policy |
Historical Context: A Pattern Vendors Keep Downplaying
License-plate-reader controversies are not new. Reporting over the past several years has repeatedly surfaced cases of ALPR queries crossing state and jurisdictional lines for purposes the originating department never authorized, from immigration enforcement to abortion-related investigations. What makes the Savannah case distinct is how mundane the breach actually was. There was no hacking, no stolen password, no exploited software vulnerability. A sworn officer simply handed her own valid credentials to her spouse, who used them exactly as a legitimate account holder would, for nearly seven months, before an internal audit caught it.
That is arguably more alarming for departments evaluating their own exposure than a sophisticated breach would be, because it shows the control failure sits at the simplest possible layer: basic password hygiene and the absence of any technical barrier to one person using another’s login. Departments that have spent money hardening firewalls and network perimeters around their surveillance systems may have overlooked the much more ordinary risk of an employee simply sharing access with a family member.
The Legal Gray Zone Around ICE Access to Local Police Data
Savannah Police Department has stated plainly that it does not share its Flock Safety data with ICE. That policy stance puts the department in the same camp as a number of cities that have adopted “sanctuary”-style restrictions on cooperating with federal immigration enforcement, even as it maintains an ALPR network that is, by design, built for broad law-enforcement data sharing. The Harpe case shows how a single shared password can route around that policy entirely, because the Flock Safety platform does not appear to have any automated mechanism distinguishing a legitimate departmental query from one made on behalf of an agency the department has specifically declined to partner with.
The Georgia Bureau of Investigation’s decision not to pursue criminal charges against Amber Harpe leaves the matter in an unusual legal space: a termination for a clear policy violation, paired with cited reporting that found no state-law violation in the conduct itself. That gap between an administrative consequence and a criminal one is likely to fuel further debate among civil-liberties groups and lawmakers who have already pushed for tighter statutory controls on ALPR data sharing in several states.
What Police Departments Are Likely to Change
Expect departments running Flock Safety and comparable systems to face new internal pressure to adopt multi-factor authentication tied to an individual officer’s device, not just a username and password that can be read off a sticky note or shared over text. Some departments may also move toward quarterly or monthly audits of query volume by account, rather than relying on a complaint or routine review to surface anomalies the way Savannah’s internal affairs process eventually did.
Vendors, for their part, are likely to face procurement-contract pressure to build real-time alerting into their platforms: a sudden spike in queries tied to out-of-state plates, or a login pattern inconsistent with an officer’s usual shift hours, are the kinds of signals that could have flagged this activity months earlier than an after-the-fact audit did.
Predictions: Where This Story Goes Next
- Expect at least a handful of other police departments running Flock Safety networks to conduct their own internal audits of account-sharing patterns in the coming months, prompted directly by the Savannah coverage.
- Civil-liberties organizations and state lawmakers are likely to cite this case specifically in pushing for statutory limits on ALPR data sharing with federal immigration authorities.
- Flock Safety and competing ALPR vendors will likely face renewed pressure from city councils to add mandatory multi-factor authentication and real-time anomaly detection as standard contract terms rather than optional add-ons.
- ICE’s internal review of Tyler Harpe is likely to conclude with an administrative outcome rather than criminal charges, mirroring the path taken by the Georgia Bureau of Investigation with Amber Harpe.
- Expect continued reporting scrutiny of regional ALPR data-sharing networks, since Harpe’s 983 flagged searches crossed six states, a reminder that a single department’s access controls can expose data far beyond its own jurisdiction.
What Comes Next for the Harpes
Amber Harpe has appealed her termination, arguing in that appeal that the violation was limited to giving her husband, as a certified Department of Homeland Security law-enforcement officer, access to her account, according to Gizmodo’s reporting. Whether that appeal succeeds is still unresolved. ICE has said it is reviewing Tyler Harpe’s conduct internally given his direct involvement, though the agency has not published a timeline or outcome for that review. Neither the Savannah Police Department nor ICE has indicated that any broader policy change is imminent beyond the individual personnel action already taken.
The Bigger Picture for Surveillance Technology Governance
The Savannah case lands at a moment when local police departments across the country are already under pressure over how aggressively surveillance tools like license-plate-reader networks get deployed and shared. It also arrives alongside a string of unrelated but thematically connected stories this year about government data systems failing to control who can see sensitive records, from a state DMV breach exposing hundreds of thousands of files to a cloud-backup breach that froze access for 173 tenants. Each incident has a different root cause, but the common denominator is the same: platforms built to move data quickly between organizations tend to outpace the access controls meant to govern who is actually allowed to query that data.
That tension is also playing out around election-season surveillance tools, where jurisdictions like Cook County’s ballot-tracking system have drawn scrutiny over who can access tracking data and why, and where federal agencies have had to respond to platform-level misuse, as seen when X purged thousands of accounts tied to foreign interference efforts ahead of the midterms. Flock Safety’s own position in this story echoes a broader pattern documented across rising cybersecurity incidents this year: the technology itself usually works as designed, but the humans and policies wrapped around it are where the actual failures happen.
Why Software Engineers Should Pay Attention
For engineers building or maintaining systems that handle sensitive government or law-enforcement data, the Savannah case is a clean, almost textbook example of why identity verification needs to be treated as a first-class design problem rather than an assumed property of a login screen. A system that logs every query accurately, as Flock Safety apparently did here, still fails if it cannot distinguish the account holder from someone using their borrowed credentials. That’s a solvable engineering problem: device-binding, behavioral biometrics, mandatory hardware security keys, and automated anomaly detection on query patterns are all established techniques. The fact that a credential handoff between a married couple went undetected for roughly seven months, surfacing only through a routine audit rather than a real-time alert, suggests those techniques were not part of Flock Safety’s default deployment for the Savannah Police Department.
It’s also a reminder that access-control failures in public-safety software carry a different weight than a typical SaaS breach. A leaked spreadsheet is bad; 983 queries against a law-enforcement database, run by someone outside the authorizing agency’s chain of command, touches due-process and civil-liberties questions that most enterprise software never has to account for. Developers working on government contracts, particularly in the public-safety and immigration-adjacent space, should expect this case to become a reference point in procurement conversations about mandatory security controls going forward.
Frequently Asked Questions
Who is Amber Harpe?
Amber Harpe is a former Savannah Police Department officer who was fired in August 2026 after an internal investigation found she shared her department-issued Flock Safety login with her husband.
Who is Tyler Harpe?
Tyler Harpe is identified in investigative records as a federal ICE agent who used his wife’s Flock Safety credentials because he did not have an independent account through the Department of Homeland Security.
What is Flock Safety?
Flock Safety is a company that provides automated license-plate-reader camera networks to police departments, homeowners associations, and businesses, with searchable databases that participating agencies can query.
How many searches were involved in this case?
An audit attributed 983 entries to Amber Harpe’s account between January and July 2026, covering 97 license plates across six states.
Was Amber Harpe criminally charged?
No. The Georgia Bureau of Investigation reviewed the case and did not file criminal charges against her, according to Gizmodo’s reporting.
Does Savannah Police Department share Flock Safety data with ICE?
No. The department has stated publicly that it does not share its Flock data with ICE and that an outside agency’s investigative purpose does not, by itself, authorize access to its system.
Is Tyler Harpe facing any consequences?
ICE has said it is investigating the matter internally because of its agent’s involvement, though no outcome has been made public.
What could prevent similar incidents in the future?
Security experts generally point to mandatory multi-factor authentication, device-binding, and real-time anomaly detection on query volume as technical controls that could catch credential-sharing before it runs for months undetected.
