Legal
Privacy Policy
What personal information Blockout Games keeps, why, for how long, who else sees it, and how to use your rights.
Last updated
This policy covers every site Blockout Games runs: blockoutgames.com, docs.blockoutgames.com, status.blockoutgames.com, account.blockoutgames.com, studio.blockoutgames.com, the developer API and, once it opens, mcp.blockoutgames.com. It is written for Quebec's Act respecting the protection of personal information in the private sector (as amended by Law 25) and Canada's Personal Information Protection and Electronic Documents Act (PIPEDA).
The public sites need no account, and we keep nothing about you when you only read them, beyond the short technical records described under What we collect.
The person in charge
Isaac Wallace is the person in charge of protecting personal information at Blockout Games. Write to them at [email protected] for any question, request or complaint about your personal information.
What we collect
Most of what we keep is about the studio's members, who sign in. Item by item:
| What | Why | Where it comes from |
|---|---|---|
| Your GitHub user id, login, name and profile picture address | To know who you are and show it in menus | GitHub, at each sign-in |
| Your membership of the BlockoutGames organization on GitHub, your role, and when it was last checked | Only members may sign in; owners have more access | GitHub, at sign-in and about every five minutes after |
An encrypted GitHub access token, with the read:org permission only | To recheck your membership | GitHub, at sign-in |
| Your sessions: when each started and was last used, its network address and browser | To keep you signed in, and so you can see and end them | Your browser |
| The audit log: sign-ins, refused sign-ins, sign-outs and ended sessions, with network address and browser; changes you make to studio keys; your privacy requests | Security, and to show you your recent activity | Your use of the sites |
| Questions the assistant declined: the category, and the first 200 characters of the question, with anything that looks like a key or an email address removed | To stop misuse of the assistant | Your use of the assistant |
| Your choices: notification settings, the home pages and widgets you lay out, starred pages, the games you watch | To give you the studio the way you set it up | You |
| Notifications the studio sends you, and the browsers or phones you turned notifications on for (a label such as "iPhone · Safari", and the push service's address and keys for that device) | To tell you about studio events | You and the studio |
| Contract signatures: which terms you signed, when, from which network address and browser, under which consent wording, and your drawn or typed signature | To prove the agreements studio projects rely on | You, when you sign |
| Points and shares: points you earned, and shares you bought with them | The studio's rules on how a game's earnings are shared | The studio |
Two more kinds of information are not about members:
Players of the studio's games. A game can send player feedback through the developer API: the player's Roblox user id, their message, and the place and server it came from. For a game's own players, the studio also reads bans from Roblox (the player's Roblox id and the reason). Only the game's crew and the studio's owners see these.
The market and the studio's code. We collect public data about Roblox games and their creators from Roblox and Rolimon's, and activity in the studio's own GitHub organization (members' logins, pull requests and commits). This data is public or the studio's own.
When anyone visits a site, our servers and our network provider see the visitor's network address and browser, as every website does. These are written to logs that are kept for 14 days and used only to run and protect the sites.
The assistant does not keep conversations. A question and its answer live only in your open browser tab, and our logs record how long an answer took, never what was asked. The model runs on the studio's own server: questions are not sent to an outside AI company.
We do not use analytics or advertising cookies, we do not sell personal information, and we do not use it to build profiles for advertising. The cookie notice lists every cookie.
Why, and on what basis
We use personal information only for the purposes in the table above: to run the sites, to let members work in the studio, to keep the sites secure, to keep records the law or a signed agreement needs, and to answer you.
Members consent when they sign in, which is said on the sign-in page; using the studio needs this information. A contract signature is collected with its own consent wording at the moment of signing. You can withdraw consent at any time (see Your rights); some records must still be kept, as said below.
How long we keep it
| What | How long |
|---|---|
| Sessions | Until you sign out, 30 days without use, or 90 days at most; then deleted within about an hour |
| A sign-in in progress | 10 minutes at most |
| The audit log, including the assistant's declined questions and privacy requests | 180 days from each entry |
| Server logs (network address, browser, the page asked for) | 14 days |
| Your profile, connected GitHub account, choices, notifications and push devices | Until your account is deleted. A push device is removed sooner when its push service says it is gone |
| Contract signatures and the signed contracts | For as long as the contract has effect, and afterwards for as long as it may have to be proven |
| Points and shares | As long as the studio's records of a game's earnings need them |
| Player feedback | Until the studio deletes it; a fixed period is being decided and will be written here |
| Players' bans | Until Roblox no longer lists the ban |
| Backups of the database | Nightly, kept 14 days on the studio's servers and up to 60 days in the off-site copy |
Who else sees it
We share personal information only with these providers, only for what they do for us, and never to sell it:
GitHub (GitHub, Inc., United States), for signing in and the organization's membership. GitHub already holds your GitHub account; we send it your sign-in and ask about your membership.
Cloudflare (Cloudflare, Inc., United States, with servers worldwide), which carries every request to our sites: names, encryption and the connection to our servers. It sees each visitor's network address and browser.
The push services of browser and phone makers (Google, Mozilla, Apple, Microsoft), only if you turn notifications on, to deliver them. They see the notification's title and text.
Roblox, when the studio's servers read its public data or a studio game's own data. We do not send Roblox members' personal information.
Our servers are the studio's own, in Quebec, Canada, and the database, its backups and the assistant's model run on them. Using GitHub, Cloudflare and the push services means some personal information leaves Quebec and Canada, mostly to the United States, where it is protected by those providers' terms and the law there, which may differ from ours.
Inside the studio, owners see the audit log and members' standing; a project's members see its contracts and signatures; everyone signed in sees other members' names and pictures.
We may also disclose personal information when the law requires it.
How we protect it
Every connection to our sites is encrypted.
Session tokens and game keys are stored only as hashes, and GitHub tokens are encrypted; a copy of the database opens no account.
Access inside the studio follows each person's role, and the API checks it on every request.
Requests are rate-limited, and sign-ins, refusals and changes to keys are recorded in the audit log.
The servers, the database and their backups are under the studio's control.
No system is perfectly secure. See Incidents for what we do if something goes wrong.
Your rights
You have the right to:
Access the personal information we hold about you, and know how it is used and who has seen it.
Correct it. Your name and picture come from GitHub and are refreshed at each sign-in; change them there. For anything else, write to us.
Delete it, and have it no longer shared, subject to what the law requires us to keep.
Take a copy of it in a common, structured format (portability).
Withdraw your consent: sign out, leave the organization, turn notifications off, or ask for your account to be deleted.
Complain to us, and to the Commission d'accès à l'information du Québec or the Office of the Privacy Commissioner of Canada.
How to use them:
Download my data. Signed in, go to Settings › Privacy and choose Download my data. You get a JSON file of everything listed above that is about you, except credentials (tokens and keys), which would let someone act as you. You can do this five times an hour; each download is recorded in the audit log.
Delete my account. In the same place, choose Delete my account. The request is recorded and every session you have ends at once. The person in charge completes it within 30 days and confirms it to you. We keep only what we must: contract signatures and signed contracts, which prove agreements other people rely on; the audit log's entries, for their 180 days, for security; and backups until they roll off. Once your account is deleted, signing in again would start a new one.
Anything else, or if you cannot sign in: write to [email protected]. We answer within 30 days, and may ask you to prove who you are first.
Children
Our sites are not meant for children under 14, and we do not knowingly keep personal information about them. Quebec's law needs a parent's consent before personal information about a child under 14 is collected; we ask for none, so we collect none. If you think we hold a child's information, write to us and we will delete it.
Incidents
If personal information is lost, accessed or disclosed without authorisation, we act to reduce the risk of harm, keep a record of the incident, and, where it presents a risk of serious injury, notify the Commission d'accès à l'information, the Office of the Privacy Commissioner of Canada and the people concerned promptly.
Changes
The date at the top says when this policy last changed, and this list says what changed.
3 November 2026: the minimum age is 14, as Quebec's law asks for a parent's consent below it.
28 October 2026: first version.



