Effective 12 August 2026 · Last reviewed 12 August 2026
Applies to mypettopia.org, www.mypettopia.org, mypettopia.web.app and mypettopia.firebaseapp.com — one application on several addresses.
← Back to PetTopiaPetTopia is a browser game that teaches financial literacy and school subjects to preschool and elementary learners. Because our players are children, this policy is written to be checked rather than trusted: everything below was verified against the application's source code on the date above, and the "known gaps" section exists specifically so this document does not quietly overstate our protections.
PetTopia is operated jointly by its co-owners as an independent educational project. It is not owned by, affiliated with, or endorsed by any school, district or publisher. Mail to admin@mypettopia.org reaches the owners directly.
We are the data controller for independent players who sign up on their own. For children enrolled through a class code, we act as a service provider on behalf of the teacher and their school — see section 4.
Described by where the data actually lives, because that is the only description that can be audited.
| What | Why | Notes |
|---|---|---|
| Username | To identify the account | Becomes an internal address like username@pettopia.com. This is not a
real email address, it is never delivered to, and we do not collect email addresses from
children. |
| Password | To sign in | Stored by Google Firebase Authentication as a salted hash. We never see it and cannot recover it. |
Pre-K children use no password. They tap their name on a class list, then tap a sequence of three pictures. That sequence is turned into a password on the child's own device; the pictures themselves are stored where only that child's own teacher can read them (3.5).
Written whenever the game saves: pet name, species and avatar, coins, savings, a spending log (most recent 100 entries), pet care stats, savings goal, difficulty, evolution level, total earned, XP, level, badges, equipped accessory, islands unlocked, cities visited, flights taken, tour progress, play streak, last play day, per-subject mastery, quiz topic statistics, assignment progress, the read-aloud preference, the pre-K flag, the account role, the class code if any, and creation and last-saved timestamps.
All of it is game progress. None of it is a real-world identifier — with one honest exception: a child may type their own real first name as their username or pet name, and nothing stops them. We advise teachers to issue usernames that are not full names, but we cannot enforce what a child types. See section 9.
Created by a teacher: class name, the teacher's username, a roster of pupils (username, the display name the teacher chose — usually a first name — and a muted flag), class settings, teacher-authored quiz sets, teacher-added tutor video links, and assignments.
A simple class chat. Each message stores its text (240 characters maximum), the sender's username and a timestamp. Only members of that class and their teacher can read them. The teacher can read and delete every message in their class — this is intended oversight, not surveillance by stealth, and children should be told about it.
The picture sequence for one child, plus sign-in counters. The most tightly restricted data in the application: no pupil can read it, including the child it belongs to. Only the owning teacher can read it (to print sign-in cards) or write it (to enrol a child or reset their pictures).
Username, pet name, evolution level, total earned, and quiz correct/total counts. The leaderboard is publicly readable. The game displays only the top ten independent players; class members are filtered out and ranked within their class instead. Treat a leaderboard entry as public information.
Never transmitted to us: the signed-in username, the chosen work grade and subject, the sound-muted flag, the read-aloud flag, the pre-K flag, and a "tutorial already seen" flag. Clearing your browser's site data removes all of it. Firebase also stores a session token in the browser so the child stays signed in.
Firebase Hosting and Google Cloud keep standard server logs (IP address, user agent, requested URL, timestamp), as any web server does. We do not analyse these, build profiles from them, or connect them to a player account. They are retained under Google's operational schedule, not ours.
PetTopia is knowingly directed at children under 13, so the US Children's Online Privacy Protection Act applies to us directly. There are two ways an account comes to exist, and the consent basis differs.
When a teacher creates a class and enrols pupils, we rely on the school consent exception recognised by the FTC: the teacher, acting for the school, consents on parents' behalf for the educational use of the service. Our obligations under that exception, which we accept:
A child can also sign up without a class code. If your child is under 13 and signed up independently, we are relying on you, the parent or guardian, having permitted it. We do not currently operate a verifiable parental-consent flow — this is a real gap, stated plainly in section 9 — and in the meantime we deliberately keep independent accounts to the smallest data set the game can run on: a username, a pet name and progress.
A parent may at any time review what we hold about their child, ask us to correct it, ask us to delete it, or refuse further collection, by writing to admin@mypettopia.org. Refusing further collection means the account is closed; we will not retaliate by degrading a child's other access.
| Data | Public | Other players | Their teacher | Us |
|---|---|---|---|---|
| Password / picture sequence | No | No | Pictures only, own class | No |
| Game progress | No | No | Yes, own class | Yes, on request |
| Username, pet name, level | Top 10 independent players | Yes, on the board | Yes | Yes |
| Class name, teacher username, roster display names | Yes — see 3.3 | Yes | Yes | Yes |
| Class messages | No | Class members only | Yes, including delete | Yes, on request |
"Us, on request" means the owners can read the database when investigating a support issue or a safety report. We do not browse it routinely.
We use very few, and none of them are marketing companies.
We use no analytics or advertising service. Firebase Analytics was removed from the code on 12 August 2026, and every Google Analytics and Tag Manager origin was removed from our Content Security Policy at the same time, so one cannot be re-added without that change being visible.
What is in place, honestly scoped:
No system is perfectly secure, and a project this size should not claim otherwise. We are currently conducting a second, wider security review precisely because we judged our first one insufficient. If we ever discover a breach affecting children's data, we will notify affected teachers and parents at the addresses we have, and post a notice here.
To report a vulnerability, write to admin@mypettopia.org. We will not pursue anyone who reports a genuine issue in good faith and does not access other people's data in the process.
Stated deliberately, because a children's privacy policy that hides its own weaknesses is worse than none.
Each of these is tracked as open work, not filed away.
Wherever you live, you may ask us to show you what we hold, correct it, delete it, or stop collecting it. Parents may exercise these on behalf of their child; teachers and schools may exercise them for their pupils. Write to admin@mypettopia.org. We do not require a special form and we do not charge.
UK / EU: our lawful basis is consent (obtained via the school or the parent); data is processed in Google's infrastructure, which may involve transfers outside your country under Google's own safeguards; and you have the right to complain to your national data protection authority.
California: we do not sell or share personal information as those terms are defined by the CCPA/CPRA, and we do not use personal information for cross-context behavioural advertising.
If we change how we handle information in a way that materially affects children — collecting something new, or sharing with someone new — we will ask for consent again rather than rely on a quiet update. Lesser changes will be posted here with a new "last reviewed" date. Material changes will also be sent to the class teachers we can reach.