Privacy, with a clear purpose.

This policy explains how LexKurion Technology, the company behind Sage Owl Academy (“we”, “us”), handles information in the Sage Owl Academy app and on sageowlacademy.com. It applies to everyone who uses the app, including children who learn through a profile that a parent or guardian creates.

1. What we collect and why

• App identifier. When the app first opens, Firebase Authentication creates an anonymous guest identifier. It contains no name or email address. We use it to keep your study data separate from everyone else’s, to apply fair-use limits and to protect the service from abuse.
• Sign-in details. Signing in is optional for learners 13 or older; an adult must sign in before a child’s profile works. If the account holder chooses Sign in with Apple, Sign in with Google or Sign in with Microsoft, we receive the identifier and the email address that provider shares with us (Apple lets you hide your real address). We use them only to sign you in and restore your backup.
• Profiles. For each profile: a first name or nickname, an age group, a learner stage (child, teen or adult), a school year, the language Sage explains in, and app settings. Learners 13 or older may add a birthday (day and month). We use these to pitch lessons at the right level and in the right language.
• Study data. The topics, lessons, answers, chat messages, scores, review schedule and progress created while learning. For learners 13 or older, also a few short notes Sage keeps about the learner’s interests to make the next lessons more personal; Sage keeps no notes about a child. We use this to run the app and schedule reviews. A guest’s studies stay on the device and are not in the cloud. If you sign in, we back up profiles, lessons, progress and the learner’s chat messages so they can be restored on another device.
• Lesson requests. The photo, file, text, dictated words or link a learner gives Sage to create or continue a lesson. These are processed to produce the lesson and are not kept on our servers afterwards, except that a signed-in learner’s chat messages are part of the backup (see section 2).
• Usage counters. Counts of lessons created and AI requests made per app identifier, and simple activity markers such as when the app was last opened. We use them to enforce daily limits, keep costs under control and see whether the service is working.
• Purchase records. If the account holder subscribes, the app store and RevenueCat confirm which plan is active for the anonymous app identifier. We never receive payment-card details.
• Analytics and crash reports. Firebase Analytics records app events, such as which kind of activity was opened or completed, together with technical details like app version, device model, operating system and approximate region. Firebase Crashlytics records technical information when the app crashes. Our events do not contain lesson content, photos or names. We use this to fix problems and improve the app. Analytics and crash reports are off while a child’s profile is open; some automatic events can happen before the app knows which profile is open.
• Content reports. If someone reports a lesson or answer from inside the app, we store the reason given, the learner’s note, the lesson title, mode, stage, locale, platform and app identifier, but not the lesson text. Our team reviews reports in an internal console to make Sage safer.
• Safety records. When Sage’s safety checks stop something, our team sees a record with no words and nothing that identifies the learner: the age group, a category, the task and the date. These records are kept for 90 days.
• Messages to us. If you email us, we receive your email address and whatever you choose to write, and use them only to answer you.

Some things stay on the device and never reach us: the original photos and the family photo album, the daily reminder (scheduled locally by the device, and only if you turn it on), and the microphone audio used for speaking practice, except for the pronunciation measure described below.

Microphone and speech. The app uses the microphone and speech recognition only when a learner taps to speak, for dictation or pronunciation practice. Speech is turned into text by the speech-recognition service built into the device’s operating system (from Apple or Google, under their own privacy terms); we do not receive or store the audio. Sage’s voice is generated by Microsoft Azure from Sage’s own text, and the device’s text-to-speech is used when offline. Neither the text nor the audio is stored by Microsoft, a child’s name is removed first, and no learner audio is involved.

Pronunciation measure. Only on Premium, only for learners 13 or older, and only when the learner taps to record, a short recording goes through our server to Microsoft Azure, which turns it into text and scores the pronunciation. Neither we nor Microsoft store the recording: it is deleted from the device right after. A child’s voice is never recorded or sent.

We do not collect precise location, contacts, advertising identifiers, or information from other apps.

2. How Sage’s AI works

When a learner asks Sage for a lesson, the app sends the request over an encrypted connection to our backend, which runs on Google Cloud and Firebase. The backend checks the request and passes what is needed to our AI provider, Anthropic, whose Claude models write the lesson. The lesson returns to the app and is saved on the device (and in the backup, if the account holder has signed in). Everyone is told about Anthropic and asked to agree before using lessons; for a child, a parent is asked.

• Photos are resized on the device, and metadata such as location is removed, before they are sent. A photo is used only to create that lesson and is not stored on our servers. The original stays on your device.
• Typed text, dictated words, files and links are handled the same way, except that a signed-in learner’s chat messages are part of the backup.
• Together with every request we send the context needed to pitch the lesson: learner stage, school year, country and language. For learners 13 or older, we also send the profile’s first name or nickname (so examples can speak to the learner) and Sage’s short notes about the learner’s interests. For a child’s profile, we never send the name and never send notes; Sage keeps no notes about a child. We never send the learner’s exact age, email addresses or account details. To help detect abuse, each request carries a one-way code derived from the app identifier.
• Anthropic processes this data on our behalf under its commercial terms. Under those terms, data sent through the API is not used to train its models. Anthropic deletes it within 30 days, and may keep content its safety systems flag for longer.
• Requests and answers are checked by an automatic safety review with Claude before anyone sees them. Rules are stricter for children and teens, and any request that doesn’t state an age gets teen rules. Blocked content is replaced by a gentle message.
• If a learner seems in distress, Sage stops and tells them to talk to a trusted adult, and shows a help line and a child protection line in Brazil, the US and the UK.

Sage is instructed to treat photos and text only as material to teach from, never to identify real people in photos and never to infer sensitive traits. Sage can make mistakes. We do not use AI to make decisions about learners that have legal or similarly significant effects.

3. Children and families

Sage Owl Academy is made for families, and some learners are children, including children under 13. We built it so that a parent or guardian stays in control.

• The adult holds the account. Before a child’s profile works, an adult must sign in with their own account, create a 4-digit parents’ PIN, read the consent screen and agree. That adult buys any subscription and can add profiles for other members of the family, including children. Children under 13 do not create accounts, sign in, or give us an email address.
• Parents’ PIN. The PIN is mandatory while a child’s profile exists. It guards purchases, external links, sign-in, deleting data, adding or removing people, and leaving to an older profile. Five wrong tries lock it for one minute, and a forgotten PIN is replaced only by signing in again with that account.
• Minimal information. A child’s profile needs only a first name or nickname, a learner stage, a school year and a language. We do not ask for a child’s full name, birth date, email address, phone number or location. A nickname works just as well. Sage keeps no notes about a child, and a child’s name and exact age are never sent to Anthropic.
• No ads, no tracking, no selling. There is no advertising in the app, no advertising SDK and no use of advertising identifiers. We do not build advertising profiles, track learners across other apps or websites, or sell or rent anyone’s personal information. Analytics and crash reports are off while a child’s profile is open (see section 1).
• Nothing public. There are no public profiles, no chat between users, and no way for strangers to contact a child through the app.
• Lesson content. Sage is instructed to keep lessons suitable for the learner’s stage, and anyone can report a lesson or answer from inside the app. On the family view, a parent sees how many conversations Sage stopped, never the words.

Reviewing and deleting a child’s data. A parent can open a child’s profile on the device to see their topics, lessons and progress, edit the profile, or delete it; deleting a profile also removes its copy from the cloud backup. Deleting the account removes every profile. A parent can also email info@lexkurion.com to ask what we hold about a child, to have it deleted, or to stop further processing; we may ask a few questions to confirm the request comes from the account holder.

Laws such as the US Children’s Online Privacy Protection Act (COPPA) and the child-specific rules of the GDPR, UK GDPR and Brazil’s LGPD give parents particular rights over their children’s information. We aim to meet them by keeping an adult in control of the account, collecting only what lessons need, and using children’s information only to provide the service. If you believe a child has given us information without a parent’s involvement, please contact us and we will delete it. Read more in our guide for parents.

4. Legal bases

Where the GDPR, UK GDPR, Brazil’s LGPD or similar laws apply, we rely on: contract, to provide the app, create lessons, back up progress and manage subscriptions; legitimate interests, to keep the service secure, apply fair-use limits, review reported content, and understand usage and crashes so we can improve the app; consent, for optional permissions such as the microphone and notifications, which you can withdraw at any time in the device settings; and legal obligation, where the law requires us to keep or disclose information. For a child under 13, the basis is the consent of a parent or guardian, in the child’s best interest.

5. Service providers and sharing

We share information only with providers that help us run Sage Owl Academy, only for that purpose, and under terms that limit how they may use it:

• Google (Firebase and Google Cloud). Authentication, Cloud Firestore backup, Cloud Functions (our backend), App Check, Analytics and Crashlytics, and Sign in with Google if you choose it.
• Anthropic. Writing lessons and answers, and checking requests and answers for safety, as described in section 2.
• Microsoft Azure. Turning Sage's text into voice and, on Premium for learners 13 or older, measuring pronunciation from a recording. It stores neither the text nor the audio.
• Microsoft Azure. Turning Sage’s text into voice and, on Premium for learners 13 or older, measuring pronunciation from a recording. It stores neither the text nor the audio.
• RevenueCat. Managing subscription status. It receives the anonymous app identifier and the purchase records from the store, not payment-card data.
• Apple and Google app stores. Processing purchases, subscriptions and refunds, and Sign in with Apple if you choose it. Their own privacy policies apply to what they collect.
• Microsoft. Sign in with Microsoft, if you choose it.
• Website delivery. sageowlacademy.com is hosted by our web host and loads its fonts from Google Fonts, which receive standard technical data such as your IP address when the page loads. The website uses no cookies and no analytics; it only remembers your language choice in your own browser.

We may also disclose information when the law requires it, or to protect the safety of learners or the integrity of the service. We do not sell or rent personal information.

6. International transfers

Our providers may process data in the United States and in other countries outside the one where you live. When data leaves the European Economic Area, the United Kingdom or Brazil, we rely on the safeguards those providers offer, such as the European Commission’s Standard Contractual Clauses and their data-processing terms.

7. Retention and deletion

• On the device: photos, lessons and progress stay until you delete them, delete a profile, erase the app’s data or uninstall the app.
• Cloud backup: kept while the account exists and deleted when the account is deleted.
• Lesson requests: not stored on our servers once the lesson is made, apart from chat messages in a signed-in learner’s backup; see section 2 for Anthropic’s retention of up to 30 days.
• Usage counters and content reports: kept only as long as they are needed for limits, security and review, and deleted when you delete your account.
• Safety records: kept for 90 days.
• Analytics and crash reports: kept by Firebase for a limited period, expire on Firebase’s schedule and are used in aggregate.

To delete your data, open your profile in the app and choose Delete my account (or Erase all my data if you never signed in). On the phone, this removes every profile, the photos, the family album, cached voices and the parents’ PIN. On our servers, it removes the backup, usage counters, plan record, referral record and reports. The sign-in identity is deleted as well, including a guest’s. It cannot be undone. You can also email info@lexkurion.com and we will delete your data for you. Small amounts of information may remain for a short time in backups or security logs before they are overwritten. We keep purchase and cost accounting records, the stores and RevenueCat keep their own purchase records, and the anonymous safety records stay for up to 90 days. An active subscription is managed by Apple or Google and must be cancelled there. See how to delete your account.

8. Security

Data travels over encrypted connections. Backups are stored in Cloud Firestore under rules that let each signed-in identity read only its own data, our AI provider’s key stays on our servers, and App Check helps block requests that do not come from the genuine app. No system is perfectly secure, but we work to protect your information and to limit who can access it.

9. Your rights

Depending on where you live, you may have the right to access, correct, download, delete or restrict the use of your personal information, to object to processing based on legitimate interests, and to withdraw consent. Much of this can be done in the app itself. For anything else, email info@lexkurion.com; we may need to confirm that a request comes from the account holder. You may also complain to your local data-protection authority.

10. Changes to this policy

If we change how we handle information, we will update this page and the date at the top. If a change is significant, especially for children’s information, we will tell you in the app before it takes effect and, where the law requires it, ask for consent again.

11. Contact

LexKurion Technology is responsible for the information described in this policy. For any privacy question or request, write to our company mailbox, info@lexkurion.com.

Need a hand?

Write to us and a real person will answer.

info@lexkurion.com