> For the complete documentation index, see [llms.txt](https://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://support.backpack.exchange/support-docs/cn/falxin-xi/vara-disclosures/vara-license-information.md). # VARA License Information Information regarding the Backpack Exchange VARA license including license number, licensed activities and names of all responsible individuals. ‍ **License Number** License No. VL/23/07/001 ‍ **Licensed Activities** **Trek Labs Ltd FZE** is licensed and regulated by the **Dubai Virtual Assets Regulatory Authority (VARA)** under an **Exchange Services License**.\ \ This authorises us to operate as a virtual asset exchange in the UAE and provide **Spot Trading Services** (i.e., trading virtual assets for immediate settlement).\ \ Our VARA license **does not cover Futures or Margin Trading**, and these services are therefore **not available in the UAE**.\ \ This License covers those users onboarded by **Trek Labs Ltd FZE** on the basis of declared UAE residency and satisfactory completion of UAE KYC requirements. It does not extend to any other entity operating under the Backpack Exchange brand. ‍ **Names of All Responsible Individuals** Vrunda Pandya, Head of Compliance Nicholas Ting, Head of Operations --- # 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://support.backpack.exchange/support-docs/cn/falxin-xi/vara-disclosures/vara-license-information.md?ask=&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.