# Security Implementing systems and processes that allow access to huge amounts of personal information is not easy. Small gaps in implementation or processes can have dire consequences. Imagine an identifcation process gone wrong, and a user receiving someone else's data. Moreover, poor security practices can lead to massive fines. In cryptography, there is an accepted axiom that "you don't roll your own crypto". Rather than thinking of a poor implementation yourself, we use well-tested and well-designed libraries that do this kind of work for us. We've accepted that using OpenSSL, OAuth and bcrypt provide both qualitative and provably secure benefit to development. This is especially true when compared with systems we can design and implement ourselves. The Open Data Rights API provides a robust set of API design principles that ensure that data is secure and private. --- # Agent Instructions: 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: ``` GET https://whitepaper.open-data-rights.org/why-a-data-request-api/security.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.