TRUST & SECURITY
A system that observes physical space owes you a clear account of itself.
This page is the whole answer in one place: where Atlas runs, what leaves your building, what the system will not do, and what we have not yet done. Nothing here is aspirational.
COMMITMENTS
Constraints on the architecture, not promises about intent.
Each of these is true because of how Atlas is built. That distinction matters: a policy can be revised quietly, an architecture cannot.
- 01
Footage stays where it is generated
Perception and reasoning run on hardware inside the building. Atlas does not upload video to us, and it does not send video to a third-party model. This is architectural, not a policy we could quietly change.
- 02
Atlas does not identify people
Tracking assigns temporary identifiers so an event can be described coherently: the same entity, across frames, within a session. Those identifiers are not identities, they do not persist between sessions, and Atlas does not perform facial recognition.
- 03
Customer footage is never pooled
The platform improves through reusable knowledge about environments, event definitions, and deployment patterns. It does not improve by training on one customer's video and selling the result to the next.
- 04
Every event is inspectable
An operator can see why an event was raised: which rule triggered it, what the reasoning stage concluded, and what evidence it was given. A system that cannot explain itself has no business in a hospital.
- 05
We say what we have not proven
Where we have an argument rather than a result, we describe it as an argument. You will find that stated plainly on our technology page, and again below.
DATA HANDLING
The questions your security team will ask first.
- What leaves the building
- Structured events: a type, a timestamp, a zone, and the reasoning behind the escalation. No video, no images, no biometric data. If a deployment requires that even event metadata stays on-site, that is a configuration, not a special build.
- What we can see
- Nothing, by default. We have no standing access to a customer's deployment. Support access is granted deliberately, scoped, and time-limited by the customer.
- Retention
- Atlas does not change your existing video retention. It reads from the infrastructure you already run, and your recording policy remains whatever it already was. Event records have their own retention period, which the customer sets.
- If you stop using Atlas
- The perception stack runs on hardware in your building. Removing it removes the system. There is no copy of your footage elsewhere to request the deletion of, because it was never sent anywhere.
DEPLOYMENT
What actually gets installed.
Runs on your network
An edge machine on the same network as the cameras. It reads existing streams; it does not require replacing hardware or re-cabling.
No inbound access required
Atlas does not need a port opened to the internet for its own operation. Where a customer wants remote support, that is an explicit, revocable decision.
Your IT team keeps control
The deployment sits inside your existing network policy, your existing physical security, and your existing access controls. We do not ask for exceptions to any of them.
CERTIFICATION
What we have not done yet.
SurveiLens holds no SOC 2 attestation and has not completed a HIPAA compliance audit. We are not going to describe ourselves as enterprise-grade or compliance-ready in the hope that it passes unexamined.
That is a sequencing decision rather than an oversight. Certification describes the maturity of an organization's processes; at our stage it would describe very little, at considerable cost, and it would not change the property that actually matters to a hospital, which is that footage never leaves the building because there is no mechanism by which it could.
We will pursue formal certification when a customer's procurement process requires it, and we will say so here when it is underway rather than when it is aspirational.
Your security review will have questions this page does not answer.
Send them. We would rather answer a hard one early than discover it during procurement.