What they're not telling you: # Telus Data Breach Victim Never Had an Account to Breach A Canadian telecom customer received notification of a data breach from Telus involving personal information—for an account they had already formally deleted months earlier, raising questions about whether the company retained customer data beyond stated deletion timelines and how that data ended up exposed in a security incident. The customer, whose account deletion was confirmed by Telus in 2024, received the breach notification email recently. According to their account, they had followed Telus's own deletion protocol: sending an email with "Unsubscribe" as the subject line and receiving confirmation that the request was processed.
What the Documents Show
Despite this documented deletion, their personal information was allegedly compromised in the breach that prompted Telus's notification campaign. The timeline creates a troubling discrepancy—if the account was deleted, why did customer data persist in Telus's systems long enough to be caught in a security incident? This incident exposes a common pattern in corporate data retention practices that often goes unreported in mainstream tech coverage. Companies frequently distinguish between "account deletion" and "data deletion," maintaining customer information in backup systems, historical records, or archived databases even after users request removal. Telus's situation suggests potential misalignment between what customers believe happens when they request deletion and what actually occurs with their information.
Follow the Money
The mainstream narrative around data breaches typically focuses on the incident itself—the attackers, the vulnerability, the number affected—rather than interrogating why deleted customer data remained accessible or stored at all. The customer's experience also highlights a procedural weakness: why would a company notify someone of a breach affecting data supposedly deleted from active systems? This notification itself serves as evidence that Telus retained the information. Either the data was never truly deleted from the systems that were breached, or it was recovered from backups and other storage locations. Neither scenario reflects the data minimization principles that privacy advocates and regulators increasingly expect from large corporations handling sensitive information. The deletion request appears to have been treated as an account closure rather than comprehensive personal data removal.
What Else We Know
For ordinary people, this situation underscores a disconnect between user expectations and corporate reality. When someone requests account deletion from a major service provider, they typically assume their personal information will be removed from that company's systems. The possibility that data persists in forgotten backups, archived databases, or retention systems designed for purposes the user never agreed to—and then gets exposed when those systems are breached—represents a hidden vulnerability in the digital ecosystem. Individuals have no practical way to verify whether their deleted data actually disappeared or simply moved to obscure corporate storage locations. The broader implication extends beyond Telus to any company maintaining customer data. If deletion requests don't result in actual data removal, then privacy policies promising deletion are marketing language rather than binding commitments.
Primary Sources
- Source: r/privacy
- Category: Corporate Watchdog
- Cross-reference independently — don't take our word for it.
Disclosure: NewsAnarchist aggregates from public records, API feeds (Federal Register, CourtListener, MuckRock, Hacker News), and independent media. AI-assisted synthesis. Always verify primary sources linked above.
