Security
Last updated: July 1, 2026
Security is a design constraint at Intuitum, not a feature bolted on afterward. This page describes how we protect the Services and the data entrusted to them.
1. Our approach
Security is a design constraint at Intuitum, not a feature bolted on afterward. We build so that a single failure does not become a catastrophe: least privilege by default, defense in depth, and small, auditable changes over sweeping ones.
2. Infrastructure
The Services run on established cloud providers with strong physical and network security. We isolate environments, restrict production access, and log administrative actions so they can be reviewed.
3. Encryption
Data is encrypted in transit with modern TLS and encrypted at rest. Secrets are held in dedicated key management and never committed to source control.
4. Access control
Access to production systems and customer data is limited to those who need it, protected by strong authentication, and reviewed regularly. We revoke access promptly once it is no longer required.
5. Monitoring and response
We monitor the Services for anomalies and maintain an incident-response process, so we can detect, contain, and communicate quickly when something goes wrong.
6. Development practices
Security review is part of how we ship. Dependency scanning, code review, and testing run before changes reach production, and we prefer changes small enough to reason about.
7. Reporting a problem
If you believe you have found a vulnerability, please tell us through our disclosure process rather than posting it publicly. We read every report and respond.
Questions about this document? Contact us.