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

---
title: "Privacy"
description: "See the data categories Lithi may handle, how AI-assisted work stays scoped to a task, when connected services change the path, and how to make a privacy request."
route: "/trust/privacy"
page_id: "trust-privacy"
locale: "en-US"
source_locale: "en-US"
last_updated: "2026-09-03"
audience: "Privacy reviewers, procurement, and account administrators"
voice: "A"
purpose: "Explain meaningful data categories, AI-assisted task scope, connected-provider exceptions, and privacy choices."
source_status: APPROVED
source_version: "trust-privacy-en-us-2026-09-03-fifteen-route-v1"
robots: noindex
---

# Privacy

Lithi handles different data categories for different purposes. What is relevant depends on the product and the task; your connection choices determine when a provider path is involved.

## The data categories that matter

The relevant category depends on what you ask Lithi to do:

- **Account and contact details:** name, email address, organization details, and information needed to administer access or answer a request.
- **Team and workspace records:** members, roles, settings, and other records needed to operate a shared workspace.
- **Service and connection records:** the selected service, account or resource, permission state, configuration, and visible connection activity.
- **Work context and outputs:** approved references, instructions, task results, and records your workflow creates or asks Lithi to return.
- **Support and security details:** the information you choose to include when asking for help or reporting a concern.

These categories are a practical guide, not an exhaustive field list. The purpose, selected scope, and terms that govern your account determine what is relevant.

## How an AI-assisted task stays scoped

The data boundary for AI-assisted work depends on the product, task, selected sources, permissions, service path, and current commercial terms. Before relying on a broad statement about training, retention, logging, or deletion, match it to the exact workflow and provider involved.

Keep approved sources, account records, connection data, and operational records as separate categories. A permission to use one source for one purpose should not be treated as permission to use every source for every purpose. Ask for the current contract and provider record when a decision depends on model training, prompt retention, diagnostic logging, human access, regional processing, or deletion.

## When a provider is connected

Connecting a provider can change the path for selected records. You choose the service, account, resource, purpose, and scope; data movement depends on that choice and on the selected service's handling. A connection does not authorize unrelated accounts or resources.

Review the permissions shown during setup and remove a connection when its purpose ends. For the related service boundary, read [Compute security](/trust/security) and the [subprocessor overview](/trust/subprocessors).

## Make a privacy request

You can ask about access, correction, or deletion of information. Email [privacy@lithi.ai](mailto:privacy@lithi.ai) with the request type, account or organization context, and enough detail to identify the relevant information or activity.

Send the minimum necessary context. Do not include passwords, access codes, payment credentials, private message bodies, or unrelated personal information in your first message. Lithi may need to confirm authority and clarify scope before discussing account-specific information.

## Read the governing terms

This page is an orientation. The [Privacy Policy](/legal/privacy) and [Data Processing Agreement](/legal/dpa) provide the governing legal text for the terms that apply to your account.

## Related links

- [Review data and processing boundaries](/trust/data)
- [Review compliance and assurance](/trust/compliance)

## Primary action

[Email privacy@lithi.ai](mailto:privacy@lithi.ai) with your request type and account context. Do not send passwords, access codes, or private message bodies.