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

# Contact

How to reach TRNCH.

How to reach TRNCH.

## Email

Email is the main way to reach us: support (a swap, your volume, your packs, your account), privacy requests, press, and reports of a fake TRNCH token, a scam or a security issue.

[**hello@trnch.fun**](mailto:hello@trnch.fun)

## Telegram

* [**t.me/trnchfun**](https://t.me/trnchfun): official announcements.
* [**t.me/trnchtalk**](https://t.me/trnchtalk): the community chat. Questions, Heat finds and feedback.
* [**t.me/trnchalerts**](https://t.me/trnchalerts): live Heat alerts.

Admins never DM first.

## Partnerships

Write to [**partners@trnch.fun**](mailto:partners@trnch.fun) or on Telegram to [**@OxLegendz**](https://t.me/OxLegendz). See [Partners](https://docs.trnch.fun/partners).

## X

[**@trnchfun**](https://x.com/trnchfun). News and announcements.

## Report a fake TRNCH token or a scam

Any token using the TRNCH name is not ours, and the imitations we detect are hidden everywhere on the site.

If you see a token, a website, an account or a message pretending to be TRNCH, write to <hello@trnch.fun> with the token address or the link, and where you saw it. Found a security issue? Please tell us before making it public.

{% hint style="danger" %}
We will never ask for your recovery phrase or your private key, and we never ask you to send funds in a private message.
{% endhint %}

## Company

TRNCH is operated by **TrnchLabs - U SALGETU LLC**, 304 S Jones Blvd, Las Vegas, NV 89107, United States of America.

See also the [Terms of Use](https://docs.trnch.fun/legal/terms), the [Privacy Policy](https://docs.trnch.fun/legal/privacy) and the [Risk Disclosure](https://docs.trnch.fun/legal/risk).


---

# 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.trnch.fun/contact.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.
