> For the complete documentation index, see [llms.txt](https://cryptic-documentation.gitbook.io/cryptic-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cryptic-documentation.gitbook.io/cryptic-documentation/frequently-asked-questions/compliance.md). # Compliance **Is Cryptic compliant?** Cryptic is built with compliance-readiness in mind. This includes alignment with: * GDPR principles * Security best practices * Post-quantum readiness standards * Non-custodial product design where applicable * Clear documentation, risk disclosures, and user-controlled key management Cryptic is designed so users retain control over their private keys and assets in non-custodial flows. This reduces reliance on centralized custody and supports a stronger trust model. Compliance requirements may vary by jurisdiction, product feature, partner integration, and user activity. {% hint style="info" %} Cryptic is not a bank, broker, custodian, or regulated financial institution unless explicitly stated in future jurisdiction-specific disclosures. Users should review the Legal section for full terms, risk disclosures, and regulatory notices. {% endhint %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cryptic-documentation.gitbook.io/cryptic-documentation/frequently-asked-questions/compliance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.