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

# Terms of Service

You can review our **Terms of Service** for Backpack EU below:

{% file src="/files/a2PToPEag03xqHNPmVth" %}

**Risk warning: Our products are traded on margin and carry a high level of risk and it is possible to lose all of your capital. Please consider our** [**Risk Disclosure**](broken://pages/zocmYdja4LPbWq71klPZ)**.**

**Legal**: This website is operated by Trek Labs Europe Ltd, registration number HE335683, with registered address at Aiolou & Panagioti Diomidous 9, Katholiki, 3020 Limassol, Cyprus. Trek Labs Europe Ltd is authorized and regulated by the Cyprus Securities and Exchange Commission (CySEC) under license number 273/15.

The company operates through [https://eu.backpack.exchange](https://eu.backpack.exchange/) and uses the trade name Backpack EU.

<details>

<summary><strong>Archive</strong></summary>

| Document                                                                                                                                                                                                                                                                                                  | Effective     | Superseded    |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------------- |
| [Terms of Service February 2025.pdf](https://1878960828-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzERL3fdDfemT8huqDaW%2Fuploads%2FwvJg9KmbQboKJH16zOXx%2FBackpack%20EU%20-%20Terms%20of%20Service%20February%202025.pdf?alt=media\&token=5fb90cfc-6f12-4412-98ea-e1a566037c3d) | February 2025 | August 2025   |
| [Terms of Service August 2025.pdf](https://1878960828-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzERL3fdDfemT8huqDaW%2Fuploads%2F4JqhlLHrROAzhPVnoxSz%2FTerms%20of%20Service.pdf?alt=media\&token=d4071e1e-c265-4311-b911-c6638bf3407a)                                         | August 2025   | November 2025 |
| [Terms of Service November 2025.pdf](https://1878960828-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzERL3fdDfemT8huqDaW%2Fuploads%2F0yYDkKPwmKHqrI0Ildwq%2FBackpack%20EU%20-%20Terms%20of%20Service%20November%202025.pdf?alt=media\&token=03617f06-15a5-48db-a6a7-8f43bbd41464) | November 2025 | June 2026     |

</details>


---

# 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://eu.support.backpack.exchange/legal-documentation/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.