Trust
How Hive Teams handles your code and data
What leaves your systems, where it goes, who can see it, and what is recorded. Where something is available on request, this page says so.
Data flow
What moves where during an agent session
Your systemsThe systems each team connects · Microsoft Entra ID
Sign-in, and access to the systems each team connects
Approved output: a pull request, a sent email, a posted entry
Your Hive Teams organizationTeam screens · Messenger · Documents · RecordsThe context each request needs: the record, relevant files, memory
Response, recorded in the session
LLM providerClaude, or your own LLM account
Session records and approvals over an API
Your SIEMOptional export
Nothing merges, deploys or touches production without the approval gate your policy defines.
Isolation, identity, encryption and AI data use
Org isolationEach organization's workspaces, projects, wiki and session records are kept apart from every other organization.
✓Workspace and project data separated per organization✓Separated at the database level by row-level access rules○A dedicated database per customer (Enterprise option)
Identity and accessPeople sign in by email with two-step verification on Starter, and with Microsoft Entra ID SSO on Pro and Enterprise. Agents have their own identity and a scope they cannot exceed.
✓Microsoft Entra ID SSO on Pro and Enterprise✓Agent identity and scope✓Approval gate, as your policy defines✓Three roles in your organization: owner, admin and member
EncryptionData is encrypted between your systems, Hive Teams and the LLM provider. Customer data is stored encrypted with AES-256 by our database infrastructure provider.
✓In transit✓At rest
AI and LLM data useYour code and data are not used to train models. Agent work uses the Hive credits included with every seat, or your own LLM key on Pro and Enterprise; with your own key, your provider's terms apply.
✓Not used for model training✓Your own LLM account, at any time✓The context each request needs is generated dynamically and sent with it
Session record and audit trail
Every agent session is written to the record it belongs to (a work item, a lead, a journal entry, a post): check-in, progress, check-out, checks and approvals. Session records can be exported over an API to your SIEM.
See how governance worksStatus
What exists today, and what is coming
One line per item. We update this table when the status changes.
Need this for a security review?
Ask for the security review pack through the demo form. Tell us what your review needs and we will answer item by item.