The Ghost Delete Academy · Module 1, Lesson 2
What a breach is, and how to read one
Free lesson · About 11 minutes · Ends with the free scan
A breach, in plain terms
A breach is simple to define and easy to misunderstand. It is data a company stored about you being exposed or stolen.
You gave that company your information for a reason. You opened an account, bought something, booked something, or signed up for a service. The company kept a record so it could serve you. A breach means that record, or a copy of it, ended up somewhere it was never meant to be.
Exposed is not always stolen. Sometimes data is left open by mistake, where anyone who knew where to look could see it. Sometimes it is taken on purpose. For you, the practical difference is small. Once your details are outside the building, you cannot control who copies them next.
You did nothing wrong. A breach is not a failure of your behaviour. It is a failure of storage by an organisation you trusted with your details. Your job starts after it happens, with reading the notice well and acting in the right order.
A breach is not identity theft by itself. It is the raw material for it. What happens next depends on what was in the record, and on what you change before someone else uses it. That is why this lesson comes before the fixing lessons. Reading comes first.
What a breach record holds
Every company stores a different record, so every breach is different. Read any notice by asking one question: what, exactly, about me was in there?
Your name and email address. This pairing is the most common piece. On its own it looks harmless. Combined with anything else, it becomes the address label for everything that follows, including scam email written to sound personal.
Your phone number. A number tied to your name is what turns a generic scam call into a call that greets you properly. It is also the key to your voicemail and to many account recovery systems.
Your home address. An address confirms where you live and helps match you to public records and broker listings. Lesson 1 showed how brokers assemble those listings. Breach data slots straight into the same picture.
Password data. Companies are supposed to store passwords in a scrambled form, not as plain text. A breach notice may say passwords were included, or that password data was included. Either way, treat it seriously. The next sections explain why a password in a breach never becomes safe again.
The service itself. Even a short record tells a stranger what you use. Knowing which bank, shop, clinic, or service holds your account is often enough to write a convincing message that pretends to come from it.
Three dates, not one
Breach news confuses people because it sounds like one event. It is three, and they can be far apart.
The breach happened. This is when the data was exposed or taken. It is the date that matters for risk, because circulation can start from this point, long before anyone tells you.
The breach was discovered. This is when the company found out. Discovery can come from its own monitoring, from a researcher, or from the data turning up somewhere it should not be. The gap between happening and discovery is the quiet period, when you were at risk and did not know it.
The breach was disclosed. This is when you were told, by letter, by email, or in the news. Disclosure is the date you can act from. When a notice gives you dates, line them up in this order and notice the gaps. A long gap is not a reason to panic. It is a reason to assume the data has had time to travel, and to act as if it has.
Keep those three dates separate in your mind and every breach story gets clearer. The headline date is usually the disclosure. Your exposure started earlier.
The Canadian rulebook
In Canada, breaches are not just bad news. They carry legal duties, and knowing them helps you judge whether a company has done its part.
Under PIPEDA, the federal private sector privacy law, an organisation must report a breach of security safeguards to the Privacy Commissioner of Canada when the breach poses a real risk of significant harm. It must also notify the people affected, for the same reason. Significant harm is a broad idea. It can include financial loss, identity theft, and damage to reputation or relationships.
Organisations must also keep records of breaches of security safeguards for 24 months. That record keeping matters because a pattern of small incidents can tell a story that one incident on its own does not.
What this means for you. If you receive a notice, the company has usually judged that the risk to you is real. Read it that way. It is not routine mail, and it is not marketing. It is a formal warning, written in careful language.
What this does not mean. Not every exposure reaches you as a notice, and a quiet inbox is not proof that nothing has happened. Some breaches are discovered late. Some are never discovered at all. That limit is honest, and it is why Lesson 3 teaches you to check for yourself instead of waiting to be told.
Why a breached password stays burned
This is the rule people resist, so it gets its own section. A password that appears in a breach is burned forever.
Changing it on the breached site is necessary, but it is not the whole fix. The problem is reuse. Most people use the same password, or a close variation, in more than one place. The old password in the breach becomes a key to try elsewhere: your email, your banking, your shopping accounts, anywhere the same habit followed you.
Attackers do not guess one password at a time by hand. They take breach lists and try the email and password pairs across many services at once. If one pair still works somewhere, that account opens. From an email account, password resets for other accounts can follow.
Burned means everywhere. When a notice says password data was involved, change that password on the breached service, then change it on every other account where you used it or anything close to it. Then stop reusing passwords at all. Module 4 covers how to do that fixing properly, with two-factor authentication as the second lock.
Two-factor changes the maths. With two-factor authentication turned on, a stolen password on its own is usually not enough to get in. It is the single strongest step you can add to an account that a breach has touched.
Checklist: how to read a breach notice
- Find the what. List the exact types of data named in the notice: name, email, phone, address, password data, or anything else. Do not skim past this part.
- Find the when. Write down the three dates if they are given: when it happened, when it was discovered, and when you were told.
- Find what the company did. Note whether it secured the system, brought in outside help, or offered you anything, and keep the notice itself in case you need it later.
- Decide what you will do. If password data was involved, put changing that password, everywhere it was reused, at the top of your list, and turn on two-factor authentication on the account.
- Expect more specific contact. A caller or message that names the breached service should be treated with extra care. Use the habits from Anatomy of a scam call, and the steps on our report fraud page if money or access was lost.
- Run the free scan with the email address tied to the account, so you can see whether that address appears in other known breaches as well.
Data travels, then it combines
A breach does not sit still. Copies are traded, merged, and resold, and breach data gets combined with broker data to build fuller profiles: the listing from Lesson 1, plus the services and passwords from a breach, is worth more to a scammer than either piece alone.
That is the honest picture, and it has a practical side. You cannot recall data that is already circulating, and no service can promise that. What you can do is make the circulating copy worth less: new passwords it does not know, two-factor it cannot pass, and broker listings removed so the profile stops being refreshed. The rest of this academy is that work, in order.
Next lesson: Check yourself: the free scan, done properly.
Be a Ghost.
Lesson sources: Office of the Privacy Commissioner of Canada, guidance on PIPEDA breach of security safeguards reporting, notification where there is a real risk of significant harm, and the requirement to keep breach records for 24 months. The broker and breach connection follows Lesson 1 of this academy.