AI Act Article 50 for non-EU providers: output used in the EU
The Commission FAQ says providers outside the EU are subject to the AI Act if their system's output is used in the EU. How it defines provider and deployer.
Yes. The Commission's Transparency obligations under Article 50 of the AI Act page says providers of AI systems established or located outside the EU are also subject to the AI Act if the output of their AI system is used in the EU. Where the provider sits does not remove the Article 50 duties for output that reaches EU viewers. This post reports the page and is not legal advice.
The same page defines two roles, provider and deployer, and the duties differ by role. Knowing which one you are comes first.
Who counts as a provider?
The FAQ points to Article 3(3): a natural or legal person, public authority, agency or other body that develops an AI system, or has one developed, and places it on the EU market or puts it into service under its own name or trademark. It adds that this holds "irrespective of whether those providers are established or located within the EU or in a third country."
Providers must meet the Article 50(1), (2) and (5) duties before placing a system on the market or putting it into service: tell people when they interact with AI, and mark generated output in a machine-readable way.
Who counts as a deployer?
A deployer is a person or body using an AI system under its authority, excluding personal, non-professional use. A person who gains an economic benefit on a regular basis, or works in a business, trade, occupation or freelance activity, is acting professionally and counts as a deployer. A company that uses the system remains the deployer even when contractors or freelancers operate it on its behalf and under its control.
Deployer duties sit in Article 50(3) and (4): inform people exposed to emotion recognition or biometric categorisation, and clearly label deepfakes and certain AI-generated text.
What does that mean for a team calling a video API?
Read the two definitions against what you actually do. If you build your own system on top of an API and sell it under your own name, the provider definition may fit. If you generate videos for your own marketing, the deployer definition fits. The page does not say that calling a third-party API settles the question, so this post does not say it either.
What Sume's own docs add is narrow: a generation request creates a durable job with an id, per Jobs and results, and the result carries Sume-hosted artifact URLs. They do not say which Article 50 role you hold. Keep that decision with whoever advises your company, and keep the job records either way.
| Role | Defined as | Article 50 paragraphs named |
|---|---|---|
| Provider | Develops or has developed an AI system and places it on the market or into service under its own name or trademark, in or outside the EU | (1), (2), (5) |
| Deployer | Uses an AI system under its authority, excluding personal non-professional use | (3), (4) |
Sources
Related posts
More in Use cases
- Can one avatar UGC ad change location mid-video? One scene only
Sume's avatar video renders one avatar and one shared scene per final video. For a second location, make two jobs and join them with a Timeline 1.0 render.
- Avatar UGC ad: captions.status failed but the video is fine, now what
Inline captions on a Sume avatar video soft-fail: the job can succeed with a clean video_url and captions.status failed. Re-caption it standalone for $0.20.
- Black Friday audio ad read: a TTS voice over a music bed
Produce a 30-second Black Friday ad read: write to character count, generate with Sume TTS, add a short music bed and mix. Costs and limits included.
- Build a 3-minute YouTube Short from clips with Sume Timeline
Stitch several clips into one Short of up to 180 seconds with Timeline 1.0: fades, a looped music bed with ducking, and the $0.30 render for three minutes.
Written by Sume