'%3e%3cpath%20fill-rule='evenodd'%20clip-rule='evenodd'%20d='M0%2062.3176C0%2027.9001%2027.8995%200.00181961%2062.3134%200.00181961L62.3999%2062.2311C62.3999%2096.6462%2034.5004%20124.544%200.0852901%20124.544'%20fill='%233A3D3C'/%3e%3c/g%3e%3cpath%20d='M62.3994%2062.2461V0C96.8133%200%20124.713%2027.8982%20124.713%2062.3158'%20fill='url(%23paint0_linear_6331_3458)'/%3e%3cpath%20fill-rule='evenodd'%20clip-rule='evenodd'%20d='M45.617%2026.2827C47.7276%2026.2827%2049.4382%2027.9933%2049.4382%2030.1052C49.4382%2032.2146%2047.7276%2033.9252%2045.617%2033.9252C43.5064%2033.9252%2041.7958%2032.2146%2041.7958%2030.1052C41.7958%2027.9933%2043.5064%2026.2827%2045.617%2026.2827Z'%20fill='%23F9F6EF'/%3e%3cpath%20fill-rule='evenodd'%20clip-rule='evenodd'%20d='M45.6168%2045.2338C37.2596%2045.2338%2030.4857%2038.461%2030.4857%2030.1038C30.4857%2021.7454%2037.2596%2014.9702%2045.6168%2014.9702C53.9753%2014.9702%2060.7492%2021.7454%2060.7492%2030.1038C60.7492%2038.461%2053.9753%2045.2338%2045.6168%2045.2338ZM45.6168%2012.6686C35.9875%2012.6686%2028.1816%2020.4744%2028.1816%2030.1038C28.1816%2039.7308%2035.9875%2047.5378%2045.6168%2047.5378C55.245%2047.5378%2063.0508%2039.7308%2063.0508%2030.1038C63.0508%2020.4744%2055.245%2012.6686%2045.6168%2012.6686Z'%20fill='%23FECE01'/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_6331_3458'%20x1='62.2719'%20y1='4.01754'%20x2='108.703'%20y2='70.5262'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%239ED5CB'/%3e%3cstop%20offset='1'%20stop-color='%23FCE18E'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e)
AI assistant data handling
Target Audience: Developers building AI chat or embed experiences with Toucan AI.
TL;DR
- The AI assistant processes your questions, database metadata, and query results to answer and build visualizations.
- Conversation history is stored on the platform so users can continue a thread.
- Sub-agents (query building, chart building, exploration) run in isolated steps; only the main assistant thread keeps long-lived history.
- Third-party AI providers may receive prompts and context when AI features run — see Third-party subprocessors.
When to use this
Use this page when assessing privacy impact of AI chat, what may be retained after a session, and what may be sent to external AI services.
What the assistant processes
During a conversation, the assistant may use:
- User messages and assistant replies
- Database metadata (table and column names, descriptions) to understand your data model
- Query results from your connected database (for example previews or aggregated answers)
- Optional context from your embed integration (non-identifying clues you provide)
Query results used in AI workflows are fetched on demand from your database; they are not bulk-downloaded into a Toucan data store. See Data storage & retention.
What the assistant stores
| Item | Stored? | Notes |
|---|---|---|
| Conversation messages | Yes | Per user/thread; can be cleared in product |
| Structured “plans” for complex tasks | Yes | Linked to the conversation thread |
| Full copy of your database | No | Queries run against your DB when needed |
| Query result rows (platform-wide cache) | No | Results may appear inside a stored conversation |
Clearing a conversation removes that thread’s stored assistant history.
Third-party processing
Depending on configuration, AI requests may be processed by:
- An LLM provider (by default Anthropic, or another provider configured for your deployment)
- AI tracing (LangSmith, EU region), for the conversations the organization chooses to share: see which conversations are shared
- Product analytics, for usage events
Best practices
- Do not include personal data in optional AI context fields.
- Use row-level security so the assistant only queries data the end user is allowed to see.
- Clear conversation history when your product requires it (for example on logout or account closure workflows you implement).
- Review subprocessors if your compliance program requires a register of external processors.