Privacy Policy

Account information (when you sign in via Roblox OAuth2):

• Roblox user ID, username, display name, and avatar URL.
• Roblox group membership and rank within groups you configure for your Org.
• Session cookies (an encrypted JWT) so you stay signed in.

Org-level data you create:

• Permissions, departments, capabilities and member assignments you define.
• Bans, kicks, warnings, tool/chat/modcall-bans, promotions and demotions you issue.
• Logbook notes you write about players.
• API keys you generate for the SDK (only a hash is stored; the plaintext is shown once at creation).
• Your org’s branding (logo bytes, primary/secondary colours).

In-game data forwarded by the SDK from your Roblox experiences, about players who join:

• Roblox user ID and username of the player and other players in the same server.
• Play sessions (join time, leave time, duration, place ID, server JobId, friend count, co-presence roster).
• Chat messages they send in-game (text + channel + recipients in the server).
• Country and (where available) finer region code, resolved server-side from RobloxLocalizationService.
• Modcalls they create.

We do not collect Roblox passwords. We do not collect payment information unless the Service introduces paid plans, in which case this policy will be updated.

• To authenticate you and grant you access to your Org’s dashboard.
• To let your Org’s staff search players, view profiles, moderate, and run the features you enable.
• To show activity, leaderboards, chatlogs, geolocation and the logbook to authorised staff.
• To enforce bans, kicks and per-capability gates in-game via the SDK.
• To keep an audit trail of staff actions for accountability.

• Contract: account and Org data necessary to deliver the Service you signed up for.
• Legitimate interests: in-game data forwarded by the SDK (used by Org Admins to moderate their Roblox experiences and keep their communities safe), audit logging, and product security.
• Consent: any optional integrations you explicitly enable (e.g. linking a Roblox account for group ranking via OAuth).

• With the Org Admin and staff members of the Org the data belongs to, per the capabilities they have been granted.
• With Roblox itself when calling Roblox public APIs and Open Cloud (e.g. to read group membership, fetch avatar headshots, or, if you linked an account, change a member’s rank).
• With our hosting and infrastructure providers strictly to operate the Service.
• When required by law, or to protect the safety of users or the Service.

• Roblox Corporation — OAuth2 login, public user/avatar/group APIs, Open Cloud Groups API (for ranking, only when linked).
• Map data — country outlines on the geolocation globe are loaded from the open-source world-atlas dataset via unpkg CDN. No personal data is sent.
• Hosting — the Service runs on infrastructure operated by RoPerms; specific providers may change over time.

• Account, Org, audit, ban, punishment and logbook records: kept for the lifetime of your Org, or until an Org Admin requests deletion.
• In-game chat lines and activity sessions: kept for as long as needed to power the Logbook, Chatlogs, Activity and Leaderboard features (typically up to 12 months on the visible dashboard).
• Session cookies: expire when you log out or after a fixed period of inactivity.
• Roblox OAuth refresh tokens for the ranking link: kept until you unlink the account or revoke the grant in your Roblox account settings.

• Access the data we hold about you.
• Request correction or deletion of inaccurate data.
• Object to or restrict certain processing.
• Request a copy of your data in a portable format.
• Withdraw consent for any optional integrations (e.g. unlink the ranking account).
• Lodge a complaint with your local data-protection authority — in the UK, the Information Commissioner’s Office (ico.org.uk).