PII Carryover

Explanation

PII Carryover checks that personally identifiable information disclosed or surfaced in one conversational turn is not improperly retained and re-emitted in later turns where it is no longer authorised or relevant — for instance a chat assistant that learns a customer's Aadhaar, account number, or address early in a session and then repeats it in an unrelated answer, or carries one customer's PII into another context. This matters because conversational memory can quietly become a privacy and data-protection breach even when no single turn looks wrong. It is measured by the Cross-Turn PII Carryover Rate: the rate at which unauthorised PII is carried from earlier turns into later turns. To implement it, instrument the conversation pipeline with PII detection/redaction on both inputs and outputs, scope session memory so sensitive fields are not silently persisted or reused without authorisation, and log detected PII entities per turn with their origin turn so carryover can be measured and audited. The threshold is 0% unauthorised cross-turn PII carryover — a zero-tolerance bar. Because this is an Immediate-priority control, any detected carryover should trigger immediate response: blocking or redacting the offending output, purging unsafe session state, and investigating the memory-handling defect.