> For the complete documentation index, see [llms.txt](https://docs.taloflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taloflow.ai/security/platform-controls/encryption.md). # Encryption Standards Encryption in transit and at rest across Taloflow services. ### Encryption Standards Communications between you and Taloflow servers are encrypted via industry best practices (HTTPS). Taloflow supports encryption of customer data at rest. #### Encryption in Transit All external traffic to and from Taloflow uses industry-standard HTTPS encryption: * **User connections** to Taloflow servers use HTTPS with modern SSL/TLS certificates * **API connections** from Vercel servers to Kubernetes clusters on Linode use HTTPS * **Database requests** use SSL encryption * **Behind-firewall requests**: Some internal requests within our firewall may not be encrypted, but these do not carry sensitive data and remain protected by firewall isolation * **Service mesh**: Full within-cluster encryption via service mesh is currently being deployed for additional defense-in-depth #### Encryption at Rest Customer data is encrypted when stored: * **Object storage**: Customer data in object storage is encrypted * **Database backups**: All backups are encrypted and compressed before storage * **Customer Personal Information (PII)**: Encrypted and managed by Auth0 * **Confidential information**: Decrypted only at the resolver level when needed for operations * **Block storage**: Linode-managed encrypted volumes * **Runtime secrets**: Delivered to workloads via Kubernetes Secrets. See [Secrets Management](/security/platform-controls/secrets-management.md). #### Cryptography governance Changes involving cryptography are peer-reviewed before deployment. --- # 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.taloflow.ai/security/platform-controls/encryption.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.