> 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/pt/servicos-empresariais-avancados/zoom-node/zoom-chat-hybrid.md).

# Zoom Chat Híbrido

#### <mark style="color:azul;">Zoom chat Hybrid: Armazenando dados de chat e infraestrutura em seus data centers</mark> <a href="#r2h3pakzuasl" id="r2h3pakzuasl"></a>

O chat Hybrid permite que Clientes/clientes armazenem mensagens do Zoom chat, metadados e infraestrutura em seus próprios data centers, ajudando as empresas a dar suporte à conformidade para arquivamento de dados, retenção e requisitos regulatórios.

O chat Hybrid inclui recursos locais de indexação de chat em equipe, cache e armazenamento de banco de dados, concedendo a Clientes/clientes controle adicional sobre a residência dos dados e as políticas de retenção ao permitir que mensagens do usuário sejam localizadas em regiões configuradas. Além disso, o chat Hybrid se integra perfeitamente aos controles de política, como [barreiras de informação](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0066037), reforçando ainda mais a conformidade e protegendo informações confidenciais com armazenamento 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/pt/servicos-empresariais-avancados/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.