About RoSignal

Identifies the creator who is signing in, so RoSignal can create and secure their workspace.

Never used to look up accounts other than the signed-in creator.

Reads the signed-in creator's username, display name, and avatar so the workspace and audit logs show who performed each action.

Never used to collect profile data about players or other users.

Publishes the creator's own operational updates — live configuration values, scheduled operational messages, and moderation commands — to the running servers of experiences the creator owns or is authorized to manage. This is the delivery channel that makes the tooling work without a code push and a full restart.

Never used to message experiences the signed-in creator does not own or manage, never used to read player data, and never used to deliver third-party or advertising content.

Reads the existing ban list for the creator's own experience so the moderation console shows the true platform state — who is currently restricted, until when, and with what reason — instead of a separate copy that can drift out of sync.

Never read for experiences the signed-in creator does not own or manage, and never used to build profiles of players outside the creator's own moderation records.

Applies and lifts bans on the creator's own experience through Roblox's official restriction API, so a ban issued in RoSignal is enforced by the platform at join time instead of relying on custom in-game code the creator has to write and maintain.

Never used to restrict players in experiences the creator does not own or manage, never applied automatically without a creator-configured rule or explicit action, and every action is recorded in an audit log with the account that performed it.

Reads the name and basic metadata of experiences the creator manages, so the dashboard can show a private or friends-only experience under its real name instead of a numeric placeholder. Without it, Roblox's public API simply hides those names.

Never used to read experiences the signed-in creator does not own or manage, never used to read player data, and never used for anything beyond displaying the experience's own name to its creator.

Reads an experience's first-party Roblox analytics (daily active players, sessions, session length) so the creator's dashboard can show those metrics next to the events their own game code reports — the same numbers they already see in Creator Hub.

Never used to read analytics for experiences the signed-in creator does not own or manage, never used to read data about individual players, and never sold or shared with anyone.

Reads the roles of a group the creator links to their own experience, so the dashboard can show the real role list and the creator can pick which role a player should hold.

Never used to read groups the signed-in creator cannot already administer, and never used to build profiles of group members.

Moves members of the creator's own linked group between roles — promoting a player who reached a milestone, ranking a whole player segment at once, or applying a rank change from a creator-configured automation. This replaces the manual, per-player rank work studios otherwise do by hand.

Never used on groups the creator does not administer, never used to change ranks at or above the creator's own rank (Roblox blocks this too), never used to post, purchase, or change group settings, and every rank change is recorded in an audit log with the account or rule that caused it.