Rights and data incidents

1. Regulatory Concept & Core Standards

In this video we will consolidate a skill: distinguish rights requests from security incidents. 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. Files contain reporters’, persons concerned’ and witnesses’ data. Confidentiality does not replace GDPR duties. Connect collection, access, retention and rights responses to a specific purpose and legal basis.

Access requests do not automatically entitle someone to another person’s identity. GDPR articles 33 and 34 apply different risk tests for authority and individual notifications.

Apply the following rule: Article 7(1) requires information to be kept for at least five years from the last decision in examining that information. The Prosecutor’s Office may give a reasoned instruction extending an institution’s retention period. Receipt or technical task closure does not automatically start the period. Clearly irrelevant personal data must not be collected, and accidentally collected irrelevant data must be destroyed immediately under Article 7(4). Align retention with the GDPR, confidentiality and lawful procedural needs.

2. Practical Implementation & Procedure

Assess request scope, others’ rights and lawful restrictions. Contain and document incidents. Notify VDAI without undue delay, where feasible within 72 hours of awareness, unless risk is unlikely. 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.

At each step, compare the information available with what is still needed for the decision. Arrange continuity when the designated worker is absent. A substitute receives only the information needed for the task, and their actions must remain verifiable.

Mark an unanswered question as a fact to verify. Identify who could confirm it and what access they actually need. A correct exercise choice alone does not show that the reasoning is understood. If the answer depends on an additional fact, state that condition explicitly.

For the workplace task, name the person who can approve the change and the person who will check that it works. Produce a concrete verifiable action, rather than only a promise to follow rules. Check effects on access rights and user information. Record questions that your organisation still needs to resolve.

3. Case Study & Compliance Action

A reporter’s name reaches the wrong recipient. The team contains disclosure and assesses risk. High risk requires notifying the person without undue delay under the applicable conditions. 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.

The exercise is as follows: Should everyone wait 72 hours? 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. It is not a waiting period. Act without undue delay, assess risk and, when needed, provide information in phases and explain delay.

One mistake to avoid is: equating authority and individual notification thresholds.

Now apply the national rule to a second decision. The system deletes every file five years after receipt. What is wrong?

Article 7 starts the period at the last decision in examining the information, and five years is a minimum. Check possible reasoned extensions and procedural needs. At the same time, accidentally collected and clearly irrelevant personal data must be destroyed immediately. Record the retention basis, restrict access and include exports and copies in the review.