AgentforceArchitect (Hardest)retentionpiicompliance
Architect data retention and PII redaction for agent conversation logs
Real World Scenario
GDPR erasure request cannot remove customer data from agent logs replicated to data lake; legal holds deployment.
Expected Answer
• Define retention periods per data class at architecture phase
• Store conversation Id linked to CRM contact for erasure propagation
• Redact PII in logs used for analytics; separate audit vault with stricter access
• Automate erasure workflow across CRM, logs, and training exports
• Minimize PII in prompts — retrieve on demand with auth not preload
• Contractual limits on vendor log retention for Einstein Trust Layer
• Document lawful basis for log processing in DPIA
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Define retention periods per data class at architecture phase Also consider: Store conversation Id linked to CRM contact for erasure propagation In practice: Redact PII in logs used for analytics; separate audit vault with stricter access Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Agent logs are personal data repositories — design erasure before storing millions of transcripts.