Skip to content
TrustList
News

CNIL fines a company EUR 5 million over plaintext customer passwords

Editorial

By TrustList Editorial

France's data protection authority has fined an unnamed company EUR 5 million for storing customer passwords in clear text, sharing admin logins between staff and keeping contact-form data for more than 10 years.

About CNIL fines a company EUR 5 million over plaintext customer passwords

CNIL fines a company EUR 5 million over plaintext customer passwords

18 November 2026: France's data protection authority, the CNIL, has fined a company EUR 5 million for failing to protect its customers' data and for keeping personal data far longer than needed. The sanction is set out in deliberation SAN-2026-016 of 12 November 2026, and CNIL chose not to name the company, saying it published the decision to remind businesses of the rules rather than to single one out.

Not yet independently verified. CNIL chose not to name the company, so its sector and the number of customers affected are not known. The facts are from CNIL's own notice of 18 November 2026, which refers to deliberation SAN-2026-016 of 12 November 2026. We will update this when it can be confirmed, and remove this note.

How the case started

CNIL says it was alerted to the way the company stored its customers' passwords and the answers to the security questions used to reach the customer area of its website. It carried out an inspection, and its restricted committee, the body that imposes sanctions, found breaches of the GDPR.

Passwords in clear text and shared logins

Under Article 32 of the GDPR, which requires appropriate security, the committee found that until the sanction procedure began, the company had not put in place some basic security measures. The passwords for customer accounts were stored in clear text, readable by anyone with access to the database. Access to the customer databases, and to the tool staff used to reach them, relied on usernames and passwords shared between several employees. CNIL points out that only individual accounts allow an effective record of who accessed what, which matters most when investigating a security incident or a breach.

Data kept too long

Under Article 5(1)(e), the rule that data must be kept no longer than necessary, CNIL found that the company kept what customers typed into its contact form for more than 10 years, which it calls excessive once the request has been handled. The company also kept customers' login data beyond the one-year period set in its own retention policy.

The company took steps during the procedure, CNIL notes: it deleted the historic data it no longer needed and now runs a monthly purge of customer data. The size of the fine reflects the seriousness of the breaches, the number of people affected and the company's financial capacity.

What to check in your own systems

Confirm that no system stores passwords in a readable form. Passwords should be stored with a slow, salted hashing function designed for passwords, and the same goes for answers to security questions, which many teams forget. Search older systems, exports and logs, not only the main application.

Replace shared administrator and support accounts with named accounts, ideally behind single sign-on with multi-factor authentication, so every access is logged to a person. Then compare your actual retention with your written policy: contact forms, support tickets and login logs are common places where data piles up for years. Set an automatic deletion or anonymisation job, and keep a record that it runs.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in

The French regulator's final recommendation covers the vendors that build replay tools and the sites that run them. No exemption applies, purposes must be set before collection, and mouse movement should be masked where login codes are typed.