Trust

Data handling

Camera feeds are processed for AI detection and patrol verification. Video footage is stored according to your configured retention policy and encrypted at rest. We do not sell, share, or use customer video data for model training without explicit consent.

Account actions are logged

Every account keeps an activity record covering sign-ins, security changes, configuration changes, AI feature activity and user-management actions, filterable by category. It is visible to the account holder under My Profile, not something that has to be requested from us.

We mention it here because it is a thing that exists today and can be checked, rather than a certification we are working towards. If you need to answer who changed a retention policy, who added a camera, or who acknowledged an alert and when, that record is already being kept.

What we do not claim

We do not claim to replace all security guards at all facilities. We do not claim zero false alarms. We do not claim compliance with certifications we have not obtained. See the security and compliance page for specific details on our security posture.

Honest numbers

We do not publish customer counts, cameras-connected totals, patrol-round volumes, uptime percentages or average response times on this site. Not because they are unflattering, but because we have not put them through a verification process we would be willing to defend, and a security vendor quoting an unverifiable reliability figure is exactly the thing this page exists to avoid.

What we will do instead: during an evaluation we will show you the real numbers for your own deployment, rounds completed against rounds scheduled, per-camera compliance, and alert volumes, from the same analytics and reporting surface your team would use in production. Those are numbers you can audit yourself rather than take on trust.

When aggregate figures are independently verified, they will appear here with the method used to produce them.