Tech Support : support@safience.io

Identification that can survive a community review board

Community review boards keep rejecting systems that follow the public around town. The objection is not identification of a known, legally defined person. The objection is persistent tracking of everyone else.

What review boards are actually rejecting

The pattern is consistent. A city deploys cameras that keep video, read plates, watch glass and moving vehicles, and retain a trail of where ordinary people went. Residents ask who can query that trail, how long it is kept, and whether it is shared. When the answers are weak, the program dies in public.

That is a tracking architecture. It is not required in order to find a fugitive, a missing child, or a person who is legally barred from a site.

What the technology has to look like instead

  • Identify a relevant, legally defined person. Do not track the public.
  • Hold no video at any tier.
  • Do not image plates, glass, or moving vehicles.
  • Capture a still for comparison only. Delete unmatched images immediately.
  • Require a trained human before anyone is alerted or approached.

Safience is built to that list. It is identity intelligence for threats and victims, not a movement history of a city.

Why the distinction matters in procurement

If a vendor cannot show deletion of non-matches, cannot show an audit trail of who saw an alert, and cannot show that video is never stored, a review board has nothing to approve. Identification without those controls is just delayed surveillance.

See RTIS, privacy, and public-private partnerships. Legal entity: Biometrica Systems, Inc., doing business as Safience.