> For the complete documentation index, see [llms.txt](https://docs.cloudback.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudback.it/troubleshooting-and-support/contact-us.md).

# Contact us

Get in touch with Cloudback support via email, submit issues or feature requests through our GitHub issue tracker, or find our company contact information.

## Contact us by email

Use any of these emails to contact us:

* Questions regarding our privacy policy: <privacy@cloudback.it>
* Questions about Cloudback functionality: <support@cloudback.it>

## Issue tracker

If you have any issues with the product or any ideas about how it can be improved, please feel free to raise a request using our [issue tracker](https://github.com/cloudback/issue-tracker):

* [Submit an issue](https://github.com/cloudback/issue-tracker/issues/new?template=bug_report.md)
* [Create a feature request](https://github.com/cloudback/issue-tracker/issues/new?template=feature_request.md)

## Company name and address

We are the MYRTLELABS S.A.S.

Address:\
Ecuador, Quito\
La Armenia, Juan Leon Mera y Numa Pompillo\
Conjunto Prados de la Armenia N9-960\
RUC 1793212306001\
Postal code 170803\
Email: <support@cloudback.it>\
Website: [cloudback.it](https://cloudback.it)


---

# 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://docs.cloudback.it/troubleshooting-and-support/contact-us.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.