Limiting collection to necessary information

1. Regulatory Concept & Core Standards

Today we will learn to apply data minimisation when receiving and handling reports. Throughout the video, consider the difference between knowing a rule and applying it to a decision. We will work through an example, identify a possible failure and develop a response that can be used at work. A reporting case may contain data about the reporting person, people concerned and third parties. Data protection must accompany the whole lifecycle, from the form to archiving. This course addresses operational decisions. Legal bases and restrictions on rights require assessment of the specific processing.

Data minimisation requires adequate, relevant information limited to what is necessary. Avoid excessive collection and remove clearly irrelevant data under applicable rules. This does not authorise destruction of relevant evidence or silent alteration of a document. Document the decision, preserve necessary material intact and use redacted copies where appropriate.

Apply the following rule: The Act accommodates anonymous reports; the section 11 register does not require an anonymous person’s name and residence. Someone later identified may meet protection conditions. Section 10(7) protects the identity of both the reporting person and the person concerned. Written consent and lawful provision for criminal or administrative-offence proceedings have specific conditions. Do not promise absolute unidentifiability.

2. Practical Implementation & Procedure

Review form fields and the need for attachments. At intake, identify clearly unrelated information, decide what to do and record the decision without reproducing deleted data. Obtain competent assessment if relevance or retention is uncertain. Do not use reporting to create parallel worker information databases without a legitimate purpose. 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.

3. Case Study & Compliance Action

An attachment accidentally includes an unrelated customer list. The team confirms irrelevance, deletes unnecessary data through the appropriate procedure and makes a limited record of the event. It does not retain a complete copy merely because it accompanied a report. 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: Is keeping everything ‘just in case’ compatible with data minimisation? 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.

Not as a general rule. Retention needs a purpose and a basis. Clearly irrelevant data follow specific deletion rules, while material necessary for the case must be preserved under applicable requirements.

One mistake to avoid is: confusing case integrity with indiscriminate retention of everything received.

Now apply the national rule to a second decision. The form requires a name and identity document although it promises anonymity. What must change?

Align the functions and user information. Do not require unnecessary identification. Check attachments and indirect identifiers too. Explain anonymity and confidentiality, restrict access, and assess existing data by legal basis and necessity. Do not promise absolute anonymity.