> 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/general.md). # General #### What is Cryptic? Cryptic is a post-quantum secure communication, cryptographic identity, and crypto-native payments ecosystem built across Mobile, Desktop, and SDK infrastructure. It combines secure communication, non-custodial wallet functionality, payment coordination, Desktop financial workflows, encrypted data transfer, Private AI, and developer infrastructure into one product stack designed for the post-quantum and AI-native era. Cryptic is not just another messenger and not just another wallet. It is a secure coordination layer for users, developers, teams, wallets, applications, crypto-native ecosystems, and future agent-based workflows. *** #### Is Cryptic an app or a protocol? Cryptic is both a product suite and an infrastructure layer. The product suite includes: **Cryptic Mobile** — the consumer app for secure communication, wallet functionality, crypto-native payments, card access, and everyday use. **Cryptic Desktop** — the power-user workspace for secure communication, wallet actions, swaps, lending, encrypted notes, storage, confidential AI workflows, and ecosystem integrations. **Cryptic SDK** — the developer and protocol layer for adding post-quantum encrypted communication, cryptographic identity, key management, payment rails, and future agent infrastructure into third-party apps, protocols, teams, wallets, and agent systems. The applications are the user-facing surfaces. The SDK is the infrastructure layer developers and partners can build on. *** #### Who is Cryptic for? Cryptic is built for: * Everyday users who want secure communication, wallet functionality, payments, card access, and everyday crypto-native use * Crypto-native users who need secure coordination, non-custodial control, and easier wallet/payment workflows * Traders, founders, DAOs, operators, and teams coordinating around digital assets, DeFi activity, private workflows, and encrypted data * Developers and protocols that want to integrate post-quantum encrypted communication, cryptographic identity, key management, and payment rails * Enterprises and high-security teams preparing for stronger communication, private coordination, and post-quantum security requirements * Future agent-based systems that need secure communication, permissions, encrypted data transfer, wallet access, and approval-based execution *** #### Why does Cryptic matter? Cryptic exists to solve a problem most platforms still treat separately: How do people, teams, wallets, applications, and AI agents communicate, coordinate, move value, and protect sensitive data in a more digital, crypto-native, and post-quantum world? Today, users often need one app to communicate, another to pay, another to manage assets, another to swap, another to store files, and another to coordinate privately. That fragmentation creates friction, exposure, and platform dependency. Cryptic brings these workflows closer together across Mobile, Desktop, and SDK infrastructure. The goal is simple: Secure communication.\ Crypto-native payments.\ Private AI.\ Encrypted data.\ Non-custodial control.\ Agent-ready coordination. One product stack built for the next era of digital interaction. --- # 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/general.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.