Security Policy
Effective Date: January 1st, 2026
Last Updated Date: January 1st, 2026
Anchorbase maintains appropriate technical and organisational measures to protect Customer Personal Data, including the measures described below. These measures are designed to ensure the security, confidentiality, integrity, and availability of the data processed in connection with the Services.
1. Data & Security Commitments
2. Approved Subprocessors The following sub-processors are used to deliver the Services. All sub-processors are bound by written agreements that impose data protection obligations.
| Subprocessor | Country / Region of Location | Anticipated Processing Task |
|---|---|---|
| Cloudflare R2 | US | Document storage (at rest, AES-256 encrypted) |
| Supabase | US East - Ohio | PostgreSQL database - Metadata and database |
| Pinecone | US East - Virginia | Vector embeddings for RAG search |
| Google (Gemini Enterprise API) | US | Search LLM, OCR, embeddings (enterprise terms prohibit training on customer data) |
| xAI (Grok API) | US | Primary LLM (enterprise terms prohibit training on customer data) |
| Posthog | US | Product analytics, usage tracking, session replay, feature flags, and error monitoring |
| Fly.io | US East - Virginia | App hosting (backend + frontend) |
| Resend | US | Transactional email |
| Sentry | US | Error tracking |
3. Additional Security Measures Anchorbase implements industry-standard controls including (but not limited to) encryption, access controls, regular security updates, and monitoring.