> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.9/crvs-systems/opencrvs-value-proposition/legal-compliance.md). # Legal Compliance **OpenCRVS is designed to be implemented in compliance with national legal frameworks governing civil registration, data protection, and privacy**. As a Digital Public Good, OpenCRVS provides a flexible and configurable platform that enables countries to align system implementation with their specific legal and regulatory requirements. This includes support for: * Role-based access control and user permissions * Secure data handling and storage practices * Auditability and traceability of all actions within the system * Configurable workflows to reflect national legislation and procedures OpenCRVS has been implemented in multiple countries under a range of legal and regulatory environments. These include, for example: * Burkina Faso: compliance with data protection requirements under the Commission de l’Informatique et des Libertés (CIL) * Madagascar: alignment with national civil registration law and data governance requirements Across these implementations, OpenCRVS has been deployed in accordance with applicable national laws, and there are no known conflicts between the platform and legal requirements in these contexts. OpenCRVS does not prescribe a single legal model. Instead, it is designed to adapt to country-specific legal frameworks, ensuring that governments retain full ownership, control, and responsibility for compliance with their national legislation. --- # 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://documentation.opencrvs.org/v1.9/crvs-systems/opencrvs-value-proposition/legal-compliance.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.