Boundaries and oversight, not adjectives.
GuardianEye sits in workflows where a wrong answer has consequences, so security is described in terms of where things run, who can see them and what is recorded. Specifics for your deployment are settled in a security review.
How the conversation is organised.
Deployment boundaries
Where application services, camera integrations and customer data operate. Agreed per engagement.
Identity and access
Enterprise sign-in, named roles, reviewer responsibilities and administrative permissions.
Data protection
Encryption and key-management requirements for the proposed deployment.
Retention
Retention and deletion of incident evidence, tickets and logs — a configured decision, because obligations differ.
Operational oversight
Logging, monitoring of inference nodes and services, and incident-response requirements.
Tenancy
Sites are separated as tenants; a site sees its own record.
Straight answers
Where does GuardianEye run?
Deployment boundaries are agreed per engagement. The right answer depends on your data residency and hosting requirements, so it is settled in a security review rather than assumed here.
Who can see our camera feeds and tickets?
Access is controlled through identity and access management with named roles, and use is recorded. The specific model for your deployment is confirmed during the security review.
How long is incident evidence kept?
Retention is a configured decision, not a fixed default, because reporting and audit obligations differ by organisation and jurisdiction.
Can we run a security review before committing?
Yes — that is the expected path. Ask for it when you book a site assessment and we will bring the relevant detail.
Start with one site.
A site assessment looks at the cameras you have, the rules that matter on your floor and how the evidence would reach your auditor. Twenty minutes to find out whether it fits.