Information for schools and districts

Mathroom is a free, browser based math practice program for grades 1 through 9. This page collects what a district usually needs in order to approve it: cost, data handling, security, accessibility, and standards alignment.

Everything on this page can be verified independently. Where something has not been established, this page says so rather than implying it.

Contact: privacy@mathroom.fun for data questions, hello@mathroom.fun for everything else.

Cost

Free to use. No purchase, no subscription, no in app purchases, and no ads. There is no tier, no per seat price, and no procurement process.

No license to sign, no contract, no quote, no renewal. Teachers can begin without approval from a budget holder, though many districts will still want the rest of this page first.

There is no purchase mechanism inside the product. The game's currencies are earned by doing math and cannot be bought with money. There is no checkout, no payment field, and no real money conversion anywhere in it.

Student data

No accounts. No email address, no password, nothing to sign up for.

No student data collected. Progress is stored on the device.

Local learner preferences include a name or initials, school grade, and optional U.S. state choice. They remain on the device and in user-exported backups. The app does not request or infer device location.

Nothing about your students leaves the room.

The product's stated privacy posture, in full: no application accounts; no passwords in the player; no analytics or advertising; no learner data sent to any application backend; no social profiles, chat, or public leaderboards; no real money purchase system; no device geolocation or inferred location; no cloud save. Backups are created only when a user chooses to create one.

One limitation, stated plainly. Because progress is stored on the device, clearing browser data can remove it unless a backup has been exported. A per learner backup file can be exported at any time and reloaded on the same or another device. We recommend a weekly backup per learner on shared classroom devices.

Network behavior and security

This section is written for district IT.

Third party requests. Fonts, audio, video, models, and all game assets are served from the Mathroom origin. No analytics, error reporting, telemetry, font CDN, or media CDN endpoint is configured anywhere in the application.

The Content Security Policy below restricts resource loading to the Mathroom origin. The release checker traces both worlds and reports the origins it observes.

Content Security Policy for the game:

default-src 'self'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; media-src 'self' blob:; font-src 'self'; connect-src 'self'; worker-src 'self'; manifest-src 'self'

The For Grown Ups studio and its named adult documents use frame-ancestors 'self' and X-Frame-Options: SAMEORIGIN so Mathroom can embed them. The game and other routes retain frame denial.

Game security headers, as served over HTTPS:

HTTP requests are redirected to HTTPS. HSTS is served with a one year max age including subdomains; the preload token is not currently set.

Note that the Permissions Policy explicitly disables camera, microphone, geolocation, payment, and USB. The product has no use for any of them.

Secure development. Development follows the intent of the NIST Secure Software Development Framework: pinned major dependencies, deterministic asset manifests, type checking before bundling, media and content synchronisation verification, sanitiser and transaction testing, deployment credentials kept outside source and build output, commit and release identity attached to every deployed generation, staging and validation before activation, retained rollback generations, and built asset inspection for unexpected secrets or endpoints. The public player has no capability to write to the source repository.

Release identity is public. release.json returns the commit and release currently serving, so you can confirm exactly what version your students are running.

Standards alignment

Practised skills are mapped to Common Core State Standards for Mathematics codes. The report describes practice coverage of the listed standards, not a formal assessment. The progress report shows, for each practised skill, its descriptor, its CCSS code, attempts, correct answers, and a level band.

All nine grade selections carry concept to standard mappings.

What is and is not claimed:

• The mapping identifies a closest primary CCSS code for each internal concept, with a parent facing descriptor. A concept spanning several standards lists the primary one.
• The report describes practice coverage of the listed standards, which standards a learner has worked on and how it went. It is not a formal assessment, a grade, a diagnosis, or a placement recommendation, and it is deliberately worded not to read as one.
• Complete coverage of a grade's full CCSS curriculum is not claimed. The product maps the standards it practises, not the standards a grade contains.
• No framework edition, adoption date, or state specific adaptation is recorded, so none is claimed here.

Accessibility

WCAG 2.2 is the normative accessibility framework, and accessibility checks are part of the release gate.

This is a conformance framework and its applied checks. It is not a VPAT or a formal Accessibility Conformance Report, and no third party audit is claimed. If your district requires a formal conformance document, contact hello@mathroom.fun and tell us which format you need.

Child safety design

Protections built into the product rather than promised around it:

• Plain language costs and odds wherever an in game choice has either
• No pressure based on real world time or scarcity
• No real money conversion of any kind
• No external social contact, chat, or messaging
• No public identity and no public leaderboard
• No automatic sharing of anything
• Recovery and reset actions require deliberate confirmation
• Progress language avoids medical, diagnostic, or high stakes assessment claims

A wrong math answer does not remove earned currency or collectibles. Action games include health and hazards; a platformer level can require another attempt.

Technical requirements

Runs in a browser. Nothing to install, no extension, no admin rights. Chromebooks, iPads, Windows and Mac laptops, and phones.

Offline. Core play and previously loaded content work offline. After a first successful visit, the cached application shell, the math engine, local progress, the progress report, and local save and restore operate without a connection. First installation, updates, and any uncached asset require a network. Radio and DJ audio stream on demand and are not part of the offline cache.

Storage. The offline cache reserves headroom against the browser's reported quota and pauses warming under data saver mode or storage pressure. Actual available space on a given district device depends on that device.

Network access. Allow mathroom.fun over HTTPS. No other origin is required.

If your filter blocks it: school content filters frequently block anything categorised as a game, and some block domains they have not categorised. Mathroom is a browser based educational math program for grades 1 through 9 with no accounts, no advertising, no purchases, and no student data collection. If it is blocked on your network and you would like help getting it categorised correctly, contact hello@mathroom.fun.

Evidence and research basis

We have no efficacy study, and no ESSA evidence tier certification. Not Tier I, not Tier IV. No randomised trial, no quasi experimental study, no correlational study, and no third party validation of learning outcomes. Mathroom is a practice tool that has not been independently measured, and anyone telling you a product's effect size should be able to show you the study.

What we can give you is the design rationale, stated plainly enough to evaluate:

• Retrieval practice. Learners answer before they are shown a method, rather than reading a worked example first.
• Worked examples on demand. Show Steps presents the full method beside the problem, and converts that round to practice rather than assessment, so asking for help costs nothing.
• Distributed practice. Cleared material returns on a schedule (currently one, three, seven and twenty one days) with success extending the interval and a miss shortening it.
• Interleaving and prerequisite reinforcement. Tracks deliberately include prerequisite standards from earlier grades, because a missing prerequisite in mathematics does not slow a learner down, it stops them.
• Mastery evidence that cannot be inflated. Assisted answers do not enter the qualifying evidence the report reads from. A learner cannot raise a band by asking for more help.
• Bounded adaptivity. Difficulty adjusts within the chosen track rather than moving a learner off their grade.

These are ordinary, well supported instructional practices, implemented deliberately. That is a rationale, not evidence of outcomes, and we would rather you know the difference than have us blur it.

If your district requires a documented rationale in a specific format (a logic model, an ESSA Tier IV submission, a completed evidence questionnaire), contact hello@mathroom.fun and tell us which. We would rather produce the document you actually need than publish an approximation.

Integration, and what we deliberately do not support

Because there are no accounts, several things a district usually asks about do not exist here:

• No SSO or LTI. There is nothing to sign into.
• No rostering: no Clever, no ClassLink, no OneRoster sync. There is no roster to sync.
• No gradebook or LMS integration. Reports print; they do not export to an SIS.
• No admin console or district dashboard. There is no account layer to administer.
• No SOC 2 report. SOC 2 attests to controls over customer data held by a vendor. We hold no customer data on any server. We can complete a security questionnaire describing the posture above, and the deployed configuration is verifiable from outside.

These are consequences of collecting nothing. If your district's process requires rostering or SSO as a precondition, Mathroom will not clear it, and we would rather say so on this page than in week six of a procurement.

What we do not claim

Being precise about the limits is what makes the rest of this page credible.

• No formal VPAT or third party accessibility audit
• No claim of complete CCSS curriculum coverage, and no framework edition or state alignment
• No ESSA evidence tier certification at any tier, and no efficacy study
• No independent verification of the standards mappings against official CCSS text
• No certified browser or device support matrix
• No SOC 2, ISO 27001, or equivalent attestation
• No SSO, LTI, rostering, or SIS integration
• No independent security audit or penetration test is claimed

If your district requires any of these, contact hello@mathroom.fun and tell us what you need. We would rather produce the document you actually require than publish an approximation of it.

Questions

For data and privacy questions: privacy@mathroom.fun For everything else: hello@mathroom.fun

Links: For teachers · Teacher quickstartDownload the one page summary (PDF)

More detail: Privacy · Accessibility · Standards · FAQ

https://mathroom.fun/for-schools