Last updated: September 11, 2026
This policy explains what Allgood Academy collects, why, and what we will never do with it. It covers AllgoodOS™ and our GoodBlocks™ learning modules, and it applies to learners, teachers and school staff alike.
Request a review or deletionThe full policy is below. This is the honest summary of it.
Three different people use Allgood Academy, and we collect very different things from each. Most of the confusion about student privacy comes from policies that blur these together, so we've kept them separate throughout.
You can also use most of Allgood Academy without signing in at all. A visitor who starts a lesson is given a readable session name generated on their own device — nothing is written to our database, and nothing is reserved, unless and until they choose to save their progress.
A Recruit Code — a memorable three-word passphrase, for example "arctic-fox-trot" — generated automatically. A display name and an avatar, both assigned automatically. Nothing a learner types identifies them, because they are never asked to type anything identifying.
Alongside that pseudonymous identity we store what the learner did: answers and choices made inside GoodBlocks™, scores, completion status, which Case they reached, time spent on a module, and which classroom code (if any) they joined.
If a learner signs in with Google, we receive their name, email address and profile picture from Google, and use them to create their Digital Passport and issue certificates and badges. We store the same learning and progress data described above.
Name and email address from the Google account used to sign in, the classrooms created, and the roster of learners who joined them. Before creating a classroom for the first time, a teacher is shown a plain-language notice and must confirm they are authorized staff using this tool under their school's policies.
At the end of a GoodBlock™ a learner may leave an optional star rating and a written comment. That comment box is the only place in Allgood Academy where a learner types words that we store. We can't inspect what someone chooses to write there, so we are explicit about how we handle it:
We ask learners not to include their real name or any personal detail in that box. If you believe a child has entered something identifying, email us and we will delete it — see Section 9.
To keep a session working between page loads and visits, we cache a small amount of non-identifying data in the browser's Local Storage on the device itself. This includes a session identifier, the auto-assigned display name and avatar, an age-tier marker, whether the session is a guest session, and flags recording which modules have been completed.
This data stays on the device. Clearing your browser's site data removes it. On a shared device — a school Chromebook, for example — signing out or clearing site data is what prevents the next person from resuming the previous session.
Allgood Academy is free for learners, permanently. That is a product commitment, and it is part of why none of the above is ever on the table.
You must be 13 years of age or older to create an account or sign in via Google.
If you are under 13, you use the Recruit Code system instead of creating an account. A Recruit Code is a 3-word passphrase (for example, "arctic-fox-trot") automatically generated for you — no real name, email address, or account creation is ever required. Your display name and avatar are also generated automatically, so nothing you enter identifies you personally. We do not knowingly collect personally identifiable information (PII) from children under 13. If we discover that a user under 13 has created a real (13+) account, we will delete that account and all associated data.
A Recruit Code is a convenience, not a password. Anyone who knows the exact passphrase can resume that learner's progress — that is deliberately how a child moves to a different device without an email address. Treat it the way you would a library card number, not a password, and tell us if one needs to be retired.
We collect zero Personally Identifiable Information (PII) for under-13 agent learners. Learners under 13 never provide a name, email address, or any other real-world identifying detail — instead, each is assigned a pseudonymized Recruit Code (a memorable three-word passphrase) and an auto-assigned avatar, which together serve as that learner's identity within AllgoodOS™ and let them resume progress on a different device.
All anonymous interaction data and telemetry logs are permanently purged from our systems after 90 days of inactivity. This includes session records (time on task, steps reached, completion status) and event logs (module opens, in-module choices, module completions) tied to an under-13 learner's pseudonymized session. Records still receiving activity are retained only for as long as that activity continues; once 90 days pass with no further activity, the underlying data is deleted from our production database.
If you are a parent, guardian, teacher or school administrator and you want to review or delete a specific learner's data, email us and we will take care of it. You do not need an account to make this request, and you do not need to explain why.
Tell us what you can — a Recruit Code, a display name, a classroom code, or the approximate dates — and we will locate the records and confirm in writing once they are removed.
We keep this list short on purpose, and we name everything on it.
Our GoodBlocks™ and Challenges load their code and styling from our own servers rather than from third-party content networks, so a learner working through a lesson is not making requests to other companies.
When a teacher creates a Task Force and shares a classroom code, learners who join it appear on that teacher's roster under their pseudonymous display names. A teacher sees only the Task Force they own.
We do not ask a school to provide consent on parents' behalf, and we do not rely on a school having done so, because we do not collect personally identifiable information from learners under 13 in the first place. A teacher or staff member using Allgood Academy with students remains responsible for doing so in line with their school's and district's own policies.
Schools and districts that need a written agreement, a data-processing addendum, or answers for a vendor review should email us — we would rather answer a procurement questionnaire than have you guess from this page.
Access to learner records is restricted at the database level: a teacher can read only their own classroom's roster, administrative access is limited to a named allowlist, and a learner can read only their own progress. We implement industry-standard security measures to protect your data. However, no method of transmission over the Internet is 100% secure, and we cannot guarantee absolute security.
When we change this policy we update the "Last updated" date at the top. That date reflects the last time the words on this page actually changed — it is not generated automatically, so you can use it to tell whether anything is different since you last read it.
If we make a change that materially affects what we collect from learners or how long we keep it, we will say so plainly at the top of this page rather than relying on you to notice.
Questions about this policy, a deletion request, or a district vendor review all go to the same place: learning@allgoodacademy.com. A real person reads it.