What matters for your decision
Distinguish user-facing conversation history, analytics events and developer traces. They may need different access, redaction and deletion rules; contracts and applicable obligations can differ.
Check the boundary
- List fields in every transcript destination and strip passwords, tokens, unnecessary identifiers and payment details before they are stored where feasible.
- Limit which roles can access logs; define retention, deletion and exceptions separately for each system.
- Use synthetic canary values to confirm redaction and audit that they do not appear in exports or escalated tickets.