Privacy

The name your child gives the animal, the world they picked, what has been practised and how long the streak is: all of that lives in the browser’s storage on the device itself. As long as nobody is signed in it is not sent anywhere, we cannot reach it, and it disappears when you clear the site’s data.

A child only signs in if you set that up yourself. You link an address to one child in your dashboard, you can withdraw it with one button, and without that link there is no account for your child. There is no profile picture in any case, and no way to be in contact with other children.

If you want the tablet and the phone to show the same thing, that progress has to pass through somewhere. From the moment you sign in we therefore keep, in one document under your account: per child the name, the colour, the animal, the world, what was practised and how many days in a row. Nothing more is in it, and it belongs to your account. If you give a child their own sign-in, that stays the same: the family is yours, the child may practise and switch between brothers and sisters, and the subscription and the settings stay yours.

You can undo that: signing out puts this device back on local storage only, and on request we delete the stored progress.

If you choose to take a subscription, payment goes through Stripe. Stripe handles the payment details; we never see your card number. What we keep afterwards: your email address, which plan you have, whether it is running, and Stripe’s customer and subscription reference. Nothing more.

If you sign in to manage the subscription, that goes through Google. We receive your email address and a user id, and keep them with the subscription.

A pupil signs in with a class code and their own code, or, if the school switches it on, with their Google school account or through Entree (more on that below). What is kept about a pupil — a name, a colour, an animal and which facts they know — sits with the teacher’s class, and none of it travels to a parent account, not even when that same parent has a subscription at home. When the teacher deletes a pupil or a class, what belongs to them goes with it.

If a teacher makes a worksheet with a QR code, we keep with that worksheet the answers filled in, the result and the name typed with it. If the teacher links the sheet to a class, each child gets their own QR code with a token in it that is not the sign-in code on their card and gives nothing away on its own — only which child a submission on that one worksheet belongs to. That sits with the school, visible to the teacher — not in the child’s profile and not with our administration. The teacher can delete the worksheet with everything attached.

That answer form is one of the two channels through which a child sends us anything themselves. It only works with the worksheet code printed on the sheet, without an account and without signing in; what the child fills in goes only to the teacher who made the sheet, and it changes nothing about what the app knows about the child or has them practise.

The second channel is a Live session: the teacher sets up a game on the whiteboard and every pupil joins in on their own laptop, with their own sums. What is recorded per child is exactly what an ordinary practice session records already — which sums, right or wrong, how long and which items — never more than that. Afterwards there is a lesson report with the class, with the same result the teacher saw on the teacher panel; nothing from a Live session goes to a parent account. During the game the whiteboard shows the first names of the children in the class — visible to whoever is in the room, stored nowhere else, and a teacher can switch them off. The game standing itself (who is ahead, which items someone has) disappears once the game is over; it is never kept on the child. A parent can also start such a game at home, with the family’s own children instead of a class; otherwise exactly the same rules apply — the same recording, the same disappearing standing, and the result stays within the family’s own account.

A school can let pupils sign in with their Google school account, and a teacher can bring their class over from Google Classroom or post an assignment in it. What we then get from Google is this, and nothing more:

• Signing in with Google, as a pupil or a teacher: the name, the email address and the Google ID of whoever signs in.
• Importing a class, only by the teacher and with their permission at that moment: the names of the courses they teach, and for the course they pick, the names and Google IDs of the pupils. We do not ask for their email addresses.
• Posting an assignment in Classroom, only by the teacher: only the assignment we create ourselves, in the course they pick. We do not read other assignments, submissions or grades.

What for. Only to create the class, to let pupils sign in and link them to their place in the class, and to post the assignment the teacher asks for. Nothing else.

What we keep. On our server, with the pupil in the class: the link between their Google ID (and, once they sign in with Google or the teacher enters it, their school address) and their place in the class. With the class: which Classroom course it is. With a worksheet: which assignment we posted in Classroom. A pupil’s email address is not in their profile and never goes to their device. We keep no access tokens from Google: permission for an import holds for that one time, and nothing runs in the background.

What we do not do. We do not sell this data, and do not use it for advertising or to train or improve AI models. We pass it to no one, except where that is needed to run the app or where the law requires it. Nobody at our end reads it, unless you ask us to yourself, for security, or because the law requires it.

Deleting. When the teacher deletes a pupil or a class, the link with Google goes with it. You can also withdraw the app’s access at Google itself, in your Google account.

learnbits.app’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Put plainly: we use what Google gives us for the things listed above, and for nothing else.

A school connected to Kennisnet’s Entree Federation can let pupils and teachers sign in through Entree. We then only get the data the school releases through Entree: usually an encrypted user id, the first name, whether someone is a pupil or staff, and the school. An email address, a surname or the class only if the school releases them to us. We use them only to sign you in and link you to your place in the class, keep that link on our server, and delete it when the teacher deletes the pupil or the class. Here too: no selling, no advertising, no AI training.

If you switch on reminders in the app on your phone, we keep a device token: the address the notification is delivered to. Only if you switch them on, only for you as a parent, and it is deleted as soon as you switch them off. A reminder is a message to you that it is time to practise — never to your child.

Only one kind of notification ever reaches a child’s or a pupil’s device: that an adult has set something up — the teacher a Live game, a quiz or a worksheet, or you as a parent a Live game at home. For that, the device token sits with the class or with your family, never with the child, and nothing is stored with it except which child it is. A child never gets a notification to come and practise.

Nobody. No advertising networks, no trackers, no third-party analytics pixels. After the first visit, the app works without internet too.

You delete the animal and the progress yourself, in the parent dashboard under “Opnieuw beginnen” (start again); a whole child you remove there under “Kinderen” (children). If you want us to delete your subscription details and the stored progress, that can be done once the subscription has stopped.