Verdict Background
HomeCompliance VerdictDeepFace — Demo Report
Sample Audit Report — For Demonstration Purposes Only
HIGH RISK — ANNEX III TRIGGERED

SENTRY 48
COMPLIANCE
VERDICT

Repository Audited
serengil / deepface
github.com/serengil/deepface
Biometric IdentificationEmotion RecognitionSensitive Attribute Profiling
9.1
RISK SCORE / 10
CRITICAL NON-COMPLIANT
Annex III — Category 1
Audit Type
Static Architectural Audit
Classification
High-Risk — Annex III
Audit Duration
48 Hours
Report Date
June 2025
Section 1 of 4

Annex III Classification Findings

High-risk triggers identified under EU AI Act Annex III — Biometric Identification & Categorization

Triggers Found
3
Annex III — §1(a)

Real-Time Biometric Identification

CRITICAL

DeepFace exposes a real-time face recognition pipeline via `DeepFace.stream()` and `DeepFace.find()`. These functions perform live biometric identification of natural persons in publicly accessible spaces — a Category 1 prohibited use case under Annex III §1(a) without explicit exemption.

Evidence — Repository Artifacts
deepface/DeepFace.py
stream() function — real-time webcam face matching
deepface/modules/recognition.py
find() — database-level biometric search
README.md
Documented use case: "real-time face recognition"
Remediation Path

Implement mandatory human-in-the-loop override gate before any identification result is acted upon. Add Article 14 oversight logging.

Est. fix: 2–4 weeks
Annex III — §1(b)

Biometric Categorization by Sensitive Attributes

CRITICAL

The `analyze()` function explicitly categorizes individuals by race, gender, age, and emotion from facial images. Categorization by race and emotion from biometric data is a high-risk use case under Annex III §1(b) and triggers mandatory conformity assessment.

Evidence — Repository Artifacts
deepface/DeepFace.py
analyze(actions=["race","gender","age","emotion"])
deepface/modules/demography.py
Race classifier: 7-class ethnicity model
deepface/modules/demography.py
Emotion classifier: 7-class affect model
Remediation Path

Disable race and emotion classification by default. Require explicit opt-in with documented legal basis under GDPR Art. 9 and EU AI Act Art. 10.

Est. fix: 2–4 weeks
Annex III — §4

Employment & Recruitment Scoring

HIGH

The verification and recognition APIs can be integrated into HR screening pipelines. No guardrails prevent deployment in employment contexts. Annex III §4 classifies AI systems used for recruitment, promotion, or termination decisions as high-risk.

Evidence — Repository Artifacts
deepface/DeepFace.py
verify() — identity confirmation suitable for access control
README.md
Listed use case: "employee attendance systems"
Remediation Path

Add deployment context detection and block or warn when integrated into HR/ATS pipelines. Require Annex IV technical documentation for such deployments.

Est. fix: 2–4 weeks
Section 2 of 4

Technical Gap Analysis

Article 12 (Logging) & Article 14 (Human Oversight) mechanism scan

Missing
2
Partial
1
Article 12
Automatic Logging Mechanisms
MISSING

EU AI Act Article 12 requires high-risk AI systems to automatically generate logs of every inference event, including input data characteristics, output decisions, timestamps, and operator identity. DeepFace has no native logging layer.

Legal Requirement

“Art. 12(1): Logging must capture at minimum — date/time, input data reference, output, operator ID, and system version.”

Identified Gaps
No inference event logging in DeepFace.py or any module
No audit trail for identify/verify/analyze calls
No immutable log storage or tamper-evidence mechanism
No log retention policy or data minimization controls
Article 14
Human Oversight Mechanisms
MISSING

Article 14 mandates that high-risk AI systems be designed to allow human oversight, including the ability to override, interrupt, or disregard system outputs. DeepFace provides no override interface, confidence threshold gates, or human-in-the-loop controls.

Legal Requirement

“Art. 14(4): Operators must be able to decide not to use the AI system output in any given situation.”

Identified Gaps
No human override or rejection mechanism on any output
No confidence threshold enforcement before acting on results
No "stop" or "pause" capability in stream() pipeline
No designated human overseer role or access control
Article 13
Transparency & User Information
PARTIAL

Article 13 requires high-risk AI systems to be sufficiently transparent so that deployers can interpret outputs correctly. DeepFace provides model accuracy metrics in documentation but lacks per-inference explainability or uncertainty quantification.

Legal Requirement

“Art. 13(3)(b): Instructions for use must include performance metrics in the specific deployment context.”

Identified Gaps
No per-inference confidence intervals or uncertainty scores
No explainability output (e.g., attention maps, LIME/SHAP)
README documents aggregate accuracy — not deployment-context accuracy
Section 3 of 4

Data Governance — Article 10

Sensitive attribute profiling flags: Race, Emotion, Gender

Flagged Modules
3
deepface/modules/demography.py
Sensitive Attribute: Race / Ethnicity
Art. 10 + Annex III §1(b)CRITICAL

The race classifier outputs a 7-class ethnicity probability distribution from facial geometry. Processing racial origin from biometric data constitutes special category data under GDPR Art. 9 and triggers mandatory data governance controls under EU AI Act Art. 10.

Model Output Classes
AsianIndianBlackWhiteMiddle EasternLatino Hispanic
Data Governance Gaps
No consent mechanism before race inference
No data minimization — race is inferred even when not requested
No purpose limitation controls on output data
Training dataset provenance undocumented in repository
deepface/modules/demography.py
Sensitive Attribute: Emotion / Affect
Art. 10 + Recital 44HIGH

Emotion recognition from facial images is flagged in EU AI Act Recital 44 as a high-risk practice. The model infers internal psychological states from biometric data — a practice with documented scientific validity concerns and significant potential for discriminatory misuse.

Model Output Classes
AngryDisgustFearHappySadSurpriseNeutral
Data Governance Gaps
No scientific validity disclaimer on emotion outputs
No deployment context restrictions
Emotion scores exposed in raw API output without uncertainty bounds
No prohibition on use in employment or law enforcement contexts
deepface/modules/demography.py
Sensitive Attribute: Gender
Art. 10 — Data QualityMEDIUM

Binary gender classification from facial features raises Art. 10 data quality concerns. The model uses a binary classification schema that does not reflect the full spectrum of gender identity, creating systematic accuracy disparities for non-binary individuals.

Model Output Classes
ManWoman
Data Governance Gaps
Binary classification schema — accuracy disparities for non-binary individuals
No fairness audit documented in repository
Gender inferred from facial geometry without consent
Section 4 of 4

Sentry 48 Compliance Verdict

Final summary — DeepFace EU AI Act readiness assessment

Overall Risk Score
9.1
out of 10
CRITICAL NON-COMPLIANT
Annex III Exposure10/10
Art. 12/14 Gaps9/10
Data Governance8/10
Annex III Classification
3 triggers under §1(a), §1(b), §4
HIGH-RISK CONFIRMED
Article 12 — Logging
No automatic logging mechanism found
NON-COMPLIANT
Article 14 — Human Oversight
No override or interrupt mechanism
NON-COMPLIANT
Article 13 — Transparency
Aggregate metrics only, no per-inference explainability
PARTIAL
Article 10 — Data Governance
Race, emotion, gender profiling without consent or governance
NON-COMPLIANT
Maximum Penalty Exposure
€35,000,000

Or 7% of total worldwide annual turnover — whichever is higher. Applies to prohibited practice violations under EU AI Act Article 5 and high-risk system non-compliance under Articles 8–15.

Enforcement Deadline
August 2, 2026

Full EU AI Act enforcement for high-risk AI systems begins August 2, 2026. Deployers of systems like DeepFace in regulated contexts must achieve full compliance before this date or face immediate enforcement action.

This is a Demo Report

Is Your AI System Compliant?

This sample report demonstrates what a real Sentry 48 audit delivers. Our Scout Agent reads your actual repository — file trees, configs, dependency manifests, and documentation — to generate a legally defensible compliance verdict in 48 hours.

Talk with Us