Frequently Asked Questions
How do I respond to a request for erasure?
Individuals have the right to request erasure of personal data concerning them and in that case, the controller has the obligation to erase the personal data. You should respond without undue delay and at the latest within one month after receipt of the request. This deadline can be extended by another two months if the request is too complex and more time is needed to comply with the request, provided that the individual is informed of this within one month after receiving the request.
It is important to note that the right to erasure is not absolute. It does not apply when the data in question is necessary for:
- exercising the right to freedom of expression and information (e.g. for journalistic purposes);
- compliance with a legal obligation which requires the processing of personal data (e.g. processing records on employees’ work hours);
- reasons of public interest in the area of public health
- archiving purposes in the public interest or scientific or historical research purposes or statistical purposes; and
- the establishment, exercise or defence of legal claims.
When the personal data that is to be erased was previously transferred to other organisations, you must inform these recipients that the individual has requested erasure, unless this proves impossible or would require disproportionate efforts.
More information:
How long can I store personal data?
You cannot store personal data forever.
As a rule, personal data can only be stored for as long necessary in light of the purposes for which the personal data is processed.
In some cases, the storage period can be determined by specific laws, for example, labour regulations determine a storage period for payroll lists.
Organisations should put in place data retention policies to make sure that personal data is not kept longer than is necessary. Individuals’ personal data must be deleted or anonymised once this data is no longer necessary for the purpose for which is was processed.
More information:
How long do I have to respond to an access request?
You should respond without undue delay and at the latest within one month after receipt of the request. This deadline can be extended by another two months if the request is too complex and more time is needed to answer, provided that the individual is informed of this within one month after receiving the request.
You must do this free of charge.
More information:
I am organising an event as part of my business activities, can I make photos and videos of the event and the people attending?
Yes, but in order to do this, you will first need to determine the legal basis for processing this type of personal data. For example, the processing could be considered as a legitimate interest for your organisation. When processing personal data on the basis of legitimate interest, it is always necessary to conduct a balancing test to determine whether your legitimate interests outweigh individuals’ rights, particularly if children are involved.
Another possible legal basis for such processing could be consent. At any rate, individuals should always be informed in advance that the event is being photographed or filmed.
More information:
If I want to store CVs of candidates for future recruitment procedures, do I need to ask for the candidates’ consent?
Consent could indeed be a valid legal basis for storing job applicants’ CVs. Another possible legal basis could be legitimate interest. In that case, you would have to carry out a balancing test to prove that your organisation’s legitimate interests outweigh the applicants’ rights.
At any rate, you will have to inform the candidates that you plan to store their data and for which purposes.
More information:
Is it possible to process sensitive data?
No, the processing of sensitive data is generally prohibited, except under very specific circumstances:
- The individual has given their explicit consent for their sensitive data to be processed.
- The processing of sensitive data is necessary for the data controller to fulfil their obligations, specifically in the context of employment, social security and social protection. For example, the data controller may need to process a person’s sensitive data to be able to determine if they are entitled to certain social security benefits or employment stipends.
- The processing of sensitive data is necessary to protect the vital interests of a person where the individual is physically or legally incapable of giving consent. For example, if an individual is left unconscious as a result of an accident and requires immediate medical care, their health data may need to be processed for the appropriate medical care to be delivered.
- The processing of sensitive data is carried out in the context of the legitimate activities of a foundation, association or other non-for-profit organisation with a political, philosophical, religious or trade union aim, and only for the processing of the personal data of their members, former members or persons having regular contact with them.
- The sensitive data was manifestly made public by individual.
- The processing of sensitive data is necessary in the context of legal proceedings.
- The processing of sensitive data is necessary for matters of substantial public interest.
- The processing of sensitive data is necessary in the context of preventive or occupational medicine. For example, assessing an individual’s sensitive data, such as their medical data, may be necessary to determine their working capacity as an employee.
- The processing of sensitive data is necessary for matters of public health on the basis of EU or national law. For example, processing individuals’ sensitive data may be necessary to ensure a high quality of health care and a high quality of medical products, or to combat serious health threats, such as viruses.
- The processing of sensitive data is necessary for matters of archiving purposes in the public interest, or for scientific or historical research purposes, or statistical purposes. For example, processing sensitive data may be necessary to provide accurate statistics on a country’s situation in a particular field.
More information:
Is the Data Protection Officer (DPO) responsible for compliance with the GDPR?
The DPO cannot be held responsible for failure to comply with the GDPR. Compliance with the GDPR is the responsibility of the organisation that appointed the DPO.
More information:
What constitutes a conflict of interest for a Data Protection Officer (DPO)?
DPOs can fulfil other tasks within the organisation, but this cannot result in a conflict of interest. This implies that the DPO cannot have a position in which they determine the purposes and means of the processing activities. Conflicting functions include mainly management positions (chief executive, chief operating, chief financial officer, Head of HR, Head of IT, managing director) but may also involve other functions if they lead to the determination of purposes and means of processing.
The DPO must be able to perform their duties and tasks in an independent manner. This means that your organisation:
- may not give instructions to the DPO with regard to the performance of their DPO duties;
- may not penalise or dismiss the DPO for performing their tasks.
More information:
What information should I communicate to/share with individuals?
The GDPR gives individuals control over the processing of their personal data. In order to do this, transparency is key. This means you have to inform individuals whose data you process about your processing operations and the purposes. In other words, you have to explain who processes their data, but also how and why. Only if the use of personal data is 'transparent' for those involved, can they assess possible risks and make decisions about their personal data.
Under the GDPR you are obliged to share the following information with individuals:
- the identity and contact details of the controller;
- the purposes of the processing;
- the legal basis of the processing (if legitimate interest, specific information about which legitimate interests relate to the specific processing, and about which entity pursues each legitimate interest.)
- the contact details of the controller;
- the contact details of the DPO (if there is a DPO);
- the recipients or categories of recipients of the data;
- Information on whether the data will be transferred outside the European Economic Area (EEA) (where applicable: the existence or not of an adequacy decision or reference to the appropriate safeguards and how this information can be made available to data subjects);
- the categories of personal data processed, when the data is not obtained from the individual.
In addition, the GDPR requires your organisation to provide the following information to ensure fair and transparent processing:
- the retention period or, where this is not possible, the criteria used to determine this period;
- the right to request access, erasure, rectification, restriction, objection and portability of personal data;
- the right to lodge a complaint with a data protection authority;
- if the legal basis for the processing is consent: the right to withdraw consent at any time;
- in the case of automated decision-making, relevant information about the underlying logic and the intended consequences of the processing for the data subject;
- the source of the personal data (if you did not directly receive it from the individual concerned;
- whether the individual is required to provide the personal data (by law or by contract or to enter into a contract) and what the consequences of refusing to provide the data are.
More information:
What should I do in case of a data breach?
A personal data breach is a security breach leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data.
- If the data breach poses a risk to the individuals concerned, you must report it to the relevant data protection authority within 72 hours.
- If the breach is likely to result in a high risk to individuals, you will also need to communicate that breach to the individuals concerned without undue delay.
In any case, for all breaches – even those that are not notified to a DPA - you must record at least the basic details of the breach, the assessment thereof, its effects, and the steps taken in response.
More information: