gdpr germany video-games
The GDPR and how it treats online game character names
<p>I am writing a MUD server - a multiplayer game where people connect and create characters.</p>
<p>I am unsure if the GDPR applies to me - offering a game to the public is not a household task, but I am also not a large company (or a company at all) and I will not be processing data at scale. For this question, let's assume it does (though answers that address this point are welcome).</p>
<p>The character record is easy - the basis for processing is consent. If someone does not want to enter a character name then they can simply not play the game. Likewise, if they choose to withdraw that consent at any point they can simply delete their character.</p>
<p>It is assumed (but not given) that people signing up for a sci-fi computer game will not use their real name, but you never know what people will do.</p>
<p>The sticking point for me is that I wish to build an internal forum/mail/news system into the game itself. I can see in the future that articles will be written into the game along the lines of <code>Lord Thunderthighs recently took on the Foo monsters and won a great victory for the Terran Alliance</code>. Once this happens, it will be incredibly difficult to process deletion requests that scan every bit of text produced in the game to remove character names from it. This goes doubly so as there is nothing stopping someone from creating a character named <code>the</code> or <code>and</code>.</p>
<p>I'm troubled as while there are threads on the WoW forums that state 'character names aren't personal data so they aren't covered by the GDPR'*, there are also a lot of questions here with the answer 'if it can identify a single person, even if their real identity is unknown and unknowable, it is personal data'.</p>
<p>The only basis I can see to keep the in-game articles after a deletion request would be 'legitimate interest', and in my professional life 'legitimate interest is the last refuge of the scoundrel' is basically my catchphrase.</p>
<p>The interest in my case would be 'the community of the game has a legitimate interest in documenting the history of the game world for posterity, and to communicate with each other about it'. The balance test would be that there is (should be) no real world personal data in there, only data that relates to fictional characters inhabiting a game world.</p>
<p>I would welcome answers on whether the GDPR applies at all to my case, and to whether all references to character names beyond the character record need to be the subject of deletion requests.</p>
<p>Country: Germany.</p>
<p>*This thread doesn't have an answer by WoW staff, only a bunch of players. Yes, it is as toxic as you imagine it to be.</p>

<p>Yes, GDPR is going to apply – but it's not going to make everything impossible. Parts of this answer:</p>
<ul>
<li>GDPR applies</li>
<li>You are processing personal data</li>
<li>Consent is rarely a suitable legal basis</li>
<li>The right to erasure is not absolute</li>
</ul>
<h2>GDPR applies</h2>
<p>GDPR is not just for large companies.
It applies to any processing of personal data, unless one of the exceptions applies.
More formally, the processing activity must fall under the GDPR's material and territorial scope.</p>
<p>Art 2 GDPR explains the GDPR's material scope – to which activities it applies.
Here, it will apply, because</p>
<ul>
<li>you are processing personal data</li>
<li>using electronic means</li>
<li>and none of the exceptions apply.</li>
</ul>
<p>There is no exception for non-profit activities or sole proprietors.
The size of your organization only has implications for the question whether you have to appoint a data protection officer or whether you have to keep ROPAs (records of processing activities, de: <em>Verzeichnis von Verarbeitungstätigkeiten</em>).</p>
<p>There is an exception for <em>purely personal or household activities</em>.
As you've correctly guessed, this exception will not apply to your MUD server.
Even if running this server is a personal project,
it is not <em>purely</em> personal.
You're offering the service to the public, not just to close friends and family.
Relevant CJEU case law for this exception are the C-101/01 “Lindqvist” and C‑212/13 “Rynes” cases.</p>
<h2>You are processing personal data</h2>
<p>Per Art 4(1) GDPR, personal data is any information relating to an identifiable person.
For determining whether someone is identifiable,
Recital 26 GDPR tells us that we must consider “all the means reasonably likely to be used”,
including indirect identification,
use of additional information,
and help from third parties.
In particular, being able to “single out” individuals – being able to distinguish users – already counts as identifications.</p>
<p>This means that usernames and all linked information (including their user-generated content) will very likely be personal data.</p>
<p>It is possible that one piece of information is the personal data of multiple persons. For example, a forum post by user A discussing user B's actions is definitely B's personal data (it relates to them, and they are identifiable), and probably also A's personal data (A is identifiable, but depending on context it may or may not “relate” to A).</p>
<p>If you've read on a WoW forum that “character names aren't personal data”,
please disregard this.
Many people are not aware of the GDPR's very broad concept of personal data and identifiability.</p>
<p>Just because something is personal data doesn't mean that processing it is illegal.
It just means that GDPR is going to regulate <em>how</em> you can use this information.
In particular, you will need a “legal basis”.</p>
<h2>Consent is rarely a suitable legal basis</h2>
<p>To process personal data, you are supposed to have a clear purpose,
and this purpose must be covered by a legal basis.
Art 6 GDPR lists six legal bases from which we can choose.
While consent is listed first, it is usually the last legal basis that should be considered.
Instead, it makes more sense to consider them in the following order:</p>
<ul>
<li><p>Art 6(1)(c) processing is necessary for compliance with a <strong>legal obligation</strong>:
if you're <em>required</em> by German or EU law to do something,
GDPR will not prevent that.
Typical examples include financial records for a business,
or complying with court orders to disclose data.</p>
</li>
<li><p>Art 6(1)(b) processing is necessary for the <strong>performance of a contract</strong>:
if users sign up to your service,
you are allowed to do whatever is necessary to provide that service</p>
<p>For example, it is necessary for your MUD to have usernames so that users can interact with each other.
It is necessary to store progress and stats in a database.
When people use the forum, it is necessary to store the posts and to display them to other users.
If you ask for subscription fees, payment processing is strictly necessary.</p>
<p>Here, the main limitation is that necessity must  be considered from the user's perspective.
For example, personalized ads are generally not necessary to provide a service.
Facebook did attempt the argument that its users had contracted Facebook to show them personalized ads,
leading the <a href="https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-22019-processing-personal-data-under-article-61b_en" rel="nofollow noreferrer">EDPB to write a lengthy treatise about the correct interpretation of Art 6(1)(b)</a>.</p>
</li>
<li><p>Art 6(1)(f) processing is necessary for a <strong>legitimate interest</strong>:
you have a good reason to do something,
and you've done a balancing test to show that this has an acceptable privacy impact.
Legitimate interest gives rise to the <em>right to object</em> (opt-out).</p>
<p>For example, security and and anti-abuse measures are typically founded on a legitimate interest.
They are not strictly necessary for the service to work,
but there's a pretty compelling legitimate interest (e.g. safety of other players, maintaining security of your service).</p>
<p>Depending on the legitimate interest pursued, requests to object can also be denied.
For example, it would make no sense if malicious actors could opt out from the security measures designed to reign them in.</p>
<p>Recital 47 gives criteria for conducting a legitimate interest balancing test.
In particular, a legitimate interest might work if the data subject can reasonably expect the data processing to occur, given the time and context in which the personal data was collected.</p>
</li>
<li><p>Art 6(1)(a) <strong>consent</strong>:
finally, we get to consent.
Consent is appropriate when a processing activity is not necessary for your services,
and if the legitimate interest balancing test weighs against the activity,
in particular if the data subject can't reasonably expect their data to be used this way.
Requesting consent serves as a signal to the data subject that a potentially privacy-invasive activity is about to happen.
It is in many ways the legal basis of last resort.</p>
<p>The GDPR defines consent in Art 4(11), and gives further conditions for valid consent in Art 7.
The <a href="https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-052020-consent-under-regulation-2016679_en" rel="nofollow noreferrer">EDPB has written guidelines on consent</a>.</p>
<p>In your context, it's important to note that consent must be <em>freely given</em>.
Art 7(4) GDPR says that you cannot generally make access to a service conditional on unrelated consent.
Saying that “they can simply not play the game” does not provide valid choice.</p>
</li>
<li><p>Art 6(1)(d) necessary to protect <strong>vital interests</strong>: primarily applicable in life-threatening emergency situations.</p>
</li>
<li><p>Art 6(1)(e): necessary for a <strong>public interest</strong> or <strong>official authority</strong>: generally not applicable to the private sector.</p>
</li>
</ul>
<p>Looking at these legal bases,
it is likely that you will base your main processing activities on Art 6(1)(b) necessity for performance of the contract,
and secondarily on Art 6(1)(f) necessity for legitimate interests.
Consent is going to be more appropriate for non-essential aspects of your services.
For example, you might ask for consent to show profile stats publicly (if this isn't necessary for the game to work).</p>
<p>Different legal bases give rise to different sets of data subject rights.</p>
<ul>
<li><p>As mentioned, a legitimate interest allows the data subject to object (opt-out), though the objection can be denied if you can demonstrate overriding grounds. But this should be a case by case determination, taking into account the data subject's individual circumstances.</p>
</li>
<li><p>Consent can be withdrawn at any time, and it must be possible to do so without detriment.
While consent does not invalidate past processing activities,
future processing for that purpose is now impossible.
Thus, when you ask for consent to process data for some purpose,
this gives the data subject total control.
If you can't deal appropriately with withdrawn consent,
this is a strong indication that a different legal basis could be more appropriate,
or that the processing activity is illegal in entirety.</p>
</li>
</ul>
<h2>The right to erasure is not absolute</h2>
<p>The Art 17 GDPR right to erasure lets users ask you to delete their data.
In particular, this request should be granted if keeping the data is no longer necessary for the purposes for which it is being processed,
or if the legal basis for processing expired (e.g. successfully objected to legitimate interests, consent withdrawn).</p>
<p>But compared to other data subject rights (like Art 13/14 information, Art 15 access), this right is fairly qualified and subject to conditions. If you still have a legitimate interest to keep the data around, or if keeping the data is otherwise necessary, the request to erasure can be (partially) rejected. This underlines the importance of selecting a suitable legal basis for processing, instead of going straight to consent which is going to unnecessarily limit your options.</p>
<p>In the context of forums with user-generated content,
it is indeed common to only delete the account,
but not all associated posts.
Whether this is compliant depends on context,
in particular on whether you have a good reason to keep the data around.</p>
<p>It is also entirely normal to not hunt down any post that could mention a particular data subject.
Where one post is the personal data of multiple data subjects,
you must balance the rights of all involved people.
Clearly, the mentioned person's rights would prevail e.g. in the case of doxxing.
But otherwise, you should consider in particular the exception in Art 17(3)(a): that the right to erasure won't apply if continued processing is necessary for exercising the right of freedom of expression and information.</p>
