> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Data protection
> What data Hive stores, how long it keeps it, who can see it, how the optional data-sharing setting works, and what happens when you disconnect or leave.
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](/help/support).
## What Hive stores
| Data | Why Hive keeps it |
| - | - |
| **Your workspace and members** | Names, emails and roles, so people can sign in and have the right access. |
| **Connection records** | Which tools are connected, by whom, and at what autonomy level. Credentials are encrypted and held separately. |
| **Data read from your tools** | Records, metrics and file content Hive needs to detect signals and answer questions. Hive reads in place — nothing is migrated out of your systems. |
| **The Business Brain** | Facts, relationships and baselines Hive learns about your business, each with its source and trust level. |
| **Chats, projects and files you upload** | So you can return to conversations and reuse files. |
| **Workflows, agents and their runs** | Definitions, versions and run history, including inputs and outputs. |
| **Signals, approvals and audit receipts** | What Hive found, what was decided, and what happened — the record you need for oversight. |
## 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](/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:
| Data | Retention |
| - | - |
| Chats | Kept until deleted. No automatic chat-retention policy is configured today; the **Chat** settings say so. |
| Lapsed signal suppressions (mutes) | Deleted 30 days after they lapse. |
| Connector sync records | Kept for 30 days. |
| Diligence project client data | A retention window you choose, from 1 to 90 days, then removed. |
| Files deleted at the source | Marked deleted in Hive's knowledge base on the next sync. |
| Audit receipts and signals | Kept, so the record of what Hive did stays complete. |
If your organisation needs a specific retention period, [talk to us](/help/support).
## 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](/brain/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](/help/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](/help/support).
## Related
Isolation, encryption and policy.
How AI providers handle your data.
Where Hive runs.
Connection status and removal.