Trust
Who sees what, and how evidence is checked
Access
- Organisation roles
Organisations have administrator, operator and auditor roles. Administrators and auditors can read an audit log.
- Case access
Cases have owner, editor and viewer roles and are visible to their members only. An administrator can break glass into a case, and every break-glass is audited.
Case records
- What a case holds
A case holds a timeline across cameras, annotations and a relationship map of what was seen together.
- Case activity log
Each case keeps an activity log of changes to the case, its evidence, its members and its briefings, each with its time.
Screens on this page show fictional data.
Evidence
- Snapshot hashes
Snapshots are hashed as they are captured. A "Verified" chip on a citation re-checks the hash, and an image that was hashed only after capture is labelled as such.
What the Verified chip says
- "Verified": the stored image matches the hash recorded when it was captured.
- "Not sealed at capture": the image matches its hash, but the hash was recorded after capture.
- "Hash mismatch": the stored image does not match the hash recorded at capture.
- "Image missing": the stored image could not be found, so it could not be checked.
Data
- Isolation
Every organisation's data is isolated by row-level security in the database, including every frames partition.
- Retention
An administrator sets the retention period for the organisation.
Privacy
Re-identification in Focient is multi-signal fusion: build, gait, clothing, co-occurrence, time and place. It never uses faces, and face matching never replaces it or silently enhances it. Focient creates tracked-person records without an identity and never links them to one on its own. There are no employee identity profiles and no linkage to productivity or HR records. In every build and for every customer, Focient never classifies or refers to ethnicity, never infers emotion, affect or intent, never scores individuals, and gives apparent minors generic descriptions only.
They apply in every build and for every customer, including where the face recognition module is on, and they are not settings:
- No person re-identification by face. Re-identification uses multi-signal, non-face fusion only, and face recognition is never a replacement for it or a silent enhancement of it.
- No identity profiles of individual employees, and no following of an employee by identity. The platform creates anonymous tracked-person records. It does not build identity profiles linked to real-world names, productivity data or HR records.
- No ethnic-origin classification. AI outputs never classify or refer to ethnicity.
- No emotion, affect or intent inference.
- No social scoring: no risk-scoring of individuals.
- No following of apparent minors by identity. If apparent age is under 18, descriptions are generic only.
- No open-set "identify anyone" face search. Inside the module the only permitted output is match or no match against a specific, legally authorised, bounded watchlist.
Questions your reviewers ask
How do we ask about deployment and data flow?
We show you the console on recorded footage, under NDA. Demos and briefings are held under NDA. Deployment, network and data-flow questions are answered in the first conversation, under NDA.
What rules apply to people on camera?
They are set out in the Privacy section of this page.