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

# Security

> The security questions we get asked the most, with short answers and a link to the detail.

> [card] Your data is never mixed
>
> Each company works in its own workspace. Nobody from another company sees yours.

> [card] Your chats are yours
>
> Your teammates and the admin don't see them.

> [card] We don't train AI on your data
>
> The model answers and keeps nothing.

> [card] Nothing changes without permission
>
> Before creating, changing or sending something, it asks for your approval.

<video controls preload="metadata" src="https://mintcdn.com/tuquillc/Vkw4c72FgxX9ZuU9/videos/seguridad-en.mp4?fit=max&auto=format&n=Vkw4c72FgxX9ZuU9&q=85&s=42f1308ecd3d96150878eea900c4b586" poster="/images/seguridad-video-en.jpg" />

## Your data

### Can another company see my data?

No. Each company works in its own workspace, isolated from the rest. It works like your email: your provider serves millions of people, and nobody can read someone else's mail.

### Do you use my data to train AI?

No. We don't use your conversations or your data to train models. The AI providers we use don't use them to train theirs either. See the [Privacy Policy](https://docs.tuqui.com/en/privacy.md#3-how-we-use-your-data).

### Does the AI "learn" what's in my company and tell others?

No. The AI model isn't a person who remembers: it gets what it needs to answer your question, answers, and keeps nothing. What is kept (your conversations and the memories you or your team choose to save) stays in your workspace.

### What does Tuqui keep?

Your conversations, with what shows up in them, so you can pick them up again. Also the files you upload, memories and the reports you create. We don't keep a copy of the systems you connect: Tuqui queries them when you ask something. From the activity log we keep which tool was used and when, without your business data. See [Data retention](https://docs.tuqui.com/en/privacy.md#8-data-retention).

### Which providers receive my data?

To answer you, Tuqui sends your question and what it read to an AI provider, depending on the model each feature uses. No provider receives your passwords or credentials. The list of services, with the data each one receives, is in [Third-party services](https://docs.tuqui.com/en/privacy.md#4-third-party-services).

### If I use Tuqui from Claude or ChatGPT, who sees my data?

In that case the assistant belongs to Anthropic or OpenAI: what Tuqui reads reaches that assistant, under the terms of your account there. Tuqui only gives it access to your data.

### Where is my data stored?

In the United States: Tuqui's database, files and service. If you're in Europe, the United Kingdom or Switzerland, transfers are covered by the [DPA](https://docs.tuqui.com/en/dpa.md). See [International transfers](https://docs.tuqui.com/en/privacy.md#11-international-transfers).

### How do I delete my data?

You can delete a message, a conversation or a file from the chat at any time, and it's deleted right away. If you delete your account or the workspace, everything is deleted, backups included, within 90 days. See [Delete your account](https://docs.tuqui.com/en/delete-account.md).

## Your conversations

### Can my teammates or the admin read my conversations?

No. Your conversations with Tuqui are yours: other workspace members don't see them, and neither do admins.

What the admin does see are conversations that don't belong to a person: those of published agents, webhooks and scheduled tasks.

### What about what I upload to a project?

A project's files are visible to the people who have access to that project, and nobody else. Conversations inside the project are still each person's own.

### I connected my email or my files. Can anyone else read them?

No. Each person connects their own account, and Tuqui uses it only in your conversations, when you ask for something. Your teammates don't see your email. If you disconnect the account or leave the workspace, Tuqui deletes the access.

### Can someone at Tuqui read my conversations?

Only a small group of the team, and only for four things: supporting you when you ask, fixing an incident, investigating abuse or complying with a legal request. See [Who can see your chat conversations](https://docs.tuqui.com/en/privacy.md#7-who-can-see-your-chat-conversations).

### What about the reports I share?

Chat files are private and open through links that expire. The exception is an artifact you share with a public link: anyone with the link can see it, until you turn it off or it expires.

## What Tuqui sees and what it can do

### Can Tuqui see more than I can?

No. In every system you connect, Tuqui works with your user or your account, with your permissions. What that system doesn't let you see, Tuqui doesn't see either.

### Can Tuqui change or delete data?

By default, it only reads. For it to create, change, delete or send something, an admin has to enable it, and even then Tuqui can never do more than your own user is allowed to.

### Does it ask before changing something?

In the chat, by default yes: before creating, changing or sending something, Tuqui shows you what it's going to do and waits for your approval. Deleting records always asks for your confirmation, and so do actions that can't be undone (like posting an invoice or sending an email).

If you choose **Always allow**, that tool stops asking you, in that workspace. Nothing changes for your teammates.

> [!TIP]
>
> If you're an admin and don't want a tool used, deny it in **Settings → Permissions**. What the admin denies, nobody enables, not even with **Always allow**.

### Can I limit what each person does?

Yes. An admin can take away all the tools that write from a member, or some of them, in **Settings → Members**. That person can still ask questions. See [Per-member permissions](https://docs.tuqui.com/en/write-models.md#per-member-permissions).

### Is there a record of what Tuqui did?

Yes. Tuqui keeps a log of every action: which tool, on what, which user, when and with what result, without your business data. You can request it at [hello@tuqui.com](mailto:hello@tuqui.com). And whatever Tuqui changes in a system is recorded in that system under the user it worked with. See [Activity log](https://docs.tuqui.com/en/terms.md#4-2-activity-log).

## Agents and automated tasks

### Which user does an agent use when it works on its own?

An agent that answers on your website, on WhatsApp or in its automations (when it runs on its own, on a schedule) works with a **service account**: a workspace member with no person behind it, created for that. Not a person's account. That way, what the agent does is signed by that account and doesn't inherit anyone's permissions. See [The service identity](https://docs.tuqui.com/en/agents.md#the-service-identity).

### Does anyone approve what the agent does?

Not always. When an agent works on its own, there may be nobody on the other side to approve. There, it does what it has enabled without asking for approval. The exception is deleting records and actions that can't be undone: with no person to approve them, they're refused.

That's why what limits an agent is what you give it: its permissions, its data and its tools.

### What should I do before opening an agent to the public?

1. **Give the service account its own permissions**, only for what the agent needs. Never an administrator's.
2. **Start read-only.** If later it has to create something (a quotation, an appointment), enable that, and nothing else.
3. **Give it only the data anyone who talks to it may see.** Anyone can ask the agent a question, and whatever it knows, it can tell.
4. **Try it yourself before publishing it**, with the hard questions a customer would ask.

### Who is responsible for what a published agent does?

The workspace that publishes it: it decides which data and permissions the agent has and who it's open to. See [Published agents and channels with nobody on the other side](https://docs.tuqui.com/en/terms.md#5-6-published-agents-and-channels-with-nobody-on-the-other-side).

## Your account and your team

### How do I protect my account?

Turn on [two-step verification](https://docs.tuqui.com/en/two-factor.md). If you're an admin, you can require it for the whole workspace.

### What happens when someone leaves the company?

An admin removes them from the workspace in **Settings → Members**. From then on they lose access, and Tuqui deletes the access that person had given to their connected accounts.

## If you connect Odoo

### Does Tuqui respect each Odoo user's permissions?

Yes. Tuqui queries Odoo with each person's user, and Odoo applies the same permissions as on screen: access groups and record rules. If a salesperson has no access to accounting, they don't see it through Tuqui either.

### I hid a field in an Odoo view, but Tuqui shows it. Why?

Because hiding a field in a view is not a permission. Odoo hands that field to any data access: to Tuqui, to an Excel export or to an integration. Tuqui doesn't see views: it sees the data Odoo lets the user read.

If someone must not see a piece of data, restrict it with Odoo permissions: an access group on the field or a record rule. That way it stays hidden everywhere, Tuqui included.

> [!TIP]
>
> To review what each user can see before you enable Tuqui, see [Audit permissions](https://docs.tuqui.com/en/caso-auditar-permisos.md).

### Is there Odoo data Tuqui never reads?

Yes. Tuqui doesn't read passwords, tokens, two-step verification keys or sessions, even if the user can. See [Odoo data](https://docs.tuqui.com/en/odoo-data.md).

### Does Tuqui use any Odoo user besides mine?

For your questions, no: it uses yours. To learn the structure of your Odoo (which models and fields exist, and the company profile), Tuqui uses a read-only access of the workspace. That access writes nothing.

### Can several people share one Odoo user?

You can: each person still has their own Tuqui user, with their own conversations. But in Odoo they all see the same as that user, and whatever Tuqui changes is recorded under it, so you can't tell who asked for what. For security, one Odoo user per person is best. How to set it up: [Several people with the same Odoo user](https://docs.tuqui.com/en/members.md#several-people-with-the-same-odoo-user).

### How do I enable writing in Odoo?

An admin enables each Odoo model and each operation (create, write, delete, execute) separately. See [Write models](https://docs.tuqui.com/en/write-models.md).

### Can Tuqui slow down my Odoo?

Tuqui makes the same kind of queries a person would make on screen, with a limit on steps per request. A very broad query over a lot of data uses resources, just like a heavy report. See [Use of your Odoo's resources](https://docs.tuqui.com/en/terms.md#4-1-use-of-your-odoo’s-resources).

### How do I cut Tuqui's access to my Odoo?

At any time. If you connected with the Tuqui module, use **Disconnect** in Odoo's settings; **View access log** shows every query it made. If you connected with an API key, revoke it in Odoo. See [Tuqui module for Odoo](https://docs.tuqui.com/en/companion.md#disconnect).

## Compliance and support

### Do you comply with GDPR and Swiss law?

Yes. The [Data Processing Agreement (DPA)](https://docs.tuqui.com/en/dpa.md) is part of the terms and covers the EU and UK GDPR, and the Swiss nFADP.

### If something goes wrong, who helps me?

If you got Tuqui through a partner, your partner is your first contact. If not, write to [hello@tuqui.com](mailto:hello@tuqui.com). Tuqui is a tool: permissions, approvals and backups of your systems are decided by whoever runs them. See [Support](https://docs.tuqui.com/en/terms.md#11-support).

### Where do I report a security issue?

Write to [hello@tuqui.com](mailto:hello@tuqui.com).


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