The papers handed to a bank at the start of a relationship do not evaporate when the relationship ends. They sit in retention systems, get referenced in inherited files, occasionally surface in filings when the bank itself is acquired or sued. Years later, that trailing paper is often the sharpest part of a subject's footprint, and it names things the subject has long since edited out of their own story.
Documents persist past the relationship; they sit in the institution's records for retention periods that are often longer than the person realizes. They are referenced in audits, reviewed in later refreshes, and sometimes circulated within institutional groups under intercompany sharing arrangements. They occasionally surface in public actions against the institution, where the person's submission becomes part of a public filing.
They also leak. Not often, and not in the way breach headlines suggest, but the cumulative effect over a decade of relationships is that a person's identity documents have lived in many systems. Some of those systems were compromised; some were inherited by acquirers with looser controls. Some were exposed by employees with access they should not have had.
We do not pursue leaked documents; working with them would be ethically and off-limits. What we do is map the relationships in which they were submitted. A person who has brought in with twenty financial institutions has twenty copies of their passport in twenty systems with twenty different retention and security postures. The exposure surface is the count of those relationships, not any specific leak.
The useful question for a person worried about historical exposure is not "has my data leaked" but "how many places does my data live, in how many forms, and which of those places do I have any leverage over." The answer is usually surprising and usually not actionable in one move. It is the start of a longer conversation about which relationships to consolidate, which to formally close, and which to leave alone.