Only members of the BlockoutGames GitHub organization can sign in, every request is checked against who you are, and no key or token is ever shown back once stored. This page says how.
How sign-in works
You sign in with GitHub. The panel sends you to GitHub, which asks you to allow the studio's app to read your organization membership (read:org, nothing else); GitHub sends you back, and the API checks that your membership of BlockoutGames is active. A pending invitation, another organization or an outside collaborator is refused, and someone outside the organization is sent to the public website with a note that the studio is for its members. The sign-in is protected against forgery (a single-use state bound to your browser, and PKCE). See Signing in and access.
The details, every refusal and the session guard are in Authentication and permissions.
Sessions
A session is a random token in a cookie that only the browser sends and scripts cannot read (HttpOnly, Secure, SameSite=Lax).
It lasts 30 days from its last use (extended at most once an hour) and never more than 90 days from sign-in.
The database stores only a hash of the token, so a copy of the database opens no session.
Every sign-in starts a new session and ends the one the browser held before.
In Settings, Sessions & security you can end one session, end all others, or sign out everywhere. Owners can end a member's sessions from Admin.
How membership is kept current
The API re-checks each signed-in person's membership with GitHub in the background about every 5 minutes, with their own stored GitHub token; no page waits on it. If you leave the organization or revoke the app, every session of yours ends within minutes. If GitHub cannot be reached, your last confirmation stands for 30 minutes; after that you are asked to sign in again.
Roles
There are two roles, both from GitHub: an organization owner is an owner here, anyone else a member. Roles are never edited in the panel. When your GitHub role changes, every session of yours ends, so the next sign-in carries the new role: permissions never change under a running session. Within a game, its lead may change its details and release log, and its crew (its project's developers and its lead) manage its API key. See Roles.
How every request is checked
Every request to the API carries your session and is checked: who you are, your role, and your rate limits.
A change (anything but a read) must come from the panel's own address and carry the panel's header, so another site cannot make your browser change anything.
Owner-only routes refuse everyone else before reading the request.
Rate limits per person, per minute: 600 reads, 120 writes, 60 searches and assistant questions, 20 calls that reach Roblox or GitHub; each address may make twice that. See API rate limits.
The assistant reads with your permissions and can never write.
What data the platform stores about you
- Your GitHub identity
GitHub id, login, display name, avatar and role, refreshed at each sign-in. The email field is a made-up placeholder that is never written to; your real email is not stored.
- Your GitHub access token
Encrypted, used only to re-check your membership.
- Sessions
A hash of each token, with its device, address, start and last use.
- What you choose in the panel
Your watchlist, home pages and favorites, notification preferences, and the phones and browsers you turned notifications on for.
- Your notifications
And whether you read them.
- Studio records you take part in
Projects, contracts and signatures, points and shares.
- The audit log
The entries about you (below).
Which table holds each is in Data model.
Not stored: your assistant questions and its answers. The panel keeps a conversation only in the open tab's memory.
You can download all of it, or ask for your account to be deleted, in Settings › Privacy. The public Privacy Policy says why each is kept and for how long.
Player data from games
A game's servers can send player feedback with the game's key: a category, the text, the player's Roblox user id, and the place and server version. The crew and owners read it on the game's Feedback tab; the assistant reads it without player ids. A key pasted into feedback is removed before storing. Nothing deletes feedback today; a retention period is proposed and waits for a founder.
Games built on the Template before v1.0.0 also sent player reports this way, as feedback of category other starting "Player report", naming both players and their user ids, the reason, the filtered note and the reported player's last five chat lines exactly as typed. The Template removed its player report in v1.0.0 (Roblox's own report in the Roblox menu covers it), so a game on the current Template sends none. Reports already received are kept like the rest of a game's feedback. See player reports on the Feedback tab.
A game's servers also name players' Roblox user ids when they send cross-game transfers and studio bans (the developer API). Erasing everything the platform holds about one Roblox user id on request (their feedback, any older player reports by or about them, transfers and bans), so a game can answer Roblox's erasure requests within 30 days, is also a planned platform change, not built yet.
How Roblox Open Cloud keys are stored (sealed)
Each studio group's Open Cloud key, which reads its games' owned analytics, is sealed (AES-256-GCM encrypted) in the database under a root key that lives only in the cluster's secrets, and bound to its own row so a copied value opens nothing. Only the API and the worker open it, to send it to Roblox. It never appears in a response, a log line, an error, the browser or the assistant; an owner sees only its group, a short fingerprint and what Roblox last said about it. See Roblox groups and keys.
How game API keys are stored (hashed)
A studio game's platform key (bk_live_ and 43 random characters) is shown once, when it is made. The platform stores only its SHA-256 hash and last four characters, so nobody, the studio included, can show it again: a lost key is rotated. Rotating or revoking takes effect on the next request. Keys are stripped from logs and from stored feedback by their pattern. See Keeping a game's key secret.
Other secrets
Sign-in's secret, the credential root key, the assistant's service secret and the push key are cluster secrets, sealed in the repository and never logged or answered. The API refuses to start if the assistant's secret is the same as sign-in's or a root key. The assistant's gateway key is held by the assistant app alone.
The audit log
The audit log (Admin, Audit log, owners only) records sign-ins, refused sign-ins with the reason, sign-outs, ended sessions (an owner's naming the owner), expiries, lost memberships and role changes, with the person, GitHub login, address and device; owners' changes to group keys; a game's key created, rotated or revoked (naming the game, never the key); and changes to games, projects, contracts and shares. It never holds a token or a key. Sign-in and key entries are kept 180 days.
Two-factor authentication
The platform does not require GitHub two-factor authentication itself: GitHub does not tell the studio's sign-in app whether you use it. The organization setting that requires it is a founder's decision; once on, GitHub removes anyone without it and their sessions end within minutes. Owners can see who has it on the Members page.
What is never exposed to the internet
Only the panel and the public website are reachable from outside. The API, the collector, the assistant app, Postgres and Redis answer only inside the studio's cluster, and its network policies refuse every connection not listed. See Architecture.
Related: Authentication and permissions, Roles, Admin pages.
Updated