Hello,
I believe I have encountered an issue with Roblox’s automated moderation system that resulted in the termination of my account.
My Roblox alt account is @820. The moderation action appears to be related to an experience called “so crying rn [NEW]” (71552561933796).
The important details are:
• The experience had been PRIVATE since February.
• The experience contained no models, scripts, assets, inappropriate content, or other meaningful content.
• It was essentially just an empty baseplate.
• Despite this, my account was terminated, and I believe the moderation system may have acted based solely on the experience’s name.
I have already contacted Roblox Support and appealed the termination. However, my appeal was rejected with the response that the account had previously been reviewed and that the consequence would not be adjusted.
I am not trying to dispute Roblox’s right to moderate content. My concern is specifically that an automated moderation system appears to have resulted in a severe account-level punishment for an experience that was private and contained virtually no content.
I have attached screenshots showing the state of the experience and its privacy status as evidence.
I would appreciate it if an engineer or moderation specialist could investigate whether the automated moderation system incorrectly classified the experience and whether this could have caused the account termination.
I saw many other cases like mine:
Multiple cases
Multiple cases #2
Expected behavior
A private experience containing only an empty baseplate should not result in an account termination based solely on its name.
If the experience name is considered inappropriate or violates a policy, I would expect the experience itself to be moderated appropriately rather than the account receiving a severe termination when there is no other violating content present.
I would also expect the moderation system to take the experience’s privacy status and actual contents into consideration when determining the severity of an enforcement action.
A private message is associated with this bug report



