Privacy Policy

The Atfaly Amazing app (أطفالي Amazing), made by Asfar Games.

What information do we collect?

Teacher account: an email address, and a password kept only as a hash, or Google sign-in. No name is kept for a teacher.
Guardian account: name and email address, a phone number if one is given, and a password kept only as a hash, or Google sign-in. A guardian is linked to their child by a code the child makes in the app, or by the class code together with the child's PIN.
The grown-up check: before a parent's or a teacher's account is made, the app asks for that adult's date of birth, to check that an adult is setting it up. The check happens on the phone. The year is never sent to us and never stored. From that date we keep the day and the month only, with the parent's account, so the app can wish them a happy birthday. A parent can change it in the settings.
A child's profile made by a parent: a first name, an age group (3-5, 6-8 or 9-12), and a picture chosen from the app's own set of drawn faces. No email address, no password, no surname and no photo of the child. If the parent wishes, the child's birthday as a day and a month - never the year - so the app can greet the child on the day. The parent can remove it at any time.
What the child likes: if the parent wishes, what the child likes (games, stories, videos, worksheets) and the subjects the parent wants for them, chosen from a short fixed list. We use it to choose what the child's home shows first. It is the parent who states it; the app does not work it out from the child's behaviour.
Codes: a parent can make a short code that opens their child's profile on another device, or invites a second parent. A code works once and runs out after a short time. A child can have at most two parents, and a parent at most four children.
The parent's agreement: when a parent makes or links a child's profile we record that the parent agreed, when, and which version of this notice they were shown.
A student's profile in a class: the name the teacher types, the class, and a 4-digit PIN kept only as a hash — no email address and no password. A child in a class may choose one of the app's drawn faces. We store which face it is, on the child's line in the class list.
A child's own account, where one was made in the past: an email address and a name, and a password kept only as a hash, or Google sign-in. The app no longer offers to make one.
A chosen picture: a parent or a teacher may choose one of the app's drawn faces for their own account. We store which face it is. The class sees the teacher's.
Usage data: attendance, points and their reason, assignments and what is handed in, comments, badges, the child's progress in games and the words they have learned, sign-in times, the streak of days and time spent learning.
Reports and hidden comments: anyone in a class can report a comment, a class news post or a piece of homework, and can hide another person's comments from their own screen. A report keeps who reported, the reported words (and the address of its picture, if it has one), the reason chosen, and a short note if an adult writes one. The class's teacher sees the reports about children's comments, without the name of who reported; our team sees every report. A teacher can pause a child's commenting in the class, and we keep that setting.
Pictures: the pictures uploaded to class news, events and assignments. A picture is prepared on the phone before it is uploaded, which makes it smaller and drops its hidden details, such as where it was taken.
Voice: in the Quran recitation lessons the app listens to the child reading through the microphone, after asking for permission. The voice is understood on the phone itself; where the phone cannot do that, a short clip (under half a minute) is sent to Cloudflare's speech-recognition service, turned into text and dropped. We keep neither the sound nor the text — only the number of seconds each account used each day.
Notifications: the messages sent to an account, such as 'a new star' with the child's name. A child playing on a family's phone is never asked to allow notifications, and no notification address is made for the child's session. Notifications are asked for in the parent's area.
Limited technical data, to improve the app and find faults: the event's name, the user's role and school grade, the app and Android versions, a memory size band, the connection type, and a session number made new each time the app opens — no name, no email address and no account number. The country is kept with these statistics too: Cloudflare works it out from the connection. It is an approximate location only — never a city and never a precise place — and the app asks for no location permission.
To guard against repeated attempts, a few things are counted for a short time. Per network (IP) address: sign-in and PIN attempts, sign-ups, class-code lookups, tries at a child's code, requests to send the confirmation email again, messages from this website's contact form, and the statistics signals the app and this website send. Sign-in attempts are also counted per email address, PIN tries per name in its class, confirmation-email requests per account and per email address, picture uploads per teacher or class, and the linking of a guardian to a child per account. No count is kept for more than about two hours, and we store the network address nowhere else.
This website: it sends a signal when a page opens (saying which page), every 20 seconds while it is in view, when it is hidden or closed, and when a game's demo is opened or finishes (saying which game), with a random number for the browser tab and the country — no name, no cookies and no outside analytics service. The contact form sends the name, the email address, whether the sender is a teacher, a parent or a school, and the message to our team's inbox; it is not kept in our database. Each signal and each message is also counted per network address, as described above.

Children's privacy

A child who joins a class is never asked for an email address, a phone number or any contact detail: they sign in with the class code, their name and a 4-digit PIN. Nobody is asked for a photo of themselves or for their location. A child is never asked for a year of birth.

A child's activity is seen by their teacher and their linked guardian. Classmates see the names on the class list — which show to anyone who types the class code, so the code is for the class's families only — and the comments on assignments and class events, with the writer's name.

The app carries no adverts, and we never use children's data for advertising.

How we use this information

We use it to run classroom features — attendance, points, activities, and communication between teacher and parents — and to improve the app's quality and reliability. We do not sell user data to any third party.

To help schools and keep the service running, our team's dashboard shows email addresses, names, guardians' phone numbers, class lists, activity counts and the titles of assignments and events; it does not show the text of class news, comments or what a child hands in. The one exception is something that has been reported: its words are shown to our team so the report can be answered.

Where data is stored

Your data is stored on Cloudflare's infrastructure (databases and cloud storage), and connections to it are encrypted in transit (HTTPS). Passwords, PINs and sign-in tokens are never kept as they are, only as one-way hashes.

Sharing data with other parties

We rely on a small number of technical services, which receive your data only as far as running the service requires:

Cloudflare: hosting, databases, picture storage and statistics; its speech-recognition service (Workers AI), which receives the recitation clip when the phone cannot understand it itself; and the contact form's mail.
Google: Google Sign-In for those who choose it, and the app's notifications through Firebase Cloud Messaging, which a notification's words pass through and which holds the device token needed to deliver it. The school books shown on this website open from Google Drive.
Resend: sending the email-confirmation and account-deletion messages.

Nothing is paid for inside the app today, so there is no payment provider.

Your rights

A guardian and a teacher see the child's data linked to their account inside the app, and may ask to see it, or for it to be corrected or deleted, by contacting us. An account can also be deleted from inside the app itself, as the next section explains.

Data retention and deletion

The app's settings have a 'delete account permanently' button for teachers, guardians and children with an account of their own. The deletion is confirmed by a link sent to the account's email address, valid for half an hour; the account then goes, with what is tied to it: sessions, progress, words, points, badges, assignments, attendance, comments, reports, links and pictures. Deleting a teacher's account also deletes their classes and the children enrolled in them.
A child in a class has no email address, so their teacher removes them from the class list, and the same things go with them.
A parent can delete a child's profile from the child's page in the parents' area; the child's progress, words, badges and codes go with it. Deleting a parent's account also deletes every child profile that has no other parent.
A teacher can remove any comment on an assignment in their class, and a child their own.
Class and assignment pictures are deleted automatically a year after they are uploaded.
A child stays signed in for 30 days from last use, a teacher for 24 hours, and a guardian for one day from last use; signing out ends it at once.
If you no longer have the app, you can ask for your account and its data to be deleted at atfaly-amazing.com/en/delete-account/. The same page says how to ask for part of the data to be deleted while the account stays. We delete within 30 days of confirming the request.

Changes to this policy

We may update this policy from time to time; any change will appear here along with an updated date.

Contact us

Atfaly Amazing is made by Asfar Games. For any question about privacy, write to [email protected], or use the phone number at the bottom of the page.

Last updated: 13 October 2026.