> 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/audits-and-trust.md). # Audits & Trust #### **Has Cryptic been audited?** Cryptic uses established infrastructure and standardized cryptographic primitives where applicable, including Solana-based infrastructure and NIST-standardized post-quantum cryptography. Cryptic’s product stack includes multiple layers: Mobile, Desktop, SDK, server infrastructure, wallet flows, integrations, and cryptographic modules. Because of this, audits need to be scoped carefully around the specific systems being reviewed. A full platform security review and third-party audit process is planned as the product stack matures and the relevant production components are ready for holistic review. *** #### **Why not audit everything before launch?** Audits are most effective when they evaluate a complete and clearly scoped system. Cryptic is launching and evolving across Mobile, Desktop, SDK, and infrastructure layers. Some components are already live or verified, while others are feature-flagged, being hardened, or moving toward broader release. Launching with clear documentation allows Cryptic to: * Identify real-world usage patterns * Define the full attack surface more accurately * Prioritize the highest-risk systems first * Use audit resources efficiently * Align audits with production-ready components * Continue security hardening through the roadmap *** #### **What trust foundations does Cryptic have today?** Cryptic’s trust foundation is built around: * Doxxed and verified leadership * Public documentation * Standardized post-quantum cryptographic primitives * Non-custodial architecture * Clear roadmap communication * Secure key management practices * Ongoing product and protocol hardening * Planned third-party security review as systems mature *** #### **Can Cryptic access user private keys?** Cryptic is designed around non-custodial key control. Where non-custodial wallet flows are used, users remain in control of their private keys and assets. Cryptic support cannot access, recover, or restore private keys on behalf of users. *** {% hint style="info" %} Security reviews, audits, and formal verification work are part of Cryptic’s long-term trust roadmap. Audit scope, timing, and public disclosure may depend on product readiness, release status, third-party availability, and operational requirements. {% 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/audits-and-trust.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.