Trust centre
How we protect what your cameras see.
KENAEZ handles footage of real people, the movements of people who wear our trackers, and access to computers on your sites. This page sets out how we secure all of it, where it lives, how long we keep it, and what we have not done yet.
Identity
Authentication we run ourselves
- Accounts, sessions and second factors live in our own database. There is no third-party identity provider to depend on.
- Passwords must be at least 12 characters, and every sign-in also needs a six-digit code sent by email, valid for five minutes with five attempts, stored only as a hash and enforced on the server.
- A sign-in from a new device triggers an email to the account holder.
- Sessions use secure cookies and last seven days. Requests are checked for their origin, and sign-in and other sensitive routes are rate-limited.
- Accounts are created by invitation from an organisation's administrators; there is no open sign-up.
Encryption
In transit and at rest
- Browsers, apps and edge nodes connect over TLS. GPS trackers use the manufacturer's own TCP protocol to our relay in London.
- Event media is stored in Amazon S3 in eu-west-2 with server-side encryption and public access blocked. Media is served through signed links that expire after an hour.
- Camera stream credentials, your own AI provider keys, WhatsApp tokens and stored remote-access logins are encrypted with AES-256-GCM.
- Edge node keys, MCP tokens and evidence share-link tokens are stored only as SHA-256 hashes.
Access
Everyone sees only what they should
- Owner, admin and member roles, with members restricted to particular sites where needed.
- Every read of cameras, events, trackers and cases is filtered on the server by what that person may see, including in the assistant.
- Guest shares are limited to the site shared, and guests, WhatsApp and MCP tokens can never reach trackers, Retrace or remote access.
On site
The edge node and remote access
- Edge nodes connect outwards only; no inbound ports are opened on your network.
- Edge software is signed offline with Ed25519 keys that never touch our servers or build system. Nodes verify the signature and every file, and refuse older versions, before installing anything.
- On Windows, the install folder is restricted to SYSTEM and Administrators, and the node checks its own install every time it starts.
- Remote access (rolling out) runs its screen decoder in an isolated container with no database or cloud credentials, pins each computer's certificate or host keys, and needs a reason and an emailed code for every session.
Accountability
Audit trails
- An audit log of every user-administration action, including refused attempts, with the address and browser each came from.
- An append-only Retrace audit of every case, probe, search, verdict and report, kept for 365 days.
- A remote access audit of every session, kept for 365 days.
- An access log for every view of a shared link, and a log of every tool the assistant uses, recorded against the person who asked.
Retention
How long we keep things.
Data is deleted on a schedule, not left to accumulate. Where a period can be changed, the range is shown.
| Data | Kept for |
|---|---|
| Event stills and clips | 48 hours, or 7, 14 or 30 days on a paid retention tier |
| GPS positions | 30 days, oldest first. Last known position and alarm locations are kept with the device |
| Cross-camera visit links | 30 days by default (1 to 90) |
| Assistant conversations | 30 days by default (1 to 365) |
| Night Guard patrol records and frames | 30 days |
| Camera health samples | 14 days |
| Retrace draft cases | 7 days if untouched |
| Closed Retrace cases and their evidence | 90 days by default (7 to 365) |
| Retrace and remote access audit | 365 days |
| Evidence share links | Expire after 24 hours, 72 hours or 7 days |
| A closed organisation's data | Deleted 30 days after the account is closed |
What we have not done yet
KENAEZ has not yet completed an independent penetration test or a formal certification such as ISO 27001 or SOC 2. We will say so here when we have. Until then, we are happy to answer your security questionnaire in detail and walk your team through the architecture.
Found a vulnerability?
Tell us first, and we will act fast
Email [email protected] with "Security" in the subject line and enough detail to reproduce the issue. Please give us a reasonable time to fix it before sharing it, and don't access other people's data or disrupt the service while testing.
Report a security issue →Reveal what's hidden
See every site you run on one live map.
Bring the cameras you already own. We'll show you KENAEZ on your own buildings, from the first edge node to the morning report.
14-day trial · Monthly licences · UK hosted