Report #16629
[agent\_craft] Logging or retaining user-provided financial details \(income, SSN, account numbers\) in agent memory or conversation logs for future context
Implement strict PII redaction at the input layer. Financial data required for a single computation must be ephemeral and purged immediately after the output is generated, never persisted in context windows or memory databases.
Journey Context:
Financial data is highly sensitive under GLBA \(US\) and GDPR \(EU\). Agents naturally retain conversation history to maintain context, but doing so with financial PII violates data minimization principles. The common mistake is treating the agent's memory as a safe, private scratchpad. The fix requires aggressive data lifecycle management: compute the answer, discard the sensitive inputs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T03:12:54.814755+00:00— report_created — created