Is Facial Image Data GDPR Compliant and Where Is It Stored?

Quick Answer

Whether facial image data from a skin analyzer like the ISEMECO 3D D9 is GDPR-compliant depends on the legal basis for processing, the data’s storage location, and the contractual terms the clinic has with its patients and its software provider—not on the device’s technical specifications alone. 3D facial images used for aesthetic analysis may constitute biometric data under GDPR Article 9 when processed to uniquely identify a person, triggering special-category protections requiring explicit consent or another Article 9(2) condition. The D9’s documentation describes multi-terminal remote access and an optional “Skin Cloud” platform for aggregating patient data across locations, but does not specify server locations, retention periods, or GDPR Data Processing Agreement terms on the product page. Buyers in the EU must obtain this information in writing before processing patient images.

Key Takeaways

Facial images can be biometric data: Under GDPR, 3D facial scans processed for identification or unique verification fall under Article 9 special categories, requiring a lawful basis beyond ordinary consent.

Device-level remote access ≠ cloud storage: The D9 supports viewing reports on iPads and PCs, but this is a workflow feature; the actual data location depends on where the clinic’s server or the optional Skin Cloud platform stores the images.

The Skin Cloud platform aggregates data: MEICET’s optional cloud layer consolidates patient records across devices and locations, which raises cross-border transfer and data residency questions.

GDPR compliance is a shared responsibility: The clinic is the data controller; MEICET is likely a processor. A Data Processing Agreement (DPA) specifying storage location, retention, and security is required.

EU-hosted does not automatically equal compliant: Even if data is stored in the EU, the clinic must still establish a lawful basis, minimize data collection, and honor patient rights.

What Makes Facial Image Data “Biometric” Under GDPR

GDPR Article 4(14) defines biometric data as personal data resulting from specific technical processing relating to the physical, physiological, or behavioral characteristics of a natural person, which allow or confirm the unique identification of that person. Facial images become biometric data when they are processed through specific technical means—such as 3D modeling, depth mapping, and algorithmic analysis—for the purpose of uniquely identifying a person.

The D9’s technical workflow creates exactly this condition. The device captures 42 million full-face pixels using binocular grating structured light with 0.2mm modeling accuracy, generating a 3D point cloud of the patient’s facial geometry. This 3D model is not a photograph; it is a measurable representation of facial structure. When stored alongside patient identifiers and used for longitudinal comparison—the “overlap comparison” and “3D before-after” features—the data enables unique identification of the individual across time points.

Whether this processing constitutes “biometric data” under GDPR depends on the purpose. If the clinic uses the images solely for aesthetic assessment and treatment planning, without using the facial geometry to identify the patient against a database, a strong argument exists that the data is not biometric in the Article 9 sense. However, if the clinic uses the 3D model to verify patient identity at subsequent visits, or if the Skin Cloud platform matches facial data across locations, the processing crosses into biometric territory requiring an Article 9(2) condition—most commonly explicit consent.

The EDPB has emphasized that controllers must assess whether less intrusive means can achieve the same purpose before processing biometric data. For a skin clinic, the alternative is straightforward: use a patient ID number or name for identification, and treat the 3D images as health data rather than biometric identifiers.

Where the D9 Stores Data: Device, Local Network, or Cloud

The D9 product page does not specify where facial image data is stored. This absence is material. The device captures and generates data, but storage architecture determines the GDPR obligations that apply.

The D9’s published features describe multi-terminal access: clinicians can view analysis reports on iPads, Android tablets, Macs, or Windows PCs, with local or remote synchronization. This feature—marketed as “scan-consultation separation”—frees the capture device for the next patient while the clinician reviews results elsewhere. But remote viewing is not the same as cloud storage. The data may reside on a local server within the clinic, on the capture device itself, or on a cloud platform, depending on how the system is configured.

MEICET’s Skin Cloud (肌肤云) platform is the optional layer that aggregates data from multiple devices and locations into a unified archive. The Skin Cloud is described as supporting cross-location case retrieval and role-based access control. For a multi-location clinic group, this solves the fragmentation problem: a patient scanned at Location A can be reviewed at Location B. But the Skin Cloud also introduces a new data residency question: where are the cloud servers located, and do they fall under EU jurisdiction?

Storage Layer What It Holds GDPR Implication
D9 device local storage Scan images, analysis results on the capture unit Clinic controls physical access; device encryption and access controls must be verified
Clinic local server/PC Reports viewed on iPad/PC; synchronized data Clinic is controller; server location determines jurisdiction
Skin Cloud platform (optional) Aggregated patient profiles across locations MEICET becomes processor; DPA and transfer mechanism required if servers are outside EU

The Controller-Processor Relationship: What the Clinic Must Contract

The clinic using the D9 is the GDPR data controller. The clinic determines why the facial images are collected and how long they are retained. MEICET, as the software and platform provider, is a processor when it stores or processes data on the clinic’s behalf through the Skin Cloud or any remote access feature.

GDPR Article 28 requires a written contract—a Data Processing Agreement (DPA)—between controller and processor. The DPA must specify:

  • The subject matter and duration of processing
  • The nature and purpose of processing
  • The type of personal data and categories of data subjects
  • The processor’s obligations and rights

Cross-Border Transfer: The Question the Product Page Does Not Answer

MEICET is a Shanghai-based company. If the Skin Cloud platform or any remote support function routes facial image data to servers in China or another non-EU jurisdiction, the transfer triggers GDPR Chapter V requirements. The transfer is lawful only if:

  1. The destination country has an EU adequacy decision (China does not)
  2. Appropriate safeguards are in place, such as Standard Contractual Clauses (SCCs) with a Transfer Impact Assessment
  3. A specific derogation applies (rarely suitable for systematic processing of patient data)

Practical Compliance Checklist for EU Clinics

Step 1: Determine whether the processing is biometric. Document the purpose of the 3D scan.
Step 2: Establish the lawful basis. For health data, Article 9(2)(h) may apply. For aesthetic clinics, explicit consent under Article 9(2)(a) is required.
Step 3: Obtain a DPA from MEICET. The DPA must specify storage locations, sub-processors, and security measures.
Step 4: Map the data flow. Identify every system that touches the facial images.
Step 5: Configure retention and deletion. Define how long facial images are retained and how they are deleted.
Step 6: Conduct a Data Protection Impact Assessment (DPIA). Systematic processing of 3D facial images meets this high-risk threshold.

Frequently Asked Questions

Is a 3D facial scan always considered biometric data under GDPR?

No. A 3D facial scan is biometric data only when it is processed through specific technical means for the purpose of uniquely identifying a person. If used solely for aesthetic assessment, it is health data.

Where does the ISEMECO D9 store facial images?

The product page does not specify. The clinic must confirm with MEICET whether data is stored on the device, a local server, or cloud infrastructure.

Does the D9’s “Skin Cloud” platform store data in the EU?

MEICET does not state server locations. EU clinics must obtain a written commitment on data residency before processing patient data through the Skin Cloud.

What is a Data Processing Agreement and why does the clinic need one?

A DPA is the GDPR Article 28 contract between the clinic (controller) and MEICET (processor). Without it, processing through MEICET’s platform is not GDPR-compliant.

Can a clinic rely on patient consent alone for GDPR compliance?

No. Consent is one lawful basis, but the clinic must also have a DPA, implement security measures, and honor data subject rights.

What happens if facial image data is transferred to China without a transfer mechanism?

The transfer would violate GDPR Chapter V, potentially leading to enforcement action and patient compensation claims.

How long can a clinic retain 3D facial images?

GDPR does not specify a fixed period. The clinic must define a period necessary for the purpose and document it in the privacy notice and DPA.


Post time: Nov-16-2026

Contact US to Learn More

Write your message here and send it to us