> 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 %}