Skip to content
SecureOps

[ 18 ]  Security

Evidence isonly as goodas its vault.

Your records may be read by a client, an insurer or a court. Here's how we keep them intact and private.

Rows of servers in a data centre

Security

Records built to be read by a client, an insurer or a court.

[ 18.1 ]  How we protect it

Defence in depth.

  • 01

    Encrypted everywhere

    All traffic uses TLS. Databases and file storage are encrypted at rest by our managed cloud providers.

  • 02

    Access enforced in the database

    Row-level security rules decide who sees what inside the database itself: guards see their shifts, clients see their sites, companies never see each other.

  • 03

    Append-only proof

    Patrol events can be added but not edited or deleted by users. Corrections are stored as annotations next to the original, with a name and time.

  • 04

    Private evidence

    Incident photos sit in private storage and are shared only through short-lived signed links.

  • 05

    Server time, not phone time

    Every event is stamped with the server's clock on arrival, alongside the device time, so changing a phone's clock can't fake a round.

  • 06

    Least privilege for our team

    Production access is restricted to named administrators who sign in with multi-factor authentication.

  • 07

    Backups and recovery

    Production databases are backed up daily with point-in-time recovery on our production hosting plan.

Security | SecureOps