The App, the Server, and Where a Child's Work Lives
Where a child's work goes
A child taps an answer on a tablet. Where does that answer go, who can see it, and what happens when the Wi-Fi drops? This article answers them as of November 2026: who uses the app, what the server does, how a school day works without a connection, and the three data modes a family or school chooses between. It is written for parents, educators, funders, and anyone who might help build it.
The Shape of Fido's Software names the parts of the software. The Mastery Engine explains the record of what a child does and what the engine decides from it. This article builds on both and does not repeat them.
Privacy is at its center. We state what is stored and where, exactly as the software does it today, and promise nothing it does not do. As in the whole series, we say what runs today, what is planned, and what is still undecided.
One App for Five Kinds of Users
Fido has one app. Who signs in decides which part of it opens.
- Children practice, read, and follow the map of their course. They see their own progress, never a classmate's.
- Guides, the adults who teach at Fido, see their class, create the children's accounts, set up shared tablets for sign-in, and can set a child's starting point in a subject.
- Parents use the app at home. For children who are just learning to read, it has a mode in which a parent sits with the child and leads a short lesson.
- The school office manages accounts, rooms, and timetables, and sees how much the software is used.
- Contributors, the teachers and authors who help write the curriculum, propose changes and send feedback from inside the app.
The same app runs on Android tablets and in a web browser, so a child can use a school tablet in the morning and a family laptop at home.
The server, not the app, decides who may see what. On every request it checks who is signed in and what that person's role allows.
What the Server Does, and What It Leaves to the Tablet
The server is a program that runs on Fido's side, not on the tablet. It has four jobs.
-
It keeps each child's record: the account, and the
event log of everything the child has done. - It handles sign-in for children and adults.
- It works out what guides and the school office see, from that same record and with the same engine code the tablet runs.
- It delivers new curriculum content to the app.
What the server does not do matters just as much. It does not choose a child's next exercise; the tablet does that itself. And it does not have to be reachable while a child practices. The app carries the curriculum and the engine with it, so even a tablet that has never been online can open its first lesson. When the server has newer content, the app fetches only the parts that changed, and never in the middle of a child's practice.
This division has a price. A guide sees a child's answers only once the tablet has sent them, so a tablet that stays offline all morning leaves that child's row in the guide's view behind.
The record does not lock a school in. An administrator can export a child's record as one file: the account details, every entry of practice, and the notes guides have made.
A Morning Without Wi-Fi
Picture a school morning. Halfway through practice, the Wi-Fi drops. On the child's screen nothing changes. The next exercise appears, the answer is checked, and the topic moves on, because all of that happens on the tablet. That is what we mean by offline first.
Every answer is written to the tablet's own storage first, each time,
whether or not there is a connection. It becomes an entry in the
child's
Sending can go wrong halfway: the connection breaks before the server confirms, and the tablet sends the same answers again. So each answer gets a label of its own the moment it is recorded. The server keeps the first copy of each label and ignores any later one. Sending twice never counts an answer twice, and trying again never loses one.
The record also travels the other way. When a child signs in on a second device, such as a laptop at home, the app fetches the entries it has not seen and works out the same progress from them. A starting point a guide set for the child arrives the same way.
A shared tablet must not show one child's work to the next. When a child signs out, the app first sends their waiting entries, then removes their data from the tablet. Entries that could not be sent wait under that child's own name and never join another child's record. A school's course can also be set to sign a child out after a while without use, so a laptop closed at lunchtime does not greet the next child with the last one's work.
Three Modes: Demonstration, This Device Only, Signed In
Every device runs in one of three data modes. The mode decides where a child's work is kept and whether it ever leaves the device.
Demonstration. A world of made-up children, guides, and a school, already partway through their practice. It lets a parent, teacher, or funder try the app without an account, including the guide's view. The demonstration runs inside the app, apart from any real data, and nothing from it reaches the real server. A banner on every screen says DEMO. Leaving it restores the device's earlier mode and settings.
This device only. A child can practice, read, and follow their course, and the app sends no name, no answer, and no progress anywhere; the one report that still leaves is a crash report, described below. This local mode exists for classes whose parents have not consented to storing data elsewhere. The device fetches only what is the same for everyone, such as new curriculum content, and only when someone asks for it. Usage statistics and feedback are off. Answers that AI judges are judged on the device itself, or, where it cannot, not at all. A lock badge on every screen shows the mode. The price: no guide can follow the child's progress, and the record lives on that one device.
Signed in. The child signs in, and their answers go to the server, where the guides of their school can see them. This mode exists for a school that wants progress shared between tablet, guide, and home. Here the app also reports how it is used, such as which pages open, so that we can find what is slow or confusing. And an answer that AI judges goes, unless the on-device check is chosen, through the server to an outside AI service.
A new device starts in the local mode, and none of a child's work leaves it until a person acts. A school's own link puts its tablets into the signed-in mode. Material shared as a plain link, such as this article, keeps a device local. Starting a sign-in is the choice to go online.
Practice recorded in the local mode is never uploaded silently. A switch in the settings asks first, and keeping that practice on the device is the default answer. A link or a sign-in keeps it on the device without asking. The one exception is an invitation link a guide sends to a child: redeeming it moves the practice on that device into the child's new account, and the app says so.
In every mode: crash reports. When the Android app runs into an error it did not expect, it sends a crash report to an outside service, in the local mode too. We collect them because a fault often shows up first on a tablet a child is using, and a report is how we learn of it and find its cause. A report holds the error, where in the code it happened, and the device's model and system version. It names no account and carries no record of practice. Its error text, though, can quote what the app was handling at that moment, which in rare cases may be a name or an answer. The web version sends no crash reports.
What Is Stored, and How Children Sign In
In the signed-in mode, the server keeps a child's account: a name, the role, and the school. It keeps the record of practice: which exercise, which answer, right or wrong, and when. It keeps the notes a guide records. And it keeps a log of sign-ins, with the kind of device and the network address each came from, to keep accounts secure. The database that holds all of this is in the EU. The guides of the child's school can see the child's record, and so can Fido's administrators.
Some things we never collect: no camera that watches attention, no location tracking, and no typing rhythm turned into a "focus score".
How children sign in. Children never need an email address. On a shared school tablet, a guide first sets the tablet up for the class. A child then taps their own name and types a short PIN, which works only on a tablet a guide has set up. At home, a child signs in with a name and a password. The guide either sets the password or sends a one-time link with which the child chooses one. A guide can give children made-up sign-in names, such as an animal and a number, so that the server need not hold a child's real name. A forgotten password is reset by the guide. There is no reset by email, because the account has no email address.
How adults sign in. Guides and other adults sign in with an account they already have elsewhere, so Fido keeps no password of theirs.
What is not settled. A guide can close a child's account, which ends every way of signing in to it at once. The record of practice stays on the server. How long it is kept after that, and when it is deleted for good, is still to be decided.
Speed, Running It Yourself, and What Is Planned
Speed is a commitment. On a school tablet, a frozen screen looks the same as a broken one. So the app is held to stated limits. A tap must get a visible response within a tenth of a second. A screen a child opens must show content within a second, not a spinner. Any freeze longer than half a second, even on our own fast computers, goes on a list with someone's name against it. Automatic checks stop the app's start from growing slower without anyone noticing. Not every screen meets these limits yet; the slow ones are on that list.
A school can run it itself. A setup exists that runs the app and the server on one machine a school operates, so that everything stays in the school's hands. Our automatic checks test its configuration. No school uses it yet; today's pilots use the server Fido runs. The public website and the curriculum explorer are not part of it.
What is still to come. A parent's view of their child's progress at school exists only in the demonstration, with sample data. The rule for deleting a closed account's record is undecided.
Two more articles on the software follow: How We Know It Works and How a Small Team Builds Fido's Software with AI.
Questions, objections, or keen to help build it? Write to us.