Savannah Officer Shared Flock Login With ICE Husband [2026]

A Savannah, Georgia police officer who gave her Flock Safety login to her husband, an ICE agent, was fired in August 2026, and the details surfaced this week. According to records obtained by local station WJCL and reported on October 18, 2026 by The Verge, the shared account was used for 983 license plate searches involving 97 plates across six states, and most of the searched vehicles were registered to Hispanic owners.

The Savannah Police Department says it does not share Flock data with ICE. The case shows how little that promise is worth when a single password can move data outside the policy. If you drive, film in public, or publish dashcam and security video, this is a concrete example of how license plate data travels once it is collected.

This article explains what the records say, what Savannah and ICE have said, why shared credentials defeat oversight, and what you can do today. If you want the wider picture, our earlier coverage of police misuse of Flock data and the federal ruling on Flock as mass surveillance sets the context.

What Happened in the Savannah Flock and ICE Case?

Amber Harpe, a Savannah police officer, admitted to investigators that her husband used her Flock account, and she was fired in August 2026. WJCL, whose report was syndicated by CNN Newsource affiliates, obtained internal records and recorded interviews. In one recording an investigator asks, "Did you run these flocks?" and Harpe answers, "I didn't," later confirming it was her husband, identified as Tyler Harpe.

The key facts reported so far:

• Between January and July 2026, her account was used for 983 searches involving 97 license plates.
• The searches spanned six states: Florida, Georgia, New Jersey, Maryland, North Carolina and South Carolina. South Carolina accounted for 788 of them.
• Investigators found that most registered owners of the searched vehicles were Hispanic.
• Harpe was fired in August along with five other Savannah Police Department employees after an internal investigation uncovered Flock misuse. Four of them were later arrested and charged by the Georgia Bureau of Investigation. Harpe was not.
• She initially appealed her termination, then apparently withdrew the appeal. WTOC reported that she canceled her hearing.

The Verge adds a detail about the internal discipline: an interim major first recommended only an eight-hour suspension, but two senior officers disagreed and removed her from the force.

What did the husband say he used the access for?

Tyler Harpe told WJCL that he asked his wife for her login because it would be easier to locate people while out on the street. In his words, "Every name that I ever ran was an ICE target," and he said he wanted access once "target packages for people that had arrest warrants" had been developed. WTOC's review of documents reached the same point: the couple said the searches were for ICE targets specifically.

That explanation is the couple's account, not a finding by a court. It does not change the department's conclusion that policy was violated.

Does ICE Have Access to Savannah's Flock Data?

Officially, no. A Savannah Police Department spokesperson told WTOC: "SPD does share credentials with different agencies, but ICE is not one of them." WJCL's records show Savannah shares Flock data with more than 1,700 agencies, and ICE is not on the list. The city's own statement was blunt: "An outside law enforcement agency's investigative purpose does not, by itself, authorize access to SPD's system."

The interview recordings include a telling exchange. When the investigator remarked that ICE does not have access to Flock, Amber Harpe responded, "No one really wants to work with them, sir." The records confirm ICE had no Flock access of its own; the reporting does not establish why.

WTOC also reports that ICE confirmed it is investigating the matter because of its agent's involvement. Neither the outcome of that review nor any action against the husband has been reported at the time of writing.

Why Does Credential Sharing Break ALPR Oversight?

Automated license plate reader systems rely on named accounts, so a shared password makes every safeguard unreliable. Flock's audit trail records which account ran a search, when, and the reason typed in. That log is how most misuse is discovered. If the account belongs to an officer but the person typing is someone else, the log points at the wrong human, the stated reason is unverifiable, and the data leaves the control of the city that collected it.

Three structural problems show up in this case:

1. Sharing agreements are only as strong as passwords. A city can decline to share data with a federal agency and still have it queried through a family member's login.
2. Out-of-state searches are a red flag. Searches across six states between January and July look far outside what a local officer's casework would explain, and the reporting does not say that anything flagged them before the internal investigation.
3. Discovery depended on an internal investigation. The names of fired employees only became public through civil hearings and records requests.

None of this is unique to Savannah. We covered earlier cases where officers used the system to track people they knew in our report on Flock data misuse and stalking. What is new here is the federal-immigration dimension and the explicit question of who is allowed behind the login.

How is this different from official data sharing with federal agencies?

Official sharing happens through documented agreements and, in some places, through state laws that restrict out-of-state or immigration-related queries. Credential sharing is the opposite: it is invisible in any agreement list. Cities that cancel contracts or adopt non-cooperation rules, as in our coverage of Flock city council cancellations and non-cooperation policies, still have to defend against this gap.

What Is Savannah Doing About Flock Transparency?

The department has promised a public transparency portal. In its WTOC statement, a spokesperson said the list of agencies holding credentials "will be available to the public when we launch" the portal. WTOC notes it had previously been planned to open by the end of September, so it was behind schedule when the statement was made.

A transparency portal helps only if it lists every agency and every account type, shows search counts and reasons, and is updated routinely. Residents who want to test it can compare the portal against what a public records request returns.

Is Warrantless Plate Tracking Legal?

The law is unsettled, and courts are only now taking it up. In our summary of the federal judge's Flock ruling, the central question is whether a network that records every passing vehicle becomes a Fourth Amendment search once the data is retained and searchable. Related cases in California and Kansas ask similar questions about retention and warrantless lookups.

The Savannah story adds a different legal angle that does not depend on the constitutional debate. Even if a search by an authorized officer is lawful, a search by an unauthorized person using someone else's credentials violates the department's own rules, and in some states may raise computer-misuse or official-misconduct issues. The Georgia Bureau of Investigation's decisions to charge four employees but not Harpe illustrate how unevenly those rules get enforced. Whether any charge could apply to the husband has not been reported.

What Are People Searching for After This News?

The questions readers type after a story like this are consistent, and they are worth answering plainly:

• Can an ICE agent use local Flock data? Only if the local agency shares it. In Savannah the department says it does not, and that is why the login sharing was treated as a violation.
• Can I find out whether my plate was searched? Often through a public records request for audit logs, subject to state law and redactions.
• Do Flock cameras only capture plates? They capture vehicle images and attributes, and the plate reads are what make the data searchable by number. See our explainer on what Flock cameras are and the risks they carry.
• Is there a way to opt out? Not individually. Our guide to Flock Safety cameras and your license plate privacy rights lists the realistic options: records requests, local advocacy and state law.

Where Does BGBlur Fit In?

BGBlur cannot stop a camera mounted on a pole from reading your plate, and it does not touch police databases. What it does is help with the part you control: the video and photos you publish yourself. Dashcam clips, driveway camera footage, real estate walkthroughs and street vlogs routinely show readable plates and faces. Once posted, they can be scraped, matched and indexed by anyone.

BGBlur runs in your browser. You upload the clip, the AI finds license plates and faces, motion-tracks them through the video, and exports a version with them blurred. The free plan covers short clips with a 720p export and a monthly limit, and paid plans lift those limits. Our license plate redaction guide explains why a weak blur is not enough and what to check before exporting.

A caveat worth stating: blurring protects the people in your footage from the people who watch it. It does not remove them from Flock's own records, and it does not change what police or federal agents can query. Treat it as one layer in a privacy routine, not a shield against surveillance infrastructure.

What Should You Do About License Plate Reader Privacy Today?

Take small, concrete steps rather than waiting for a ruling. If you live in a city with Flock cameras, or you post video that shows other people's vehicles, this list is a practical starting point.

1. Find out whether your city uses Flock and who has access. Search your city's website or council agenda for the contract, and look for a transparency portal listing agencies with credentials.
2. File a public records request for your own plate. Ask for the audit log of searches involving your plate number for a defined period, including the user, agency and stated reason.
3. Ask your council about account controls. Individual named logins, multi-factor authentication, mandatory case numbers and alerts on out-of-state queries are the controls that would have flagged this pattern.
4. Read the data-sharing list. Count the agencies with access. Savannah's is more than 1,700 on WJCL's records.
5. Blur plates and faces before you post. Use BGBlur's license plate blur for dashcam and security clips, then watch the export before you publish.
6. Check your own camera's settings. If you run a home or business camera, limit who can log in and who can download footage, and delete what you do not need.
7. Follow local reporting. WJCL and WTOC have been tracking the Savannah Flock cases; the ICE review and the transparency portal are the next developments to watch.

What Comes Next for Flock and Federal Access?

Expect more attention on who holds a login, not just which agencies sign agreements. The Savannah case combines three things that draw regulators and councils: a federal immigration agent, a private surveillance vendor and an audit trail that only worked after the fact. Cities that have cancelled or paused contracts, such as those in our report on a cancelled Flock contract and plate data, will cite cases like this one.

Several open items are worth tracking: the result of ICE's review, whether the Georgia Bureau of Investigation or state lawmakers take further action, whether Savannah's portal launches with a complete agency list, and whether other departments audit their own logs for out-of-area searches. If you see any of these confirmed, we will update this post.

Conclusion

The Savannah story is small in scale and large in implication. One officer's login produced 983 searches on 97 plates across six states, and the city only learned the data had reached an ICE agent because an internal investigation caught it. The department's position that ICE is not a sharing partner is credible on paper and beside the point in practice, because the access never went through an agreement.

For ordinary drivers and creators, the lesson is twofold. First, push for the unglamorous safeguards that make misuse visible: named accounts, audits, transparency portals and short retention. Second, control what you can. The video you publish is yours to protect, and a plate or face that is blurred before upload is one fewer thing for anyone to search, match or scrape later.

If you post driving, street or security footage, try BGBlur to blur plates and faces in your browser, check the result frame by frame, and publish with fewer risks to the people who happened to be in your shot.

Related: EFF's case for requiring a judge's warrant before any ALPR search is covered in ALPR warrant requirement: why EFF says police need a judge.

Update — October 23, 2026: A different kind of Flock misuse reached court today: a Georgetown, Indiana officer was arrested for allegedly running hundreds of personal searches on his wife and an acquaintance. See Indiana officer arrested for Flock searches of his wife.

Sources: The Verge, WJCL via WLOX, WTOC.