> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/data-protection.md). # Data Protection At Flosum, we are committed to protecting the privacy and security of our customers' data. Our SaaS application fully complies with the General Data Protection Regulation (GDPR), ensuring that we handle personal data in accordance with the highest standards of data protection and privacy.\ We have implemented robust technical and organizational measures to safeguard the personal data we process on behalf of our customers. This includes: * Strict data access controls and authentication mechanisms * Encryption of personal data both in transit and at rest * Regular security audits and assessments * Data processing agreements with our sub-processors * Providing customers with tools to manage data subject requests * Ensuring data portability and the right to be forgotten Our dedicated privacy team continually monitors and updates our practices to maintain compliance with GDPR and other relevant data protection regulations. We are transparent about our data processing activities and provide our customers with clear information about how we collect, use, and protect their personal data.\ \ **Trust, Availability, and Business Continuity Plans** The Flosum Disaster Recovery Plan documents our processes to recover from outages. More information can be found here: . --- # 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.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/data-protection.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.