> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/technical-library/fr/services-avances-pour-lentreprise/zoom-node/zoom-chat-hybrid.md).

# Zoom Chat hybride

#### <mark style="color:bleu;">Zoom chat hybride : stocker les données de chat et l’infrastructure dans vos centres de données</mark> <a href="#r2h3pakzuasl" id="r2h3pakzuasl"></a>

Chat Hybrid permet aux Clients de stocker les messages, les métadonnées et l’infrastructure Zoom chat dans leurs propres centres de données, aidant les entreprises à assurer la conformité pour l’archivage des données, la conservation et les exigences réglementaires.

Chat Hybrid inclut des capacités sur site d’indexation, de mise en cache et de stockage de base de données du chat de groupe, offrant aux Clients un contrôle supplémentaire sur la résidence des données et les politiques de conservation en permettant de localiser les messages utilisateur dans les régions configurées. De plus, Chat Hybrid s’intègre de manière transparente aux contrôles de stratégie, comme [barrières d’information](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0066037), renforçant davantage la conformité tout en protégeant les informations sensibles grâce au stockage local.


---

# 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://library.zoom.com/technical-library/fr/services-avances-pour-lentreprise/zoom-node/zoom-chat-hybrid.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.