People decide. The evidence is one click away.

• Every alert carries its camera, time and rule. An alert from a scene reading or a plate watchlist hit carries a still; one from a zone, line, dwell or item-left rule leads to the sighting and its still; count and camera-offline alerts have none.In the product
• An alert stays New until a named person marks it Acknowledged or False positive.In the product
• Acknowledged records who took the alert on, and when. It is not a finding about what happened, and it does not verify an identity.In the product
• Marking several alerts at once applies the same recorded mark to each, under your name. It does not verify anything and does not close a case.In the product
• Grouped sightings are candidates. Sightings that overlap in time are kept apart, which stops two similar-looking people in one view being merged, and means one person seen by two overlapping cameras at once appears as two candidates.In the product
• Uploaded footage never raises alerts, so reviewing history cannot alert anyone by mistake.In the product
• Acknowledged and False positive are the only recorded marks. Reviewed, escalated and resolved live in notes and in your own process, not as states in the product.In the product

• Runs on your workstation or, after assessment, on your server or a virtual machine in your own cloud account. Only the workstation has been run end to end in our own testing.Set at deployment
• Camera streams are read from inside your network. Cameras are not exposed to the internet.Set at deployment
• Everyone signs in with their own account, created by invitation. Repeated failed attempts lock the address for a time.In the product
• Sessions end after a period of inactivity and after a maximum age, and can be ended by an administrator.In the product
• Passwords are stored as salted hashes. Keys for AI services and mail are stored encrypted and cannot be read back through the interface.In the product
• HTTPS for the dashboard. It is off by default, has been verified with a locally issued certificate only, and leaves the unencrypted ports reachable unless they are closed at the host.Set at deployment
• One automation token per deployment, with platform-administrator rights across all organisations. Tokens limited to one organisation or one role do not exist.In the product
• The health report and performance figures can be read without signing in by anyone who can reach the API port, so that port is kept off untrusted networks.Set at deployment
• Sign-in is by email and password within the product. There is no single sign-on through an identity provider.In the product
• Stills and exports are not cryptographically sealed.In the product

• Video is processed where the platform runs. VisionObject does not retain live video; your recorder does.In the product
• For each sighting the platform stores a record and, where a frame was captured, two stills, on your storage.In the product
• Sighting records and their stills are deleted after 90 days by default; a platform administrator sets this period. Frame-level detection data is deleted after 30 days, which is fixed.In the product
• Audit entries are kept for 365 days by default and the system log for 90 days.In the product
• Plate-read history, events, alerts and their notes, weekly briefs and uploaded footage have no retention period and no delete operation in the current release.In the product
• Nothing is sent to VisionObject. We see footage only if you choose to share it.Set at deployment
• AI scene reading, if switched on, sends one still of the whole camera view per sighting to the AI service you configure, with the object type, the plate as read, the camera's identifier, colours, how long the object was followed and the time. A failed request is retried and may go to a second configured AI service.In the product
• The weekly brief, if switched on, sends aggregate figures with the names of your rules, cameras, areas and watchlist labels to the AI service you configure, and is emailed through your mail relay. It sends no footage and no stills, and no plate numbers unless a watchlist label contains one.In the product
• The map background is loaded by the operator's browser from a public map service.In the product
• Switching a module off stops it running and hides what it produced. It does not delete what was already stored.In the product
• How long uploaded footage is kept, and who backs up the database and stills.Agreed with you

• Five roles: administrator, supervisor, operator, investigator and viewer.In the product
• Each person can be limited to a named list of cameras.In the product
• Each camera belongs to one organisation and is shared with others one by one, by a platform administrator.In the product
• Changes, and searches by plate, scene description and route, are recorded with who made them and when. The log can be exported.In the product
• The audit log records that an action happened. It does not store the text of a note, a camera address or a secret.In the product
• Who holds which role, and who may search.Agreed with you

• Face search is not offered in the current release. It is switched off in every deployment we deliver, and its recognition model is not licensed for production use. An organisation's administrator cannot switch it on; only a change to the deployment's configuration could, and our agreement does not allow it.Set at deployment
• Number plates, appearance, AI scene reading and the weekly brief are separate switches for each organisation.In the product
• No model in the product classifies emotion, intent or demographics. The AI scene reading is instructed to describe clothing, vehicles and behaviour only; its text is not filtered.In the product
• Records are not anonymous without face search. Plates, appearance groups and times can still relate to a person, so purpose, access and retention are agreed for them too.Agreed with you
• The purpose of each sensitive capability, and the people allowed to use it, are written down before it is switched on.Agreed with you

• The API specification
• The deployment and operations guide
• A summary of what data is stored, where, and for how long
• The list of what each role may do

Questions we are asked first