---
title: "How your data is handled"
description: "What Curade keeps, who can see it, what CLEO sends to its AI provider, how it is protected, how long it is kept and your choices."
url: https://curade.ai/en/curade/docs/data-and-privacy/data-handling/
product: "Curade"
version: "3.0.0"
breadcrumbs:
  - "Curade docs"
  - "Data and privacy"
  - "How your data is handled"
---

# How your data is handled

What Curade keeps, who can see it, what CLEO sends to its AI provider, how it is protected, how long it is kept and your choices.

Curade keeps what it needs to run each tenant: the data it collects from the tenant's sources, the accounts of the people who use it and what they create in it.

## What is kept

- Accounts: each person's username, email address, password and roles. The password is never stored in readable form.
- Tenants: each tenant's name, status, responsible engineers, logo and AI model, with the AI provider token, and each source's address and access token.
- Monitoring data: the inventory of hosts, applications and services, host and disk readings, and transactions, collected from the tenant's sources ([Data collection](https://curade.ai/en/curade/docs/concepts/data-collection/)).
- What people create: dashboards, chats with CLEO and the files attached to them, reports and their recipients, and each tenant's configuration.

Pipelines, their builds and the automation credentials live on the automation server that Curade drives, not in Curade itself.

## Who can see it

- What you see depends on your platform role and on your role in each tenant ([Roles and permissions](https://curade.ai/en/curade/docs/administration/roles-and-permissions/)).
- A dashboard shows to the rest of its tenant as its visibility allows, and a new one starts **Private** ([Dashboard](https://curade.ai/en/curade/docs/features/dashboard/#visibility)).
- A chat with CLEO shows to the rest of its tenant as its visibility allows, and a new one starts **Read Only** ([CLEO](https://curade.ai/en/curade/docs/features/cleo/#chats)).
- What you send CLEO goes to the AI provider chosen for the tenant ([What CLEO sends](https://curade.ai/en/curade/docs/data-and-privacy/data-handling/#cleo)).

## What CLEO sends

To answer, CLEO sends your question, the chat so far, any files you attach and the data it looks up to the AI provider chosen for the tenant. CLEO only reads: it cannot change your environment or run a pipeline.

## How it is protected

Access controls let each account see only what its platform role and tenant roles allow. Your password is never stored in readable form, and once saved, a source token, an AI provider token or an automation credential is never shown again.

## How long it is kept

Most of what Curade keeps stays until someone deletes it: deleting a tenant deletes everything in it, and deleting an account deletes the dashboards and chats it owns. Host, disk and transaction history is kept for seven years.

## Your choices

You decide who else sees your dashboards and your chats with CLEO through their visibility, and you can delete the ones you own. A Platform Admin changes your roles and password, and deletes accounts ([Manage users](https://curade.ai/en/curade/docs/administration/managing-users/)).