Article 20 GDPR: Difference between revisions

From GDPRhub
Line 207: Line 207:


The right to data portability complements the right of access ([[Article 15 GDPR]]) by empowering users to receive a copy of their data in a structured, commonly used, and machine-readable format. Users can decide what they want to do with such data and either store it on their computer, send it to another controller, or send it to another third party. The right to portability is not limited to the providers that offer similar or comparable services, it can be exercised with any controller a data subject chooses under the conditions specified below.     
The right to data portability complements the right of access ([[Article 15 GDPR]]) by empowering users to receive a copy of their data in a structured, commonly used, and machine-readable format. Users can decide what they want to do with such data and either store it on their computer, send it to another controller, or send it to another third party. The right to portability is not limited to the providers that offer similar or comparable services, it can be exercised with any controller a data subject chooses under the conditions specified below.     
===(1) Right to Data Portability===


=== Responsibilities of Controllers ===
The data subject has the right to request and obtain a copy of the personal data previously provided to the controller. In order to make it easier to read, both for the data subject himself and for any controllers who may receive it in the future, this information must be structured in accordance with certain requirements. Once received, the information can obviously be shared with other data controllers.
Controllers which address portability requests ("sending controllers") act on behalf of a data subject and are responsible for:


*providing prior information about the existence of such a right (e.g. in the privacy notice) and clearly explaining the difference between the right of access and the right to data portability;
==== Material Scope ====
*processing the request without undue delay, within 1 month (up to 3 months);
Data subjects may request the transmission of data that concerns them (i.e. not anonymous data) and that they provided to the controller. The data "provided" is the data that was actively given to the controller (e.g. photos uploaded to the service) or which was "observed" by a controller (e.g. activity logs, food preferences, etc). This definition also includes data that have been transferred to the controller in the context of the exercise of the right to data portability.<ref name=":2">''Herbst'', in Kühling, Buchner, DS-GVO BDSG, Article 20 GDPR, margin number 11 (Beck 2020, 3rd ed.) (accessed 18 August 2021).</ref> According to this suggestion, "''data collected by a device such as a 'quantified self' application that tracks an individual's movements (exercise, sleep etc.) would be within the scope of the right while any insights gleaned on the basis of that information (for example, about the individual's health status or working patterns) would be excluded from the scope of the right''".<ref>''Lynskey'' in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 20 GDPR, p. 503 (Oxford University Press 2020). Along the same lines, the recent EDPB, Guidelines 01/2022 on data subject rights - Right of access (Version for open consultation), 18.1.2022, p. 32.</ref>
*carrying out authentication;
*setting safeguards to ensure they genuinely act on the data subject’s behalf (e.g. ensure that they transmit the exact type of personal data that the data subject wants to transmit);
*in light of the principles set forth in [[Article 5 GDPR|Article 5(1) GDPR]], ensuring that the data transmitted is accurate and up to date;
*taking all the security measures for transmissions.
*


The sending controllers are, however, not responsible for the processing handled by the data subject or by another company receiving personal data. ''"In this respect, the data controller is not responsible for compliance of the receiving data controller with data protection law, considering that it is not the sending data controller that chooses the recipient."''<ref name=":0">WP29, Guidelines on the right to "data portability", 5 April 2017, [https://ec.europa.eu/newsroom/article29/items/611233 p. 8].</ref>
==== Conditions to Exercise Data Portability ====
The right to data portability only applies if (i) the individual has either consented to the processing or if the information is processed for the execution of a contract between the data subject and controller<ref name=":3">However, according to the WP29, it is a good practice to address portability requests also in such cases that do not explicitly provide for a general right to data portability, i.e. when processing is based on the legitimate interests or for the performance of a task carried out in the public interest. See, WP29, Guidelines on the right to "data portability", 5 April 2017, [https://ec.europa.eu/newsroom/article29/items/611233 p. 8].</ref> and (ii) data is processed automatically. Therefore, data which is available e.g. only on paper and which is processed manually falls out of the data portability scope.


Data controllers which receive portability requests ("receiving controllers") have an obligation to:
==== Responsibilities of Controllers ====
Controllers which address portability requests ("sending controllers") act on behalf of a data subject and are responsible for:


*"clearly and directly" state the purpose of the new processing before they accept the request in accordance with the transparency requirements set out in [[Article 14 GDPR]];''<ref name=":1">WP29, Guidelines on the right to "data portability", 5 April 2017, [https://ec.europa.eu/newsroom/article29/items/611233 p. 7].</ref>''
* providing prior information about the existence of such a right (e.g. in the privacy notice) and clearly explaining the difference between the right of access and the right to data portability;
*process the request without undue delay, within 1 month (up to 3 months);
* processing the request without undue delay, within 1 month (up to 3 months);
*ensure that the data they accept is relevant and not excessive for the intended data processing;
* carrying out authentication;
*delete the personal data which are not necessary to achieve the purpose of the new processing as soon as possible.
* setting safeguards to ensure they genuinely act on the data subject’s behalf (e.g. ensure that they transmit the exact type of personal data that the data subject wants to transmit);
* in light of the principles set forth in [[Article 5 GDPR|Article 5(1) GDPR]], ensuring that the data transmitted is accurate and up to date;
* taking all the security measures for transmissions.


The receiving controllers can decide whether to accept and process data from a portability request. 
Data controllers which receive portability requests ("receiving controllers") have an obligation to:
===(1) The Right to Receive and Transmit Personal Data===
 
The data subject can ask to transmit the data as long as the data controller processes it. This is to say that a controller cannot refuse a portability request only because the retention period is ending soon.


==== Material Scope ====
* "clearly and directly" state the purpose of the new processing before they accept the request in accordance with the transparency requirements set out in [[Article 14 GDPR]];
Data subjects may request the transmission of data that concerns them (i.e. not anonymous data) and that they provided to the controller. The data "provided" is the data that was actively given to the controller (e.g. photos uploaded to the service) or such which was "observed" by a controller (e.g. activity logs, food preferences etc).
''Lynskey''
* process the request without undue delay, within 1 month (up to 3 months);
* ensure that the data they accept is relevant and not excessive for the intended data processing;
* delete the personal data which are not necessary to achieve the purpose of the new processing as soon as possible.


The personal data which was transferred from one controller to another in the context of the exercise of the right to data portability should be considered as having been provided by the data subject.<ref name=":2">''Herbst'', in Kühling, Buchner, DS-GVO BDSG, Article 20 GDPR, margin number 11 (Beck 2020, 3rd ed.) (accessed 18 August 2021).</ref>
The receiving controllers can decide whether to accept and process data from a portability request.


The data portability right has the two following conditions:
==== Data Format ====
According to Article 20(1) GDPR the data should be provided to the data subject in a "structured, commonly used and machine-readable format". Apart from this, the GDPR is does not specify the format of the data transmitted.


====(a) Legal Basis for Processing====
According to Recital 68, the data should be available in an "interoperable format", which data controllers "''should be encouraged to develop''". The WP29 defines interoperability as the "''capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units''".<ref>WP29, Guidelines on the right to data portability (As last Revised and adopted on 5 April 2017), p. </ref>


The categories of data that can be requested are those processed either for the performance of a contract ([[Article 6 GDPR|Article 6(1)(b) GDPR]]) or to which processing a data subject gave his or her consent ([[Article 6 GDPR|Article 6(1)(a) GDPR]]). However, according to the WP29, it is a good practice to address portability requests also in such cases that do not explicitly provide for a general right to data portability, i.e. when processing is based on the legitimate interests or for the performance of a task carried out in the public interest.<ref name=":3">WP29, Guidelines on the right to "data portability", 5 April 2017, [https://ec.europa.eu/newsroom/article29/items/611233 p. 8].</ref>
The Commission has published a Communication on 'ICT Standardization Priorities for the Digital Single Market', which may be used as a basis on which to develop standards for the purposes of data portability.<ref>EU Commission Communication on ICT Standardisation Priorities for the Digital Single Market (Available [https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX:52016DC0176 here]).</ref> The WP29 recommends that data controllers offer several options to the data subject. They suggest, for instance, that data subjects should be offered an opportunity to directly download the data as well as to transmit it directly to another data controller, and that this could be implemented by making an Application Programme Interface ('API') available.<ref>Cormack expresses doubt regarding the viability of this solution, noting that many organisations will hold their data on internal databases that are securely firewalled from internet access as opposed to APis. Without standards leading to interoperability, the right to data portability may "''remain more a declaration of principle than a real and effective tool for individual self-determination in the digital environment''". See, ''Lynskey'' in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 20 GDPR, p. 503 (Oxford University Press 2020).</ref>


====(b) Processing by Automated Means====
===(2) Right to have Personal Data Directly Transmitted to Another Controller===
Data subjects can also ask the controller to send their personal data directly to another controller, if this is technically feasible. The sending controllers are, however, not responsible for the processing handled by the data subject or by another company receiving personal data. ''"In this respect, the data controller is not responsible for compliance of the receiving data controller with data protection law, considering that it is not the sending data controller that chooses the recipient".''<ref>WP29, Guidelines on the right to "data portability", 5 April 2017, p. 8.</ref>


Another condition is that the personal data is processed automatically, therefore the data which is available e.g. only on paper and which is processed manually falls out of the data portability scope.
Data portability is supposed to facilitate the reuse of personal data concerning the data subject provided that the copy of the data should be transmitted in the defined format. Controllers are therefore encouraged to use interoperable formats in order to facilitate such an exchange of personal data between each other. Companies may create sector-specific interoperable formats within an industry to allow for easier transmissions of personal data (see above).  
 
===(2) Right to Transmit Personal Data Directly to Another Controller===
Data subjects can also ask the controller to send their personal data directly to another controller, if this is technically feasible. Controllers are therefore encouraged to use interoperable formats in order to facilitate such an exchange of personal data between each other. Companies may create sector-specific interoperable formats within an industry to allow for easier transmissions of personal data.
 
Data portability is supposed to facilitate the reuse of personal data concerning the data subject provided that the copy of the data should be transmitted in the defined format.


===(3) Right to Erasure===
===(3) Right to Erasure===
The exercise of the right to data portability is without prejudice to any other rights under the GDPR. Thus, if data subjects want to delete their data from the controller's system (exercise the “right to be forgotten” under [[Article 17 GDPR]]), the controller cannot justify its denial to erase such data by the data portability request.
The exercise of the right to data portability is without prejudice to any other rights under the GDPR. Thus, if data subjects want to delete their data from the controller's system (exercise the “right to be forgotten” under [[Article 17 GDPR]]), the controller cannot justify its denial to erase such data by the data portability request.
===(4) Rights of Third Parties===
===(4) Rights of Third Parties===
The portability request should not include any third party data if there is a likelihood that the new processing will adversely affect the rights and freedoms of the other data subjects. ''"Such an adverse effect would occur, for instance, if the transmission of data from one data controller to another, would prevent third parties from exercising their rights as data subjects under the GDPR."''<ref name=":4">WP29, Guidelines on the right to "data portability", 5 April 2017, [https://ec.europa.eu/newsroom/article29/items/611233 p. 11]. </ref>
The portability request should not include any third party data if there is a likelihood that the new processing will adversely affect the rights and freedoms of the other data subjects. ''"Such an adverse effect would occur, for instance, if the transmission of data from one data controller to another, would prevent third parties from exercising their rights as data subjects under the GDPR."''<ref name=":4">WP29, Guidelines on the right to "data portability", 5 April 2017, [https://ec.europa.eu/newsroom/article29/items/611233 p. 11]. </ref> The rights and freedoms are unlikely to be adversely affected if the receiving controller processes the data of other data subjects for the same purpose it was processed by the sending controller.
 
The rights and freedoms are unlikely to be adversely affected if the receiving controller processes the data of other data subjects for the same purpose it was processed by the sending controller.


==Decisions==
==Decisions==

Revision as of 14:54, 13 February 2022

Article 20 - Right to data portability
Gdpricon.png
Chapter 10: Delegated and implementing acts

Legal Text

Article 20 - Right to data portability

1. The data subject shall have the right to receive the personal data concerning him or her, which he or she has provided to a controller, in a structured, commonly used and machine-readable format and have the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, where:

(a) the processing is based on consent pursuant to point (a) of Article 6(1) or point (a) of Article 9(2) or on a contract pursuant to point (b) of Article 6(1); and
(b) the processing is carried out by automated means.

2. In exercising his or her right to data portability pursuant to paragraph 1, the data subject shall have the right to have the personal data transmitted directly from one controller to another, where technically feasible.

3. The exercise of the right referred to in paragraph 1 of this Article shall be without prejudice to Article 17. That right shall not apply to processing necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.

4. The right referred to in paragraph 1 shall not adversely affect the rights and freedoms of others.

Relevant Recitals

Recital 68: Right to Data Portability
To further strengthen the control over his or her own data, where the processing of personal data is carried out by automated means, the data subject should also be allowed to receive personal data concerning him or her which he or she has provided to a controller in a structured, commonly used, machine-readable and interoperable format, and to transmit it to another controller. Data controllers should be encouraged to develop interoperable formats that enable data portability. That right should apply where the data subject provided the personal data on the basis of his or her consent or the processing is necessary for the performance of a contract. It should not apply where processing is based on a legal ground other than consent or contract. By its very nature, that right should not be exercised against controllers processing personal data in the exercise of their public duties. It should therefore not apply where the processing of the personal data is necessary for compliance with a legal obligation to which the controller is subject or for the performance of a task carried out in the public interest or in the exercise of an official authority vested in the controller. The data subject's right to transmit or receive personal data concerning him or her should not create an obligation for the controllers to adopt or maintain processing systems which are technically compatible. Where, in a certain set of personal data, more than one data subject is concerned, the right to receive the personal data should be without prejudice to the rights and freedoms of other data subjects in accordance with this Regulation. Furthermore, that right should not prejudice the right of the data subject to obtain the erasure of personal data and the limitations of that right as set out in this Regulation and should, in particular, not imply the erasure of personal data concerning the data subject which have been provided by him or her for the performance of a contract to the extent that and for as long as the personal data are necessary for the performance of that contract. Where technically feasible, the data subject should have the right to have the personal data transmitted directly from one controller to another.

Recital 73: Restrictions by Member States
Restrictions concerning specific principles and the rights of information, access to and rectification or erasure of personal data, the right to data portability, the right to object, decisions based on profiling, as well as the communication of a personal data breach to a data subject and certain related obligations of the controllers may be imposed by Union or Member State law, as far as necessary and proportionate in a democratic society to safeguard public security, including the protection of human life especially in response to natural or manmade disasters, the prevention, investigation and prosecution of criminal offences or the execution of criminal penalties, including the safeguarding against and the prevention of threats to public security, or of breaches of ethics for regulated professions, other important objectives of general public interest of the Union or of a Member State, in particular an important economic or financial interest of the Union or of a Member State, the keeping of public registers kept for reasons of general public interest, further processing of archived personal data to provide specific information related to the political behaviour under former totalitarian state regimes or the protection of the data subject or the rights and freedoms of others, including social protection, public health and humanitarian purposes. Those restrictions should be in accordance with the requirements set out in the Charter and in the European Convention for the Protection of Human Rights and Fundamental Freedoms.

Recital 156: Processing of Personal Data for Archiving Purposes in the Public Interest, Scientific, Historical Research or Statistical Purposes
The processing of personal data for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes should be subject to appropriate safeguards for the rights and freedoms of the data subject pursuant to this Regulation. Those safeguards should ensure that technical and organisational measures are in place in order to ensure, in particular, the principle of data minimisation. The further processing of personal data for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes is to be carried out when the controller has assessed the feasibility to fulfil those purposes by processing data which do not permit or no longer permit the identification of data subjects, provided that appropriate safeguards exist (such as, for instance, pseudonymisation of the data). Member States should provide for appropriate safeguards for the processing of personal data for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes. Member States should be authorised to provide, under specific conditions and subject to appropriate safeguards for data subjects, specifications and derogations with regard to the information requirements and rights to rectification, to erasure, to be forgotten, to restriction of processing, to data portability, and to object when processing personal data for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes. The conditions and safeguards in question may entail specific procedures for data subjects to exercise those rights if this is appropriate in the light of the purposes sought by the specific processing along with technical and organisational measures aimed at minimising the processing of personal data in pursuance of the proportionality and necessity principles. The processing of personal data for scientific purposes should also comply with other relevant legislation such as on clinical trials.

Commentary on Article 20

The purpose of the right to data portability is to give data subjects more control over their personal data by granting them a certain type of "ownership". The goal is to increase competition on the market by allowing for the free movement of data between providers. Data portability is especially relevant in cases when one controller offers a higher level of protection of personal data than another within the same industry sector or across sectors.

The right to data portability complements the right of access (Article 15 GDPR) by empowering users to receive a copy of their data in a structured, commonly used, and machine-readable format. Users can decide what they want to do with such data and either store it on their computer, send it to another controller, or send it to another third party. The right to portability is not limited to the providers that offer similar or comparable services, it can be exercised with any controller a data subject chooses under the conditions specified below.

(1) Right to Data Portability

The data subject has the right to request and obtain a copy of the personal data previously provided to the controller. In order to make it easier to read, both for the data subject himself and for any controllers who may receive it in the future, this information must be structured in accordance with certain requirements. Once received, the information can obviously be shared with other data controllers.

Material Scope

Data subjects may request the transmission of data that concerns them (i.e. not anonymous data) and that they provided to the controller. The data "provided" is the data that was actively given to the controller (e.g. photos uploaded to the service) or which was "observed" by a controller (e.g. activity logs, food preferences, etc). This definition also includes data that have been transferred to the controller in the context of the exercise of the right to data portability.[1] According to this suggestion, "data collected by a device such as a 'quantified self' application that tracks an individual's movements (exercise, sleep etc.) would be within the scope of the right while any insights gleaned on the basis of that information (for example, about the individual's health status or working patterns) would be excluded from the scope of the right".[2]

Conditions to Exercise Data Portability

The right to data portability only applies if (i) the individual has either consented to the processing or if the information is processed for the execution of a contract between the data subject and controller[3] and (ii) data is processed automatically. Therefore, data which is available e.g. only on paper and which is processed manually falls out of the data portability scope.

Responsibilities of Controllers

Controllers which address portability requests ("sending controllers") act on behalf of a data subject and are responsible for:

  • providing prior information about the existence of such a right (e.g. in the privacy notice) and clearly explaining the difference between the right of access and the right to data portability;
  • processing the request without undue delay, within 1 month (up to 3 months);
  • carrying out authentication;
  • setting safeguards to ensure they genuinely act on the data subject’s behalf (e.g. ensure that they transmit the exact type of personal data that the data subject wants to transmit);
  • in light of the principles set forth in Article 5(1) GDPR, ensuring that the data transmitted is accurate and up to date;
  • taking all the security measures for transmissions.

Data controllers which receive portability requests ("receiving controllers") have an obligation to:

  • "clearly and directly" state the purpose of the new processing before they accept the request in accordance with the transparency requirements set out in Article 14 GDPR;

Lynskey

  • process the request without undue delay, within 1 month (up to 3 months);
  • ensure that the data they accept is relevant and not excessive for the intended data processing;
  • delete the personal data which are not necessary to achieve the purpose of the new processing as soon as possible.

The receiving controllers can decide whether to accept and process data from a portability request.

Data Format

According to Article 20(1) GDPR the data should be provided to the data subject in a "structured, commonly used and machine-readable format". Apart from this, the GDPR is does not specify the format of the data transmitted.

According to Recital 68, the data should be available in an "interoperable format", which data controllers "should be encouraged to develop". The WP29 defines interoperability as the "capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units".[4]

The Commission has published a Communication on 'ICT Standardization Priorities for the Digital Single Market', which may be used as a basis on which to develop standards for the purposes of data portability.[5] The WP29 recommends that data controllers offer several options to the data subject. They suggest, for instance, that data subjects should be offered an opportunity to directly download the data as well as to transmit it directly to another data controller, and that this could be implemented by making an Application Programme Interface ('API') available.[6]

(2) Right to have Personal Data Directly Transmitted to Another Controller

Data subjects can also ask the controller to send their personal data directly to another controller, if this is technically feasible. The sending controllers are, however, not responsible for the processing handled by the data subject or by another company receiving personal data. "In this respect, the data controller is not responsible for compliance of the receiving data controller with data protection law, considering that it is not the sending data controller that chooses the recipient".[7]

Data portability is supposed to facilitate the reuse of personal data concerning the data subject provided that the copy of the data should be transmitted in the defined format. Controllers are therefore encouraged to use interoperable formats in order to facilitate such an exchange of personal data between each other. Companies may create sector-specific interoperable formats within an industry to allow for easier transmissions of personal data (see above).

(3) Right to Erasure

The exercise of the right to data portability is without prejudice to any other rights under the GDPR. Thus, if data subjects want to delete their data from the controller's system (exercise the “right to be forgotten” under Article 17 GDPR), the controller cannot justify its denial to erase such data by the data portability request.

(4) Rights of Third Parties

The portability request should not include any third party data if there is a likelihood that the new processing will adversely affect the rights and freedoms of the other data subjects. "Such an adverse effect would occur, for instance, if the transmission of data from one data controller to another, would prevent third parties from exercising their rights as data subjects under the GDPR."[8] The rights and freedoms are unlikely to be adversely affected if the receiving controller processes the data of other data subjects for the same purpose it was processed by the sending controller.

Decisions

→ You can find all related decisions in Category:Article 20 GDPR

References

  1. Herbst, in Kühling, Buchner, DS-GVO BDSG, Article 20 GDPR, margin number 11 (Beck 2020, 3rd ed.) (accessed 18 August 2021).
  2. Lynskey in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 20 GDPR, p. 503 (Oxford University Press 2020). Along the same lines, the recent EDPB, Guidelines 01/2022 on data subject rights - Right of access (Version for open consultation), 18.1.2022, p. 32.
  3. However, according to the WP29, it is a good practice to address portability requests also in such cases that do not explicitly provide for a general right to data portability, i.e. when processing is based on the legitimate interests or for the performance of a task carried out in the public interest. See, WP29, Guidelines on the right to "data portability", 5 April 2017, p. 8.
  4. WP29, Guidelines on the right to data portability (As last Revised and adopted on 5 April 2017), p.
  5. EU Commission Communication on ICT Standardisation Priorities for the Digital Single Market (Available here).
  6. Cormack expresses doubt regarding the viability of this solution, noting that many organisations will hold their data on internal databases that are securely firewalled from internet access as opposed to APis. Without standards leading to interoperability, the right to data portability may "remain more a declaration of principle than a real and effective tool for individual self-determination in the digital environment". See, Lynskey in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 20 GDPR, p. 503 (Oxford University Press 2020).
  7. WP29, Guidelines on the right to "data portability", 5 April 2017, p. 8.
  8. WP29, Guidelines on the right to "data portability", 5 April 2017, p. 11.