> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/technical-details/how-we-process-data-from-third-party-integrations.md).

# Data Processing from Integrations

As a data platform, HockeyStack is more powerful when it is connected with [other data sources](https://hockeystack.com/integrations). We can pull all kinds of marketing, sales, and even customer support data from these third-party tools. This guide aims to answer any concerns on the security side of this data flow.

Although the kind of data we pull differs vastly depending on the integration, we don’t process or store any data that you can’t see within your HockeyStack dashboard.

We need to store some PII (Personally Identifiable Information) for integrations such as CRMs and customer support tools in order to show you a full account-based journey. However this is limited to data such as:

* Email address (in most integrations that have a User entity)
* Contact name (in CRMs)
* Message content (in customer support tools)


---

# 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.hockeystack.com/technical-details/how-we-process-data-from-third-party-integrations.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.