Open-Sourcing our GDPR Compliance Preparation For Articles 30, 32, and 35
I found one of the toughest things about GDPR is determining what is or isn't personal data, when dealing with less common types of data.<p>R6DB for example, a video game stats website, decided to shut down [1] due to unknown territory over whether or not player account IDs and statistics they were scraping from official APIs, are "personal data". (They have now reversed their decision to shut down I believe)<p>As soon as you leave the classic Website tracking/Product usage categories, the definitions get murkier. If I shoot a GDPR data request to eg. Blizzard, do they have to give me any game/stats history they have on me?<p>[1] <a href="https://medium.com/@r6db/r6db-is-shutting-down-db1b59b031ac" rel="nofollow">https://medium.com/@r6db/r6db-is-shutting-down-db1b59b031ac</a>