01
Identity
Microsoft Entra work/school authentication with tenant and object IDs used as durable identity boundaries.
Security
Safety software should fail visibly, isolate tenants and minimise secrets.
This page describes LoneWatch security architecture and product principles. It does not claim certifications that have not been independently obtained.
02
Least privilege
Directory manager import uses delegated Graph access for an authorised admin workflow rather than broad application-wide directory access.
03
Scoped contact data
Worker mobile numbers are intended for the worker and currently assigned incident responders, not general notification payloads.
04
Explainable health
Protection health uses Healthy, Degraded, Unavailable and Unknown states so missing evidence does not silently appear green.
05
Auditability
Incident, notification, responder and routing decisions are designed to preserve state changes and the reason a notification channel was used.
06
Production secret management
Production deployment is designed for managed secret storage and TLS-only public endpoints rather than local environment files or embedded credentials.
Responsible disclosure
If you believe you have discovered a security issue in LoneWatch, contact security@lonewatch.app. Please do not include sensitive personal information in the initial report.
Current status
LoneWatch is preparing for controlled enterprise pilots. Security controls, cloud infrastructure and operational runbooks should be validated before any organisation relies on the service for production safety operations.