On this page
Your SituationWe had a privacy incident →
In the middle of a breach?
ClearBreach shows whether you must report, to whom and by when, under each law that applies, and writes the reports.
Lost or Stolen Device, What Canadian Organizations Must Do
By Yong Du · Updated May 2, 2026
A lost or stolen device triggers PIPEDA and PIPA obligations that depend heavily on encryption status, how to assess and respond.
⚡ In an active breach right now?
Use the quick reference guide, built for use during an incident.
This playbook is educational and does not constitute legal advice. It is grounded in the text of PIPEDA, Alberta PIPA, and BC PIPA and published guidance from the OPC, OIPC Alberta, and OIPC BC. If your situation involves regulatory investigation, litigation risk, or circumstances not addressed here, engage a qualified privacy lawyer.
A lost or stolen laptop or phone usually has to be reported unless you can show it was encrypted, with the key kept elsewhere. Wipe or lock it remotely first. Without confirmed encryption, treat the data as accessed. Start the assessment when you learn it is missing, not when you give up hope of finding it.
What makes this scenario different
Most breach scenarios leave access probability as an open question. A lost or stolen device leaves it as the central question, and the answer usually cannot be confirmed.
With ransomware, you know an attacker was inside. A lost or stolen device may have been found by someone with no interest in your data, picked up by an opportunist, or taken on purpose. You often do not know. That uncertainty is what makes this scenario unique: your RROSH assessment turns almost entirely on whether you can resolve the access question, and in most cases, you cannot.
Two variables determine the outcome. The first is encryption: was the device encrypted at rest, and can you confirm the encryption keys were not accessible to whoever had the device? The second is recovery: was the device recovered in a state that allows you to verify the data was never accessed?
When neither variable can be confirmed in your favour, treat access as having occurred unless evidence affirmatively rules it out. Do not split the difference. This is the cautious approach regulators expect under PIPEDA and Alberta PIPA. Regulators do not accept "we don't know" as a basis for concluding no harm risk exists.
Immediate containment, this scenario only
Act before you assess. For every other breach type, containment happens concurrently with investigation. For a lost or stolen device, one action takes priority over everything else: remotely wipe or lock the device through your MDM platform while it may still be connected to a network.
- Trigger a remote wipe or lock through your MDM platform (Intune, Jamf, etc.) immediately, document the timestamp and the MDM response
- Revoke any credentials, tokens, or certificates cached on the device: VPN access, corporate email, cloud storage, SSO sessions
- Revoke the device's certificate or remove it from your device management enrollment if it has not already been wiped
- File a police report if the device was stolen, do this promptly, as the report is relevant to your breach record and insurance claim
- Identify what personal information was on the device: locally stored files, cached email, browser-stored credentials, application data
- Determine encryption status: was BitLocker, FileVault, or equivalent enabled? Can you confirm it was active at the time of loss? Were the encryption keys escrowed in your MDM or in an accessible location?
If your MDM shows the remote wipe completed before the device connected to any external network, document this as part of your RROSH assessment, it is a meaningful mitigating factor. If the MDM shows the device never checked in after the loss event, you cannot confirm the wipe succeeded.
What drives RROSH in a lost or stolen device scenario
Encryption status is the dominant factor. A device with confirmed full-disk encryption, where recovery keys were not stored on or near the device, presents meaningfully lower access risk than an unencrypted device. But "we require encryption" is not the same as "this device was encrypted." You need confirmation, not policy.
If you cannot confirm encryption, treat the data as accessed. Unless you can show the device was encrypted and the person who had it could not get the key, assume they got in. This is consistent with how the OPC and provincial commissioners approach uncertainty in breach assessments.
Probability of misuse depends on context. A device stolen from a locked car by a break-and-enter is different from a device left at a coffee shop and found by another patron. Both are breaches, but the theft scenario carries higher intentional misuse probability, which is a weighted RROSH factor. Be accurate in how you characterize the event.
Sensitive data types determine the harm ceiling. Contact information only (names, email addresses) carries lower inherent harm than financial records, health data, SINs, or passwords. The data types on the device set the ceiling for potential harm if access occurred. In most business contexts, a laptop holds email, which in turn holds far more sensitive information than the employee who owned it may have recognized.
Getting it back with proof it was not opened is the only strong mitigating factor. If the device is recovered and forensics or device management logs show no files were opened, the risk drops a lot. Recovery without verification does not.
Likely verdict range
RROSH in most cases where the device was not recovered or encryption cannot be confirmed.
No duty to report needs two things. First, confirmed full-disk encryption, with keys the person holding the device could not reach. Second, either recovery with proof nothing was opened, or a confirmed remote wipe before the device connected to any network.
If you cannot confirm one or both of those conditions, assume RROSH. Most business devices hold significantly more than low-sensitivity contact information, treat the assessment seriously.
RROSH is near-certain where the device held health records, financial data, SINs, or employee credential files and encryption cannot be confirmed. If your organization handles that category of data on portable devices without confirmed encryption and MDM enforcement, RROSH is the expected outcome.
Was your device encrypted, with the key kept elsewhere? That decides most of these. That is the decision ClearBreach makes, under PIPEDA, Alberta PIPA and BC PIPA at once. See it made on a real case →
Scenario-specific obligations and complications
BC PIPA covers your activity in BC. If your organization operates in BC, including employees working there, BC PIPA applies to that information. Serving BC clients from Alberta or another province is interprovincial and falls under PIPEDA. BC PIPA has no breach reporting duty, so a report to the OIPC BC is voluntary, although the BC Commissioner expects affected people to be told where there is a risk of harm. See BC PIPA Breach Reporting.
Alberta PIPA simultaneous notification. Under the OIPC Alberta's April 2024 streamlined review process, organizations that notify affected individuals simultaneously with their regulatory filing receive a private closing letter rather than a public investigation. Do not delay individual notification to await direction from the regulator, simultaneous filing is the correct approach.
For Ontario organizations. Ontario has no provincial private-sector privacy legislation, PIPEDA is the applicable framework. Report to the OPC at priv.gc.ca. No separate provincial regulator report is required. See Ontario Data Breach Reporting Requirements.
Gaps in encryption. A lost device almost always reveals one: devices not actually encrypted as the policy said, encryption not enforced through device management, or recovery keys not stored safely apart. This gap is relevant both to your breach report (it affects RROSH) and to your regulatory standing. The OPC and OIPC Alberta have both noted inadequate device encryption safeguards in investigation findings. If this incident reveals a systemic gap, document your remediation steps.
Credential exposure beyond the device. A stolen device with cached credentials (email, VPN, cloud storage) extends the breach scope beyond the files on the device itself. If the thief uses those credentials to access connected systems, you have a second breach. Revoke credentials immediately and monitor for unauthorized access to connected accounts after the device is reported missing.
Insurance notification timing. Most cyber insurance policies require notification within a specified window after discovering a breach. A lost or stolen device qualifies. Check your policy language before concluding this incident is below the notification threshold, insurers and regulators apply different tests.
Documents you will need
For a lost or stolen device where RROSH is confirmed:
- Internal Incident Record: required under PIPEDA, good practice otherwise; begin populating immediately, retain for 24 months minimum
- OPC PIPEDA Breach Report: required if PIPEDA RROSH threshold is met; file as soon as feasible after determining RROSH
- OIPC Alberta PIPA Notification Form: required if Alberta PIPA applies and RROSH is met; email to breachnotice@oipc.ab.ca
- OIPC BC voluntary report: BC PIPA requires none; recommended for a significant breach in your BC activity
- Individual Notification Letter: required for all affected individuals where the individual notification obligation fires
- AB PIPA Individual Notice (s.19.1): required for Alberta PIPA individual notification; attach to your OIPC Alberta submission
ClearBreach tells you which of these you need, and gives you each one from your assessment answers.
Common mistakes, this scenario specifically
Assuming "encryption required" means "device was encrypted." Policy is not the same as enforcement. If your MDM does not confirm encryption compliance at the time of loss, you cannot rely on your encryption policy as evidence the device was encrypted. This is the most common and most consequential error in device loss assessments.
Treating recovery as resolution. A device returned by a Good Samaritan, or found in the lost and found, is not a closed breach. You need forensic or MDM evidence that the data was not accessed while the device was out of your control. Recovery without that evidence does not eliminate the RROSH question.
Waiting to see if the device turns up. The obligation to assess begins when you become aware the device is missing, not when you decide it is definitely lost. Waiting days to report the loss internally, or waiting weeks to begin the RROSH assessment while hoping the device is found, is not an acceptable approach. Regulators consider when you first became aware in assessing whether your response was timely.
Characterizing every device loss as "probably nothing." The instinct to minimize is understandable. It is also the reason most lost device breaches are reported late or not at all. The RROSH assessment exists precisely to apply consistent criteria rather than gut feel. Run the assessment before reaching a conclusion.
Not revoking credentials promptly. Revoking a device from MDM does not automatically revoke cached credentials for email, VPN, or SSO. These must be revoked separately. A stolen device with valid credentials is a more serious breach than a stolen device with expired or invalidated access.
Real-world example, lost or stolen device
An Alberta law office was broken into while closed. Thieves removed the server and the backup drive, both stored in the same location in the back office. The firm lost not just its primary data store but its only recovery path in a single event.
Every active client file on the server was treated as compromised. OIPC Alberta found RROSH was present, legal client files routinely contain financial details, personal identification information, and sensitive communications capable of enabling identity theft and causing significant reputational harm. The organization was required to notify all affected clients under PIPA.
The case resolves two common assumptions. First, that backup storage is a safeguard even when it sits adjacent to what it backs up. It is not, a backup physically colocated with primary storage can be removed in the same incident, eliminating recovery and compounding scope at the same moment. Second, that a break-in without confirmed data exfiltration is not a reportable breach. It is: unauthorized physical access to personal information triggers the RROSH assessment regardless of whether the thief's intent was data theft or hardware resale.
What a prepared organization would have had: an off-site or cloud backup that could not be carried off in the same theft. It keeps a way to recover, and limits what must be treated as compromised.
Source: OIPC Alberta, Decision P2023-ND-015, Breach notification decisions
MSP note
If you are an MSP managing devices for a client and a client device is lost or stolen, your obligations depend on whether you hold or can access personal information through your management role.
If your MDM platform manages the device, you have access to MDM logs and may be the one to execute the remote wipe. Do that immediately, regardless of who leads the breach response. Document the MDM action with timestamps.
If the lost device connects to systems you manage, revoke its access credentials immediately, do not wait for client direction.
Confirm with your client who leads regulatory notification before acting unilaterally. Your service agreement should define this. If it does not, get written confirmation from the client before filing on their behalf. Run the ClearBreach assessment under your MSP account for the affected client organization to establish the RROSH verdict before advising them on obligations.
Related guides
- How Canadian Regulators Decide Whether a Breach Must Be Reported. More real regulator decisions, across every type of breach
- PIPEDA Breach Reporting Requirements, full coverage of the federal RROSH threshold, OPC reporting obligations, individual notification requirements, and the 24-month record-keeping rule
- Alberta PIPA Breach Notification, Alberta-specific obligations, OIPC Alberta submission process, and the April 2024 simultaneous notification streamlined review process
- BC PIPA Breach Reporting, BC-specific obligations, the voluntary regulator reporting distinction, and OIPC BC submission guidance
- Ontario Data Breach Reporting Requirements, PIPEDA as Ontario's applicable framework, single-regulator advantage, and Ontario-specific context for small businesses
Ready to assess this breach? Find out whether you must report it, to whom and by when, under each law that applies, with the regulator reports and notification letters to send. See it done on a worked case →
The demonstration is the real assessment, already answered for a fictional company, with three answers left for you to change. It ends on the verdict and the documents it produced. See a real verdict → to run it on your own breach.
Frequently asked questions
Do I have to report a lost or stolen laptop under PIPEDA if it might be encrypted?
Maybe, and 'might be encrypted' is not the same as 'was encrypted.' If you cannot confirm through MDM logs, BitLocker recovery keys, or forensic verification that the device was encrypted and that the encryption keys were not accessible to whoever found or stole it, regulators expect you to treat access as having occurred. Uncertainty you cannot resolve counts against you, not for you. If RROSH is triggered, you must report to the OPC and notify affected individuals.
What if the device was recovered?
Recovery reduces risk, it does not eliminate the obligation to assess. If the device was recovered and you can verify through MDM access logs, forensic analysis, or confirmed remote wipe completion that the data was never accessed, this materially reduces the risk and may bring the outcome below the reporting threshold. That verification must be documented. If you cannot verify non-access, recovery alone is not a basis to conclude no breach occurred.
Is a lost device different from a stolen device for reporting purposes?
Yes, in one specific way. Theft by a motivated actor indicates higher probability of intentional data misuse, which is a weighted RROSH factor. A device left on a bus and found by a stranger carries lower misuse probability than a device physically taken from a locked office. However, both are breaches if personal information was on the device and encryption cannot be confirmed. Do not treat 'lost' as meaning 'no breach', that is the most common error in this scenario.
Does BC PIPA apply to my Alberta business if I have BC clients or employees?
If your organization operates in BC, yes, for that activity, including employees working there. BC PIPA covers activity within BC; serving BC clients from another province is interprovincial and falls under PIPEDA. BC PIPA has no breach reporting duty, but the BC Commissioner expects affected people to be told where there is a risk of harm.
What is the deadline for reporting under PIPEDA and the provincial PIPA laws?
PIPEDA requires reporting 'as soon as feasible' after you determine the breach occurred; it sets no number of days, so do not hold the report back. Alberta PIPA requires notice to the OIPC Alberta 'without unreasonable delay'. BC PIPA has no reporting duty; the BC Commissioner asks for a voluntary report, and notice to affected people, as soon as possible. Do not wait for device recovery or full forensic results, assess on available information and supplement as new facts emerge.
Ready to assess this breach?
See whether you must report, to whom and by when, under each privacy law that applies to you, with the reports and letters to show for it.
How ClearBreach handles a breach →Privacy case of the month
Once a month, a five-minute read: a real case a Canadian privacy commissioner investigated, what went wrong, and what to check in your own organization so it doesn't happen to you. Written for organizations under federal, Alberta and BC privacy law. Not written for Quebec.
We send one email to confirm. Nothing else arrives until you confirm, and an unconfirmed address is deleted after 7 days. Sent by ClearBreach Technologies Inc. Mailing address and contact details · Privacy policy