L1-M3 / lesson 2 of 2
An employee realises an unapproved upload may include confidential information.
Start here / Watch the workplace case
2:29 · Narrated visual walkthrough · English captions and transcript
Watch for thisSeparate the employee's immediate actions from decisions that belong to the privacy and security response team.
Scene 1 of 6
Emails, salaries and unique job titles
Approval for these records is unconfirmed
Removing names does not make a dataset anonymous.
Leo notices that he uploaded a client spreadsheet to an unapproved assistant. He removed names, but email addresses and unique job titles remain. Those fields can still identify people. The generated summary may also contain confidential details. Start from the information actually shared, not the reassurance that names were removed.
Leo is tempted to send another prompt to find out where the information went. That could create more copies or disclose more context. Stop further input instead. You do not need a complete technical explanation before taking this simple containment step. Keep other people from repeating the same upload while the issue is assessed.
A sharing option is visible, but visibility alone does not prove that a public link was created. Check the facts through the approved process. If an exposed link exists and you are authorised to restrict it, do so. Do not publish a new link to test the feature or forward the file widely as a warning.
Record when the upload happened, which service and account were used, and what categories of information were involved. Preserve necessary evidence through the secure incident route. Do not blindly delete the investigation trail, and do not send the full spreadsheet to everyone who might be interested. The response team can request what it needs.
Leo should report promptly to the designated privacy and security contacts. Staff do not need to decide the legal outcome alone. A reference to a seventy-two-hour notification deadline is not permission to wait before reporting internally. The responsible response team assesses the applicable trigger, timing and whether any external notification is required.
The first response should leave a clear record of known facts, open questions and the person coordinating the next step. A no-training setting would not, by itself, establish zero retention or permitted use. Resume only through the approved process. In the activity, distinguish immediate staff actions from decisions assigned to privacy and security specialists.
After watching or reading / Think it through
Pause and form your answer, then compare the reasoning. This reflection is not scored.
Email addresses and distinctive roles can still identify people, and confidential information may remain. Stop further input, preserve necessary facts securely and use the designated incident route. Do not keep experimenting or decide notification duties alone.
Next, learn the boundaries of approved data use and incident response. Return to the accidental upload in the written example.
Removing names may leave people identifiable.
Unique roles, dates and combinations can reveal identity.
In a small office, 'the only cardiologist on night duty' may identify someone. Test combinations rather than single fields.
Pseudonymised data remains personal data.
Leo pastes a client spreadsheet into an unapproved assistant. He removed names but retained email addresses, salary figures and unique job titles. The tool offers a public sharing link. Leo notices the mistake ten minutes later.