MAINSYSTEMS 
1. Core Concepts and Legal Context
In this video we will consolidate a skill: distinguish access requests from security breaches. Use the case to test what you would do in a similar situation. We will explain the proposed response step by step so that you can understand each choice and recognise when more information would be needed. The GDPR applies alongside Maltese reporting rules. Collection, access and retention require purpose and lawful basis. Protection also covers people named in reports, without removing lawful confidentiality safeguards.
Data-subject rights apply with specific lawful safeguards. Channel confidentiality does not remove examination of a personal-data breach. GDPR articles 33 and 34 have different tests.
Apply the following rule: Article 21A requires records of reports and retention no longer than necessary and proportionate for the Act or other legal requirements. Article 6A prohibits collecting manifestly irrelevant data and requires deletion without undue delay if accidentally collected. Document purpose, pending proceedings, review ownership and secure deletion including copies and exports. These provisions do not impose a universal five-year period.
2. Practical Application and National Rule
Record the request or incident and involve authorised people. Assess risk, deadlines and lawful restrictions. Document each notification or communication decision separately. Before moving on, turn this procedure into a sequence you could explain to a colleague. Identify the first check, the action that depends on its outcome and the record that allows the decision to be reconstructed. Follow the sequence on screen and identify the point where an error would change the result.
Consider how a colleague taking over tomorrow would understand the decision. Identify the verified information and its source, who is authorised to decide and who checks the result. The record should connect the decision to the material actually used rather than repeat the whole file. State critical gaps and assign a specific action to resolve them. This makes continuity independent of one person’s memory. Apply the proposed organisational steps within legal powers. In the case, distinguish observation, conclusion and hypothesis. An observation describes available evidence, a conclusion explains what can reasonably be inferred and a hypothesis still needs checking. Do not infer motives merely from unusual behaviour. Identify which further information could change the decision and whether it can be obtained lawfully and proportionately. Incomplete knowledge justifies neither certainty of guilt nor indifference to an actual risk.
GDPR article 33 requires notification to the supervisory authority without undue delay and, where feasible, within 72 hours of the controller becoming aware of a personal-data breach, unless it is unlikely to pose a risk to rights and freedoms. Delay requires reasons. Article 34 has a separate high-risk test for communication to individuals, with specific exceptions. Each decision needs assessment and a record. Report confidentiality does not create a general exemption from these duties.
A file goes to the wrong recipient. The team assumes confidentiality means that nothing needs to be reported. Now read the case carefully. Separate established facts from information you would still need to confirm. Do not add motives or events that have not been described. This distinction matters when choosing a response proportionate to the information available.
3. Case Study and Key Decision Points
The exercise is as follows: Is this conclusion sufficient? Choose an answer and write one sentence explaining it. During the pause, compare your choice with the criteria we have just considered. Also think about the material you would retain to explain the decision later.
No. Assess the incident, risk and each obligation under its specific conditions.
One mistake to avoid is: confusing a communication exception with a complete exemption.
Now apply the national rule to a second decision. The system deletes every case five years after receipt regardless of country and pending proceedings. Is this suitable?
No. Apply Malta’s necessity and proportionality rule and relevant legal duties. Consider pending proceedings. Record the decision for each category, include copies and identify who reviews a suspension of deletion. Do not retain everything forever.
Remember these three points. First: Separate duties. Second: Risk assessment. Third: Documented decision.
To apply this learning, retrieve the procedure used in your organisation or consider how you would create it. Identify one difference between that procedure and the case we have just resolved. Write down the change you would propose and the information needed to justify it. You can complete this short task in the handout accompanying the video.
The expected outcome of this unit is the ability to distinguish access requests from security breaches. Review the explained answer whenever you are unsure and keep the summary to support a future decision.
In the worksheet, connect your proposal to this video's national rule. Identify the document or platform field that would need to change and who should approve the change. If you conclude that it is good practice, explain the risk you intend to reduce. If you conclude that there is a legal duty, record its source and scope.