> 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/legal/privacy-policy.md). # Privacy Policy **Last Updated:** 15 May 2026 ### 1. Introduction Cryptic (“Cryptic”, “we”, “our”, or “us”) is committed to protecting user privacy and minimizing data collection by design. This Privacy Policy explains how Cryptic handles information when you use our mobile applications, websites, and related services (collectively, the “Services”). Cryptic is built on principles of **user sovereignty, non-custodial control, and privacy-first architecture**. *** ### 2. Information We Do **Not** Collect Cryptic does **not**: * Custody user private keys * Store plaintext messages * Access message content * Access wallet balances or assets * Collect biometric data * Require real-world identity by default Private keys and sensitive cryptographic material are generated and stored **locally on the user’s device** using OS-level secure hardware (e.g., Secure Enclave, Android Keystore). *** ### 3. Information We May Collect (Minimal & Operational) We may collect limited, non-sensitive information strictly necessary to operate and improve the Services: * App version and device type (non-identifying) * Crash reports and performance metrics * Aggregated usage statistics (e.g., feature adoption) * Optional support communications you initiate This data **cannot be used to read messages, access funds, or identify users personally**. *** ### 4. Messaging & Encryption All communications within Cryptic are encrypted end-to-end using **post-quantum cryptographic algorithms**. Only intended participants can decrypt message content. Cryptic does not have access to message keys or content. *** ### 5. Payments & Wallets Cryptic operates as a **non-custodial platform**. Users retain full control over their wallets and assets at all times. Cryptic does not: * Hold funds * Control transactions * Reverse payments * Access private keys Blockchain transactions occur on public networks and are subject to the privacy characteristics of those networks. *** ### 6. Metadata & Network Information While Cryptic minimizes metadata exposure by design, some network-level information (e.g., IP routing, timing, packet size) may be observable by third-party infrastructure providers. Cryptic does not claim to eliminate all forms of metadata. *** ### 7. Third-Party Services Cryptic may integrate third-party services (e.g., fiat on/off-ramps, analytics, infrastructure providers). These services operate under their own privacy policies. Cryptic does not sell or share user data with third parties for advertising purposes. *** ### 8. Data Retention Cryptic retains minimal operational data only as long as necessary for functionality, security, and legal compliance. Users may delete local data by uninstalling the application. *** ### 9. Security Cryptic implements industry best practices, including: * Hardware-backed key storage * Post-quantum cryptographic primitives * Secure application architecture * Ongoing security reviews However, no system can guarantee absolute security. *** ### 10. Changes to This Policy We may update this Privacy Policy from time to time. Updates will be posted with a revised “Last Updated” date. *** ### 11. Contact For privacy-related inquiries, contact:\ **** (or your preferred contact) --- # 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: ``` GET https://cryptic-documentation.gitbook.io/cryptic-documentation/legal/privacy-policy.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.