> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/admin-and-settings/security/security-and-data-protection-overview.md).
# Security & Data Protection Overview
Birdie is built with security, privacy, and compliance at its core. Our platform adheres to industry best practices to ensure that customer data is protected throughout its entire lifecycle — from ingestion to processing and storage.
Key pillars of our security program include:
• Certifications & Compliance: SOC 2 Type II, GDPR, LGPD, USDP, and HIPAA-aligned controls
• Data Protection: Encryption in transit and at rest, strict access controls, and environment isolation
• Privacy by Design: Data minimization, anonymization, and purpose limitation built into the platform
• Operational Security: Continuous monitoring, vulnerability management, and incident response procedures
• Governance: Documented policies covering information security, access management, risk management, and vendor oversight
Detailed security documentation, policies, and compliance reports are available upon request.
After signing an NDA, authorized stakeholders can request access through our [Trust Center in Vanta.](https://trust.birdie.ai/)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://ask.birdie.ai/admin-and-settings/security/security-and-data-protection-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.