As a Roblox developer, it is currently too hard to take action against Right to Erasure requests since I receive them for all my games regardless of whether they store user data or not as confirmed by @Hooksmith
If Roblox is able to address this issue, it would improve my development experience because Right to Erasure requests should only show up for games where I actually need to take action against them. This would reduce clutter from unnecessary notifications and help make the system more reliable for developers.
even better, make it easier to automate deleting them without having to make a whole discord server.
and doesn’t roblox have access to all the datastores ever made anyway? why can’t they just delete it themselves?
Roblox has no definitive way of knowing how a game saves DataStores as it can be done in various forms such as OrderedDataStores and DataStore keys can be formatted differently e.g. 1234, Player_1234, User_1234, etc, they cannot just use a search because someone with a userId of 1234 could delete data for 123456.
There is actually now an auto delete system but I still seem to get messages with this enabled so it only does half the work. I haven’t checked if this actually works either but I am assuming it does.
For games that don’t use data stores, it is still possible that data is stored off platform (e.g. on AWS). This is why we will still send the messages to creators.
While we can’t get rid of the Right to Erasure messages, we understand how spammy they are in the Roblox inbox. The team is working on a way to reduce the frequency of these messages to make your workflows easier
Hello! Thank you for providing more information about how the Right to Erasure messages work. Are there any plans to add sorting options to the inbox so developers can view these messages based on type?
I do not have an issue with taking action against these messages, but it can be difficult to keep track of them alongside other messages due to them all being in the same inbox. Better organisation would make it easier to respond to different message types efficiently.
