Privacy Policy
Last updated November 18, 2026
Summary
Amalgam never stores a child’s real name. Children appear only as animal nicknames, and the list of which child is which stays on the teacher’s own device. Districts and publishers see results only as totals, and never for a group of fewer than 10 children. Publishers own the content they send us, and we use it only to build their units. We keep each district’s results for as long as its agreement is active, so schools can see growth from year to year, and delete them when the agreement ends or on request.
Children’s information
What we collect, by nickname only:
- The teacher’s one-tap marks during a lesson (right without help, or needed help)
- How long each activity took
- Check-in scores out of 7, with the date
- The unit the child is working on
What we never collect: real names, photos, voice recordings, handwriting, typed text, location, or any third-party tracking or advertising data. Children never create an account or sign in. Amalgam has no microphone access anywhere.
The name key: a teacher can type a child’s name next to their animal nickname so they know who is who. That list is saved only in the teacher’s browser on their own device and is never sent to Amalgam. Our database rules accept only nicknames from a fixed list of colors and animals, so a real name cannot be saved even by mistake.
Unfinished work on a child’s screen (for example, blocks a child moved) stays on that device and is never sent to Amalgam.
Who can see what
| Who | What they can see |
|---|---|
| Teacher | Their own classes, child by child, by nickname |
| District | Totals for their own schools and classes. No children, no nicknames. Groups under 10 children are hidden. |
| Publisher | Totals across their own program and how much it is used. No school or class names. Groups under 10 children are hidden. |
| Amalgam’s team | Everything above, by nickname, to support teachers and improve content. Never real names. |
District and publisher totals are calculated on Amalgam’s servers, and groups under 10 children are removed there, before anything reaches a district or publisher. They cannot read class-level or child-level records.
How long we keep it
- Child-level results (by nickname) are kept while the district’s or school’s agreement is active, so teachers and districts can see growth across units and school years. After an agreement ends they are kept, unless the publisher has chosen deletion; then they are deleted within 60 days after the agreement ends. A district can also ask us to delete them sooner.
- Totals (no children or nicknames, groups of 10 or more) may be kept after an agreement ends, to measure the program’s growth over time.
- A district can ask for an export of its data at any time.
Teachers can archive a class: it is hidden from their menu, and its data is kept and still counted. Only Amalgam deletes class data, when a district or school asks, or to clear out test classes. Teachers can delete only their own practice classes, which are never counted anywhere.
Publisher content
- Publishers own their content: scope and sequence, word lists, book titles, artwork, logos and comments.
- We use it only to build and review that publisher’s units. It is never shown to another publisher.
- Scope and sequence: the original Google Sheet stays in the publisher’s Drive. Amalgam reads it, read-only, through its own Google service account, and saves a snapshot of what it read (the units, letters and words, the sheet link, and who confirmed it and when). The publisher can stop sharing at any time. Amalgam staff see the original sheet only if the publisher shares it with them directly.
- Snapshots and uploads are kept for the length of the agreement and after it ends, unless the publisher has chosen deletion; then they are deleted within 90 days after the agreement ends. A renewal stops it. Released Binders are kept as the certified record of each unit.
- The publisher decides. Deletion after an agreement ends is off unless the publisher turns it on, in its Portal under Access. A publisher can also ask Amalgam to delete its program’s data at any time.
AI tools
Amalgam uses AI tools to help build and check units. Publisher content and children’s results are never used to train AI models. Children’s results are never sent to an AI tool with anything that could identify a child.
Sign-in and accounts
- Adults sign in with an emailed link, or with their Google or Microsoft account. Amalgam never stores passwords.
- District contacts can limit school codes to their own staff email domains, and set a seat limit per school. A district or publisher can turn off a school code at once.
- When a publisher’s access ends, their Portal becomes read-only until renewal. Nothing is deleted at that moment.
Where it is stored
Amalgam runs on Google Cloud (Firebase). Data is stored in Google’s Firestore database in the United States, with access controlled by database rules that are tested on every change. The production project has daily backups. Separate projects are used for testing and for real schools, and test data is never mixed with real data.
Test, practice and pilot classes
Every class has a type, set by the link a teacher joins with: Pilot, Test or Classroom. A teacher can also add their own Practice class.
Test classes are for Amalgam’s own network: founders’ families, trusted community members, education professionals and key contacts. Their lessons are stored the same way as any class, by nickname only, and are never included in pilot results or in any district’s or publisher’s reports.
Practice classes are never counted anywhere.
Before families outside Amalgam’s network join a pilot, each family receives a short, plain explanation of what is collected and gives consent.
Contact
Questions about privacy, or a request to see, export or delete data: privacy@amalgamliteracy.com.