[Important] Right to Erasure - Action Requested: What Does It Mean?
As your Roblox game gains more players, you might start receiving messages from Roblox titled “[Important] Right to Erasure - Action Requested” like this one:
But do you actually know what this message means?
If you’re thinking, “Yeah, I’ve gotten that before, but I didn’t really get it, so I just ignored it,”—then you should pay attention!
This message is an official request under international data protection laws such as GDPR or CCPA, asking you to immediately delete all saved data of a specific user from all your games.
To respect the player’s legal rights—often referred to as the “Right to Erasure” or “Right to Be Forgotten”—you must delete the player’s data promptly after receiving this message.
Fortunately, the actual task is simple: just delete all data related to that player.
If your game only stores data in a DataStore, you just need to run:
playerDataStore:RemoveAsync(key)
For Roblox’s official explanation of GDPR and CCPA, check the link below:
https://create.roblox.com/docs/production/publishing/about-GDPR-and-CCPA
How to Automate Data Deletion
Now, here comes the next problem:
It’s a huge pain!
Every time a deletion request arrives, you have to open Roblox Studio, find the key, and manually remove it…
If it happens once a year, fine. But when your game grows, you might start getting requests every few months, weeks, or even days.
Nobody wants to handle that manually, especially when you’re busy.
Thankfully, Roblox provides a solution: you can set up a Webhook to automatically receive notifications when a deletion request arrives.
However, Roblox itself cannot receive Webhooks directly, so you need to build an external system that listens for Webhooks and deletes the data accordingly.
The official documentation even shows an example using a Discord Bot:
https://create.roblox.com/docs/cloud/webhooks/automate-right-to-erasure
But here’s the catch:
You never know when a Webhook notification will be sent. That means you need your Webhook receiver—like the Discord Bot—to be running 24/7.
If you already have a constantly running server, great. But most people don’t.
And setting one up usually costs money every month.
You might wonder—why did Roblox choose that example…?
Roblox Deletion Queue (RDQ)
That’s why I developed a tool called Roblox Deletion Queue, or RDQ for short.
Features:
Free! – It uses Cloudflare Workers and Cloudflare D1, both of which are free.
Simple! – You can set it up in just 30 minutes to automatically receive and process deletion requests.
Reliable! – Built on Cloudflare, a platform trusted by major companies worldwide.
Safe! – RDQ only handles the Webhook; it doesn’t actually delete your data. You control how deletion happens.
Convenient! – Comes with optional Discord notifications.
Here’s how it works in a nutshell:
- Roblox sends a deletion request.
- RDQ receives it and stores a list of user IDs whose data must be deleted.
- Your Roblox scripts fetch that “user ID list” from RDQ.
- Once data is deleted, your script tells RDQ, “This user’s data has been removed.”
- RDQ updates its list, removing users who’ve already been handled.
Even if this sounds complicated—don’t worry.
A sample script is provided. Just follow the manual, and you can complete everything in 30 minutes with only about 15 lines of code (for basic games).
You can set it up by following this manual.
I created RDQ and this guide to help creators both respect users’ rights and reduce their own workload.
I hope it proves useful to you!
If you have any feedback or requests regarding RDQ or the sample scripts, feel free to reach out.
Thank you!
- Extremely helpful
- Helpful
- Not very helpful
- Not helpful