HOIST FINANCE AB – Court Ruling (Netherlands, 2021)

Court Ruling
DPA RbAmsterdam21 January 2021Netherlands
final
Court Ruling

General GDPR enforcement action

This case relates to broader data protection obligations, not specifically to cookie or consent banner compliance. It is not included in cookie statistics or the Risk Calculator.

Hoist Finance faced a court ruling regarding a user's request to remove negative credit registration codes. The court decided that the user's request was not valid because it was submitted too late. This case illustrates the importance of timely action when dealing with personal data issues.

What happened

Hoist Finance rejected a user's request to remove negative credit registration codes after the user claimed they were unfairly affected.

Who was affected

The user who was trying to buy a house and wanted to remove negative credit codes from their record.

What the authority found

The court ruled that the user's request was inadmissible because it was not submitted within the legal timeframe.

Why this matters

This ruling highlights the need for individuals to act quickly when addressing issues related to their personal data. Companies should ensure they have clear processes for handling such requests.

GDPR Articles Cited

AI-verified

Art. 6(1)(c) GDPR
Art. 6(1)(f) GDPR
Art. 17(1) GDPR
Art. 21(1) GDPR
View original scraped data
Art. 6(1)(c) GDPR
Art. 6(1)(f) GDPR
Art. 17(1) GDPR
Art. 21(1) GDPR

Original data from scraper before AI verification against source document.

National Law Articles

AI-identified

Article 35(2) Uitvoeringswet Algemene verordening gegevensbescherming
Decision AuthorityRb. Amsterdam
Source verified 20 March 2026
national law identified
Full Legal Summary
Detailed

Complainant’s debt at the predecessor of Hoist Finance was claimed by Hoist on 5 July 2006 because payment arrears. On 8 May 2006 a record of the payment irregularities was made in the Stichting Bureau Kredietregistratie (BKR register): code “A” was added to complainant’s name. On 28 June 2006 an additional code 2 was added to the registration, which mark the existence of a claimed debt. After the decision of the District Court of Groningen, the complainant agreed on a payment arrangement to pay the debt. On 1 June 2017 a code 3 was added to the complainant’s BKR registration to signify the payment agreement. The entire debt was paid on 27 June 2017. On 17 July 2020 Hoist Finance notified the complainant that it would have the 3-code removed from his BKR registration in response to the complainant’s request. On 10 September 2020 another BKR registration deletion request was submitted, but Hoist Finance rejected it on 21 September 2020. Complainant claims that codes “A” and “2” must be removed from his registration because he is disproportionately affected by it. He is in the process of buying a house and he cannot get his mortgage approved. Complainant also points out that he hasn’t had any debts for 3 years. Hoist Finance disagrees: the complainant did not submit his objection to the rejection to Court within the legal term of 6 weeks (under Article 35(2) UAVG), which makes his request inadmissible. Heist Finance also argues that the complainant does not have an urgent interest, his A2 registration should remain for the term of 5 years and that the deletion request is not sufficiently substantiated. In particular, the reason for maintaining the registration is that the complainant has had financial problems for a long time, which means that lenders still require protection in this case. The Court considered that there is doubt about whether Hoist Finance as a participant in the credit registration system makes credit registrations under Article 6(1)(c) or Arti

Outcome

Court Ruling

A ruling by a national court on a data-protection matter.

Details

Ruling Date

21 January 2021

Authority

DPA RbAmsterdam

About this data

Data: GDPRhub (noyb.eu)
Licensed under CC BY-NC-SA 4.0
AI-verified and classified

Cite as: Cookie Fines. HOIST FINANCE AB - Netherlands (2021). Retrieved from cookiefines.eu

Report Inaccuracy

Last updated: