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

# Security and privacy

> In plain language: what the assistant sees, what it never does on its own, who sees what, and how your data is handled.

This page answers, without legalese, the questions everyone asks before putting company information into an AI tool. The formal commitments live in the [Terms of service](/morada-os/en/terms-of-service) and the [Privacy policy](/morada-os/en/privacy-policy).

***

## In one sentence

The assistant only sees what you could already see, only acts when you ask, and never changes anything outside Morada OS without your explicit approval.

***

## The four commitments

<CardGroup cols={2}>
  <Card title="Your data does not train AI models" icon="shield-halved">
    Your organization's conversations, files, and documents are never used to train or improve third-party AI models. Model providers are accessed under corporate agreements that restrict usage to generating the answer.
  </Card>

  <Card title="You approve before it happens" icon="hand">
    Every action that leaves Morada OS (sending an email, updating the CRM, posting a message) is assembled, shown in full, and only executed after you click **Aprovar** (Approve).
  </Card>

  <Card title="The assistant inherits your permissions" icon="user-lock">
    When you connect a tool, the assistant sees what **your** account sees in that service. It never widens an access you don't have.
  </Card>

  <Card title="Your conversations are yours" icon="comments">
    No administrator reads another person's conversation content. Management sees usage numbers only, never what was discussed.
  </Card>
</CardGroup>

***

## What the assistant sees

<AccordionGroup>
  <Accordion title="The files you send in the chat">
    Spreadsheets, documents, presentations, PDFs, images, and audio you attach are available to that conversation. Analysis runs in an isolated, temporary environment designed so your files neither leave it nor mix with another customer's.
  </Accordion>

  <Accordion title="The organization's knowledge base (Brain)">
    Documents your company added to the Brain (price tables, policies, manuals) are available to whoever has permission in that collection. Answers show which document the information came from, so you can check it.
  </Accordion>

  <Accordion title="The tools you connected">
    Nothing is accessed before you connect. Once connected, the assistant queries the service when your request calls for it, with your permissions, and you can disconnect at any time.
  </Accordion>

  <Accordion title="What it does NOT see">
    * Other people's conversations, including your own team's.
    * Documents in someone else's *Espaço Pessoal* (Personal space) in the Brain.
    * Data belonging to another customer organization. Morada OS data lives in a dedicated database, strictly separated by organization and workspace.
    * Tools you have not connected.
  </Accordion>
</AccordionGroup>

***

## Who sees what

| Content                             | Who sees it                                                                             |
| ----------------------------------- | --------------------------------------------------------------------------------------- |
| **Your conversations**              | Only you. Administrators see aggregated usage data, never the content.                  |
| **Files sent in a conversation**    | Whoever has access to that conversation, which means you.                               |
| **Brain: organization collections** | Whoever has permission in the collection, as configured by your company.                |
| **Brain: Personal space**           | The owner only.                                                                         |
| **Connected tools**                 | Only you, with your permissions in the service. Each person connects their own account. |

***

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does Morada.ai read our conversations?">
    Not as a routine. Morada.ai staff access is restricted to what is needed to operate and support the service, under the conditions set out in the contract. No content is used to train models.
  </Accordion>

  <Accordion title="What happens when someone leaves the company?">
    Access ends together with the corporate login. That person's history is preserved and becomes inaccessible: nobody inherits their conversations.
  </Accordion>

  <Accordion title="Can the assistant send an email or change something on its own?">
    No. Queries and reads run directly, because they change nothing. Anything that changes something outside Morada OS appears as an approval card with the full details and waits for your click. You can adjust or cancel.
  </Accordion>

  <Accordion title="How do I remove a tool's access?">
    Under **Conectores** (Connectors), open the tool's card and click **Desvincular** (Unlink). The stored authorization is deleted immediately. To end it on the provider's side as well, see the [page for IT teams](/morada-os/en/for-it-teams).
  </Accordion>

  <Accordion title="What if I send a file with customer data?">
    Morada OS is built to work with that kind of material, and every upload is recorded in audit trails tied to the user. Even so, send only what your company authorizes: your organization decides what enters the platform.
  </Accordion>

  <Accordion title="Which laws does Morada OS follow?">
    Data processing follows Brazil's LGPD (Law 13.709/2018), with the roles, legal bases, retention periods, and the Data Protection Officer channel described in the [Privacy policy](/morada-os/en/privacy-policy).
  </Accordion>
</AccordionGroup>

***

## Official documents

<Columns cols={3}>
  <Card title="Privacy policy" icon="shield-check" href="/morada-os/en/privacy-policy">
    Roles, legal bases, retention, and DPO contact.
  </Card>

  <Card title="Terms of service" icon="file-contract" href="/morada-os/en/terms-of-service">
    Usage conditions, responsibilities, and service levels.
  </Card>

  <Card title="For IT teams" icon="server" href="/morada-os/en/for-it-teams">
    What the administrator approves, why, and how to revoke on each provider.
  </Card>
</Columns>