> 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/terms-of-service.md).
# Terms of Service
**Last Updated:** 15 May 2026
### 1. Acceptance of Terms
By accessing or using Cryptic’s Services, you agree to these Terms of Service (“Terms”). If you do not agree, do not use the Services.
***
### 2. Nature of the Service
Cryptic provides software tools for:
* Secure communication
* Non-custodial digital wallet interaction
* Blockchain-based settlement
* Privacy-preserving financial workflows
Cryptic is **not** a bank, broker, custodian, or financial advisor.
***
### 3. User Responsibilities
You are solely responsible for:
* Safeguarding your private keys
* Maintaining device security
* Complying with applicable laws
* Understanding blockchain transaction risks
Cryptic cannot recover lost keys or reverse transactions.
***
### 4. No Financial or Investment Advice
Nothing provided through Cryptic constitutes legal, financial, or investment advice. Cryptic does not guarantee profits, returns, or outcomes.
The Cryptic token (***CT***), where applicable, is a **utility token** intended for platform participation and ecosystem alignment.
***
### 5. Prohibited Use
You agree not to use Cryptic for:
* Illegal activities
* Sanctions violations
* Fraud or deception
* Circumventing laws or regulations
* Harmful or malicious conduct
Cryptic reserves the right to restrict access for violations.
***
### 6. Intellectual Property
All software, branding, documentation, and content provided by Cryptic are protected by intellectual property laws. Users receive a limited, non-exclusive, non-transferable license to use the Services.
***
### 7. Third-Party Integrations
Cryptic may integrate third-party protocols or services. Cryptic is not responsible for third-party actions, outages, or losses.
***
### 8. Disclaimer of Warranties
The Services are provided **“as is”** and **“as available.”**
Cryptic makes no warranties regarding:
* Continuous availability
* Error-free operation
* Absolute security
* Compatibility with all devices or networks
***
### 9. Limitation of Liability
To the maximum extent permitted by law, Cryptic shall not be liable for:
* Loss of funds
* Loss of keys
* Network failures
* User errors
* Third-party actions
***
### 10. Forward-Looking Statements
Certain features, integrations, or roadmap items may be described as forward-looking and are subject to change.
***
### 11. Governing Law
These Terms shall be governed by the laws of \[Insert Jurisdiction], without regard to conflict-of-law principles.
***
### 12. Changes to Terms
Cryptic may update these Terms at any time. Continued use of the Services constitutes acceptance of updated Terms.
***
### 13. Contact
For legal or support inquiries:
---
# 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/legal/terms-of-service.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.