For School IT Administrators

Approving Pixel Game Lab on your network

Pixel Game Lab is a browser-based game design and pixel art tool used in schools and after-school programs, built by Game Design Academy®. This page has everything you need to review and allow it on student devices. If anything here is missing, please contact us and we will answer the same day.

1. Domains to allow

Pixel Game Lab runs entirely in the browser over standard HTTPS on port 443. No installation, no extension, and no plugin is required.

Please allow all three required domains together. Allowing only pixelgamelab.com results in a page that loads but cannot sign anyone in and shows no artwork — which looks like a broken site rather than a filtered one.

Domain	Purpose	Status
pixelgamelab.com	The application itself (also serves www., which redirects here).	Required
kdyxrsqegockezuehqaq.supabase.co	Sign-in and all account data. Blocked ⇒ students cannot log in at all.	Required
ced0cb7ea4c471c6958e4205bba714ee.r2.cloudflarestorage.com	All student artwork and images. Blocked ⇒ the app loads but every drawing, thumbnail and background is blank.	Required
challenges.cloudflare.com	Bot check shown only on the public sign-up form. Students sign in with a class code and never see it.	Optional

If your filter prefers wildcards, *.supabase.co and *.r2.cloudflarestorage.com are equally acceptable.

2. What we collect from students — and what we do not

Pixel Game Lab is built for children, and its data handling is deliberately minimal. Students in a school program are given accounts by their teacher; they never sign up themselves and are never asked for personal information by us.

No advertising, ever. There are no ads and no ad networks anywhere in the product.
No third-party analytics or tracking. We removed analytics entirely rather than track children. Nothing about student behaviour is sent to any outside company.
No email address or phone number is collected from students. School accounts are created by the teacher and used with a class code.
No student work is public by default. A game is only visible outside the class if it is deliberately published, and every publication is reviewed by a human first.
Published school work is credited collectively — for example “GDA Carlstadt students” — so no child is ever named on a public page.

Data stored for a school student: their name as entered by the teacher, their class assignment, and the artwork and games they create. That is the complete list.

3. Security, hosting and compliance

HTTPS everywhere. All traffic is encrypted; the site is served over TLS on port 443 only.
Data residency. Application and database hosting are in the United States.
Access control. Students see only their own work and their classmates’ work within their own class. Teachers see only their assigned classes.
Communication. Students have no open chat. Messaging and friend features are disabled for school accounts entirely.
Moderation. Every published game and every shared artwork is reviewed by a person before it becomes visible to anyone outside the class.
Deletion. Account and content deletion is available on request and is carried out immediately — see our data deletion page.
COPPA. The service is designed around COPPA’s data-minimisation requirements. Full detail in our Privacy Policy.

If your district requires a signed data privacy agreement before approval, please get in touch and we will work through your district’s paperwork with you.

4. Device requirements

Any modern browser — Chrome, Safari, Edge or Firefox — on a Chromebook, laptop, desktop or tablet. The creation tools need a landscape screen at least 1000 pixels wide, which every school Chromebook comfortably exceeds. Phones can play published games but cannot run the creation tools.

Questions, or need something in a particular format? Email us — we are a small team and answer quickly. You can also read the School Partnerships page for how schools use Pixel Game Lab.