Security & Trust
Iron Watch is designed around controlled access, tenant isolation, least privilege and visible human oversight.
See Iron Watch in ActionHuman-controlled decision support
01 · Isolate
Each customer environment is designed to keep users, guards, clients, sites, shifts, credentials, documents, incidents, reports, financial data and AI context isolated.
The request is authorised for this customer environment.
02 · Restrict
Least privilege helps ensure that a scheduler, compliance user, guard, client viewer and platform Founder do not see the same information.
This action requires an authorised role.
03 · Record
Privileged actions and Founder Support Mode should be explicit, visibly labelled and logged — never a casual bypass of tenant boundaries.
Authorised access is time-limited and auditable.
04 · Control
AI credentials remain server-side. AI is tenant scoped, schema validated and designed to fall back safely while deterministic operations remain available.
AI assistance is temporarily unavailable.
No internet-connected system can be guaranteed completely secure. Iron Watch uses layered controls and expects users to protect their credentials and report suspected unauthorised access.
Ready before it becomes urgent
See how Iron Watch connects guards, shifts, credentials, sites and operational decisions.