AgentforceAdvancedretentiongdprprivacycompliance
Plan data retention and deletion for agent conversation logs
Real World Scenario
GDPR erasure requests must delete customer chat transcripts but cases referencing conversation summaries must remain for legal holds.
Expected Answer
• Classify transcript fields vs derived summary fields with different retention rules
• Implement erasure API workflow cascading to related analytics stores
• Legal hold flags preventing deletion of linked case records
• Document lawful basis for retention periods per jurisdiction
• Anonymize analytics datasets replacing PII with pseudonymous keys
• Regular retention job with audit logs of deletions performed
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Classify transcript fields vs derived summary fields with different retention rules Also consider: Implement erasure API workflow cascading to related analytics stores In practice: Legal hold flags preventing deletion of linked case records Optimize for scale and operational observability.
Architect Perspective
Retention architecture must be designed pre-launch—GDPR erasure across LLM logs is painful retrofits.