
Fingerprints used to identify people are special-category data under GDPR. Smart-lock buyers in Europe must design roles, consent, retention and storage location before deployment.
The EU General Data Protection Regulation (2016/679) protects personal data, and its Article 9 treats biometric data used to uniquely identify a natural person — including fingerprint templates captured by a smart lock — as a special category requiring both a lawful basis under Article 6 and an additional ground under Article 9, commonly explicit consent or necessity in employment under member-state law. Compliance is architectural: decide whether templates are stored on the device or in the cloud, minimize who enrolls and who can export, set retention and deletion rules, sign a data-processing agreement with any SaaS platform (controller/processor roles under Articles 26 and 28), and run a Data Protection Impact Assessment (Article 35) for systematic monitoring or large-scale sensitive processing, with employment rules in each member state (such as Germany’s BDSG §26) checked locally. Similar regimes exist beyond the EU, so international projects review local biometric law separately. This guide explains the requirements and the privacy configuration our factory’s platforms support, documented per quotation.
| When it applies | Fingerprint, face or other biometric templates processed to uniquely identify a person in the EU context, regardless of where the server sits. |
| Special category | Article 9 lists biometric data for unique identification alongside health and racial data; generic access logs alone are ordinary personal data. |
| Two legal layers | A lawful basis under Article 6 plus an Article 9 ground — typically explicit consent, an employment-law ground or another listed exception. |
| Controller and processor | The property or employer usually controls purposes; the cloud platform processes under contract; Article 28 DPAs and Article 26 joint-controller terms may both appear. |
| On-device option | Storing templates only on the lock’s secure element sharply narrows exposure: no central biometric database, easier minimization and deletion. |
| DPIA | Article 35 impact assessments are expected where biometric access systematically monitors staff or tenants; some member states add prior consultation rules. |
| Evidence | Privacy architecture description, data-flow map, retention policy, DPA, DPIA and records of processing; marketing reassurances are not compliance evidence. |
The storage architecture determines most of the legal risk: on-device templates support data minimization; server-side templates enable convenience at the cost of a much larger compliance footprint.
| Design choice | Privacy effect | Typical project |
|---|---|---|
| Template on lock only | No central biometric database; deletion is local and immediate. | Small offices, rentals, clinics. |
| Cloud-synced templates | Convenient multi-door enrollment; fuller Article 9 and DPIA burden. | Enterprise and multi-site deployments. |
| Non-biometric credentials | PIN, card or phone avoids Article 9 biometrics entirely. | Sites seeking the lowest legal risk. |
| Fingerprint image discarded | Only irreversible templates retained, never raw images. | Standard expectation in product design. |
| Role-based admin access | Enrollment and export limited to named administrators. | Required as an access-control safeguard. |
| Defined retention windows | Templates deleted on departure and logs aged out on schedule. | Backs up the records-of-processing register. |
Biometric compliance is decided project by project: employment residences, short-term rentals and public buildings sit in different legal postures, and member-state law adds requirements on top of the GDPR floor.
| Opening | Typical door | Lock approach |
|---|---|---|
| Employer access control | Art. 9 ground often via employment law or works-council agreement | Works-council consultation common in some member states. |
| Residential landlords | Explicit consent questioned where tenants feel coerced | Non-biometric alternatives usually offered. |
| Hotels and short-term rentals | Guests rarely need biometrics; mobile codes preferred | Avoids special-category data for transient users. |
| Healthcare and labs | DPIA plus role zoning and strict retention | Sensitive premises justify documented necessity. |
| Shared offices and gyms | Members can choose between credential types | Consent must be freely given and withdrawable. |
| Common areas in the EU | Signage, DPIA and member-state rules checked together | Local counsel signs off the final posture. |
For projects using our smart-lock platforms we provide technical and organizational inputs per quotation so the controller’s legal team can assemble its own GDPR documentation; the factory does not provide the controller’s legal determination itself.
| Component | Typical logic | Notes |
|---|---|---|
| Data-flow description | What data is collected, where templates and logs reside and who can access them. | Input to the records of processing and DPIA. |
| Security measures summary | Encryption, secure-element storage, transport security and admin controls. | Supports Article 32 security obligations. |
| DPA template | Article 28 contract terms for the platform service. | Signed between controller and platform provider. |
| Deletion procedures | Per-user and per-site template and log deletion workflows. | Operationalizes erasure and departure handling. |
| Sub-processor list | Cloud and hosting sub-processors with locations. | Required for transparency and transfer assessments. |
The trigger is purpose, not the sensor alone. Article 9 applies when biometric data is processed for the purpose of uniquely identifying a natural person, which is exactly how fingerprint unlock operates: the template is compared to identify a specific user and grant access. So a lock enrolling tenant or staff fingerprints in an EU context processes special-category data, even though the stored data is a derived template rather than a photo. Merely logging that “user 14 opened the door” is ordinary personal data, but the enrollment that binds a finger to user 14 is the biometric step. Systems that use fingerprints only for liveness without identification, or no fingerprints at all, avoid the Article 9 classification.
Not on consent alone in most analyses: consent must be freely given, and employees often cannot freely refuse their employer, so European data-protection authorities look for another Article 9 ground, typically necessity in employment under member-state law (for example §26 of the German BDSG), supported by a legitimate security need, an absence of less-intrusive alternatives, appropriate safeguards and often works-council or staff-representative involvement. A documented DPIA, choice of credential types, strict access controls and deletion on termination are expected. Best practice in multi-country deployments is to offer cards or phone credentials as the default and treat fingerprints as an opt-in convenience, with local counsel confirming the posture in each member state.
It materially reduces the data-protection footprint. When the derived template lives only in a secure element inside the lock, with enrollment performed locally and no template exported, there is no central biometric database to breach or transfer, deletion happens by clearing the device, and the processing is easier to justify as minimized and proportionate. Cloud-synced templates add real convenience for large multi-site rollouts but create export, hosting, sub-processor and transfer analysis. Either way the GDPR still applies — lawful basis, information notices, admin controls and retention remain required — but on-device architecture is the simpler path and the configuration our privacy-focused projects specify first.
A Data Protection Impact Assessment under Article 35 is a structured analysis of a processing operation’s risks to individuals and the mitigations in place. It is required where processing is likely to result in high risk, and supervisory authorities consistently treat systematic biometric access control — especially employee monitoring, sensitive premises or large user populations — as a DPIA case. The assessment covers necessity and proportionality, the Article 6 and Article 9 bases, storage architecture, access rights, retention, vendor security and residual risk, and in some member states failure to resolve high risk triggers prior consultation. The controller (the property or employer) owns and signs the DPIA; the platform and factory supply the technical inputs, data-flow descriptions and security measures it relies on.
Tenants and staff retain their GDPR rights: access, rectification, erasure, restriction, objection and, where applicable, portability. Operationally that means an administrator procedure to identify every place a user’s data exists — the lock’s secure element, gateways, the cloud platform, backups and access logs — and to erase the template promptly on departure or request, with logs aged out on the documented schedule while honoring any legal retention. Because a fingerprint cannot be “changed” like a password, prompt and provable deletion matters disproportionately. Platforms should expose per-user data export and deletion in the admin console and log those actions; our deployment guidance maps these workflows so the controller can answer subject requests without ad-hoc database work.
Request our privacy architecture notes with the RFQ: data flows, on-device template storage, admin controls, DPAs and deletion workflows, so your legal team can complete its Article 9 assessment and DPIA.
Request Spec Sheet + QuoteCertifications overviewLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team