Streaming matches
Streaming processes personal data, and that needs a legal basis. Which one depends on the scenario. Consent is not the starting point here but the fallback.
In esports the broadcast is the condition for anyone being able to watch at all. The action happens on a screen, and without a stream there is no audience. The data protection question therefore goes to the core of the business.
Four situations, four assessments
- Public tournamentWide reach, often a professional production, contracts between organiser, teams and players. Outside the professional game those contracts are usually missing, and the need for protection is greater.
- Internal practiceA small circle, but frequently voice chat and webcams. What matters here is whether a recording remains and who can watch it later.
- Scrim against othersEach side also processes data of the opposing players, with whom there is no contract. The scope belongs in an agreement beforehand.
- Your own channelA single person broadcasts, often under the club name. Who is the controller turns on the influence of the club, not on the logo in the overlay.
Technology reduces the effort
Much of what becomes legally difficult only arises from the scope of the broadcast. Reduce the scope and you need fewer declarations, and the bases that exist anyway will more often be enough.
- A delay of 30 to 90 seconds so the production can intervene before anything reaches the audience
- Framing and capture area chosen so that bystanders and other people’s screens stay out
- Separate audio channels so that tactical talk is not broadcast along with the rest
- Overlays that place names and statistics deliberately rather than letting them run
- Deletion routines for recordings, with a period that is actually observed
How we help
We map the scenarios in your organisation, name the legal basis for each, and settle controllership between club, team and the person streaming. What comes out of that is an arrangement that fits how you operate, not a form nobody reads.
Tournament or practice on stream?
Tell us what goes out. We will tell you what carries it and where consent is genuinely needed.
Get in touchFrequently asked questions
Do we need consent for every stream?
No, and starting there is starting at the wrong end. In the professional game, player and participation contracts carry the broadcast, in a club the membership relationship formed by the application and the statutes carries part of it, and legitimate interests stand alongside. Only where a stream carries a great deal, such as webcam footage and recorded voice chat, do those bases reach their limit. Then consent is needed, and it has to be freely given.
Who is the controller when a member streams under the club's name?
As a rule the member, because they decide on purposes and means. The club is drawn in once it exerts influence and pursues its own purposes, through requirements, branding or further use of the recordings. This is not a formality: information duties and liability follow controllership.
Is Twitch our processor?
No. Platforms such as Twitch and YouTube use the data for their own purposes and are therefore controllers in their own right. An Article 28 GDPR contract does not fit there. It fits IT service providers and storage providers acting only on instructions. Where servers sit outside the EU, the question of transfers comes on top.
What applies to scrims against other clubs?
The hardest case, because each side also processes data of the opposing players, with whom there is no contract. Anyone broadcasting or recording such practice matches should agree it with the opponent beforehand and limit the scope, for instance to their own perspective without the other side's voice chat.
Does the media privilege help us?
Only for independent journalistic reporting. A broadcast produced by the organiser, the club or the team itself is self-promotion rather than reporting, however professional the production. Relying on it tends to fail precisely where it would be needed.