Three Modes: Demonstration, This Device Only, Signed In
Three Modes: Demonstration, This Device Only, Signed In
Every device runs in one of three data modes: a demonstration world of made-up children that never reaches the real server, a local mode in which no name, answer or progress leaves the device, and the signed-in mode in which answers reach the server and the child's guides. Why each exists, who chooses, and what follows for privacy.
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.