Skip to main content
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 and the 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

Your data does not train AI models

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.

You approve before it happens

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).

The assistant inherits your permissions

When you connect a tool, the assistant sees what your account sees in that service. It never widens an access you don’t have.

Your conversations are yours

No administrator reads another person’s conversation content. Management sees usage numbers only, never what was discussed.

​
What the assistant sees

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.
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.
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.
  • 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.

​
Who sees what

​
Frequently asked questions

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.
Access ends together with the corporate login. That person’s history is preserved and becomes inaccessible: nobody inherits their conversations.
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.
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 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.
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.

​
Official documents

Privacy policy

Roles, legal bases, retention, and DPO contact.

Terms of service

Usage conditions, responsibilities, and service levels.

For IT teams

What the administrator approves, why, and how to revoke on each provider.