Make compliance with GDPR Erasure Requests seamless for developers

As a Roblox developer, it is currently too hard to respond to the massive amount of GDPR Right to Erasure requests I receive under the current format Roblox forwards these requests to me.

If Roblox is able to address this issue, it would improve my development experience because all the time I spend complying with erasures in the current inefficient manner would be able to be used for developing games instead.

Sometimes I get bursts of up to one request per minute:

To comply with these requests I have to open Studio for each game for each UserID for which a removal is requested, search through the data stores (perhaps through multiple past versions of data store formats used in the game because Roblox does not tell me when this player played my game) and manually delete their data.

I imagine that devs who run much larger games than me simply ignore these requests because there would be no way to keep up with them and also have time to develop games.

Roblox has already stated they are unwilling to automatically perform these removals, even if we utilize the Datastore2 UserID tagging functionality because “We don’t want to directly delete it unless authorized by you.”

Here are two proposed solutions, respecting the “we won’t directly delete without authorization” mantra, that would make the developer experience much more seamless.

Proposal 1

Proposal 2

Both of these proposals would take advantage of the DataStore v2 User ID metadata tagging to detect which data store records are associated with which User IDs.


I’d rather have an API which pushes events directly to the server in queue, like a datastore. If it’s not dealt within 7 days, create a message to the dev telling them.

It’s important to note that not all places deal with data exclusively within Roblox and any solution must include it and allow for review of this content to ensure best practice.

The amount of visible GDPR violations is unacceptable and the lack of care from Roblox is real unfortunate. All this takes is one organisation to notice to bring absolute hell for everyone, you must expect some of the fines to run down to developers who failed their legal duty.

Did Google get fined 7.6 million Euros for failing to delete GDPR erasure requests across two countries in 2020? Yes. Here’s a list of reported GDPR fines. It is critical that this sort of incident is avoided for everyone’s sake.


Since making this thread I learned about OpenCloud which allows us to access datastores through a web API. I’m writing a python script that checks my Roblox messages for GDPR messages from Roblox and then automatically performs the deletion.

One problem in my view with this approach is the fact that Roblox sends the GDPR removal requests directly to my account’s inbox. That means (as far as I can tell) my script needs to have my .ROBLOSECURITY cookie to be able to check my PMs - which expires after a certain amount of time, and every time I log out.

And it also makes me wary of deploying this code on a remote server because I’d have to trust whoever is running it not to take the cookie and have access to my entire account.

It would be a lot better if these GDPR requests came somewhere through the group, and I could access them through the OpenCloud API. Then I could have a single API key that only has permission to read GDPR erasure requests, and to write to my games’ datastores.

That way, in the event the code was compromised, there would be virtually 0 harm: My cookie remains safe, and the attacker probably cannot even use the limited API key because of the IP address whitelist.