Privacy policy
Effective date: 4 October 2026
This Privacy Policy explains how the LuMaths Android app (“LuMaths” or the “App”), a family maths-learning app for children, handles information. It applies to the App distributed through Google Play. It does not cover this website.
1. Information used in the App
LuMaths does not require a child account and does not ask for a child’s real name, date of birth, voice recording, precise location, contacts, camera images or photos. A parent or user may create a local learner profile and choose a nickname or learning level. The App also uses learning information such as answers, skills attempted, progress, practice summaries, settings and collected forest friends to provide the learning experience.
These learning records are stored in the App’s local database on the device. Lucius Studio does not currently operate a LuMaths account or cloud-sync service, and these learning records are not automatically uploaded to Lucius Studio or shared with the advertising SDK.
2. Storage, retention and deletion
Learning information remains on the device until it is deleted in the App or the App’s data is removed. Completed practice-session summaries are automatically retained for up to 90 days. Deleting a learner profile removes its associated progress, summaries and collection data from the App’s local database. Uninstalling the App normally removes its local data, but Android device or Google backup settings may affect what is retained in a system backup. Lucius Studio does not receive or control such device backups.
3. Parent-initiated learning summary export
A parent can choose to export a learning summary as a JSON file using the App’s parent area and the Android sharing interface. The exported summary contains learning totals, skills and recent session summaries. It is designed not to include the learner nickname, profile ID or question-by-question answers. Once shared, the selected recipient or app handles the file under its own privacy practices.
4. Advertising and consent
The free Android version may request and display a clearly labelled banner ad in a reserved area of a practice screen. The App is configured to treat requests as child-directed and to request non-personalised ads; an ad is requested only when the applicable consent and SDK checks allow it. The App currently does not implement native, interstitial or rewarded ads, or a “watch an ad to continue” feature. The PRO experience is configured not to request ads.
When an ad request is made, Google Mobile Ads (AdMob) and its service providers may process technical and advertising-related information, such as IP/network information, approximate location inferred from network data, device or app identifiers available under Android and SDK settings, ad or app interactions, diagnostics, and consent choices. The exact processing and ad availability depend on the device, consent choices, Google’s services and configuration. Please also review Google’s AdMob data disclosure, Google’s consent information and Google’s Privacy Policy.
5. In-app purchases
Purchases are offered and processed through Google Play Billing. Lucius Studio does not receive payment card details or your Google account password. Versions configured for secure PRO purchase verification use Firebase and Google Cloud when purchasing, restoring a purchase, or checking a saved PRO entitlement. Core learning does not require a purchase, and this service does not provide child accounts or cloud synchronisation of learning records.
For these checks, the App sends transaction and security information over HTTPS: a Google Play purchase token or its hash, product and app identifiers, a signed entitlement receipt, request/challenge identifiers, and Firebase App Check/Google Play Integrity attestation information. Google services may also process Firebase installation or device identifiers, network/IP information and technical diagnostics. This information is used to verify and restore the ad-free entitlement, prevent replay and fraud, and handle refunds or revoked purchases, not for advertising tracking. Learner nicknames, answers and learning progress are not included in the purchase requests. The purchase database is in the United States (us-central1); Google’s related services may process data in other locations.
The backend stores token hashes, signed entitlement receipts, entitlement/acknowledgement/revocation status, and notification/reconciliation records. Raw purchase tokens are temporarily retained only in acknowledgement retry jobs and removed when successful acknowledgement, revocation or expired-job processing occurs; service interruptions may delay processing. Challenges become invalid after about five minutes and Firestore TTL cleans them up later, not immediately. Long-lived entitlement and notification records currently have no automatic retention cutoff and are retained to support restoration, replay protection and refund handling. Shared usage counters contain server time buckets and counts, not IP addresses or child identifiers. Cloud hosting may still process network/request diagnostics.
Deleting a local learner profile or uninstalling the App does not automatically delete Google Play or backend purchase records. Parents can contact the privacy email below to ask about these records or request deletion; requests require purchase verification and review of applicable retention needs and are not automatically or instantly completed. Deleting an entitlement record may affect purchase restoration. Do not send a child’s name, payment card details or account password.
6. Children and parental control
LuMaths is designed for children to use with family guidance. Parents can manage learner profiles and initiate summary exports in the parent area. The App does not knowingly ask children to submit their real-world contact details. If you believe information has been provided to us outside the App’s described local operation, contact us using the address below so we can review it.
7. Changes and contact
We may update this policy when the App’s features, advertising or data practices change. The effective date above will be revised when a new version is posted.
Privacy contact email: barbieclapton@gmail.com