> 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/legal/vara-disclosures/complaints.md). # Complaints Process and contact information for submitting a complaint about products or services of the Backpack Exchange website or mobile application. ‍ You may file a complaint [here](https://forms.gle/SVUQEfQeRCu9QsEc6). You may also contact us at or submit your complaint in writing to: Trek Labs Ltd FZE dba Backpack Exchange Attn: 236 (6D) RME, Floor 02, The Offices 1 - One Central Dubai World Trade Centre Dubai, UAE If you are emailing or writing to us directly, please include the following information in your complaint: * Your name and account email address * Date of complaint * Your contact information * Details of your complaint * Any supporting documentation relating to your complaint We will acknowledge all complaints as soon as possible, but in no event later than one week of receiving your complaint.\ \ This complaints process applies solely to clients onboarded by Trek Labs Ltd FZE on the basis of declared UAE residency and UAE KYC completion. If your account was not onboarded on this basis, this process does not apply to you; other entities within the Backpack Exchange group may be subject to different complaints processes and policies as required by their respective jurisdictions. Please contact for assistance --- # 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/legal/vara-disclosures/complaints.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.