The estate. The operator. The DPIA the SIRO can sign.

UK local-authority CCTV is the most-watched, least-resourced surveillance footprint in the country. Estate ASB review, town-centre night-time-economy footage, transport-interchange incidents — the people doing the work are running 50 cameras per pair of eyes. Embedding-only ReID gives them cross-camera reach without dragging the authority into a new biometric processing category. The DPIA stays a continuation of the existing CCTV one. The SIRO signs.

§ NAMED PAINS

What the CCTV Manager tells us first.

01

Estate ASB is a one-operator-per-fifty-cameras problem

A typical metropolitan council CCTV room runs 200–600 cameras across housing estates, town centres, parks and bus interchanges, with three to six operators on a shift. The bandwidth to investigate a sustained ASB complaint on an estate over a 3-hour window without ReID is roughly zero. With ReID, the same complaint resolves in a thumbnail strip.
02

CCTV operator burnout is the workforce risk you don't write down

Twelve-hour public-sector control-room shifts on screens that show very little, very slowly, are corrosive. Sickness rates and turnover in local-authority CCTV teams are publicly bad. ReID re-architects the shift around event review rather than continuous watching — which is what the staff and the union have asked for.
03

ZB-registration is the difference between defensible and not

An ICO ZA-class registration covers ordinary data-controller processing; a ZB-class step appears for biometric processing in some local-authority deployments. Embedding-only ReID stays inside the ZA-class posture the council already runs — the system does not add a new lawful-basis category to the DPIA, and PSED EIA review treats it as continuous with existing CCTV rather than a new biometric workload.

Pain 01

Three-hour ASB complaint on a housing estate, surfaced in seconds.

What we see

Cross-camera traces across the estate's housing blocks, communal areas and stairwells. When a sustained pattern matches a configured rule (repeat entry, communal-area dwell, after-hours stairwell), the operator gets a thumbnail strip.

What we don’t see

Tenant names — no link to the housing-management system.
Faces — embedding-only.
Public realm beyond the estate's CCTV footprint — adjacent town-centre cameras are scoped separately.
Anything outside the configured rule set — no general-purpose surveillance dip-in.

What concierge does

Community-safety officer + CCTV manager configure the rule set with Estates Services during onboarding.
Pattern match surfaces to the duty operator with a 3-thumbnail strip and the rule label.
Operator triages — clear, log, or escalate to estate housing officer / police per the authority's existing ASB protocol.
Quarterly community-safety review tunes rules and reviews intervention outcomes.

Data lifecycle

Raw video sits in a 72-hour ring buffer on the on-prem edge appliance, then auto-overwrites — we never copy frames off the site. Embeddings (the abstract vectors the system actually compares) live for 30 days in the UK-resident database. Event records (a timestamp + a camera ID + a similarity score) live for 90 days for investigation continuity, then auto-purge. None of the three layers contain a face image, a name, or an ID document.

Legal posture

UK GDPR Art 6(1)(e) — public-task processing (community safety, statutory housing-management duty) — and ICO surveillance camera code compliance. ZA-class registration; embedding-only ReID treated as continuous with the existing CCTV DPIA. PSED EIA continuous. DSPT v8 self-assessment shared with the SIRO.

Procurement Q&A

What does the SIRO need to sign?: The DPIA addendum, the PSED EIA, the legal opinion on embeddings-vs-biometric, and the procurement governance pack. The SIROs we've worked with read the addendum + EIA in a day; the legal opinion takes longer because the legal team need to sit with the comparator.
How does this read against the surveillance camera code?: The 12-principle code maps cleanly: the system is operated for a specific purpose (community safety + housing-management duty), is necessary and proportionate (embedding-only, no biometric escalation), has a clear governance posture (SIRO-owned), and respects the public-task lawful basis. We share the mapping document.
What about Article 22 — automated decision-making?: Operators decide, not the system. The system surfaces a pattern; the human operator triages, escalates or clears. We do not ship any auto-action capability and would not without a separate DPIA addressing Article 22 directly.

Pain 02

Twelve-hour shifts watching screens, re-architected around event review.

What we see

The system handles continuous monitoring; operators handle event review. The shift's job becomes triaging matched patterns rather than scanning 50 feeds for a needle.

What we don’t see

Anything that looks like operator-displacement automation — operators remain the decision-makers and the headcount conversation is the authority's, not ours.
Productivity surveillance of operators — we do not track operator response time or escalation rate as a workforce metric; the system's metrics are about its own false-positive rate.
Behavioural inference on the public — pattern matches, not motive scoring.

What concierge does

Operator session starts with a queue of pattern matches from the previous shift's tail + the current shift's first matches.
Operator triages each match — clear, log, escalate. The console refuses unactioned matches to roll over a shift boundary without sign-off.
Supervisor shift handover walks unresolved escalations + the night's false-positive review.
Monthly: union rep + community-safety lead + CCTV manager review the shift design and tune the rule set.

Data lifecycle

Legal posture

Processed under UK GDPR Art 6(1)(f) — legitimate interest in operator safety, balanced against a data subject who is not identified by the system. ICO registration: ZA-class data-controller posture (no biometric-processing escalation; embeddings of body-shape + clothing carry no Schedule 1 special category by construction). DSPT v8 self-assessment shared with the customer's DPO under NDA before contract; written legal opinion on the embeddings-vs-facial-recognition distinction included.

Procurement Q&A

How does this interact with the operator union?: We brief the union rep with the same DPIA addendum + workforce-impact note we give the SIRO. The deployments that went smoothest had the union rep in the shift-design conversation from day one. We provide a workforce-impact template.
Is this used to performance-manage operators?: No — explicitly. We do not ship operator-productivity metrics. The system's reported metrics are its own false-positive rate, its own match queue depth and its own uptime. Operator performance is the authority's existing workforce posture.
What does the staffing model look like post-deployment?: Authority-specific. Two pilots kept the same headcount with reduced sickness; one re-roled an operator into a community-safety analyst position handling pattern analysis. We don't recommend a headcount cut; the value is in the bandwidth, not the wage bill.

Pain 03

ZB-class biometric processing is the line we don't cross.

What we see

Embeddings — body-shape and clothing-colour. ICO Schedule 1 biometric data is face, fingerprint, iris, voiceprint — categorically distinct from what we process.

What we don’t see

Face features.
Biometric templates.
Anything that would trigger ZB-class processing on the authority's ICO registration.
Anything that would require an Article 9 lawful basis.

What concierge does

Procurement starts with the legal opinion + DPIA addendum + EIA + DSPT v8 self-assessment landing on the SIRO's desk and the DPO's desk simultaneously.
Authority's information-risk committee reviews; the comparator (this vs facial recognition) is part of the standing pack.
If approved, the ICO registration remains ZA-class — no biometric category added.
Annual review confirms no drift; if the authority ever procures a facial-recognition capability, that's a separate ZB-class registration update and a separate Article 9 conversation.

Data lifecycle

Legal posture

UK GDPR Art 6(1)(e), public-task lawful basis. ICO ZA-class registration explicitly preserved — no biometric-processing escalation, no Schedule 1 special-category processing, no Article 9 lawful basis required. PSED EIA continuous with existing CCTV. DSPT v8 self-assessment + written legal opinion on the embeddings-vs-biometric distinction shared institutionally.

Procurement Q&A

What if a councillor wants facial recognition added?: That's a separate procurement, a separate DPIA, an Article 9 lawful-basis test, and a ZB-class registration update. We do not ship facial recognition as a feature toggle on this product; the categorical separation is the point.
How is this position defensible at a coronial review or judicial review?: Three legs: documented EIA showing no protected-class processing, documented DPIA showing no Schedule 1 escalation, and an external legal opinion on the embeddings-vs-biometric distinction shared with the authority's legal team before contract. The bar is reasonableness; we evidence reasonableness.
What does ICO say about this category specifically?: There is no published ICO finding on embedding-only ReID as a category as of 2026. The ICO's published positions are on facial recognition (Facewatch, Serco, AFR by police forces). We share an outline of the regulatory landscape with the DPO and revisit annually as the ICO's published guidance evolves.

§ ICO POSTURE FOR LOCAL AUTHORITIES

ZB is the line. We stay on the ZA side of it.

The Information Commissioner's surveillance camera guidance is unambiguous on facial recognition by public authorities: it requires an Article 9 lawful basis, a Public Sector Equality Duty (PSED) Equality Impact Assessment with named protected-class consideration, and an explicit biometric-processing entry in the DPIA. Embedding-only ReID needs none of those — the data is non-biometric in the Schedule 1 sense, the EIA is continuous with the existing CCTV one, and the DPIA addendum is short.

For the Senior Information Risk Owner (SIRO) signing the council's information risk register, that distinction is the difference between a routine renewal and an annual audit headache. We share the legal opinion and the mapping to the surveillance camera code controls with the authority before contract.

Read the rest of the stack.

How it works → See the demo → The UK posture → Pricing →