Skip to main content
Use this page when you need public references for how Fetch Hive handles privacy, retention, and third-party model access.

​
Privacy and data handling

Fetch Hive’s public Privacy Policy describes the categories of personal information and business data it collects and processes. The policy states that personal information and business data are stored and processed in the European Economic Area or in facilities used by partners, affiliates, and third-party providers. It also states that appropriate safeguards are used when data is transferred outside the EEA. The public retention periods listed in the policy are:
  • Account information: while your account is active, plus 24 months after account closure
  • Payment information: for as long as required by applicable financial and tax regulations
  • Communication data: 24 months after the last communication
  • Log and analytics data: 12 months from collection

​
Workspace data isolation

Fetch Hive enforces workspace-level data isolation at the database layer using PostgreSQL Row-Level Security (RLS). Every request runs in the context of the authenticated user’s workspace, and the database itself restricts reads and writes to records belonging to that workspace. This means workspace data is segregated defence-in-depth: even if application-level checks were bypassed, the database would still prevent access to data from other workspaces. This applies across the platform, including agents, workflows, runs, knowledge bases, documents, and API keys.

​
AI model providers

Fetch Hive currently exposes models from these providers in the product:
  • OpenAI
  • Anthropic
  • Google
  • xAI
  • Perplexity
  • Cohere
  • DeepSeek
You can review the current provider and model list in Model library. If you use Personal charge type, connect provider credentials through Integrations. See Use your own API Key for that setup flow.

​
Policy references

The public Privacy Policy states that Fetch Hive is GDPR compliant and that its use of Google API data adheres to the Google API Services User Data Policy, including Limited Use requirements. The same policy also lists third-party processor categories used for analytics tracking, user authentication, advertising and promotion, email marketing, and payment processing.

​
Contact

For privacy, data protection, or policy questions, use the contact details listed in the Privacy Policy or the general Get in contact page.