Security & Privacy
Security Architecture
Overview of Termina’s infrastructure security, data protection, and operational safeguards.
Security Principles
Termina is built to observe systems, not control them.
Integrations should use the minimum permissions required to read deployment and environment information. Termina does not perform infrastructure changes or trigger deployments.
Your existing CI/CD pipelines and cloud providers remain responsible for executing changes.
Data Handling
Termina stores operational metadata such as environments, deployments, services, and system relationships.
Application secrets, source code, and private credentials are not stored by the platform.
This ensures teams can understand production state without exposing sensitive infrastructure data.
Secure Connections
Connections to external systems should always use encrypted APIs and authenticated tokens.
Integration credentials should be managed through your organization’s normal secret management practices.