Article 12 GDPR
Legal Text
1. The controller shall take appropriate measures to provide any information referred to in Articles 13 and 14 and any communication under Articles 15 to 22 and 34 relating to processing to the data subject in a concise, transparent, intelligible and easily accessible form, using clear and plain language, in particular for any information addressed specifically to a child. The information shall be provided in writing, or by other means, including, where appropriate, by electronic means. When requested by the data subject, the information may be provided orally, provided that the identity of the data subject is proven by other means.
2. The controller shall facilitate the exercise of data subject rights under Articles 15 to 22. In the cases referred to in Article 11(2), the controller shall not refuse to act on the request of the data subject for exercising his or her rights under Articles 15 to 22, unless the controller demonstrates that it is not in a position to identify the data subject.
3. The controller shall provide information on action taken on a request under Articles 15 to 22 to the data subject without undue delay and in any event within one month of receipt of the request. That period may be extended by two further months where necessary, taking into account the complexity and number of the requests. The controller shall inform the data subject of any such extension within one month of receipt of the request, together with the reasons for the delay. Where the data subject makes the request by electronic form means, the information shall be provided by electronic means where possible, unless otherwise requested by the data subject.
4. If the controller does not take action on the request of the data subject, the controller shall inform the data subject without delay and at the latest within one month of receipt of the request of the reasons for not taking action and on the possibility of lodging a complaint with a supervisory authority and seeking a judicial remedy.
5. Information provided under Articles 13 and 14 and any communication and any actions taken under Articles 15 to 22 and 34 shall be provided free of charge. Where requests from a data subject are manifestly unfounded or excessive, in particular because of their repetitive character, the controller may either:
- (a) charge a reasonable fee taking into account the administrative costs of providing the information or communication or taking the action requested; or
- (b) refuse to act on the request.
The controller shall bear the burden of demonstrating the manifestly unfounded or excessive character of the request.
6. Without prejudice to Article 11, where the controller has reasonable doubts concerning the identity of the natural person making the request referred to in Articles 15 to 21, the controller may request the provision of additional information necessary to confirm the identity of the data subject.
7. The information to be provided to data subjects pursuant to Articles 13 and 14 may be provided in combination with standardised icons in order to give in an easily visible, intelligible and clearly legible manner a meaningful overview of the intended processing. Where the icons are presented electronically they shall be machine-readable.
8. The Commission shall be empowered to adopt delegated acts in accordance with Article 92 for the purpose of determining the information to be presented by the icons and the procedures for providing standardised icons.
Relevant Recitals
Commentary
Article 12 GDPR ensures the efficient exercise of the data subject’s rights. To do so, it regulates clarity and accessibility standards regarding communications with the data subject. It also lays down procedural rules the controller must follow once a GDPR right is exercised.
(1) Requirements of information in the GDPR
Article 12(1) GDPR requires controllers to take appropriate measures to provide "any" information under Articles 13, 14, 15 to 22 and 34 GDPR[1] in a manner that is concise, transparent, intelligible and easily accessible, using clear and plain language.
A "measure" is any method, internal process, policy or technical tool used by the controller during its processing operations. Within this wide category, the "measures" falling under the scope of Article 12(1) are just those whose goal is to provide the data subject with information and communications under Articles 13, 14, 15 to 22 and 34 GDPR.[2]
A measure or, most likely, a set of measures, is "appropriate" when it generates information under Articles 13, 14, 15 to 22 and 34 GDPR which is both (i) complete and (ii) clear.[3]
(i) Completeness
This includes, where appropriate, measures to correctly detect the content of the request and assign it to the responsible department. The same goes for internal policies and technical equipment enabling the controller's staff to retrieve the data and perform any required operation (e.g. copy, rectification, deletion).
Example: Markus is annoyed by some marketing emails he has been receiving for the last few months. He files an access and erasure request. Ideally, the controller already put in place all the measures to fully address the requests. This includes being able to recognize the two requests, assign them to the relevant department, retrieve all the information required, explain it to the data subject in clear, simple and tailored terms, and delete all the data subject's contact details from its marketing lists.
In practice, deciding what is appropriate will not always be easy. In certain circumstances, for instance, a given processing may not be easy to explain, especially where a considerable amount of data is processed and numerous actors are involved in the processing chain. In such cases, finding the appropriate measure will not always be straightforward. In any case, the complexity of the processing is not a justification for reducing the transparency standards imposed by the Regulation.
EDPB: The [controller's] assessment should aim at choosing the most appropriate method for providing all information covered by this right, depending on the specific circumstances in each case. As a consequence, a controller who processes a vast amount of data on a large scale must accept to undertake great efforts to ensure the right of access to the data subjects in a concise, transparent, intelligible and easily accessible form, by using plain and clear language.[4]
(ii) Clarity
The appropriateness of a measure shall also be assessed against the clarity requirement set forth in Article12. The information or communications must always be presented in a concise, transparent, intelligible and easily accessible way, using clear and plain language.
Conciseness
Information about the processing must be presented concisely. This is intended to prevent controllers from providing a too detailed description of the processing activity, as data subjects generally have very limited attention spans. Thus, controllers have a positive obligation to prevent data subjects from experiencing information overload.[5] For example, the use of a layered privacy statement may present the most relevant section to the data subject rather than providing them with an unconscionable notice.
EDPB: In an online context, the use of a layered privacy statement/ notice will enable a data subject to navigate to the particular section of the privacy statement/ notice which they want to immediately access rather than having to scroll through large amounts of text searching for particular issues.[6]
Transparency
The main goal of transparency is the actual understanding of data processing operations.[7] A data subject should be able to determine in advance what the scope and consequences of the processing entails and they should not be surprised at a later point about the ways in which their personal data has been used.[8]
Example: If a controller (e.g. provider of a website) does not have sufficient information about the functioning of software it uses (e.g. because the manufacturer of this software does not disclose it), or simply does not understand it (so that it cannot fulfil its duty to inform the data subject), it should refrain from using the software.[9]
For complex, technical or unexpected data processing, in addition to providing the prescribed information under Articles 13 and 14 GDPR, controllers should also separately spell out in unambiguous language what the most important consequences of the processing will be.[10]
EDPB: in case of mobile apps, the privacy information in question should be specific to the particular app and should not merely be the generic privacy policy of the company that owns the app or makes it available to the public.[11]
Intelligibility
Information is “intelligible” when it is understandable by an average member of the intended audience. Therefore, an accountable data controller must have an understanding of the people that it collects information about, which it should use to determine what they are likely to understand. For example, a controller collecting the personal data of working professionals can assume its audience has a higher level of understanding than a controller that obtains the personal data of children.
EDPB: If controllers are uncertain about the level of intelligibility, they can test these through mechanisms such as, inter alia, user panels, readability testing, as well as formal and informal dialogue with industry groups, consumer advocacy groups and regulatory bodies (Article 35(9) GDPR). [FN]
Easily Accessible Form
Under Article 12(1), controllers must provide any information to the data subject. The verb "provide" makes it clear that the controller must take every step necessary to provide that information. In other words, the data subject need not make any special effort to "seek" the information to which it is entitled. On the contrary, the controller will provide data subjects with direct links to the information, or clearly signpost information as an answer to a natural language question (e.g. in an online layered privacy statement, in FAQs, by way of contextual pop-ups which activate when a data subject fills in an online form, in an interactive digital context through a chatbot interface, etc.).[12]
EDPB: For apps, the necessary information should also be made available from an online store prior to download. Once the app is installed, the information still needs to be easily accessible from within the app. One way to meet this requirement is to ensure that the information is never more than “two taps away” (e.g. by including a “Privacy”/ “Data Protection” option in the menu functionality of the app). [FN]
Clear and plain language
The requirement for clear and plain language means that information should be provided in as simple a manner as possible, avoiding complex sentence and language structures.[13] The information should be concrete as well as definitive, and should neither be phrased in abstract or ambivalent terms, nor leave room for diverging interpretations. In particular, the purposes of and legal basis for processing the personal data should be clear.[14]
Common misunderstanding: Language qualifiers such as “may”, “might”, “some”, “often” and “possible” should be avoided. Where data controllers opt to use vague language, they should be able to, in accordance with the principle of accountability, demonstrate why the use of such language could not be avoided and how it does not undermine the fairness of processing.[15]
This requirement also affects the language used for the communication. Whilst the GDPR does not expressly regulate the matter, it is clear that the level of intelligibility of information is directly linked to the user’s capacity of understanding a certain language.
EDPB: Where the information is translated into one or more other languages, the data controller should ensure that all the translations are accurate and that the phraseology and syntax makes sense in the second language(s) so that the translated text does not have to be deciphered or re-interpreted. (A translation in one or more other languages should be provided where the controller targets15 data subjects speaking those languages.)[FN]
In writing or by other means
Under Article 12(1) GDPR, information “shall be provided in writing, or by other means, including, where appropriate, by electronic means.” Written form is therefore the default option. However, where writing is not possible, other means can be used. For instance, if a data controller operates a website, a written notice is not necessary and electronic forms are to be preferred. In such cases, the use of a webpage containing the information will adequately serve the purpose.
The WP29 suggested the implementation of layered privacy statements which allow website visitors to navigate to particular aspects of the relevant privacy statement that are of most interest to them.[16] The use of a layered approach is nonetheless not the only available option. Other electronic means include “just-in-time” contextual pop-up notices, 3D touch or hover-over notices, and privacy dashboards. Non-written electronic means which may be used in addition to a layered privacy statement might also include videos and smartphone or IoT voice alerts.
“Other [not necessarily electronic] means” might include cartoons, infographics or flowcharts.[17] The method chosen by controllers must fit the particular circumstances. For example, if a certain device does not have a screen, providing information in an electronic written format would not make much sense. In such cases, controllers can provide a printed privacy statement inside the device package or redirect the data subject to the URL website address where the privacy notice can be found.[18]
Finally, the GDPR also empowers data subjects to be provided orally, but only under two conditions: (i) the data subject must request oral information or communication and (ii) the controller must have otherwise verified the data subject’s identity.[19] The second requirement, (ii), only refers to cases where data subject's authentication is necessary. Consequently, it generally applies when a data subject exercises one of their GDPR rights (Articles 15 - 22) or when a communication of personal data breach is needed under Article 34 GDPR.
(2) Obligation to facilitate the exercise of rights
Under Article 12(2), first sentence, GDPR the controller must facilitate the data subject in the exercise of their GDPR rights.
Shall facilitate
The term "facilitate" implies a proactive approach by the controller who must take any action to ease the exercise of GDPR rights.[20] The Regulation does not define the notion of “facilitation”, but warns that “modalities" should be provided for facilitating the exercise of the data subject's rights.[21] These “modalities” should cover the whole range of activities a controller undertakes to fully address a GDPR request. To be more precise, controllers must demonstrate that "the way to handle the request aims to give the broadest effect to the right [...] and that it is in line with its obligation to facilitate the exercise of data subjects rights (Art. 12(2) GDPR)."[22] Among the others, data subjects should be allowed to reach the controller and its DPO “in an easy way (a postal address, a dedicated telephone number, and a dedicated e-mail address)”.[23] Once the request is received, the controller should be able to handle it internally as efficiently as possible, and ensure the request be handled by the appropriate department.[24] Data subject authentication should be free of unnecessary burdens. The method used for authentication should be "relevant, appropriate, proportionate and respect the data minimisation principle."[25] Any subsequent interaction that the controller feels it must have with the data subject must also be facilitated. This dynamic, however, must once again be marked by the principle of fairness and must not result in unnecessary "ping-pongs" whose only goal is to prevent the data subject from obtaining the response.[26]
Data subject requests always addressed unless identification is impossible
The final part of Article 12(2) GDPR states that the controller shall not refuse to act on a request of the data subject to exercise their rights, unless it demonstrates that it is not in a position to identify the data subject. However, in such circumstances the data subject may provide additional information enabling their identification (Article 11(2) GDPR). In order to allow the data subject to provide this additional information, the controller should inform the data subject of the nature of what is required to allow identification. This provision, prevents the controller from adopting obstructive tactics relating to alleged "difficulties of identification" unless these actually exist. Consequently, all attempts at verification which require excessive efforts (while adding nothing in terms of security) become inadmissible - and do not constitute 'facilitation'. [27]
Example: a user signs up to a social network by providing their email and generating a login password. After a few years of use, they decide to send an email login request because the information download tool provided by the controller does not provide certain information. Upon receipt of the email, the controller requests the user to send a scan of their identification document to verify their identity. This conduct constitutes a breach of the obligation to facilitate the exercise of rights. The controller may nonetheless send a unique identification link to the email address used by the user for registration.[28]
(3) Time limit and form of the request
Under Article 12(3) GDPR, the controller must inform the data subject about the "action taken" following receipt of a request. Article 12 deals with the exercise of GDPR rights in general. The wording "action taken" is therefore appropriate. In some cases, the "action" will consist of retrieving and arranging personal data (the copy of data undergoing processing under Article 15(3) GDPR). In others, the action takes place within the controller's IT systems (data rectification and deletion, under Articles 16 and 17 GDPR).
A "response" to the data subject, communicating the results of which action was taken is always necessary. This must happen as soon as possible ("without undue delay") and in any event within one month. The EDPB confirms that the period in question should be calculated according to Regulation (UE) 1182/71.
EDPB: Example 1: An organisation receives a request on 5 March. The time limit starts from the same day. This gives the organisation until and including 5 April to comply with the request, at the latest. Example 2: If the organisation receives a request on 31 August, and as the following month is shorter there is no corresponding date, the date for response, at the latest, is the last day of the following month, hence 30 September. [FN, Access, 48]]
The one-month deadline may be extended by two months if the requests are so complex or numerous that they cannot be answered within one month. A controller cannot extend the duration simply because its inadequate internal organisation prevents them from complying with a request in a timely manner. As mentioned before, "a controller who processes a vast amount of data on a large scale must accept to undertake great efforts" to ensure GDPR compliance [FN]. In any case, when a controller is unable to comply with the one-month deadline, it must inform the data subject of the reasons for the delay within one month of receiving the request.
The final sentence of Article 12(3) specifies that where the data subject makes the request by electronic means, and unless otherwise requested by them, the information shall be provided in a commonly used electronic form. However, the provision of electronic means is not an obligation for the controller. Nevertheless, Recital 63 GDPR expressly indicates that, where possible, the controller should be able to provide remote access to a secure system which would provide the data subject with direct access to their personal data. This is clearly intended to encourage controllers to facilitate the exercise of access rights.
(4) Failure to act on the request
If a controller does not act on the data subject's request, it must explain why this is the case as soon as possible, and at the latest within one month of receiving the request. It must also tell the data subject about their right to lodge a complaint with a supervisory authority or to seek a judicial remedy.
These are obviously cases in which one or more of the prerequisites of the GDPR or the right exercised do not exist, or there are other grounds for exclusion of the right. To give a few examples, the controller may reject the request if he considers that no personal data is being processed, thus failing to apply the GDPR in its entirety (Article 4(1) and (2) GDPR). Or if the request is 'manifestly unfounded or excessive' (Article 12(5) GDPR). Again, the controller may reject a request for access, or a part thereof, in order to defend "the rights and freedoms of others" (Article 15(4) GDPR) or, a request for deletion, on the basis of one of the cases provided for in Article 17(3) GDPR.
In such circumstances, the communication must convey "the reasons for not taking action". It is therefore necessary to at least indicate the legal title on which the rejection. Based on the above-mentioned examples, Articles 4(1), 12(5), 15(4) or 17(3) GDPR.
(5) Free of charge
Under Article 12(5) GDPR, controllers may generally not charge data subjects for the provision of information under Articles 13 and 14 GDPR, or for communications and actions taken under Articles 15-22 GDPR (data subject rights) and Article 34 GDPR (communication of personal data breaches to data subjects). The principle of transparency requires that the provision of such information is not made conditional upon a financial transaction. There are exceptions to this rule, which should nonetheless be interpreted narrowly to avoid undermining the principle of transparency and gratuity of the request.[29] For instance, if the request is manifestly unfounded or excessive, controllers may either charge a reasonable fee or refuse to act on the request. In these cases, controllers must be able to demonstrate the manifestly unfounded or excessive character of a request (Article 12(5), third sentence, GDPR). Hence, controllers should maintain a proper documentation of the underlying facts.
Manifestly unfounded
A request is considered manifestly unfounded if it does not meet essential legal requirements and is therefore “obvious”.[30] For example, if an unauthorised person wants to assert the rights of a data subject, or when an individual requests the erasure of their personal data vis-à-vis a controller who has not stored any data concerning them.[31]
Excessive requests
There is no definition of the term “excessive” in the GDPR. On the one hand, the wording “in particular because of their repetitive character” in Article 12(5) GDPR suggests that the main scenario to which this limb applies is when a data subject makes a large amount of access requests under Article 15 GDPR. On the other hand, the qualifier “in particular” indicates that other reasons that might cause excessiveness are not excluded a priori.[32]
A data subject may nonetheless undoubtedly submit more than one request to a controller. In this case, it has to be assessed whether the threshold of reasonable intervals (see Recital 63) has been exceeded. Controllers must take into account the particular circumstances of the single case carefully. In general, “The more often changes occur in the database of the controller, the more often data subjects may be permitted to request access without it being excessive”.[33] That said, other factors such as the nature of the data, the purpose of the processing and whether the subsequent requests concern the same type of information or processing activities should all be taken into account.[34]
Another relevant factor is the nature of the communication channel between the data subject and controller. Taking the example of an access request, if it is possible to easily provide the relevant information by electronic means or by remote access to a secure system, which makes compliance simple for the controller, it is unlikely that repetitive requests can be regarded as excessive.[35]
(a) Reasonable fee
If information requests are manifestly unfounded or excessive, in particular due to their repetitive nature, the data controller may charge a reasonable fee. This exception must be interpreted restrictively in order to not excessively constrain data subjects’ right to information. Consequently, provided the request is not manifestly unfounded or repetitive, the controller cannot charge a fee even it was provided for in the contract terms. Controllers should inform data subjects of their intention to charge them a reasonable fee based on Article 12(5) GDPR before doing so, to allow them to decide whether they should withdraw their request to avoid being charged.[36]
(b) Refuse to act
Alternatively, if requests are manifestly unfounded or excessive, the controller can outright refuse to act on the request. For both of the aforementioned exceptions to the no-fee rule, the controller bears the burden of demonstrating the manifestly unfounded or excessive character of the request.
(6) Verifying the data subject
Controllers often reject data subjects’ requests because of alleged problems in identifying them and the risk of disclosing personal data to an unauthorised person which, for example, might contribute to identity theft. If the controller has reasonable doubts concerning the identity of a natural person making a request under Articles 15 to 21 GDPR, additional information may be requested to verify their identity. However, this cannot lead to excessive demands and to the collection of personal data which are not relevant or necessary to strengthen the link between the individual and the personal data requested.
EDPB: For instance, when a given processing operation begins with the storage of a cookie into the user's device, a controller cannot ask the data subject to provide IDs, signatures and in general anything that cannot help the identification purpose. However, if Mr. X tries to exercise his access right by e-mail or by regular mail, then in this context C will have no other choice to ask Mr. X to provide “additional information” (Art. 12(6)) in order to be able to identify the advertising profile associated with Mr. X. In this case, the additional information will be the cookie identifier stored in the terminal equipment of Mr. X.
In the context of online services, the data subject can be authenticated, inter alia, by sending a secret code, a link containing a unique token to their email address, or any other contact method used for the registration.[37] Further information about this can be found in the commentary under Article 11 GDPR.
(7) Standardised icons
Information can also be provided visually, using certain kind of tools (e.g. icons, certification mechanisms, and data protection seals and marks). However, the use of icons should not replace the information needed by data subjects to enforce their rights, nor should they be used as a substitute to compliance with the controller’s obligations under Articles 13 and 14 GDPR. Instead, they could constitute an acceptable first layer of information. For example, an icon representing a lock might be used to signal that data is safely collected or encrypted. Whilst it is one of the EDPB’s tasks under Article 70(1)(r) to provide the Commission with an opinion on the icons, it has not yet published such a document.
(8) Code of icons
The Commission has the power to determine the information to be displayed by icons as well as the procedures for providing standardised icons. Its competence does not include the binding establishment of specific icons. Per Recital 166 GDPR, the process of developing a code of icons should involve the carrying out of consultations, and research on the efficacy of icons. Article 12(8) does not expressly specify whose responsibility it is to conduct such research, meaning standardised icons could come from either the Commission or standard-setting organisations.
Decisions
→ You can find all related decisions in Category:Article 12 GDPR
References
- ↑ Considered together, these provisions list all communication and information obligations the controller owes to the data subject.
- ↑ Hence, the "measures" under Article 12(1) form a stricter group than those mentioned, among the others, in Article 24 GDPR. In the latter case, measures concerned are those used to ensure compliance with the Regulation as a whole (and not only Articles 15-22).
- ↑ Bäcker, in Kühling, Buchner, DS-GVO BDSG, Article 12, margin number 11 (C.H. Beck 2020, 3rd Edition).
- ↑ EDPB, ‘Guidelines 01/2022 on data subject rights - Right of access’, 18 January 2022 (Version 1.0), p. 40.
- ↑ Heckmann, Paschke, in Ehmann, Selmayr, Datenschutz-Grundverordnung, Article 12 GDPR, margin number 12 (C.H. Beck 2018, 2nd Edition).
- ↑ WP29, ‘Guidelines on Transparency under Regulation 2016/679’, 17/EN WP260 rev.01, 11 April 2018, p. 7 (available here).
- ↑ Recitals 39 and 58 GDPR require that information must not only be clear, but also “easy to understand”. Along these lines, the CJEU criticised the behaviour of a controller "in the absence of any indications confirming that that clause was actually read and digested". See, CJEU, C‑61/19, Orange România, 11 November 2020, margin number 46 (available here).
- ↑ This provision reflects the German doctrine of informational self-determination, according to which substantive rights of data subjects can only serve their purpose when supported by clear information as well as proportionate and effective procedures. Polčák, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 12 GDPR, pp. 401-402 (Oxford University Press 2020). See, Polčák, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 12 GDPR, pp. 401-402 (Oxford University Press 2020).
- ↑ Dix, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 12 GDPR, margin number 22 (C.H. Beck 2019).
- ↑ WP29, ‘Guidelines on Transparency under Regulation 2016/679’, 17/EN WP260 rev.01, 11 April 2018, p. 7 (available here).
- ↑ WP29, ‘Guidelines on Transparency under Regulation 2016/679’, 17/EN WP260 rev.01, 11 April 2018, p. 8 (available here).
- ↑ WP29, ‘Guidelines on Transparency under Regulation 2016/679’, 17/EN WP260 rev.01, 11 April 2018, p. 8 (available here).
- ↑ Best practices for clear communication should be followed regardless whether information is written, delivered orally, or by audio/audio-visual methods (including for vision-impaired data subjects).
- ↑ Recital 39: "The principle of transparency [...] concerns, in particular, information to the data subjects on the identity of the controller and the purposes of the processing and further information to ensure fair and transparent processing in respect of the natural persons concerned and their right to obtain confirmation and communication of personal data concerning them which are being processed".
- ↑ WP29, ‘Guidelines on Transparency under Regulation 2016/679’, 17/EN WP260 rev.01, 11 April 2018, p. 9 (available here).
- ↑ WP29, ‘Guidelines on Transparency under Regulation 2016/679’, 17/EN WP260 rev.01, 11 April 2018, pp. 11-12 (available here).
- ↑ WP29, ‘Guidelines on Transparency under Regulation 2016/679’, 17/EN WP260 rev.01, 11 April 2018, p. 12 (available here).
- ↑ WP29, ‘Guidelines on Transparency under Regulation 2016/679’, 17/EN WP260 rev.01, 11 April 2018, p. 12 (available here).
- ↑ Dix, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 12 GDPR, margin number 22 (C.H. Beck 2019).
- ↑ Paal, Hennemann, in Paal, Pauly, DS-GVO BDSG, Article 12 GDPR, margin number 45 (C.H. Beck 2021, 3rd ed.).
- ↑ This includes “mechanisms to request and, if applicable, obtain, free of charge, in particular, access to and rectification or erasure of personal data and the exercise of the right to object” (Recital 59).
- ↑ [FN, Access, 16]
- ↑ The WP29 also points out that, “[w]hen appropriate, for purposes of communications with the public, other means of communications could also be provided”. WP29, ‘Guidelines on Data Protection Officers (‘DPOs’)’, 16/EN WP243 rev.01, 5 April 2017, p. 13 (available here).
- ↑ The EDPB recommends, as good practice, that controllers introduce, where possible, mechanisms to improve internal communication between employees on requests received by those who may not be competent to deal with such requests. In order to facilitate the exercise of data subjects’ rights.[FN]
- ↑ If the controller imposes measures aimed at identifying "the data subject which are burdensome, it needs to adequately justify this and ensure compliance with all fundamental principles, including data minimisation and the obligation to facilitate the exercise of data subjects’ rights (Art. 12(2) GDPR)." FN
- ↑ EDPB: It is important to underline that the request for specification shall not aim at a limitation of the reply to the access request and shall not be used to hide any information on the data or the processing concerning the data subject. If the data subject, who has been asked to specify the scope of its request, confirms to seek all personal data concerning him or her, the controller of course has to provide it in full.
- ↑ [Ref to Art. 11]
- ↑ EDPB, ‘Guidelines 01/2022 on data subject rights - Right of access’, 18 January 2022 (Version 1.0), p. 26 (available here).
- ↑ EDPB, ‘Guidelines 01/2022 on data subject rights - Right of access’, 18 January 2022 (Version 1.0), p. 53 (available here).
- ↑ In its Guidelines on access requests, the EDPB emphasises that “there is only very limited scope for relying on the «manifestly unfounded» alternative of Art. 12(5) in terms of requests for the right of access”. See, EDPB, ‘Guidelines 01/2022 on data subject rights - Right of access’, 18 January 2022 (Version 1.0), p. 51 (available here).
- ↑ Heckmann, Paschke, in Ehmann, Selmayr, Datenschutz-Grundverordnung, Article 12 GDPR, margin number 43 (C.H. Beck, 2nd Edition 2018).
- ↑ EDPB, ‘Guidelines 01/2022 on data subject rights - Right of access’, 18 January 2022 (Version 1.0), p. 53 (available here).
- ↑ EDPB, ‘Guidelines 01/2022 on data subject rights - Right of access’, 18 January 2022 (Version 1.0), p. 54 (available here).
- ↑ EDPB, ‘Guidelines 01/2022 on data subject rights - Right of access’, 18 January 2022 (Version 1.0), p. 54 (available here, p. 54).
- ↑ Importantly, and once again, especially for what concerns access requests, the simple fact that it would take the controller a vast amount of time and effort to provide the information cannot on its own render the request excessive. See, EDPB, ‘Guidelines 01/2022 on data subject rights - Right of access’, 18 January 2022 (Version 1.0), p. 55 (available here).
- ↑ EDPB, ‘Guidelines 01/2022 on data subject rights - Right of access’, 18 January 2022 (Version 1.0), pp. 56-57 (available here).
- ↑ According to the WP29’s guidelines on the right to data portability, as endorsed by the EDPB, insofar as a digital communication channel already exists between the data subject and the controller, the latter must implement or re-use an authentication procedure in order to ascertain the identity of the data subjects requesting their personal data or exercising the rights granted by the GDPR. See, WP29 ‘Guidelines on the right to data portability’, 16/EN WP 242 rev.01, 5 April 2017, p.14 (available here).
