← Kidecuate

Privacy Policy

Last updated: 2-sep-2026 · Effective: 2-sep-2026

Kidecuate is a learning app for children aged 5–12. This policy explains exactly what the app collects, why, where it goes, and how to get it deleted.

1. Who we are

Kidecuate ("we", "the app") is operated by Kidecuate-Lebanon, an independent app developer based in Lebanon. For any privacy question or request, contact omaimathabet56@gmail.com.

2. What the app collects

Information you give us

DataWhenWhy
First name or nickname During onboarding To greet the child by name in the app
Chosen buddy character and language During onboarding Personalising the interface
Google account: email address, name, profile picture Only if you sign in with Google To identify your account so lessons sync across devices
Lesson material: photos of pages you upload, and text you type Each time you create a lesson To generate reading, dictation, memory and game activities

Information created as you use the app

DataWhy
Generated lessons, exercises and games Saved to your library so you can return to them
Activity scores and progress (reading accuracy, dictation, games) To show progress and award stars
Voice audio while a reading or dictation exercise is running — processed on the device and never transmitted or stored To check whether words were read or spoken correctly
What we deliberately do not collect No advertising identifiers. No location. No contacts. No third-party analytics or advertising SDKs. There are no ads in the app, and we do not sell personal information or share it for behavioural advertising.

3. How voice recording works

The microphone is used only while a reading, dictation, memory or classroom exercise is actively running, and only after you grant microphone permission. The app does not record in the background.

Your child's voice never leaves the device Speech is recognised entirely on the phone or tablet. We never store voice recordings, and we never transmit them — not to us, and not to anyone else.

How that is achieved depends on the language and device:

Only the recognised text is compared against the lesson, in memory, and then discarded.

4. How photos of lesson pages are handled

When you photograph a page, the app reads the text on your device, using two built-in recognisers — one for Latin script, one for Arabic. For a legible page, no copy of the image is sent to an AI provider to be read.

Only if both on-device recognisers fail to read the page is the image itself sent to our AI provider to extract the text.

Separately, the photo is uploaded to our storage so it can appear as the lesson's thumbnail in your library. Stored images are kept in a private bucket, readable only through short-lived links issued to your own signed-in account, and are deleted when you delete the lesson or your account.

5. AI processing

Lesson text (and, in the fallback case above, the page image) is sent to these providers to generate the activities:

ProviderPurposePolicy
Groq, Inc. Turning lesson text into exercises, hints and games groq.com/privacy-policy
NVIDIA Corporation Same, and reading text from images when on-device OCR fails nvidia.com privacy policy

We do not attach your child's name, email address or account identifier to these requests — the providers receive the lesson content and nothing that identifies who sent it.

Please note that the lesson content is whatever is on the page. If a child's name, their school, or their handwriting appears on the sheet you photograph, and that page has to be sent because it could not be read on the device, then that information is part of what is sent. If you would rather it were not, cover or crop it before taking the photo, or type the lesson text in instead.

6. Where data is stored

Accounts, lessons, progress and uploaded images are stored with Supabase, our database and storage provider (supabase.com/privacy), on servers located in South Korea. Row-level security means each account can only ever read its own rows.

Your name, chosen buddy, and language preference are also kept locally on your device so the app works offline.

7. Playing without an account

You can use Kidecuate without signing in. The app then creates an anonymous account that exists only on that device. It holds no email address and no name unless you type one. If you later sign in with Google, lessons saved anonymously stay tied to the anonymous account unless you tell us otherwise.

8. How long we keep things

Deleting a lesson in the app removes both the database row and the stored image.

9. Children's privacy

Kidecuate is designed for children and intended to be set up by a parent, guardian or teacher. We ask only for a first name or nickname — we do not ask a child for a surname, address, phone number, school, or date of birth.

Google sign-in is optional, and is intended for the adult setting the app up. If you believe a child has provided us personal information without the consent of a parent or guardian, email omaimathabet56@gmail.com and we will delete it.

10. Your rights

You can request access to, correction of, export of, or deletion of your data at any time. Depending on where you live you may also have the right to object to or restrict processing, and to complain to your data protection authority.

Delete your account →

11. Security

Traffic is encrypted in transit with TLS. Stored lesson images sit in a private bucket reachable only through expiring signed links tied to your account. Database access is constrained per-account by row-level security. No system is perfectly secure, but we will notify affected users of any breach as required by law.

12. Changes

If this policy changes materially we will update the date at the top and notify you in the app before the change takes effect.

13. Contact

Kidecuate-Lebanon — independent app developer
Lebanon
omaimathabet56@gmail.com