> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/architecture-and-security/threat-model-and-limitations.md). # Threat model and limitations What Cifer protects, what it does not, and how integrators should describe it ## Intended protections * Protect application payloads with hybrid post-quantum encryption. * Keep private-key material distributed as threshold shards. * Restrict decryption to an authorized owner, delegate, permit, or session. * Reduce signed-request replay through block or timestamp freshness. * Provide verifiable on-chain authorization and optional record commitments. ## Outside the cryptographic boundary Cifer cannot guarantee the safety of plaintext before encryption or after authorized decryption. It does not by itself protect: * A compromised endpoint or browser * A stolen wallet, Ed25519 key, password, or active session * Malicious application code * Plaintext copied by an authorized recipient * Traffic, timing, file-size, or application metadata * False information encrypted and committed by a user * Incorrect environment or contract configuration ## Language policy Describe the SDK and network as **quantum-resistant**. Do not use “quantum-proof,” “unhackable,” “zero trust required,” or claims that exceed the implemented threat model. ## Beta policy Pin an exact SDK release. Validate changelog entries, generated types, chain configuration, and end-to-end encryption before upgrading production applications. --- # 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://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/architecture-and-security/threat-model-and-limitations.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.