Article 50: deployer vs provider

A creator on Versely is usually a deployer of the file they publish, not the model provider. Providers machine-mark synthetic output so a detector can read it, with a grace period to 2 December 2026 for systems already on the market before 2 August 2026. Deployers who publish deepfakes put a visible or audible label at first exposure. Those are two duties, two artefacts, two readers. Confusing them is how a team waits for a watermark and ships an unlabelled talking head.

Article 50 of the EU AI Act has applied since 2 August 2026. Commission guidelines were adopted 20 July 2026. Fines can reach €15 million or 3% of worldwide turnover. This page is the role split for a hosted generator. It is not legal advice.

Two duties, two artefacts

The Commission's transparency FAQ splits the work by actor.

Provider — whoever places the generative system on the market or puts it into service under their own name. Article 50(2) asks them to mark synthetic audio, image, video, and text in a machine-readable way so it is detectable as generated or manipulated. SynthID, other invisible watermarks, and Content Credentials are the class of answers. The reader is a detector, a platform, or a downstream verifier. The grace to 2 December 2026 is for that marking duty on systems already on the market before 2 August. It is not a general postponement of Article 50. It is not a holiday for the on-screen line.

Deployer — whoever uses that system under their authority. Article 50(4) asks deployers who publish a deepfake — content resembling real people, places, or events that would appear authentic — to disclose that it was artificially generated or manipulated, in a way a person can perceive, at the latest at first exposure. The reader is the viewer. A caption, a spoken line, an official EU icon on the file: those are deployer objects. Metadata is not.

Neither artefact absorbs the other. A watermark is not a caption. A caption is not a detector mark. The provider (AI Act) glossary and the deployer glossary are the short versions of the same split.

Article 50(4) is not a duty to label every synthetic pixel. Colour grade and denoise on a real recording are assistive editing. A photoreal person who was never in a room is the deepfake-shaped case. Public-interest AI text has its own limb, with a human-editorial-control exemption. This page stays on the video file you publish.

Why a Versely creator is usually the deployer

If you sign in, pick a row, prompt it, download the clip, and post it, you used someone else's system under your authority. You did not place Veo or Kling or Seedance on the market. You cannot retrofit a robust machine-readable watermark if the export did not carry one. That engineering sits upstream.

You still owe the 50(4) label when the published file is a deepfake going to an EU audience. First exposure means the viewer can perceive the disclosure when they first encounter the content, without extra taps and without waiting out the clip. A description-field footnote is a poor fit for a mobile feed. A two-frame flash is a screenshot, not a viewer. Burn the line, or speak it on the first seconds, and use the platform toggle as well.

That is the accurate description for agencies, brands, in-house teams, and solo creators on a hosted studio. It is also the accurate description on Versely. The catalog is other people's models plus finishing. You are the publisher of the file that leaves the building.

The edge that is not this story: you embed a generative system in your own product and present it to customers under your own name. White-label, a branded generator, an API you resell as yours. That can flip you toward provider territory. Whose name the end user sees on the generation surface is the signal. Take that to counsel. The middle ground — you prompt hosted models, the output goes out as your work — is deployer territory.

Do not wait for the provider's 2 December 2026 grace to "finish." The grace is their marking timeline. Your first-exposure duty has applied since 2 August 2026. Content generated and published before 2 August is not retroactive. Generated before and published after is covered. If you are sitting on a July take, the publication date is the one that counts.

What you do not build

You do not need a watermarking pipeline, a detection API, or a C2PA signing desk to meet 50(2), because 50(2) is not addressed to you when you only prompted a hosted row.

You do need a production step for 50(4):

1. Flag realistic people, places, or events at brief. Talking-head generates start flagged.
2. Put a perceivable line on the file. The Article 50 disclosure template is the copy. Official icons are optional; labelling is not.
3. Keep it on the cut that actually ships. A 9:16 that leaves without the line is a new first exposure.
4. Set YouTube, TikTok, and Meta toggles. Those are contract, not the Act.

Provider watermark vs deployer label is the artefact page: SynthID and C2PA versus the visible line. This page is only who you are. If the clip is a UGC talking head for an EU feed, you are the deployer of that file.

A platform badge is not a substitute. YouTube's overlay, TikTok's AIGC label, Meta's AI Info — each is that app's detector and composer control. Clearing Studio does not clear Article 50. Clearing Article 50 does not tick TikTok.

The Versely-shaped week

Run the model. Caption. Label. Publish. The label is not a fourth product. It is picture lock.

Veo 3.1 will not print your 50(4) line. Neither will a UGC video generator. The row you picked is the provider's system, or a host of that system. You are the person who put the deepfake in front of a viewer. If you want the overlay on the same timeline as the take, sign up and treat first exposure as a frame you can point at, not as a caption you hope someone expands.

Artistic, satirical, or fictional work may label in a way that does not spoil the work. Ads and UGC testimonials are a poor fit for that quieter shape. Article 50 artistic exception is narrow is that boundary. Do not use it to hide a fake customer.

Personal, non-professional use sits outside the Act. Regular economic benefit — a paid creator, a brand, an agency — is professional use. If you are reading this as a production checklist, assume you are the deployer.

FAQ

Does Versely's export mark discharge my Article 50 duty?

No. A machine-readable mark, if present, is the provider-side artefact aimed at a detector. If you publish a deepfake to an EU audience, the perceivable label is still yours. Keep the original export if you care about the mark. Do not treat the mark as the label.

What if the model I used is still inside the 2 December 2026 grace?

The grace is for provider marking on systems already on the market before 2 August 2026. It does not pause deployer labelling. Publish after 2 August and the first-exposure duty is live.

If I only post to YouTube, am I still a deployer?

Role follows how you used the system and what you published, not which app you opened. YouTube's overlay is extra. If the file is a deepfake and the audience includes the EU, 50(4) is still a deployer problem. The platform is not the actor the Act named.