On August 10th, 2026, my Roblox account “kpc” was permanently terminated for “Harmful Content/Behavior – Other.” I have been using Roblox for approximately three years, and I genuinely believe this termination was made in error.
There is a critical issue with the Violations and Appeals Safety Dashboard, where accounts subjected to automated bans (specifically categorized under “Harmful Content/Behavior – Other”) appear to be unable to submit an appeal directly through the UI. Furthermore, there is a discrepancy between what is displayed on the frontend UI and what is returned in the backend API payload.
Additionally, the “Activity we reviewed” section is only showing “More details about this violation aren’t available.” This appears to be an error with the automated moderation system, as the system does not provide any specific information about what activity supposedly caused the termination. This makes it impossible for me to understand what I allegedly did wrong or properly challenge the enforcement.
The ban page vs. how it should look:
I understand that the notice states that appeals should be submitted through Roblox Support. However, I have already followed this process and submitted multiple appeals regarding my termination, but I have not received a meaningful response. My support requests have remained unanswered for an extended period of time, leaving me without a functioning way to properly appeal the enforcement or receive clarification about the reason for my termination.
Under the front-end “Activity we reviewed” section, it simply states: “More details about this violation aren’t available.” However, inspecting the raw data or endpoint payload reveals hidden internal flags like VIOLATION_TYPE_CHILD_ENDANGERMENT attached to my violation IDs, which makes no sense and proves the automated categorization is completely bugged out.
https://apis.roblox.com/moderation-appeal-service/v1/users/userid/violations
Expected behavior
Transparent Review Context:
The frontend UI under “Activity we reviewed” should clearly display the specific context that triggered the moderation action—such as a specific chat message, voice chat log, or asset ID—allowing users to understand the reason for the enforcement rather than returning a blank “More details about this violation aren’t available” message.
Functional Dashboard Appeal Flow:
The Violations and Appeals safety dashboard should render an active, working Appeal button directly on the page for eligible accounts, allowing users to submit an appeal straight to human reviewers without being forced into broken external support ticket loops.
Frontend and Backend Synchronization:
/moderation-appeal-service/v1/users/userid/violations) should precisely match what is displayed to the user on the frontend. Internal flags (such as severity tags) should only be assigned when actual, verifiable evidence exists and is properly displayed to the user. Automated categorization should not throw unevidenced severe flags while simultaneously locking the user out of the appeal interface.
A private message is associated with this bug report
