Schools using license plate readers for residency checks should treat the practice as a high-impact data decision, not a routine enrollment shortcut. A 2026 Electronic Frontier Foundation analysis found that some police and school-linked users searched broad automated license plate reader networks to investigate whether families lived inside district boundaries. The findings raise practical questions about purpose, proportionality, accuracy, human review, and how families can challenge a conclusion.
Key Takeaways
- EFF reported hundreds of residency-related ALPR searches connected to one Georgia school system and dozens connected to five Ohio schools.
- A database search can reveal far more vehicle-location history than a school needs to answer a residency question.
- Flock Safety says its platform uses role-based access, search logging, and preset retention; districts still need local rules governing when and why searches occur.
- Residency investigations are materially different from a limited school pickup workflow that recognizes an arriving authorized vehicle for dismissal.
- Schools should define notice, suspicion thresholds, alternative evidence, human review, appeals, access controls, sharing, and deletion before using ALPR information in an enrollment decision.
What This Workflow Involves
A residency investigation attempts to determine whether a student lives within the geographic boundary required for enrollment. Traditionally, districts review documents such as a lease, mortgage statement, utility bill, government identification, or other evidence allowed by district policy and state law. Some districts also investigate suspected false statements.
ALPR changes the scale of that investigation. Instead of reviewing only information submitted by the family, an authorized user may search stored observations showing when and where a vehicle appeared. If the search reaches many camera networks, it can expose trips that have nothing to do with enrollment. A vehicle may also be shared, loaned to a relative, used by more than one household member, or registered somewhere other than the student’s primary residence.
The operational issue is therefore not simply whether a plate was seen outside the district. The school must decide what the observation proves, what competing evidence will be considered, who reviews the result, and how a parent can correct an error before a student loses access to school.
Why This Problem Is Showing Up Now
Networked ALPR systems have made vehicle observations easier to search across jurisdictions. In May 2026, the Electronic Frontier Foundation published an analysis of millions of Flock Safety search records and identified searches labeled for school residency verification, employment checks, and minor complaints.
The EFF report followed a March 2026 NBC Chicago investigation into an Illinois enrollment dispute. In that case, a parent said she supplied multiple conventional residency documents but the district cited license plate information showing her vehicle at Chicago addresses. The parent said the vehicle had been loaned to a relative. The dispute illustrates why vehicle location is evidence to evaluate, not an automatic answer about where a child lives.
The Core Operational Problem
The central problem is evidence mismatch. A plate observation establishes that a vehicle was seen at a place and time. It does not necessarily establish who was driving, who had possession of the vehicle, or where a student sleeps most nights. Treating the plate result as conclusive can convert a probabilistic signal into a high-impact enrollment decision.
Scope is equally important. A district may need to review a narrow concern, while a broad ALPR query can return movement records from thousands of networks. That creates a purpose-limitation problem: the school may receive much more information than it needs and expose families to scrutiny unrelated to education.
What the Report Found About Schools Using License Plate Readers for Residency Checks
EFF reported that Buford City Schools in Georgia ran more than 375 searches labeled for school residency verification between January 2025 and March 2026. Those searches represented more than half of the system’s ALPR searches during that period; during the first three months of 2026, EFF said roughly three-quarters were residency related.
According to the report, some Buford searches reached more than 5,800 camera networks. The district told EFF that residency fraud is an ongoing challenge and that Flock Safety is one tool used to protect the integrity of the school system for residents.
EFF also identified 35 searches associated with students at five schools by the Delhi Township Police Department in Ohio during a three-month period in spring 2025. The department said the searches were used in cases where officials suspected a residency form contained false information, rather than as an automatic check of every submission. Following EFF’s inquiry, the department said it would change how those queries were documented to improve accountability.
What Flock Safety Says About Its Safeguards
Flock Safety’s public data privacy materials say ALPR access is limited to approved users with role-based permissions, searches are recorded and reviewable, and data is automatically deleted after a preset period—often 30 days unless law or local policy requires otherwise. The company says its ALPR captures plate images, vehicle characteristics, timestamps, and camera-location identifiers rather than facial-recognition data.
Those controls matter, but they do not decide the school district’s policy. A technically authorized search can still be too broad for the stated educational purpose. Audit logs are most useful when a district has written rules defining permitted reasons, required suspicion, search scope, supervisory approval, and consequences for misuse.
Residency Surveillance Is Not the Same as School Pickup Automation
| Question | Residency investigation | Limited dismissal workflow |
|---|---|---|
| Primary purpose | Investigate whether a family lives inside a district boundary | Recognize an arriving authorized vehicle during pickup |
| Search scope | May query stored observations across many locations or networks | Should be limited to the school’s configured pickup lane and authorization list |
| Decision affected | Enrollment eligibility and possible fraud review | Staging and staff-controlled release of a student |
| Human review | Needed to weigh documents, explanations, and contradictory evidence | Needed before release and whenever a plate or authorization is uncertain |
| Family alternative | Conventional residency documents and an appeal process | QR, manual, or other school-approved verification route |
PLACA’s school pickup privacy approach is positioned around parent choice, staff approval, role-based access, and alternatives such as QR verification. Districts should verify those controls in their own configuration and contract rather than assuming every LPR product or use case operates the same way.
Questions School Boards Should Ask Before Approving Residency Searches
- What starts an investigation? Require documented facts or a defined discrepancy rather than an open-ended search.
- How narrow is the query? Limit dates, locations, networks, and vehicle identifiers to what the concern actually requires.
- Who approves and reviews it? Separate the person requesting the search from the person making the enrollment decision when practical.
- What other evidence is accepted? Give families a fair opportunity to provide documents and explain shared, borrowed, fleet, rental, or recently purchased vehicles.
- How can a family appeal? Provide written notice, the basis of the decision, a correction path, and a review deadline.
- Who can access or share results? Document roles, outside access, exports, disclosures, and audit review.
- When is information deleted? Set a retention rule for query results, screenshots, notes, and any record attached to an enrollment file.
- Has counsel reviewed the policy? Residency rules, student privacy requirements, public-record obligations, and ALPR laws vary by jurisdiction.
FERPA and Student-Linked Vehicle Data
The U.S. Department of Education defines an education record as information directly related to a student and maintained by a school or a party acting for the school. Its official FERPA guidance also recognizes context-specific exclusions, including certain law-enforcement-unit records.
A plate observation by itself is not automatically a student education record in every setting. When a district links vehicle information, investigation notes, or pickup events to an identifiable student and maintains that information, however, the school should have its privacy officer and counsel evaluate how FERPA and state student-data laws apply. PLACA’s FERPA and school LPR planning guide provides a starting checklist, but it is not a substitute for legal advice.
Risks, Limits, and Fairness
Residency fraud can impose real financial and administrative costs on districts, and officials may have a legitimate duty to investigate credible concerns. The privacy issue is not solved by ignoring that responsibility. It is addressed by using evidence proportionately, documenting the reason for access, considering less intrusive sources first, and preserving meaningful human review.
This article does not determine whether any named district or agency acted lawfully, and it is not legal advice. The EFF report presents a civil-liberties analysis; Flock Safety presents a different view of its safeguards. District leaders should review original records, applicable law, signed contracts, system configuration, and counsel advice before adopting or changing policy.
Frequently Asked Questions
Can a license plate location prove where a student lives?
Not by itself. It shows where a vehicle was observed, not necessarily who was driving or where a student resides. Districts should evaluate it alongside permitted documents and the family’s explanation.
Are all school license plate reader uses the same?
No. A broad historical search for residency is different from recognizing a registered vehicle as it arrives in a defined pickup lane. Purpose, scope, sharing, retention, and the decision being made all matter.
Should districts prohibit every ALPR search?
That is a policy and legal decision for each jurisdiction. At minimum, districts should define suspicion thresholds, narrow the query, require approval, review audit logs, accept alternative evidence, and provide an appeal process.
What should parents ask their school?
Ask what data is collected, why it is used, which networks are searched, who can access results, how long records remain, whether outside parties receive them, and how a family can inspect or challenge information used in an enrollment decision.
How should a district evaluate LPR for dismissal?
Begin with purpose limitation. Review the plain-language guide to LPR for schools, then require staff-controlled release, restricted access, short documented retention, parent communication, alternative verification, and a written data-processing agreement.
Next Step
Before approving any school LPR workflow, write a one-page use statement covering purpose, camera and search scope, authorized roles, sharing, retention, human review, family alternatives, and appeals. If the vendor cannot configure the system to match that statement, the district has identified a governance gap before it becomes a family dispute.