Skip to main content
Hive reads the tools your business already uses so it can spot problems and help you act. This page explains what that means for your data: what Hive keeps, who can see it, how long it stays, and the choices you control.
This page describes how the product behaves. Your contract and Hive’s privacy terms govern the legal relationship. For a data processing agreement or a specific question, contact us.

​
What Hive stores

​
Who can see it

  • Only members of your workspace. Every record is tied to one workspace and isolated at the database level. See Security overview.
  • Private items stay private. Chats, files, workflows and agents belong to their creator until shared with a named colleague.
  • Email stays with its owner. Mail Hive reads from a connected mailbox is stored as private to the person who connected it. Mail-based signals carry no address, subject or excerpt.
  • File permissions travel with files. When Hive syncs Google Drive, Dropbox, OneDrive or SharePoint, it records each file’s access list and respects it when answering.
  • Admins see metadata, not credentials. Owners and Admins can see which connections exist, but not anyone else’s credentials, scopes or actions.
  • Support access. A small number of Hive staff accounts can open a workspace to provide support.

​
Retention

Hive does not yet apply one retention period to everything. What is in place today: If your organisation needs a specific retention period, talk to us.

​
Your personal memory

If you choose to use it, Settings → Account → Memory holds short notes Hive remembers about you. They are private to you and used only in your regular chats, and only when your workspace allows chat memory. Delete all memories removes them after you type a confirmation; it does not delete past chats or workspace rules. See Personal memory.

​
The data-sharing setting

Settings → Workspace → Data sharing has one switch, Help improve Hive. Its wording in the product:
When this is on, Hive will use this workspace’s chat and workflow data to further improve and enhance Hive’s product offerings. No personal data will be used.
  • It is off unless an Owner or Admin turns it on, and can be turned off again at any time.
  • Only Owners and Admins can see or change it.
  • If Hive cannot read the setting, it treats it as off.

​
Product analytics

Hive uses product analytics to understand how the product is used and improve it:
  • Analytics are processed in the EU.
  • IP addresses are not collected, and all text and input values are masked.
  • Session recordings, where used, are masked and exclude request headers and bodies.
  • Browser Do Not Track is respected. Otherwise analytics are on by default, and you can turn them off with Decline on the consent banner.
  • Connection labels such as mailbox addresses are kept out of analytics, and custom integration names are anonymised.

​
Disconnecting a tool

When you disconnect an account (Integrations → the tool → Disconnect):
  • Hive stops reading from it immediately.
  • Open signals that account was feeding are dismissed and their pending approvals removed.
  • Nothing you already approved is undone.
  • For MCP servers and incoming webhooks, the stored secrets and pinned tools are deleted.
Disconnecting stops future reads. If you want data Hive previously collected from that tool removed, contact support.

​
Leaving Hive

When a workspace is deleted, Hive:
  1. engages the workspace’s kill switch so nothing can act;
  2. removes private attachments;
  3. stops all scheduled jobs for the workspace;
  4. ends billing.
The workspace’s remaining records are retained so it can be restored if you return. To request full deletion or an export of your data, contact support.

Security overview

Isolation, encryption and policy.

AI and models

How AI providers handle your data.

Infrastructure

Where Hive runs.

Health and disconnect

Connection status and removal.