> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mithunai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Subprocessors: the services your data is sent to

> The hosted service stores data with Hetzner Cloud in Germany, uses NVIDIA models and Resend email. Other services receive data only when switched on.

The hosted MITHUNAI service uses three outside services for every organisation: Hetzner Cloud, which hosts the servers in Germany; NVIDIA, whose models write answers and embed your content; and Resend, which delivers invitation and password-reset email. Any other service receives your data only when it is switched on, by MITHUNAI for the deployment or by your organisation for itself. The list is given for information. It is not yet a contractual list, and there is no notice of changes to it yet.

## Always used

| Service | What it does | What it receives | Location |
| - | - | - | - |
| Hetzner Cloud | Hosts the servers | Everything the service stores, at rest | Germany |
| NVIDIA | Answer and embedding models | Your content when it is embedded, and each question with the passages retrieved for it | Per NVIDIA's terms |
| Resend | Delivers invitation, password-reset and access-request email | The recipient's address and the message, which carries your organisation's name, the sender's name and a single-use link. No content from your sources | Per Resend's terms |

MITHUNAI does not train models on your content. Each provider processes what it receives under its own terms. See [Models and providers](https://docs.mithunai.com/assistants/models-and-providers.md).

## Used only when switched on

| Service | When | What it receives |
| - | - | - |
| OpenAI, Anthropic, Perplexity | Your organisation turns an engine on for [AI search visibility](https://docs.mithunai.com/analyze/ai-search-visibility.md) | The buyer questions your organisation wrote, nothing else |
| Slack | Your organisation connects a workspace to the [Slack bot](https://docs.mithunai.com/channels/slack.md) | The question asked in Slack, and the answer with its source titles and links |
| The model provider behind the Gateway | You use [Chat](https://docs.mithunai.com/chat/overview.md) or send requests through the [Gateway](https://docs.mithunai.com/gateway/overview.md) | Your messages and requests |

## Services you connect

When your organisation connects a source or gives an AI employee a tool, MITHUNAI contacts that service on your instruction, with your own saved token where one is needed, and sends that token nowhere else: websites and sitemaps, GitHub, Confluence, Jira, Notion, Zendesk, Discourse, and for AI employees helpdesks, CRMs, mailboxes, identity providers and monitoring tools. These are your own vendors, under your own contracts with them. See [Saved connections](https://docs.mithunai.com/knowledge/connections.md) and [Connect your tools](https://docs.mithunai.com/team/connect-your-tools.md).

## Services that receive none of your content

Let's Encrypt issues the TLS certificates, the documentation site is hosted by Mintlify, and the marketing site at [www.mithunai.com](http://www.mithunai.com) is hosted by Vercel. None of them receives anything from your organisation's use of the product.

## Related pages

* [Where MITHUNAI runs](https://docs.mithunai.com/administration/deployment.md): what a deployment calls outside itself.
* [Data handling](https://docs.mithunai.com/trust/data-handling.md): what is stored and for how long.
* [Compliance](https://docs.mithunai.com/resources/compliance.md): what MITHUNAI can and cannot claim.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.