Hugging Face and the EU AI Act
US–French company running the leading open platform for hosting and sharing models, datasets and ML apps, plus paid inference and enterprise services.
What the Act means when you deploy Hugging Face
Hugging Face is primarily a hub and platform, not the provider of the models it hosts — GPAI obligations for a given model sit with that model's provider, so due diligence must go one level deeper: identify the actual model and its provider before you rely on hub content. If you use their paid inference or enterprise offerings, the usual processor questions (data location, retention, sub-processors) apply to Hugging Face itself.
Questions to send Hugging Face
Copy these into your supplier questionnaire. Answers in writing beat answers on a call — your Article 26 file needs evidence, not recollection.
- Q1
For models we consume through your inference services, how do you surface the model provider and its documentation to us?
- Q2
What guarantees does the enterprise offering give on data location, retention and telemetry?
- Q3
How are models with problematic licences or gated access flagged, so our teams don't pull them into production unnoticed?
- Q4
What is your DPA and sub-processor setup for the paid services we would use?
Documents to request for your file
- Instructions for use / product documentation for the exact service and version you deploy
- Identification of the underlying model(s) and their provider, plus the documentation passed through to you
- Data processing agreement, sub-processor list and processing locations
- Security documentation: certifications, retention defaults and access controls
- Written statement on whether your inputs and outputs are used for training, and how to opt out
- Licence terms for the exact version you deploy, including commercial-use conditions
Which of these you can actually obtain depends on your contract and tier — treat the list as a checklist to work through with the vendor, not as an entitlement.
Articles to have on the table
- Art. 26Deployer obligations
If you use this vendor's technology professionally in a high-risk context, you must follow the instructions for use, assign competent human oversight, keep logs and monitor operation.
- Art. 25When you become the provider
Putting your own name on the system, changing its intended purpose or substantially modifying it moves you from deployer to provider — with Article 16 obligations attached.
- Art. 50Transparency towards people
Where people interact with an AI system, or where content is AI-generated or manipulated, disclosure and — in defined cases — machine-readable marking are required. This duty sits with you, not the vendor.
Most buyers of AI land in the deployer role. Read the full deployer obligations under Article 26 — or the overview of all operator roles if you are not sure which one you hold.
Go to the source
Verify everything on this page with Hugging Face directly. Public pages change; profiles do not update themselves.
Important: what this page is not
This profile is based on publicly available information about Hugging Face and describes only who they are and what they offer. It makes no assessment of Hugging Face’s compliance, contains no rating or certification claim, and is not endorsed by or affiliated with Hugging Face.
EU AI Act obligations depend on how you deploy this vendor's technology and on your role (provider, deployer, importer, distributor). Verify every fact and commitment directly with the vendor before relying on it — this profile is a starting point, not legal advice.
Nothing here is legal advice. Confirm the facts with the vendor and your own counsel before you rely on them.
Run the free 2-minute checker — deterministic classification, no sign-up.