Wednesday, 14 October 2026

Georgia man sues over suspected retaliatory ALPR searches by sheriff’s office

A Georgia entrepreneur claims a sheriff’s department used license plate data as retaliation, with searches tied to vague, nonspecific reasons.

Generic data center-inspired workspace with monitors and filing shelves

The short version

  • A Georgia small-business owner files a lawsuit against Flock and the Coweta County Sheriff’s Office alleging ALPR searches were used as retaliation.
  • The plaintiff says officers ran license plate checks with free-text entries that bore little relation to any real investigation, including entries like “investigation” and “hehehe.”
  • The complaint argues the ALPR platform allowed nondestructive queries without a verifiable case number or investigation code, raising privacy and civil-liberty concerns.
  • The case underscores ongoing debates about how police use automated plate readers and who should oversee data access and safeguards.
Quick read · 1 min

A Georgia entrepreneur is suing the local sheriff’s office and the ALPR provider over uses of license plate data that the plaintiff calls retaliatory. The core issue is that searches were performed with vague prompts not tied to any specific case.

The lawsuit highlights privacy concerns around ALPR systems and calls for stronger safeguards to prevent abuse. The outcome could lead to tighter controls on who can query plate data and how long it’s kept.

  • ALPRs are common in many communities for safety and investigations.
  • Privacy concerns grow with more permissive data access rules.
  • The case could push for audits and stronger oversight of ALPR use.

A Georgia entrepreneur has filed a lawsuit accusing a local sheriff’s office and the license plate reader provider behind the system of using ALPR data as retaliation. The dispute centers on how plate data was searched and the lack of clear, investigation-based justification for those queries, bringing renewed focus to privacy and accountability in local policing tech.

The plaintiff, Tyler Murkerson, alleges that deputies repeatedly searched his vehicle within the Flock system over an extended period, but the reasons given did not tie to any identifiable investigation. The court document describes searches conducted with free-form text instead of standard case numbers or investigation codes. Examples cited include terms like “investigation” and, in numerous instances, the word “hehehe.” The complaint argues these entries show no legitimate inquiry and suggest the searches were unrelated to any real case.

According to the lawsuit, Flock’s platform allowed such free-text entries and did not mandate a verifiable justification before performing a search. The filing notes that Flock has since acknowledged, per the complaint, that stronger safeguards were warranted to prevent unfounded surveillance.

Beyond the data platform, the suit contends that Murkerson was followed or monitored during trips to and from his home, a detail the plaintiffs say signals that the ALPR data was being used beyond routine safety or investigative needs. The overall narrative ties a prior legal dispute with the department to a broader pattern of alleged misuse of the technology.

Neither Flock nor the sheriff’s office have issued detailed public comments about the case. In general, both vendors and police departments emphasize privacy protections and oversight, but the specifics of this lawsuit will determine how those assurances hold up in court.

What this means for everyday readers is straightforward: license plate readers are common in many communities, used for traffic safety, investigations, and locating vehicles of interest. The core concerns are who can access the data, how long it’s stored, what qualifies as a legitimate query, and what safeguards are in place to prevent misuse. This lawsuit spotlights what can happen when data access rules are too loose and when there’s a perception of retaliation instead of neutral policing.

As the case unfolds, the central questions will be about accountability and the level of control that should accompany ALPR systems. The outcome could influence how departments implement access rules, how vendors design their software, and how communities oversee the use of license-plate data in the future.

01

Privacy and policing in the crosshairs

If the court finds merit to claims that searches were conducted without proper justification or that the system allowed vague queries, it could push for tighter controls on ALPR access, stronger logging requirements, and clearer rules around data storage and usage in civil matters. Communities might even see calls for independent audits of how plate data is handled.

A person speaking with a police officer during a roadside stop (generic scene)
02

The bigger picture

While this case centers on a Georgia department, the questions it raises, data access, verification, and oversight, are relevant to many communities that rely on ALPRs for public safety. The outcome could reverberate beyond this single dispute and shape policy around government data use.

03

What happens next

The defendants will answer in court, and a judge will decide whether remedies or policy changes are warranted. For readers, the key takeaway is to consider how your own license-plate data is accessed and what safeguards protect your privacy when such tools are in use.

04

Quick answers

What is ALPR?

ALPR stands for automated license plate reader. In this case, the concern is about how data from those scans is queried and used.

What could change for Georgia drivers?

Should the case succeed, expect tighter querying rules, clearer justification requirements, and more transparency around data storage and access.

You're reading the quick version.