# Security model (/core/govern/security-model)



<CalloutContainer type="info">
  <CalloutDescription>
    **Target Audience**: Developers, security reviewers, and technical decision-makers integrating Toucan AI.
  </CalloutDescription>
</CalloutContainer>

### TL;DR [#tldr]

Toucan AI protects data with layered controls: short-lived embed tokens, organization isolation, row-level security on queries, encrypted database credentials, and clear boundaries between **platform data** and **your connected data**.

***

### What this section covers [#what-this-section-covers]

* [Data access boundaries](/core/govern/security-model/data-access-boundaries) — who can access what
* [Data storage & retention](/core/govern/security-model/data-storage-and-retention) — what Toucan stores, query data flow, caching
* [PII & personal data](/core/govern/security-model/pii-and-personal-data) — where personal data can appear and how to minimize it
* [Secrets & encryption](/core/govern/security-model/secrets-and-encryption) — credentials and tokens
* [Token security](/core/govern/security-model/token-security) — embed authentication
* [API security](https://github.com/ToucanToco/toucan-ai/blob/main/docs/govern/security-model/api-security.md) — access controls for APIs
* [AI assistant data handling](/core/govern/security-model/ai-assistant-data-handling) — conversations and AI workflows
* [Third-party subprocessors](/core/govern/security-model/third-party-subprocessors) — external providers that may process data

For embed-specific responsibilities, see also [Security boundaries](/core/embed/embedding-overview/security-boundaries).
