Data handling & security.
A technical description of what data QueueFlow Sentinel processes, stores, and explicitly excludes.
What is processed.
- Event timestamps (ISO 8601)
- Event type identifiers (motion, doorbell, etc.)
- Device identifiers (camera/device ID strings)
- Location tags assigned by the operator
- Event frequency aggregates
- Dwell interval calculations
- Video frames or recorded video
- Live video streams
- Audio content of any kind
- Facial recognition data
- Biometric identifiers
- Individual identity information
- Physical location of persons
How the system is built.
Read-only integration
The integration model is strictly read-only. QueueFlow Sentinel does not issue commands, modify device configuration, or interact with device control APIs.
Deterministic evaluation
All alert decisions are produced by a rule-based engine with explicit thresholds. No machine learning models are used in the decision path. Identical inputs produce identical outputs.
Immutable audit trail
Every decision — allow or suppress — is written to an append-only log with full input state and rule match data. Records cannot be modified or deleted.
Serverless infrastructure
Deployed on AWS Lambda with event-driven architecture. No persistent compute instances. Data processed in isolated execution environments per event.
Encrypted at rest & transit
All stored metadata is encrypted at rest (AES-256). All data in transit uses TLS 1.2 minimum. No plaintext transmission at any layer.
Retention policy
Event metadata and audit records are retained for 90 days by default. Enterprise customers may configure custom retention windows within contractual limits.
Report a security concern.
For security disclosures, architecture questions, or compliance documentation requests, contact the ExecLayer security team directly.