> For the complete documentation index, see [llms.txt](https://docs.taxaible.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taxaible.co/readme/privacy-and-security.md). # Privacy & Security Data Protection & Encryption At TaxAible, we understand that tax data is highly sensitive. We have implemented several layers of security to protect your information. ### Data Encryption * **In-Transit**: All communication between your browser and our servers is encrypted using SSL/TLS. * **At-Rest**: Sensitive data, such as IRIS credentials, is encrypted using industry-standard AES encryption protocols before being stored in our database. ### Secure Authentication We use secure session management to protect your account. This ensures that your session is tied to your browser and expires after a period of inactivity. ### Bot Protection To prevent brute-force attacks and automated sign-ups, we use advanced bot protection on all authentication endpoints. ### Third-Party Integrations * **AI Processing**: We use highly secure, enterprise-grade AI models for data processing. All data is processed according to strict privacy standards. * **Infrastructure**: Our database and infrastructure are hosted on secure enterprise cloud platforms that provide robust physical and network security. ### Your Rights You can request to delete your account and all associated tax data at any time through the support. --- # 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://docs.taxaible.co/readme/privacy-and-security.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.