> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/enterprise-compliance/security-and-privacy.md).

# Security and Privacy

Feathery was built from the ground up with security and privacy in mind.

To learn more about how we think about data privacy at Feathery, you can read our [privacy policy](https://assets.website-files.com/5994ba20a9572800013a4d4d/6257710785e0d33229e376e7_Privacy%20Notice%20Policy%202022.pdf).

## Our security posture

Feathery is SOC 2, HIPAA, GDPR, and PIPEDA compliant, which means we:

1. Adhere to best development and security practices
2. Encrypt all data at rest and in transition
3. Leverage industry-standard monitoring and alerting tools
4. Secure our systems with two-factor authentication and other best practices

We will never send your data to a third party without your consent.

If you need a copy of our SOC 2 report, please reach out at [support@feathery.io](/platform/build-forms/elements/fields/email.md)*.*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.feathery.io/platform/enterprise-compliance/security-and-privacy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.