I need to bring my Luxembourg organisation into compliance with article 87 of GDPR (UE 2016/679). What are the concrete requirements, the sanctions, and how can Luxgap support me?

EU frameworkGDPRNIS 2 DORA AI Act Whistleblowing

CSSF circularsCSSF 22/806 CSSF 25/883 CSSF 25/880 CSSF 25/881 CSSF 25/882 CSSF 20/750 CSSF 12/552 CSSF 11/504 (repealed)CSSF 24/847

Article 87

Processing of the national identification number

General Data Protection Regulation · UE 2016/679

Processing of the national identification number

Member States may further determine the specific conditions for the processing of a national identification number or any other identifier of general application. In that case the national identification number or any other identifier of general application shall be used only under appropriate safeguards for the rights and freedoms of the data subject pursuant to this Regulation.

Luxembourg specificity

loi modifiee du 19 juin 2013 relative a l'identification des personnes physiques

In Luxembourg, the matricule (national identification number, 13 digits) is governed by the amended law of 19 June 2013 on the identification of natural persons, and its use outside the national register is restricted. The CNPD ensures it does not become a universal interconnection identifier: using it as a generalised technical key requires appropriate safeguards under Article 87 and a legally justified purpose.

Luxgap practice: first map every occurrence of the matricule, then replace it with a neutral internal identifier wherever it is not legally required, and document the safeguards in your record.

Luxgap guidance · DPO & CISO

How to comply

The classic trap

Article 87 opens a national margin, but in Luxembourg the national identification number (the matricule, 13 digits) is tightly controlled. The trap: reusing this matricule as a universal technical key (customer ID, login, file reference, join key between databases) without a legal basis or specific safeguards. The CNPD penalises purpose deviation and the use of the matricule as an unauthorised pivot identifier, which turns every database into a mass interconnection tool. Many organisations store the matricule out of HR or billing convenience, without realising it triggers a reinforced protection regime.

Concrete pitfalls around the matricule

Using the matricule as a primary key in a database, when a neutral internal identifier would suffice.
Letting it travel in clear text in URLs, application logs or unencrypted CSV exports.
Sharing it between services with distinct purposes (HR, marketing, support) without partitioning, creating de facto interconnection.
Embedding it in composite identifiers (badge number, Active Directory login) that make it visible and guessable.
Neglecting minimisation: collecting the full matricule when only a date of birth or a truncated identifier would be needed.
Omitting the purpose and specific legal basis in the record and the Article 13 notice.

How Luxgap automates this risk

Our Luxgap National ID Sentinel makes the silent leak of the Luxembourg matricule across your systems impossible: it continuously scans your databases, files and flows to flush out every occurrence of the 13-digit format, even where you do not expect it. The tool applies a pattern recognition engine (regex plus validation of the LU matricule check key) across Odoo, Sage BOB 50, M365 (SharePoint, Exchange, OneDrive), your SQL databases and your AWS S3 buckets, without asking the DPO to map anything by hand.

Automatically detects every field, document or log containing a valid national matricule, with check-key validation to rule out false positives.
Classifies the detected usage (technical key, plain storage, clear-text transit) and flags uses as an unauthorised pivot identifier.
Alerts in real time via Teams or email as soon as a new export, flow or table exposes a matricule outside the declared scope.
Generates the record and Article 13 notice sections stating the purpose and the specific safeguards required by Luxembourg law.
Proposes pseudonymisation and neutral-identifier substitution strategies, with a prioritised remediation plan.
Produces a timestamped PDF report enforceable before the CNPD, demonstrating the appropriate safeguards under Article 87.

Available as a complement to a Luxgap DPO mandate or as a dedicated SaaS module depending on your scope. Request a tailored quote and our teams will prepare a demonstration on your real data, with a free scope scan within 48h to measure your exposure before any commitment.

Need help?

Our team (lawyers + cyber engineers + developers) supports you. Free quote within 48h.

Processing of the national identification number

They trust us

Before we chat