The Commission's final Article 50 guidance says hosting platforms and broadcasters are not deployers when they merely transmit third-party AI content without authority. The decisive fact is who controlled the decision to use the AI system and how its output was produced. Owning the feed, player, server, or broadcast channel is not enough on its own.
A podcast host that stores a client's episode and pushes its RSS feed may only distribute material made elsewhere. A radio station airing a supplied clip can occupy the same limited role if it never directed voice generation, leaving the professional creator as likely deployer.
The boundary moves when a platform commissions a synthetic voice, selects the tool, directs a contractor, and approves the resulting performance. Technical access is unnecessary when authority includes responsibility for purpose and manner of use, so paying a freelancer to operate the system does not avoid status.
Evidence of authority over how AI content is produced can sit in a creative brief, approval chain, prompt instructions, or contract. A brand that orders a voice clone and dictates its lines, audience, and release may retain authority when an outside studio operates the software. Employees and contractors working under the company's instructions are not separate deployers for that system.
The reverse matters when a client orders ordinary audio and a creative agency independently decides whether and how to use AI. The role can then sit with the agency, while approval of the finished file alone does not necessarily prove control over the underlying system.
One company may passively host creator uploads, provide a built-in voice generator, and deploy that generator for advertisements it commissions itself. The corporate name does not settle the analysis because each system and workflow has its own allocation.
That allocation fits the two-sided treatment of synthetic audio because a hosting interface can carry a deployer's human-facing notice without becoming the deployer. An uploader acting as deployer must still ensure that disclosure is clear and distinguishable by the listener's first exposure. If the badge disappears on embeds or syndicated feeds, a platform button has not solved every release route.
Hosts are nevertheless strongly encouraged to preserve existing machine-readable marks and audience labels through proportionate, technically feasible detection measures. That encouragement supports the information chain, but it differs from imposing Article 50 deployer liability on a passive host.
A platform's terms may require uploaders to declare synthetic audio, but that contractual safeguard does not transfer authority over generation. It can route labels and preserve evidence while leaving deployer status with whoever decided why and how the AI system would make content.
Compression, transcoding, or repackaging can damage provenance metadata or separate a disclosure from a clipped recording without making the platform a deployer. Preservation checks belong in ingest, export, clipping, and embedding workflows even when the platform's legal role remains limited.
A recommendation system, content-moderation process, or platform-built generator must therefore be assessed separately. Hosting a user file reveals little about who provides the recommender, who deploys moderation AI, or who controls the generation tool. The same service can carry distinct duties for different systems.
Broadcasters face the same split. A station merely relaying a third-party program may not be the deployer for synthetic speech inside it, while one that orders and controls production can be. Scheduling and transmitting the finished item are not equivalent to deciding how AI made it.
A useful role record identifies the AI system, the entity that chose it, who approved its purpose, and who distributed the finished audio. It should also record the label supplied by the deployer and whether the platform preserved it across playback routes. Those facts separate authority over creation from responsibility for later transmission.
A podcast host that stores a client's episode and pushes its RSS feed may only distribute material made elsewhere. A radio station airing a supplied clip can occupy the same limited role if it never directed voice generation, leaving the professional creator as likely deployer.
The boundary moves when a platform commissions a synthetic voice, selects the tool, directs a contractor, and approves the resulting performance. Technical access is unnecessary when authority includes responsibility for purpose and manner of use, so paying a freelancer to operate the system does not avoid status.
Authority follows the AI production decision
Article 3(4) defines a deployer as a person or body using an AI system under its authority outside personal, nonprofessional activity. The final guidance makes this a decision-making test by asking who chose deployment and controlled actual use, including outputs, rather than who touched the keyboard.Evidence of authority over how AI content is produced can sit in a creative brief, approval chain, prompt instructions, or contract. A brand that orders a voice clone and dictates its lines, audience, and release may retain authority when an outside studio operates the software. Employees and contractors working under the company's instructions are not separate deployers for that system.
The reverse matters when a client orders ordinary audio and a creative agency independently decides whether and how to use AI. The role can then sit with the agency, while approval of the finished file alone does not necessarily prove control over the underlying system.
One company may passively host creator uploads, provide a built-in voice generator, and deploy that generator for advertisements it commissions itself. The corporate name does not settle the analysis because each system and workflow has its own allocation.
A platform label does not assume the creator's duty
Putting an AI badge on an uploaded episode does not turn the host into its deployer. The final guidance says merely applying or displaying a label does not convert a distributor, so platforms can facilitate labeling without taking that role. Voluntary assistance is not proof that the platform controlled the audio's generation.That allocation fits the two-sided treatment of synthetic audio because a hosting interface can carry a deployer's human-facing notice without becoming the deployer. An uploader acting as deployer must still ensure that disclosure is clear and distinguishable by the listener's first exposure. If the badge disappears on embeds or syndicated feeds, a platform button has not solved every release route.
Hosts are nevertheless strongly encouraged to preserve existing machine-readable marks and audience labels through proportionate, technically feasible detection measures. That encouragement supports the information chain, but it differs from imposing Article 50 deployer liability on a passive host.
A platform's terms may require uploaders to declare synthetic audio, but that contractual safeguard does not transfer authority over generation. It can route labels and preserve evidence while leaving deployer status with whoever decided why and how the AI system would make content.
Compression, transcoding, or repackaging can damage provenance metadata or separate a disclosure from a clipped recording without making the platform a deployer. Preservation checks belong in ingest, export, clipping, and embedding workflows even when the platform's legal role remains limited.
Other platform duties survive the hosting distinction
Article 2(5) expressly leaves the Digital Services Act rules on intermediary liability unaffected. The transparency guidance likewise says a host's non-deployer position does not remove obligations under that law or other applicable rules. Avoiding one Article 50 role is not a general exemption for the service.A recommendation system, content-moderation process, or platform-built generator must therefore be assessed separately. Hosting a user file reveals little about who provides the recommender, who deploys moderation AI, or who controls the generation tool. The same service can carry distinct duties for different systems.
Broadcasters face the same split. A station merely relaying a third-party program may not be the deployer for synthetic speech inside it, while one that orders and controls production can be. Scheduling and transmitting the finished item are not equivalent to deciding how AI made it.
A useful role record identifies the AI system, the entity that chose it, who approved its purpose, and who distributed the finished audio. It should also record the label supplied by the deployer and whether the platform preserved it across playback routes. Those facts separate authority over creation from responsibility for later transmission.
