Security

The controls, data protections, and access boundaries to review before you roll out. The security page has the full, current detail.

Core controls

Data is encrypted in transit with TLS and at rest. One Horizon does not hold a SOC 2 report today; controls are built against the SOC 2 criteria.

Integrations connect through OAuth, so One Horizon never asks for provider passwords. Integration access tokens are encrypted before they are stored.

Access boundaries

Connected apps such as GitHub, GitLab, Slack, Jira, Linear, and Google Calendar keep their own user-level permissions. If a person cannot access a repository, issue, Slack channel, or calendar in the source app, the integration does not expose it to them.

Work and agents

Initiatives, bugs, todos, comments, documents, and prompts can become context for coding agents. Agent Sessions separate trusted platform and agent policy from untrusted workspace content before an agent executes.

Permissions covers the full access model.