> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/organization-settings/others/sub-processors.md).

# Sub-processors

The full list of data sub-processors Luciq uses to deliver the platform, what each one supports, and how they apply across all accounts.

Luciq uses the following subprocessors to assist it in providing the service as described in our [Terms of Service](https://www.luciq.ai/terms).

These Data Subprocessors apply to all customers who utilize the Luciq platform and are agnostic of product utilization.

| Entity Name         | Processing Activities                  | Entity Country |
| ------------------- | -------------------------------------- | -------------- |
| Airbrake            | Quality Assurance and Support Services | United States  |
| Amazon Web Services | Cloud Service Provider                 | United States  |
| Fivetran, Inc.      | Data integration services              | United States  |
| Looker              | Data visualization tool                | United States  |
| MailChimp           | Mail Service Provider                  | United States  |
| Hubspot             | Marketing Automation                   | United States  |
| New Relic, Inc.     | Quality Assurance and Support Services | United States  |
| OpenAI, LLC         | AI-powered product features            | United States  |
| Pusher, Ltd.        | Realtime updates                       | United Kingdom |
| Salesforce.com      | Customer relations management          | United States  |
| Segment             | Event management platform              | United States  |
| Stripe              | Payment provider                       | United States  |
| Totango             | Customer relations management          | United States  |
| Zapier              | Developer tool and data connector      | United States  |
| Census              | Data Integration Services              | United States  |

For how Luciq's AI capabilities process and retain data, see [AI Privacy & Data Retention](/organization-settings/ai-privacy-and-data-retention.md).

These Data Subprocessors may be utilized to support customers who may elect to share personal data with Luciq’s support personnel.

| Entity Name   | Processing Activities                        | Entity Country |
| ------------- | -------------------------------------------- | -------------- |
| Atlassian     | Software development and collaboration tools | Australia      |
| Intercom Inc. | Support helpdesk                             | United States  |
| Slack, Inc.   | Internal Communication                       | United States  |


---

# 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.luciq.ai/organization-settings/others/sub-processors.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.