Privacy policy

Last updated 18 September 2026

This policy covers the Learning Breaks app for Android, the Learning Breaks SDK that games use, the developer portal, and this website. It says what we collect, why, who else handles it, how long we keep it and how to delete it. We have tried to write it so a busy parent can read it in one sitting.

1. Who we are

Learning Breaks is made and run by Eynon Software, LLC, an Ohio limited liability company ("we", "us"). We are the operator responsible for the information described here, including information about children. You can contact us about this policy, or about a child's information, at:

For help using Learning Breaks, you can also write to support@learningbreaks.com.

2. The short version

• Children never have accounts, and we never ask for a child's name, age or contact details.
• A child's answers are checked on the phone. What a child types or says is never sent to us, and never to a game. If a child joins a teacher's class, only results (which words and sums they practised and mastered) go to that teacher, under a made-up seat name.
• Worksheet photos are read to make practice and are not kept.
• No third-party ads in the Learning Breaks app, and we do not sell or rent anyone's information.
• You can delete what we hold at any time, from the app or as described on our delete my data page.

3. Children

Learning Breaks is used by children, and set up by their parents, carers and teachers. It is designed so that we never need to know who a child is.

• Children never create an account, sign in, or type an email address.
• A child's profile (the name they are called in the app), their practice lists, answers and progress stay on the phone. The one exception is class results, below.
• Only a grown-up can photograph a worksheet or ask for example sentences to be written (see section 5).
• If a child's phone joins a teacher's class, the child has a seat in that class with a made-up name that our server chooses, such as "Blue Otter". Teachers cannot type a child's name, or anything else about a child, into Learning Breaks: the teacher keeps the list of which child has which seat, on paper, in the classroom. The seat name is the only thing about a child our server holds, and it belongs to the teacher's class.
• A child's answers are checked on the phone, and what a child types or says is never sent to us. If a child joins a teacher's class, only results (which words and sums they practised and mastered) go to that teacher, under the seat name.

If you believe we hold something that identifies a child and should not, write to teynon@eynon.software and we will delete it.

4. What stays on the phone

These are stored only on the phone the app is installed on, and are deleted when the app is removed:

• children's profiles and the names used for them in the app;
• spelling lists, maths practice and imported homework;
• every answer, whether it was right, and progress over time (a phone in a teacher's class shares only results with the teacher, as described in section 3);
• the grown-ups' settings, including daily limits for reward breaks;
• the break activity log: which games asked for a break, and why a break did or didn't happen.

5. What reaches our server, and why

Checking a game, and break records

When a game asks for a break, the app asks our server whether that game is registered and allowed to give one. That check carries the game's publisher id and nothing about the phone or the child.

Break records are a feature that is not switched on yet: today the app does not send them, and nothing about how a break went reaches our server. When this feature is on, the app will ask our server to confirm each break before it is shown and report how it ended, so that game developers can be paid for breaks. For this the app sends a random id created when it was installed. We store that id only in a scrambled (hashed) form. With it we keep:

• which registered game asked, the name the game gave that pause (such as "between-rounds"), whether it was an ordinary or a reward break, and when;
• how the break ended (finished, ended by the time limit, or didn't really happen), how many questions it had and how long it took.

We use this to stop abuse and to work out what each game has earned. It contains no questions, answers, subjects or anything about the child. The app also tells us when it refuses a break because a game isn't registered properly (the game's package name, its signing certificate and the reason), so the game's developer can fix it.

Reports about a game

If you report a game from the app, we receive the game, the reason you chose, anything you typed in the optional details box (up to 500 characters), and a hashed form of the install id so one phone cannot report the same thing twice. Only we read the details you type; the game's developer never sees them or who sent them.

A grown-up account, if you create one

Some features need a grown-up to sign in, such as classes and reading worksheet photos. Sign-in is handled by Google Firebase Authentication, which holds your email address and sign-in details. Our server keeps only the account's Firebase user id, to know which classes are yours.

Classes, for teachers

A teacher (or a parent acting as one) can create a class, with or without a grown-up account. For a class we store its name, the word lists published to it (the words and any definitions), a seat for each child, the codes used to join, and a random access token for each phone that has joined. A classroom key, if used, is stored only in hashed form.

A teacher adds seats, not children. There is no box for a child's name: our server gives each seat a made-up name, an adjective and an animal such as "Blue Otter", different from every other seat in that class. The teacher writes the seat name next to the child's name on the slip that lets the child's phone join, and when the phone joins it shows the child which seat is theirs. Which child has which seat is known only to the teacher; we never learn it.

A phone that joins a class downloads the class's word lists. What the child types or says, and whether each answer was right, is never sent back. Sending results to a class is still being built; when it is on, only results (which words and sums were practised and mastered) will go to the teacher, under the seat name.

Worksheet photos and example sentences

When a grown-up photographs a worksheet, the photo is sent through our server to Anthropic's AI service, which reads it and returns the questions so the app can turn them into practice. When a grown-up asks for example sentences for a spelling list, the words are sent the same way. We do not store the photo, the words or the result: they pass through our server and are not written down. Anthropic processes them as our service provider (see section 9). The photo is taken by a grown-up, never by a child.

What we use it for, and our legal basis

We use this information only to run Learning Breaks: to give and count breaks, pay game developers, run classes, read worksheets, review reports about games, prevent abuse, and answer you when you write to us. We do not use it for advertising, and we do not sell it. Where the law asks for a legal basis, it is that the processing is needed to provide the service you asked for, or our legitimate interest in keeping it working, fair and safe.

6. What games receive

A game that uses Learning Breaks learns only whether a break happened (finished, ended by the time limit, or didn't really happen) and an opaque token that means nothing to it. It never receives the questions, the answers, whether they were right, the subject, how long the break took, or anything about the child. Breaks open in the Learning Breaks app's own screen, so that material never enters the game. The SDK inside the game makes no network calls of its own.

Games are made by other companies, and each has its own privacy policy. Learning Breaks does not control what a game itself collects. If a game asks your child for personal information, please report it from the app.

7. Game developers' information

If you use the developer portal, we hold:

• your email address, when it was verified and when you last signed in;
• your passkeys (public keys only; the private key never leaves your device), and your recovery codes and emailed sign-in links in hashed form;
• while you are signed in, a session record with your IP address and browser's user agent;
• your organisation, its members and their roles, and invitations you send (including the invited email address);
• for a publisher: the legal name, country, postal address, support email, privacy policy address and website domain you give us, who accepted the publisher agreement and when, and our review decisions;
• your apps: package names, signing certificates, store listings and icons, break statements, and our moderation decisions and the messages exchanged about them.

A publisher who is paid must be identifiable, which is why we hold these. When payments start, identity and tax details will be collected and held by our payment provider, Stripe, and this policy will be updated first.

8. This website and cookies

The public pages of this website (the home page, the pages for developers, this policy, the terms and the delete my data page) set no cookies, start no session, and load nothing from other companies: no analytics, no fonts, no trackers. The developer portal uses one cookie, which keeps you signed in and protects forms from forgery; it is strictly necessary for the portal to work.

Like any web server, ours briefly records the IP address and time of requests, for security and to limit abuse. IP addresses used for rate limits are kept only in hashed form and only for as long as the limit lasts.

9. Who else handles data

We use a small number of service providers, who handle data only on our instructions:

We do not share information with advertisers or data brokers. We may disclose information if the law requires it, or to protect children, our users or the service from harm.

10. How long we keep it

• Worksheet photos and sentence requests: not kept at all.
• Break records: until you ask us to forget the phone, or delete the app's data with us. After that, records from months already closed are kept for developers' statements, moved to a new random id with nothing linking them to your phone or to each other.
• Reports about games: until the phone is forgotten; our decisions about a game are kept without the report that led to them.
• Classes: until the teacher deletes them, or deletes their account.
• Developer accounts: until the developer deletes their account. Break statements and the apps they belong to are then kept without the developer's name, email or domain, because payments must still add up.
• Portal sessions and sign-in links: a session ends when you sign out or it expires; a sign-in link works once, for a few minutes.

11. Deleting your data, and your rights

You can delete what we hold from inside the app (Grown-ups, then Your data) or by writing to us. Our delete my data page explains each way, and what is kept afterwards and why. Removing the app deletes everything stored on the phone.

Depending on where you live, you may also have the right to ask what we hold about you, to correct it, to object to how we use it, or to complain to a data protection authority. Write to teynon@eynon.software and we will answer. Because we deliberately hold so little, we may not be able to find information about a child at all; that is by design.

12. Security

Connections to our server are encrypted. Secrets such as classroom keys, recovery codes and sign-in links are stored only as hashes, and the developer portal uses passkeys rather than passwords. Access to our systems is limited to the people who run Learning Breaks. No system is perfectly secure, and if something goes wrong that affects you, we will tell you.

13. Changes, and contact

If we change what we collect or how we use it, we will update this page and the date at the top before the change takes effect. Questions about this policy, or about a child's information, go to us at the address in section 1, or by email to teynon@eynon.software.