UNC-Chapel Hill students can read the UNC System’s new license-plate-camera requirements and compare them with the university’s descriptions of its system. They can also see new reporting by The News & Observer, republished by AOL, that says searches by agencies in a national network included UNC cameras. The reported counts concern query inclusion, not campus hits, image disclosures or proof of compliance.
Students cannot establish current implementation or compliance from public statements and reported search counts alone. The UNC System regulation adopted Oct. 27 takes effect Dec. 1, while campuses already operating covered systems have until Jan. 1, 2027, to bring their directives, contracts, configurations and practices into line. UNC’s public FAQ says the university is reviewing the regulation. The lack of public audit findings, deletion-test results or implementation records in the material reviewed is not proof that UNC lacks internal records or has missed a future deadline.
A network search is not a campus hit
The N&O reported that more than 206,400 searches by 2,450 agencies in 40 states included UNC cameras between late August and late September. These are not counts of unique vehicles, people or campus hits. According to UNC’s explanation in that report, an outside agency can learn whether a plate was captured; obtaining an image or vehicle details requires a request. The published audit version does not reveal how many searches produced campus hits. We have not independently reanalyzed the underlying audit.
UNC told the N&O it would not regularly audit national-network inclusion. Its FAQ says it conducts regular system-use audits. Those are different checks. Campus-user audits cannot, by themselves, answer questions about outside-network activity. UNC should explain exactly what each review covers.
UNC offers a serious safety rationale. Its FAQ says police use the system in criminal investigations and emergencies involving missing or endangered people. Those purposes can be consequential, especially when time matters. But a stated safety purpose is not evidence that a particular use was necessary, effective or properly limited. Students should not have to choose between accepting broad reassurance and demanding release of plate records, investigative details or system weaknesses.
What the System rules will require
The new regulation creates a meaningful floor once its requirements apply. It requires trained, authorized access; security controls including multifactor authentication; audit logs for searches, alerts and disclosures; and institutional responsibility when vendors host or operate data. It prohibits broad speculative searches, traffic-violation enforcement, and monitoring based solely on protected characteristics or lawful expressive activity. The regulation also requires routine data to be deleted within 30 days unless a qualifying preservation request, warrant, court order or other lawful authority is logged before the deadline.
The regulation requires periodic verification of automated deletion and documented campus audits at least twice a year, with results submitted to the campus police chief. UNC’s FAQ says police conduct regular audits and retain Flock data for 30 days. Those are important institutional statements, but the FAQ does not publish audit frequency, findings, deletion-test methods or results. The regulation requires internal oversight; it does not itself require UNC to publish the evidence that would let students assess whether the oversight worked.
Public proof needs a clear path
There is a real privacy and security boundary here. Raw plate data can expose people’s movements. Camera locations, investigative records and technical configurations can create safety or security problems if released carelessly. Section X.B of the adopted regulation permits only a generalized public overview and restricts disclosure of specific retention periods, privacy vulnerabilities, camera locations and technical configurations except where law requires it.
That language creates an accountability problem because the same regulation makes internal auditing and deletion verification central safeguards. UNC should not try to publish around the adopted restriction. Instead, the UNC System should first clarify or amend Section X.B, after legal, privacy and security review, to expressly allow useful nonoperational assurance about compliance.
Once that path is clear, UNC could publish a limited public assurance that protects individual records and investigations while answering more than “trust us.” It could include:
- a dated attestation that directives, contracts, configurations and practices were reviewed against the regulation;
- a plain-language account of the period and method used to test deletion, access controls and audit processes;
- a confirmation that vendor terms were checked for required limits on secondary use, data handling and subcontractor access; and
- deidentified aggregate reporting on preservation exceptions, substantiated misuse and corrective actions, with sensitive small counts withheld when needed.
Those are recommendations, not disclosure duties the regulation already imposes. They would not prove that every search was proper, and they should not expose plate histories, trips or investigations. But they would let UNC show that it tested the safeguards it describes. Before the Jan. 1, 2027, alignment deadline, the System’s next useful action is to say what lawful public assurance Section X.B permits, and if necessary revise that section so students can evaluate more than promises.
