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

# Data privacy, retention, and model boundaries

> Evaluate Entelligence source data, derived analytics, prompts, logs, retention, deletion, residency, model providers, and support access.

Entelligence products can process source code, pull requests, logs, incidents, tickets, messages, documents, meeting data, agent-session metrics, and model-routing context. Review each enabled product separately.

## Public privacy statement

The current [Entelligence privacy policy](https://entelligence.ai/privacy-policy) describes personal-data processing, U.S. processing and transfers, data-subject rights, and retention language. It states that service data is retained for the customer relationship and for a period afterward, and that verified data subjects can request deletion subject to applicable exceptions.

<Warning>
  The public policy is not a product-specific data-flow specification and does not provide an exact retention period for every Entelligence dataset. Use the DPA, security package, and order form for enforceable product and deployment terms.
</Warning>

## Privacy review

For every enabled workflow, confirm:

* Fields read and written
* Raw versus derived data
* Storage, cache, and backups
* Retention and deletion periods
* Processing region and transfers
* Encryption in transit and at rest
* Tenant isolation
* Subprocessors and model providers
* Model training and provider retention terms
* Support and debugging access
* Export, legal hold, and deletion evidence

## Product-specific boundaries

| Product          | Review                                                                                |
| ---------------- | ------------------------------------------------------------------------------------- |
| Code Review      | Private code, diffs, repository context, comments, statuses, and suggestions          |
| Agent Insights   | Local or centralized sessions, computed metrics, identity, usage, spend, and outcomes |
| Ask Ellie        | Cross-source question context, citations, and action destinations                     |
| Code Reliability | Logs, incident evidence, fixes, tickets, and monitoring                               |
| Documentation    | Repository-derived content, storage, sharing, and export                              |
| Model Router     | Request/response context, provider routing, credentials, and session metadata         |
| Automations      | Event source, instructions, recipients, schedules, and external writes                |

## Agent Insights

The documented standard CLI workflow synchronizes structured session and task metrics. Raw transcript synchronization is a separate opt-in mode where supported. Verify the installed CLI help, uploaded schema, centralized connector behavior, and member notice before rollout.

## Secrets

Redact production logs at the source. Keep API and provider keys in an approved secret store. Do not embed secrets in guidelines, AGENTS.md, prompts, automation instructions, screenshots, or support messages.

## Deletion and revocation exercise

Test one member, repository, connector, API key, and exported destination. Record:

* What access stops immediately
* What data disappears from the product
* What remains historically
* What remains in backups
* Which evidence confirms completion
* Which contractual exceptions apply

For personal-data requests, use the contact published in the current privacy policy.

## Next step

Review [architecture](/enterprise/architecture) and [API-key administration](/administration/api-keys).