Your cookie preferences

EDPB guidance · Art. 7 GDPR

We use technical cookies essential for the platform to work (login, security, sessions). We would also like to use analytics cookies to understand how to improve it.

You can accept all, reject all, or choose which categories to switch on.Your consent is valid for 6 months and you can withdraw it at any time from the footer.

You will find everything in our privacy notice.

All news
Regulation August 19, 2026 6 min

The score they refuse your credit with can be requested, and it has to be explained

The CNIL sets out what a lender must be able to tell someone it turns down: the main criteria, the consequences, and the score together with the values that make it intelligible. Trade secrecy limits the answer, it does not cancel it

In short

Twenty-four months: past payment incidents should not be used beyond that. Six months: how long the data of a non-client who was refused may be kept. The score can be requested through access, together with what makes it understandable. Trade secrecy may limit the answer, not turn it into a blanket refusal.

There is no right to credit, there is a duty to explain

The CNIL starts where a lawyer would: freedom of contract under article 1101 of the civil code. Nobody is obliged to grant a loan. But before granting it there is an obligation to assess creditworthiness, and that assessment processes personal data.

Lenders may use artificial intelligence or statistical models. The CNIL writes that those tools «are subject to the GDPR: they must be transparent, limit bias and not lead to discrimination», and that in every case the institution remains responsible for the decision and must be able to explain the main criteria used and the consequences of the process for the person's situation.

The three numbers

  • Twenty-four months: the CNIL recommends not using past payment incidents beyond that period, save particular circumstances.
  • Six months: a non-client who is refused may have the application data kept for six months, to handle a later application faster.
  • Beyond that, only for litigation: for the applicable limitation period, until proceedings end, and under strict confidentiality.

On incidents the CNIL adds two conditions that are easily forgotten. Only those meeting objective criteria, defined in advance, may be used. And the context must be taken into account: whether they were disputed, whether they were settled, whether a court ruled. An incident set aside by a final decision can no longer enter the assessment.

The score is requested under Article 15

The data subject may ask to know their score, and the information must come with what makes it understandable — for example the minimum and maximum marks required to obtain the credit. The CNIL is explicit: it cannot be a repetition of what was already communicated before the assessment; it must be precise and personalised.

The right of access is not absolute and trade secrecy may stand against part of the answer. But «that refusal must not be global and absolute»: the institution must endeavour to grant the request and respond as far as possible, providing as many elements as it can.

What to look at in a client who scores

The cut-off used to discard past incidents, and whether it is written down anywhere. The advance list of incident types that may be used: if it does not exist, the objective criteria do not either. The procedure for answering a request for access to the score, and who decides what trade secrecy covers. And the credits that are not called credits — instalments, deferred payment, store cards with a revolving line, overdrafts: these are credit and can trigger the assessment.

Official source:CNIL — Le refus de crédit en questions (19 août 2026)

Looking for a workspace for your DPO work?

DPO Workspace is built by a certified DPO. 30-day free trial.

Start free

Related articles

Regulation
nullathe decision on a worker taken by the algorithm alone, from 23 October

A dismissal decided by the algorithm is void: from 23 October in Italy

Published in Official Gazette no. 234 of 8 October 2026 and in force since 23 October, decree no. 179/2026 provides that final decisions on the employment relationship cannot be based solely on automated processing, that the worker may request an understandable explanation, and that decisions taken in breach are void. In parallel, AI systems affecting work organisation enter the risk assessment under Article 28 of decree 81/2008. For a DPO this is the rare case where the consequence is not economic but civil, and it changes how the check is framed.

Oct 08, 2026New 8 min
Regulation
3signals that make notification due

Poland's UODO: not every breach must be notified. Public-register data on one side, PESEL, health and financial data on the other

If an invoicing system leaks only a sole trader's name, business name, tax number and registered address, already public in the business register, risk is normally unlikely. If it also leaks the national ID number, purchase details revealing health, or financial data, notification is due. Either way, the decision goes into the internal register.

Oct 05, 2026New 5 min
Regulation
120days to charge you, not to fine you

The 120 days are not the deadline to fine you: they are the deadline to charge you

Anyone who built an appeal on the authority's delay should re-read the calendar. The Court clarifies three things: the complaint procedure and the sanctioning procedure are autonomous, so overrunning the nine-to-twelve months on the complaint does not extinguish the power to fine; the 120 days are for notifying the charge, not for imposing the fine; and they run from the «definitive finding», which is not the first notice but the moment the authority can assess every element — including the hearing of your side. After the charge, only the five-year limitation period remains.

Sep 20, 2026 7 min