> For the complete documentation index, see [llms.txt](https://guide.touchguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.touchguild.com/data-and-analytics.md).

# Data & Analytics

{% hint style="danger" %}
This page may not provide all the details. 

For comprehensive information, please refer to our [Privacy Policy](/privacy-policy.md).
{% endhint %}

## What do we collect?

* Your Data Collection Profile grouping the following properties: appID, appName, appShortname, appUserID, build, buildVersion, guildCount, ownerID.
* Trigger events when executing methods such as "gateway\_connection" or even "cache\_get\_members", most of them passing no data, or some data such as latency in ms for example.

This is a huge step forward for us to analyze the behavior of our developers, making decisions based on our accurate dataset, but also study the behavior of our library, providing useful information for us to analyze.

The Data Collection Profile is useful to assign data to specific apps, for filtering, making us able to make averages per user for example.

### Is it enabled by default?

**Yes** it is enabled by default for us to improve the library.

### Opting out

If you're concerned, we remain transparent, you can check the source-code of the library, or even disable it accordingly by setting the "dataCollection" client option to false.

*Example:*

```typescript
const client = new Client({ token: "TOKEN", dataCollection: false });
```

### Request data or data deletion

If we've already collected data about your app, you can request data deletion by contacting us:

<support@dinographicpixels.com>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.touchguild.com/data-and-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.