[
Expedia Group confirmed on Nov. 12 that attackers reached its systems through a compromised third-party data platform provider. An extortion group has claimed to possess hundreds of millions of traveler-related records, although the volume and contents of any stolen data remain unverified. The investigation is ongoing. But the incident already points to a larger problem: businesses and their vendors routinely accumulate more personal information than they need to perform the task at hand.
I have a commercial stake in this argument, and I want to be clear about it. My company, Trua, offers an alternative: verifying identity without requiring every organization to retain the underlying documents. But I also have spent years working on credentialing systems and seeing what becomes possible when organizations separate the assurance they need from the sensitive records they do not.
Before Trua, my previous company helped develop technology that ultimately became part of TSA PreCheck and other credential programs. The design question we kept returning to was not how much information we could collect, but what the checkpoint actually needed to know. Enrollment involved verifying government identification and other biographical details, conducting checks against criminal and terrorism databases, and issuing a Known Traveler Number after clearance. At screening, however, the relevant answer was much narrower: was the traveler approved? The lane could rely on credential validation and biometric authentication rather than access to the full background file, Social Security number, or other enrollment records. Those remained with the vetting authority.
That distinction mattered. We did not make the original verification less rigorous; we made the result usable without passing the underlying dossier from system to system. A screening officer needed a trustworthy determination, not a copy of the investigation behind it. The approach supported a faster process while reducing the amount of sensitive information exposed at each point of use.
Much of the private sector still operates in the opposite direction. Companies collect identity documents, payment information, travel histories, and other personal details for a particular transaction, then keep them available long afterward. Copies move into interconnected vendor environments, often with persistent access. When a trusted supplier is compromised, the exposure can extend well beyond the supplier itself—as the Expedia incident illustrates.
The problem often becomes visible only when someone audits what has accumulated. One midsize staffing firm found roughly 180,000 applicant and worker records in its systems. About 35 percent were more than six years old, and more than half related to people who had never been hired or had left years earlier. Files containing Social Security numbers and background reports had been copied to at least four vendors and two client HR systems. No single decision created that liability. It grew with each onboarding form, integration, and decision to keep a record just in case.
Most organizations do not need those permanent copies to make the decisions before them. A travel platform may need to confirm a customer’s identity and payment validity. An employer may need to know whether an applicant holds a required credential or meets screening criteria. Those are questions that can be answered with reliable, purpose-specific confirmations. Retaining every source document is not the same as improving the quality of the answer.
The incentives behind overcollection are understandable, but increasingly costly. Businesses want speed and certainty. Technology vendors often design services around access to raw data. Risk assessments can treat large stores of personal information as an unavoidable feature of doing business rather than a choice to be challenged. And as AI agents begin taking actions on people’s behalf, organizations will need to establish who authorized a transaction and what that agent is permitted to do. Without a better model, that need could become an excuse to create yet more identity databases.
There is another way. Individuals can undergo strong verification and then share only the attributes or status required for a specific purpose. The receiving organization gets a trustworthy, appropriately limited response, potentially subject to expiration or revalidation, rather than a dossier it must protect indefinitely. Selective-disclosure mobile driver’s licenses and other attribute-verification systems show how this can work. It does not eliminate cybersecurity risk, but it reduces the quantity of sensitive information dispersed across corporate and vendor systems.
The benefits are practical. Organizations that collect and retain less sensitive data reduce what an attacker can obtain, narrow the scope of third-party exposure, and make privacy obligations easier to manage. Insurers can assess unnecessary retention as a controllable risk. Individuals face fewer consequences from breaches at companies they may have dealt with only once.
The exact scope of the Expedia intrusion remains to be established. The broader lesson does not. As long as every business transaction generates another lasting store of personal records, a breach at one trusted provider can create risks for many organizations and the people who rely on them. The durable response is not merely to defend ever-larger databases. It is to collect less, retain less, and share only what a particular decision requires. Businesses should treat unnecessary retention as a liability, insurers should price that liability, and policymakers should give data minimization as much attention as breach response. Otherwise, we will keep reading versions of the same headline.
The opinions expressed in Fortune.com commentary pieces are solely the views of their authors and do not necessarily reflect the opinions and beliefs of Fortune.
https://fortune.com/img-assets/wp-content/uploads/2026/11/raj-ananthanpillai.jpg?resize=1200,600
https://fortune.com/2026/11/20/expedia-breach-data-minimization-identity-verification-trua-raj-ananthanpillai/
Raj Ananthanpillai




