> For the complete documentation index, see [llms.txt](https://card.payprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://card.payprotocol.io/legal-and-compliance/terms-of-service.md).

# Terms of Service

### Terms of Service

The Terms of Service (ToS) outline your rights and responsibilities as a PayProtocol user.

***

#### 📃 Overview

* Your use of the PayProtocol app and Card signifies acceptance of these terms.
* It includes:
  * Non-custody wallet services where you control your private keys
  * IBAN accounts and MasterCard services through Fiat24
  * Wrap and unwrap cryptocurrency services
  * Account creation and security requirements
  * ID verification (KYC) requirements for certain services
  * Prohibited activities and user obligations
  * Intellectual property rights
  * Risk disclosures for digital assets
  * Limitation of liability and indemnification clauses
  * Termination conditions and dispute resolution

> The full document can be reviewed on the official [Terms of Service](https://web.payprotocol.ch/terms/en/terms_of_service.html) page.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://card.payprotocol.io/legal-and-compliance/terms-of-service.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
