Why Urbandale’s New Contract Changed What Is Data Transparency

In 2024 the Urbandale City Council amended its contract with Flock Safety, unlocking full data transparency for city-wide surveillance. The new contract reshapes what data transparency means by mandating real-time dashboards, open APIs and audited reports, giving residents direct access to video and licence-plate data.

Legal Disclaimer: This content is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for legal matters.

What Is Data Transparency?

Key Takeaways

• Real-time dashboards let citizens verify camera activity.
• Open APIs publish anonymised data weekly.
• Audited reports are posted publicly on the council site.
• Requests for footage are processed within 72 hours.
• Quarterly encryption-key rotation safeguards data.

Data transparency, in the context of municipal surveillance, means opening every layer of the information chain - from capture through storage to any subsequent sharing - so that residents can see exactly how their recorded video is handled. In my time covering the Square Mile, I have observed that when authorities publish clear process maps, citizens acquire the power to challenge unlawful monitoring, demand deletion of unauthorised footage, and verify that cameras are truly serving community safety rather than hidden commercial interests.

When the City of Urbandale introduced the new contract, it stipulated that all camera operators must publish real-time feed dashboards. This requirement enables first responders and ordinary citizens to verify system integrity at the moment an incident occurs, rather than relying on post-hoc reports that may be filtered or delayed. The move also aligns with the broader UK trend of demanding government data transparency, as highlighted by recent commentary on the Missing Data on Rotavirus Vaccine Trial, where lack of openness was criticised as eroding public trust (Transparency Tensions, Devdiscourse).

Beyond the dashboards, the contract obliges operators to disclose the data lifecycle - how long footage is retained, the encryption standards applied, and the circumstances under which third parties may receive extracts. By laying these details out on the municipal website, the council provides a verifiable audit trail that residents can reference when questioning a particular use of the footage. This approach mirrors the principles championed by the Information Commissioner’s Office, which repeatedly stresses that transparent data practices are essential for democratic accountability.

Crucially, the contract also introduces a formal appeal route for denied requests, ensuring that the transparency promise is enforceable. Residents can now track the progress of their request via a transparent progress tracker, and if a request is rejected they have a clear 14-day window to appeal, citing specific privacy statutes. This procedural clarity is a tangible step away from the opaque processes that previously characterised municipal data handling.

Flock Camera Data Transparency

The revised agreement with Flock Safety embeds three technical pillars that elevate data transparency from a policy slogan to an operational reality. First, an open Application Programming Interface (API) now releases anonymised licence-plate data on a weekly basis. The API strips personal identifiers, publishing only vehicle types, timestamps and aggregate movement patterns, and it guarantees that re-identification can only occur when a legal warrant is presented. This mirrors the data-leak warnings raised in the recent Techie Tonic report, which warned that every AI prompt could become a privacy risk unless strict anonymisation is enforced.

Second, encryption keys governing stored footage are rotated every 90 days. The rotation means that any researcher or third-party wishing to access historic footage must re-authenticate, a measure designed to thwart data-brokering by external firms. While the technical detail may appear burdensome, it aligns with the City’s commitment to protect against unauthorised infiltration, a stance echoed by the CIC’s criticism of the ICMR for insufficient trial data transparency (CIC Slams ICMR, Devdiscourse).

Third, Flock is now required to produce quarterly compliance reports audited by an independent cyber-security auditor. These reports are automatically posted on the municipal website and detail every stage of data handling - from capture, encryption, access logs, to any third-party disclosures. The reports also include a summary of any data-subject access requests received and the outcomes of those requests. By publishing these documents, the council creates a permanent, searchable record that residents can reference, thereby removing any room for hidden data channels.

To illustrate the practical impact, consider a resident who wishes to confirm whether a particular licence-plate was recorded on a busy intersection. Using the open API, they can query the anonymised dataset for the relevant date and time, see that the plate appears only as a hashed entry, and request the full footage through the portal. The quarterly reports will confirm whether the request was fulfilled in line with the warrant requirements, providing an audit trail that is both transparent and legally robust.

Overall, the contract’s technical provisions set a benchmark for municipal surveillance in the UK, demonstrating how data transparency can be embedded directly into vendor agreements rather than left as an after-thought.

Urbandale Surveillance Footage Request

Residents seeking footage now follow a streamlined, three-step process that the council designed to eliminate the vague “time-frame” clauses that previously caused delays. First, the user must identify the precise incident date, time and location - the portal provides an interactive map that lets you pinpoint the exact camera view. Second, the online request form requires you to reference the specific footage by entering the camera ID, timestamp and a brief description of the incident. This specificity replaces the old practice of submitting a blanket request covering “all footage from a given day,” which often led to discretionary refusals.

Once submitted, the request enters an automated workflow that updates the applicant at each milestone - acknowledgement of receipt, commencement of retrieval, and final delivery. The system guarantees a maximum processing time of 72 hours, a significant improvement on the prior average of two weeks. If the request is denied, the applicant receives a detailed rationale referencing the relevant data-protection statutes, and the decision can be appealed within 14 days. The appeal must cite the specific clause of the new council ordinance that the denial allegedly contravenes, ensuring a transparent and accountable review.

From my experience liaising with the council’s data-rights team, the new portal’s progress tracker has reduced the number of follow-up emails dramatically. In one recent case, a local business owner needed footage of a traffic incident that occurred on 12 March 2024; the request was logged at 09:15, the retrieval started at 10:30, and the video was delivered at 14:45 the same day, with the system sending automatic status updates at each stage.

The legislation also empowers residents to request the audit log associated with any third-party application that accesses camera feeds. This right to an audit transcript, which must be provided within 30 days, is a safeguard against covert data sharing and reflects the whistleblower protections embedded in the new ordinance.

How to Access Local Government Video

Access begins at the CityHub portal, the council’s unified digital gateway for all civic services. After logging in with your municipal user credentials - which are issued to any resident who registers a council tax account - you navigate to the ‘Video Archive’ tab. The archive is organised by neighbourhood, camera type and compliance flag, allowing you to filter footage by a range of metadata fields.

• Use the ‘Intersection’ filter to select the exact road crossing.
• Apply the ‘Vehicle Type’ filter to narrow down to cars, trucks or motorcycles.
• Choose an ‘Incident Tag’ such as ‘collision’, ‘theft’ or ‘public-order’ to locate relevant clips.

Once the desired footage appears, you can preview a low-resolution thumbnail before downloading the full-resolution MP4 file. Files up to 200 MB are available for direct download; larger archives trigger a secondary request through the Freedom of Information Act (FOIA) portal, ensuring that the data handling limits set out in the contract are respected. The FOIA request includes a mandatory data-impact assessment, which the council uses to verify that the extraction will not compromise ongoing investigations.

For researchers requiring bulk data, the open API mentioned earlier provides a programmematic route to retrieve anonymised licence-plate datasets. The API returns JSON objects that include timestamps, GPS coordinates and vehicle classifications, but omits any personally identifiable information. Access keys for the API are issued after a brief registration process that verifies the applicant’s affiliation and purpose.

Finally, every download is logged in a public audit trail displayed on the portal’s ‘Data Access Log’ page. This log records the requestor’s ID, the footage accessed, and the time of download, reinforcing the council’s commitment to transparency and allowing any citizen to verify that the system is not being misused.

Urbandale Data Privacy Law

The new data privacy law, enacted alongside the Flock contract, imposes stringent controls on how licence-plate images and video feeds are stored and shared. All images are kept in a locked, indexed database that employs AES-256 encryption, with encryption keys rotated quarterly - the same 90-day cycle introduced in the technical provisions of the contract. This rotation mitigates the risk of key compromise, a concern repeatedly highlighted in the CIC’s critique of opaque data-handling practices in other sectors.

Under the ordinance, any resident may submit an audit request for data exposed by a third-party application. The council must then provide a transcript of the audit log within 30 days, detailing every access event, the requesting party and the purpose declared. This right mirrors the transparency expectations set out in the European Union’s General Data Protection Regulation, albeit tailored to a municipal context.

The law also introduces robust whistleblower protections. Contractors who discover undocumented usage of camera feeds are encouraged to report these incidents without fear of retaliation; reports are routed to an independent oversight committee that can impose sanctions on any party found to be breaching the transparency requirements. This mechanism is designed to close the “hidden data channel” risk that many privacy advocates warn about in the age of pervasive digital surveillance.

Enforcement is overseen by a newly created Data Integrity Unit within the council, which conducts random inspections of the encrypted database and reviews the quarterly compliance reports submitted by Flock. Any breach - for example, unauthorised sharing of raw footage with a private security firm - triggers a mandatory remediation plan and may result in fines up to £50,000, as stipulated by the ordinance.

In practice, the law has already prompted a cultural shift among the city’s contractors. A senior analyst at a local cyber-security firm told me, "Since the whistleblower clause was introduced, we have seen a 30 percent increase in internal reporting of data-handling anomalies, which has helped the council tighten its controls before any external breach occurs." This anecdote underscores how statutory safeguards can drive proactive compliance rather than merely punitive oversight.

Frequently Asked Questions

Q: What does data transparency mean for everyday residents?

A: It means you can see how surveillance footage is captured, stored and shared, request specific video clips, and verify that any use complies with the law, all via a publicly accessible portal.

Q: How quickly can I obtain footage after submitting a request?

A: The new system guarantees processing within 72 hours, with automated status updates at each stage, so you typically receive the video on the same day or the next business day.

Q: What safeguards prevent my personal data from being misused?

A: Encryption keys are rotated quarterly, an open API only releases anonymised data, and quarterly audited reports are published, ensuring that any access is logged and publicly visible.

Q: Can I appeal a denied footage request?

A: Yes, you have 14 days to appeal a denial, citing the specific clause of the council ordinance you believe was misapplied, and the appeal will be reviewed by an independent panel.

Q: Where can I find the audit logs for data accessed by third-party apps?

A: The council’s Data Integrity Unit publishes a public audit log on the CityHub portal; residents can request a detailed transcript within 30 days of filing an audit request.