Hoge Raad - 22/03293: Difference between revisions
mNo edit summary |
No edit summary |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 49: | Line 49: | ||
|Party_Link_2= | |Party_Link_2= | ||
|Appeal_From_Body=GHAMS | |Appeal_From_Body=GHAMS (Netherlands) | ||
|Appeal_From_Case_Number_Name=ECLI:NL:GHAMS:2019:3966 | |Appeal_From_Case_Number_Name=ECLI:NL:GHAMS:2019:3966 | ||
|Appeal_From_Status= | |Appeal_From_Status= | ||
Line 62: | Line 62: | ||
}} | }} | ||
The Dutch | The Dutch Supreme Court held that when a data subject seeks a judicial remedy under Article 79 GDPR for the rights under Articles 15-22 GDPR, a data subject's interest in seeking interim relief may override the 6-week time limit under Article 35 UAVG for submitting a request to the Court. | ||
== English Summary == | == English Summary == | ||
=== Facts === | === Facts === | ||
In the present case, the data subject had made an application after the six-week time limit laid down in Article 35(2) UAVG. The facts are as follows. The data subject had taken out a student loan in 2002, and consequently, the details of it were registered in the Dutch Central Credit Registration Office (BKR). This body keeps records of private parties that have taken out credit. In early 2018, the data subject had applied for a loan and was denied due to the financial records on their credit history kept by the BKR. | |||
On 27 June 2018, the data subject submitted an objection to processing (Article 21 GDPR) to BKR. By a letter dated 23 July 2018, BKR responded in the negative, refusing to comply with the objection. | |||
On 30 October 2018, the data subject made a request to the court to order the controller to comply with the request made under Article 21 GDPR. The Court at first instance dismissed the application because it fell outwith the 6-week time limit under Article 35 UAVG. The data subject appealed this decision. | |||
The main question brought before the Court was whether it was possible to raise an objection to the procesing of personal data in summary proceedings following the six-week time limit set out by Article 35(2) of the UAVG (Uitvoeringswet Algemene Verordening Gegevensbescherming). The UAVG is the Dutch national transposition of the GDPR. Article 35 UAVG implements Article 79 GDPR, and provides: | The main question brought before the Court was whether it was possible to raise an objection to the procesing of personal data in summary proceedings following the six-week time limit set out by Article 35(2) of the UAVG (Uitvoeringswet Algemene Verordening Gegevensbescherming). The UAVG is the Dutch national transposition of the GDPR. Article 35 UAVG implements Article 79 GDPR, and provides: | ||
Line 75: | Line 79: | ||
''2. The application shall be made within six weeks of receipt of the answer from the controller. If the controller has not replied within the time limits referred to in Article 12, paragraph 3 of the Regulation, the submission of the application shall not be subject to a period."'' | ''2. The application shall be made within six weeks of receipt of the answer from the controller. If the controller has not replied within the time limits referred to in Article 12, paragraph 3 of the Regulation, the submission of the application shall not be subject to a period."'' | ||
In the present | On 5 November 2019, the appeal was before the Amsterdam Court of Appeal. The Court upheld the First Instance ruling and dismissed the appeal. The Court of Appeal noted that: | ||
''"In a case like the present one, the claimant will have to <u>substantiate his urgent interests</u> against the background of Article 21 GDPR and 35 UAVG. That system is based on the idea that the parties first try to reach an agreement themselves and that, in the vent of a negative response under the penalty of inadmissability, the interested party has only a limited time to submit its objections to the Court."'' <ref>ECLI:NL:GHAMS:2019:3966, para 3.4.5</ref> | |||
Moreover, the Court held that repeated requests to the controller made under Articles 15-22 GDPR are considered manifestly unfounded or excessive on the ground that it is an appeal of a previously denied request where there has been no change in circumstances or facts. | |||
The data subject's application to the Court of Appeal to order the controller to comply with their Article 21 GDPR request failed. The Court reasoned that this was because there were no changes of circumstances or facts, the application was made after the 6-week limit, and the data subject had not adequately substantiated his urgent interest in the case. | |||
The data subject appealed the decision and on 15 September 2023, the Hoge Raad (Dutch Supreme Court) ruled on the case. | |||
=== Holding === | === Holding === | ||
The | The Supreme Court upheld the appeal and overtuned the Court of Appeal's ruling. In reaching its conclusion, the Court placed emphasis on the fundamental rights nature of the GDPR, pointing to Recitals 10 and 59 GDPR. Recital 10 establishes that Member States should provide for a high level of protection of the rights and freedoms of natural persons, and Recital 59 establishes that modalities should be provided for by the controller for facilitating the exercise of data subject's rights under the GDPR. | ||
The Court noted that Article 21 GDPR confers the right upon data subjects to confer to processing ''at any time''. The Court also pointed to Article 12 GDPR, which establishes that the burden falls upon the controller to demonstrate that a data subject's request is manifestly unfounded or excessive, not the data subject. The Court relied upon these provisions for its reading of Article 35(2) UAVG. The Court stated: | |||
''"In the light of the foregoing, Article 35(2) UAVG should be interpreted as meaning that in a case such as the one at issue here, where the controller has rejected the data subject's request within the time limits referred to in Article 12(3) UAVG and the data subject has not filed a petition as referred to in Article 35(1) UAVG against it within the six-week period mentioned in Article 35(2) UAVG, the data subject may choose to make a renewed request to the controller. If this repeated request is again rejected by the controller, the data subject may, under Article 35(1) UAVG, request the court to order the controller to still grant the request. If the controller has not responded to the repeated request within the time limits specified in Art. 12(3) UAVG, the submission of the petition is not subject to a time limit... The data subject in a case such as the one at issue here is also free to seek interim relief, both in anticipation of a repeated request to the controller and after such a request has been made."''<ref>Para 3.4.2</ref> | |||
Following from this, the Supreme Court held that the Court of Appeal had erred in the application of the law. The Supreme Court held that in this instance, the data subject's interest in seeking interim relief overrode the time limit under Article 35 UAVG. Thus, the data subject was free to seek a provisional injunction for interim measures. | |||
Lastly, the | Lastly, the Court held that it was wrong for the Court of Appeal to interpret Article 35 UAVG to mean that a data subject must base a repeated request under Articles 15-22 GDPR on new facts and circumstances to those of a previously denied request. | ||
As | As a result, the Court annuled the judgment of the Amsterdam Court of Appeal of 5 November 2019. | ||
== Comment == | == Comment == |
Latest revision as of 11:34, 4 October 2023
Hoge Raad - 22/03293 | |
---|---|
Court: | Hoge Raad (Netherlands) |
Jurisdiction: | Netherlands |
Relevant Law: | Article 15 GDPR Article 35 Uitvoeringswet Algemene Verordening Gegevensbescherming |
Decided: | 15.09.2023 |
Published: | 15.09.2023 |
Parties: | |
National Case Number/Name: | 22/03293 |
European Case Law Identifier: | ECLI:NL:HR:2023:1216 |
Appeal from: | GHAMS (Netherlands) ECLI:NL:GHAMS:2019:3966 |
Appeal to: | |
Original Language(s): | Dutch |
Original Source: | Hoge Raad (in Dutch) |
Initial Contributor: | Enzo Marquet |
The Dutch Supreme Court held that when a data subject seeks a judicial remedy under Article 79 GDPR for the rights under Articles 15-22 GDPR, a data subject's interest in seeking interim relief may override the 6-week time limit under Article 35 UAVG for submitting a request to the Court.
English Summary
Facts
In the present case, the data subject had made an application after the six-week time limit laid down in Article 35(2) UAVG. The facts are as follows. The data subject had taken out a student loan in 2002, and consequently, the details of it were registered in the Dutch Central Credit Registration Office (BKR). This body keeps records of private parties that have taken out credit. In early 2018, the data subject had applied for a loan and was denied due to the financial records on their credit history kept by the BKR.
On 27 June 2018, the data subject submitted an objection to processing (Article 21 GDPR) to BKR. By a letter dated 23 July 2018, BKR responded in the negative, refusing to comply with the objection.
On 30 October 2018, the data subject made a request to the court to order the controller to comply with the request made under Article 21 GDPR. The Court at first instance dismissed the application because it fell outwith the 6-week time limit under Article 35 UAVG. The data subject appealed this decision.
The main question brought before the Court was whether it was possible to raise an objection to the procesing of personal data in summary proceedings following the six-week time limit set out by Article 35(2) of the UAVG (Uitvoeringswet Algemene Verordening Gegevensbescherming). The UAVG is the Dutch national transposition of the GDPR. Article 35 UAVG implements Article 79 GDPR, and provides:
"1. If the decision on a request as referred to in Article 34 has been taken by a body other than an administrative body, the interested party may apply to the court with a written request to order the controller to comply with the request referred to in Articles 15 to 22 of the Regulation.
2. The application shall be made within six weeks of receipt of the answer from the controller. If the controller has not replied within the time limits referred to in Article 12, paragraph 3 of the Regulation, the submission of the application shall not be subject to a period."
On 5 November 2019, the appeal was before the Amsterdam Court of Appeal. The Court upheld the First Instance ruling and dismissed the appeal. The Court of Appeal noted that:
"In a case like the present one, the claimant will have to substantiate his urgent interests against the background of Article 21 GDPR and 35 UAVG. That system is based on the idea that the parties first try to reach an agreement themselves and that, in the vent of a negative response under the penalty of inadmissability, the interested party has only a limited time to submit its objections to the Court." [1]
Moreover, the Court held that repeated requests to the controller made under Articles 15-22 GDPR are considered manifestly unfounded or excessive on the ground that it is an appeal of a previously denied request where there has been no change in circumstances or facts.
The data subject's application to the Court of Appeal to order the controller to comply with their Article 21 GDPR request failed. The Court reasoned that this was because there were no changes of circumstances or facts, the application was made after the 6-week limit, and the data subject had not adequately substantiated his urgent interest in the case.
The data subject appealed the decision and on 15 September 2023, the Hoge Raad (Dutch Supreme Court) ruled on the case.
Holding
The Supreme Court upheld the appeal and overtuned the Court of Appeal's ruling. In reaching its conclusion, the Court placed emphasis on the fundamental rights nature of the GDPR, pointing to Recitals 10 and 59 GDPR. Recital 10 establishes that Member States should provide for a high level of protection of the rights and freedoms of natural persons, and Recital 59 establishes that modalities should be provided for by the controller for facilitating the exercise of data subject's rights under the GDPR.
The Court noted that Article 21 GDPR confers the right upon data subjects to confer to processing at any time. The Court also pointed to Article 12 GDPR, which establishes that the burden falls upon the controller to demonstrate that a data subject's request is manifestly unfounded or excessive, not the data subject. The Court relied upon these provisions for its reading of Article 35(2) UAVG. The Court stated:
"In the light of the foregoing, Article 35(2) UAVG should be interpreted as meaning that in a case such as the one at issue here, where the controller has rejected the data subject's request within the time limits referred to in Article 12(3) UAVG and the data subject has not filed a petition as referred to in Article 35(1) UAVG against it within the six-week period mentioned in Article 35(2) UAVG, the data subject may choose to make a renewed request to the controller. If this repeated request is again rejected by the controller, the data subject may, under Article 35(1) UAVG, request the court to order the controller to still grant the request. If the controller has not responded to the repeated request within the time limits specified in Art. 12(3) UAVG, the submission of the petition is not subject to a time limit... The data subject in a case such as the one at issue here is also free to seek interim relief, both in anticipation of a repeated request to the controller and after such a request has been made."[2]
Following from this, the Supreme Court held that the Court of Appeal had erred in the application of the law. The Supreme Court held that in this instance, the data subject's interest in seeking interim relief overrode the time limit under Article 35 UAVG. Thus, the data subject was free to seek a provisional injunction for interim measures.
Lastly, the Court held that it was wrong for the Court of Appeal to interpret Article 35 UAVG to mean that a data subject must base a repeated request under Articles 15-22 GDPR on new facts and circumstances to those of a previously denied request.
As a result, the Court annuled the judgment of the Amsterdam Court of Appeal of 5 November 2019.
Comment
Share your comments here!
Further Resources
Share blogs or news articles here!
English Machine Translation of the Decision
The decision below is a machine translation of the Dutch original. Please refer to the Dutch original for more details.