How the Triangle Can Check Surveillance Safeguards

UNC-Chapel Hill’s plate-camera rules and Durham’s drone policy show what residents can verify from public documents. Each program needs different records to show how safeguards work in practice.

Editorial illustration of a license-plate camera and a drone above its docking station.
Editorial illustration of a license-plate camera and a drone above its docking station.

Safeguards need records residents can use

Two different local surveillance systems point to the same practical test: a safeguard matters most when residents can see enough evidence to tell whether it is being followed.

At UNC-Chapel Hill, the new UNC System rules for license-plate cameras set a detailed floor for covered systems, including trained access, audit logs, limits on speculative searches and routine deletion within 30 days unless a qualifying exception is recorded. The regulation takes effect December 1, with campuses already using covered systems given until January 1, 2027, to align their directives, contracts, configurations and practices. Those requirements create a path for internal oversight. They do not, by themselves, give students or employees a useful public account of whether deletion tests, access reviews and vendor checks occurred.

That distinction matters. UNC-Chapel Hill’s campus FAQ says the university is reviewing the regulation and describes its cameras as tools for criminal investigations and emergencies. Audit results would answer a different question: whether controls worked in practice. The UNC System regulation also limits disclosure of operational details that could expose privacy vulnerabilities, camera locations or technical configurations. That is a real boundary. But the System can still clarify what nonoperational assurance campuses may publish: whether required reviews occurred, what period they covered, whether retention controls were tested, and whether identified problems were corrected.

Durham faces a different timeline and a similar need for usable records. The city has adopted surveillance safeguards and Durham Police has a published General Order 3008 governing drone operations. The order directs pilots to document flights and denials, sets rules for warrants in certain circumstances, and establishes retention rules for collected media. The June City Council record also reflects the council’s 7–0 vote on a surveillance resolution.

As our Durham 911 drone report found, the public record reviewed did not establish the dock-specific dispatch rules, final program procedures or executed contract terms for a future 911 drone program. Before launch, Durham could make those safeguards easier to check by publishing summaries of eligible-call rules, access and export controls, retention categories, and reviews of access logs.

Residents do not need raw plate histories or incident video to assess oversight. They need clear, limited evidence that institutions tested the controls they say will protect people.

Next week in the Triangle

Who should we know?

Send us introductions, corrections and tips.

Respond to this post

See something missing, disputed, or worth following? Send a private response to the editor. Nothing will appear publicly without permission.

Permissions

Your email remains private. CAPTCHA verification is required before WordPress accepts the response.