Privacy Policy — Lil Ummah

Last updated: 16 November 2026

This is the privacy notice for the Lil Ummah Android application and for the Lil Ummah pages on this website. Lil Ummah is a product of BOTC ENTERPRISES. It is a children’s educational app with videos, games and quizzes. A parent or guardian creates and controls the account.

This notice explains what information is collected, what stays only on the phone, why it is used, how long it is kept, who helps us run the service, and how a parent can ask for access, correction or deletion. It is written so that a parent can read it, and so that it can be linked from Google Play. It describes the app version that is current on this date. In this version, Google Play Billing is not active and the app does not take a payment.

The public website for this notice is:

https://www.botcenterprises.com/apps/lil-ummah/privacy-policy

The account deletion page is:

https://www.botcenterprises.com/apps/lil-ummah/delete-account

Help and support:

https://www.botcenterprises.com/apps/lil-ummah/help-support

Company contact page:

https://www.botcenterprises.com/contact

The Android application id is com.lilummah.kids. The name shown on the device is Lil Ummah.

1. Who this notice is for

This notice is for the parent or legal guardian who creates the Lil Ummah account, and for the child who uses the learning content on that parent’s device.

The learning content is aimed at children of about 3 to 13 years. Under the Digital Personal Data Protection Act, 2023 (“DPDP Act”), a child is a person under 18 years of age. Lil Ummah is built so that the account belongs to the parent, not to the child.

By entering a mobile number and accepting the Terms and this Privacy Policy, you confirm that you are the parent or legal guardian, that you are allowed to provide that mobile number, and that you allow a child to use the app on the device you control.

If you are a child, please ask your parent to read this page and to manage the account.

2. Who is responsible

BOTC ENTERPRISES is the operator of Lil Ummah and is the data fiduciary for the personal data described in this notice. “Personal data” means information that can identify a person, directly or indirectly, as that idea is used in the DPDP Act.

BOTC ENTERPRISES decides why the account information is used. Supabase and Bunny.net process information for us so that the app can run. They do not decide the purpose of the parent’s account. Authorised staff of BOTC ENTERPRISES use a separate admin application, which is not published on Google Play, to manage content, feedback, deletion requests and account status.

The official postal address is No. 1, S/O She Husain She Abbas, Main Road, Hatrun, Balapur, Akola, Maharashtra 444109, India. The phone number is +91 9765684174. Udyam Registration Number: UDYAM-MH-02-0104814. BOTC ENTERPRISES is registered as a micro enterprise whose major activity is services. The proprietor named on the Udyam certificate is MOHAMMAD NAVED. For general company enquiries, email info@botcenterprises.com; for website contact, email contact@botcenterprises.com; for Lil Ummah app support, email support@botcenterprises.com. A parent can also write to us from Parents Zone inside the app. See the Contact section at the end of this notice.

3. Short summary

  • We ask for an Indian mobile number so a parent can open an account.
  • We create a random app-instance identifier on the phone. We do not read the Android advertising ID, the hardware Android ID, IMEI or IMSI.
  • There is no OTP and no password in this version. The account is tied to one app install at a time.
  • The child’s name, avatar, age group, class, and the parent’s optional profile notes stay on the phone. They are not uploaded as the account profile.
  • We do not show ads. We do not use advertising, analytics or crash-reporting SDKs.
  • Videos are streamed through Bunny.net with a short-lived link. We send Bunny the video path, not the parent’s phone number or the child’s name.
  • Account data and server functions run on Supabase.
  • A parent can request deletion in the app or on the website. Deletion is completed after review. The target is 7 working days after ownership is verified.
  • This version does not charge the user. Google Play Billing is not switched on.

4. The account, and what “parent consent” means in this version

Sign-in uses a 10-digit Indian mobile number. The app stores it in international form, beginning with +91. The parent must tick a box agreeing to the Terms and this Privacy Policy before the number is sent.

The current app does not send an OTP and does not use a password. A phone number typed on the website, by itself, is not treated as proof that the person owns the account. A simple maths question is used as a parent gate before Parents Zone, feedback, account deletion and the subscription screen. That gate reduces the chance that a young child opens those screens by accident. It is not a DigiLocker check, and it is not a government identity check.

What we do ask the adult to do is:

  • Confirm they are the parent or guardian by continuing past the login screen.
  • Read or open the Terms and this Privacy Policy, and tick the agreement box.
  • Provide their own mobile number, not a number that belongs to the child if that can be avoided.
  • Use the parent gate before adult settings.

Please do not type a child’s full legal name, school name, home address or any identity document into the app. Those fields are not required. Optional child details that you do type stay on the device, as described below.

Because login is not OTP-checked, a person who knows the mobile number and can install the app could enter that number on another device. If the same number is used on a new install, the previous install can lose access. Keep the signed-in device with the parent.

5. Information stored on our servers

When a parent signs in, the Lil Ummah server function creates or updates one account row. The server stores:

  • The mobile number, in +91 form.
  • The app-instance identifier generated on that install.
  • An internal account identifier.
  • An internal secret generated on the server to operate the account. It is not shown as the child’s name, and it is not sent to Bunny.net.
  • The first login date and time.
  • Trial start and trial end. A new account can receive a free trial. The usual default is 7 days. The length is set on the server.
  • Subscription status, such as trial.
  • Whether a premium flag is on, and a premium end date if one has been set.
  • Whether the account is blocked.
  • Account status, such as active, pending deletion, or deleted.
  • An amount-paid field. In this version the app does not take a payment, and a new account is stored with amount paid as zero.

The child app cannot turn premium on by itself. Premium, blocked and trial dates are controlled on the server. Authorised staff can change those flags from the admin application, for example to grant or remove access.

The server also stores the minimum information needed to answer a request:

  • Feedback records, only if the parent sends feedback. See section 8.
  • Deletion-request records, if the parent asks for deletion. See sections 18 and 19.
  • Payment rows, only if a payment has actually been recorded. This version of the app does not create a Google Play purchase. See section 13.

Content that every user can see, such as video titles, quiz questions and game definitions, is also stored on the server. That catalogue is the learning material. It is not the child’s profile.

6. The app-instance identifier

On first launch the app creates a random identifier in UUID form and stores it on the phone. It is used only so the server can tell which install is allowed to use the account. It is created inside the app. The app does not read:

  • The Android advertising identifier (AAID).
  • The hardware Android ID (SSAID).
  • IMEI, IMSI, or the phone serial number.
  • A contact list, photo library, or precise GPS location.

The identifier can stay on the phone after logout so the same install remains stable. It is removed from the phone when a deletion request is accepted by the server and the app clears local account data, or when the app’s data is cleared or the app is uninstalled.

We use this identifier for account security and to reduce account sharing. We do not use it for advertising.

7. Information that stays on the phone

The following items are stored locally on the device, in the app’s private storage. They are used to personalise the app on that phone. They are not uploaded as the account profile.

  • An optional child display name. If none is saved, the app can show a generic label.
  • An optional avatar, limited to the picture choices built into the app.
  • An optional age group, limited to these choices: 3–5 years, 6–9 years, or 10–13 years.
  • An optional parent name.
  • An optional parent contact number saved in Parents Zone.
  • An optional city or state text.
  • An optional child class selection.
  • Likes, favourites, learning activity and streak information.
  • An in-app notification list, including whether an item was read, and the last video, game or quiz identifier used to build that local list.
  • Cached learning content so screens can open more quickly.
  • Search text typed in the app. Search filters the catalogue already downloaded to the phone. The search box is not a separate profile stored on the account.

A parent can change the optional local details in the app. Uninstalling Lil Ummah, or clearing the app’s storage in Android settings, removes this local information from that device. Uninstalling does not delete the server account. A deletion request made on the website cannot reach into the phone and erase local data. The parent should also clear the app on the device, or submit deletion from the signed-in app, which clears local account data after the server accepts the request.

Do not put sensitive information into the optional local fields. The city or state field is free text. It is not GPS, and we do not ask Android for location permission.

8. Feedback

Feedback is optional. It is sent only when a parent opens Parents Zone, passes the parent gate, writes a message, and submits it.

The server then receives:

  • The app-instance identifier, so the message can be matched to the signed-in install.
  • The account mobile number, so the server can confirm that the account exists and is active on that install. The saved feedback row stores the app-instance identifier, the name, the contact field, the message and the time. It is not a public post.
  • The parent name, if one was typed. If the name is empty, the server stores “Anonymous”.
  • The optional contact number typed in Parents Zone, if any.
  • The message, up to 4,000 characters.
  • The time the message was stored.

Feedback is visible to authorised BOTC ENTERPRISES staff in the admin application. It is not shown to other families. There is no public profile, no chat between users, and no comment wall.

Please do not include a child’s identity documents, a precise home address, or a password in a feedback message.

9. Information we do not collect

In the current Lil Ummah app we do not collect:

  • A password, OTP code, or email address at login. The deletion function has a place for a contact email, and the app sends that field empty.
  • Card numbers, UPI IDs, bank account numbers, or government identity numbers.
  • Precise location, approximate GPS, or location permission.
  • Contacts, SMS, call logs, calendar, camera photos, microphone recordings, or files from shared storage.
  • The Android advertising ID or a hardware device identifier.
  • Crash reports or analytics events from Firebase, Crashlytics, or an advertising SDK. Those products are not part of this app.
  • A push-notification token. The notification list inside the app is stored on the phone. We do not use Firebase Cloud Messaging in this version.
  • Voice of the child. The app can speak text aloud for learning. That is playback on the device. It is not a recording uploaded to us.
  • Behavioural advertising profiles, and we do not sell personal data.

Google Play itself, the phone maker, and the network provider collect information under their own rules when a person downloads an app or uses the internet. That collection is not done by the Lil Ummah code. Google’s privacy policy applies to the Google account and to the Play Store.

10. Android permissions

The app requests:

  • Internet, so it can reach the Lil Ummah server, load learning content, and play videos.
  • Network state, so it can tell whether the device is online.

The app does not request location, camera, microphone, contacts, SMS, phone-state, or background-location permissions. Traffic is sent over HTTPS. Cleartext HTTP is switched off for the app.

If a future version needs a new permission, this notice will be updated before that version is published, and the permission will be shown by Android in the usual way.

11. Why we use the information

We use the information for these purposes only:

  • To create the parent account and recognise the same account later.
  • To keep the account on one install at a time and to release that install when the parent logs out.
  • To show whether a free trial, a staff-granted premium flag, or a block is active.
  • To deliver videos, games, quizzes and other learning content.
  • To receive a feedback message the parent chose to send.
  • To record and review an account-deletion request, and then to delete or detach the data described in this notice.
  • To keep a detached financial record if a real payment exists, for tax and accounting, without using it to contact the parent or to reopen the app account.
  • To protect the service against misuse, duplicate trial abuse, and accounts that have been blocked or marked for deletion.
  • To answer a privacy request from the parent.

We do not use personal data for targeted advertising. We do not sell personal data. We do not use a child’s information for behavioural monitoring or for advertising directed at children. Local likes, streaks and favourites are there so the same phone can remember learning progress. They are not sent to an advertising network.

A new account is given a trial so the family can use the app before any paid plan exists. The trial is an access flag on the account. It is not a charge.

12. Legal basis under Indian law

BOTC ENTERPRISES handles personal data under the DPDP Act and the rules made under it.

The parent voluntarily provides the mobile number, and any feedback, for the purposes in this notice, and confirms agreement before the number is sent. The parent may withdraw that consent by requesting account deletion, as described below. Withdrawal does not make earlier processing unlawful, and it does not erase a financial record that the law still requires us to keep, once that record has been detached from the app account.

Some processing is required for a legal duty. If a payment has been recorded, books and tax records may have to be kept for the period Indian tax law requires. GST records are generally kept for 6 years from the due date of the annual return. Income-tax records can be required for a longer period, commonly up to 8 years from the end of the relevant year, and longer if a tax authority lawfully requires it. Those detached records are kept for that legal purpose and not to market to the family.

Children’s data. The DPDP Act requires verifiable consent of a parent before a data fiduciary processes personal data of a child, and it restricts tracking, behavioural monitoring and targeted advertising directed at a child. Lil Ummah is designed so that the server account is the parent’s mobile number and the app-instance identifier, not a stored child profile. Optional details about the child stay on the device unless a parent chooses to type them into a feedback message. We do not run advertising, and we do not build an advertising or tracking profile of the child. The parent gate and the agreement box are the controls in this version. They are not a government e-KYC flow. A parent who is not comfortable with that model should not create an account.

This notice is our privacy notice under the DPDP Act: it states the personal data, the purpose, how to use the rights below, and how to complain.

Lil Ummah does not offer a public social network, public comments, or user-to-user messaging. Families do not publish content to other users. We describe the product as a private educational app with an operator-managed catalogue, not as a social-media intermediary.

13. Subscriptions and payments in this version

Google Play Billing is not available in this app version. No payment or automatic renewal is available, and pricing will be shown after billing is activated. Tapping the button does not charge a card, a UPI account, or a Google Play balance.

There is no Google Play Billing library active in this purchase flow. We do not collect card or bank data. We do not redirect the parent to an outside website to pay for digital content.

A banner in the app can show trial days remaining, or that a trial has ended. Until Play Billing is live, that screen is information about access. It is not a completed purchase.

Authorised staff can still mark an account as premium or blocked in the admin application. That is an internal access flag. It is not a Google Play charge.

If a payment row already exists in our database from an administrative record, approved account deletion does not keep that row tied to the parent’s phone number. The link to the app account is removed, a random financial-record identifier is assigned, and free-text notes on that row are cleared. The row is then visible only to authorised staff as a detached financial record. There is no automatic computer job that deletes those rows on a fixed date. Our rule is:

  • Keep a detached payment record only for tax, accounting, and to show that a charge, if any, was handled.
  • Do not use it to identify the child, to restore the deleted app account, or to send marketing.
  • Delete it or continue to hold it without the parent’s phone number when the legal retention period described in section 12 has ended.
  • Do not promise a refund in this version, because this version does not take a Play payment. When Play Billing is switched on, this notice and the Subscription and Refund Policy will be updated before that version is published. Refunds of a future Play purchase will follow Google Play’s rules. The parent will cancel a future subscription from Google Play’s subscription settings.

Until that update is published, on-screen copy must not be read as a live price or as a completed subscription.

14. Videos and Bunny.net

Learning videos are protected streams. The app asks our server for a short-lived playback link. That request sends the video path. It does not send the parent’s phone number, the child’s name, or the age group to Bunny.net.

The server returns a signed Bunny.net address that expires. The phone then plays the video from Bunny.net’s network. Bunny.net (BunnyWay / the Bunny.net content-delivery service) therefore receives the technical information needed to send the video, which can include the device’s IP address, the time of the request, and the video address. That is how a video network delivers a file. We do not authorise Bunny.net to use that information for its own advertising about the child, and we do not send Bunny.net a child profile.

If playback fails, the usual cause is network access or an expired link. The app can request a new link. We do not keep a separate watch-history profile on the server for advertising. Local progress on the phone is described in section 7.

15. Supabase, our backend

Account records, feedback, deletion requests, the content catalogue, configuration such as the trial length, and the server functions that the app calls are hosted with Supabase. Supabase provides the database and the edge functions. The privileged service credential stays on the server. The app and the public website use a publishable key so they can call the functions we have defined. That publishable key is not a permit to read the whole database. Row-level rules and server checks restrict access. Authorised admin users access data through the admin application under those rules.

Supabase infrastructure can be located outside India. A parent’s mobile number and the other server fields listed in this notice may be processed on that infrastructure. See section 17.

We use Supabase to run Lil Ummah. We do not allow that data to be sold.

The server functions used by the app include login, releasing the device on logout, reading subscription or trial status, submitting feedback, and submitting a deletion request. Each call is sent over HTTPS.

16. This website

The Lil Ummah policy, help and deletion pages are published at the website address listed at the top of this notice. The site is a set of pages. It does not contain an advertising script, a Google Analytics tag, or a marketing cookie banner script in the application code.

If a parent submits the deletion form, the browser sends the mobile number directly to our Supabase function, together with a confirmation that the parent typed DELETE. A hidden anti-spam field is included. If that field is filled, the request is rejected. The website does not ask for the child’s name.

The company that hosts the website can keep ordinary connection logs, such as IP address, date, and the page requested, in order to deliver and protect the site. Those logs are not used by us to advertise to children.

Opening a policy page from inside the app uses an in-app web view. The web view is limited to the host of our own website and to HTTPS. It is used so the parent can read this notice, the terms, the subscription notice, the deletion page, or help, without sending the child to an unrelated site. JavaScript is enabled so those pages can display. The web view is not an advertising frame.

17. The admin application

BOTC ENTERPRISES uses a separate admin application for staff. It is an internal tool. It is not the children’s app and it is not offered on Google Play as Lil Ummah.

Authorised staff can use it to publish or remove learning content, read feedback, review deletion requests, and set account flags such as trial, premium or blocked. Staff must use it only for operating Lil Ummah. A deletion can be approved only by an active master admin, and only after the request is marked verified and matched to the account, as described in section 19.

18. Who else receives information

We do not sell personal data. We do not share personal data with advertising networks. We do not allow other families to see the account.

These parties receive information only as needed to run the service:

  • Supabase, to host the database and server functions described above.
  • Bunny.net, to deliver a video after a short-lived link is created. The token request carries the video path.
  • Authorised BOTC ENTERPRISES staff, through the admin application.
  • A website host, for ordinary delivery logs of the public pages.
  • Google, when the parent uses Google Play to install or update the app, under Google’s own policy. When Google Play Billing is later enabled, Google will process the payment. We will update this notice before that version is published. We would then receive purchase status from Google, not the parent’s full card number.
  • A legal authority, if a valid law requires us to provide information, or to establish, exercise or defend a legal claim.

We do not authorise these providers to use Lil Ummah account data for their own marketing to the child.

19. Transfers outside India

Supabase and Bunny.net may process data on servers outside India, including when a video is served from a network location close to the device. The DPDP Act allows transfer of personal data outside India except to a country or territory that the Central Government restricts by notification. We do not transfer personal data in order to sell it. If the Government notifies a restriction that affects a provider we use, we will stop that transfer or change the provider, and we will update this notice if the change affects parents.

20. How long we keep information

Account data. The mobile number, app-instance link, trial and status fields are kept while the account is active so the app can sign in and apply the correct access.

Pending deletion. After an in-app request is accepted, the account is marked pending deletion and cannot be used to sign in. It stays in that state until an authorised administrator completes a verified request, or the request is refused because ownership was not verified.

After approval. The app account row is deleted. Feedback linked to that account identifier or to that install’s app-instance identifier is deleted. Older feedback that is not linked to that account identifier or that current app-instance identifier can remain, because the cleanup matches those links. Local data on a phone is cleared when the request is submitted from that signed-in app. A website request does not clear the phone.

Deletion-request audit. After completion we clear the phone number, the app-instance identifier, any contact email, the request description, admin notes, and the link to the account. We keep the request identifier, the source of the request (app or website), the status, the request and completion times, and the verification audit fields. We keep those fields as a record that a deletion was requested and completed, without the phone number.

Detached payment records. If any exist, they are kept without the app-account link, under a random record identifier, for the tax and accounting period in section 12. No automatic purge date is stored on the row today. The retention rule in this notice is the rule staff must follow.

Local data. It remains on the device until the app clears it, the parent clears app storage, or the app is uninstalled.

Feedback that was never linked to the account. Kept until deleted by staff or until a matched deletion removes it, and it is not shown publicly.

Server logs of technical errors may exist for a short operational period so we can fix faults. They are not a child profile and they are not used for advertising.

21. Security

We use HTTPS for app and website traffic. Server secrets stay on the server. Database access for payment records is restricted, including limits that keep anonymous public access from reading those rows. Admin approval of deletion requires an authorised master admin and a verified, matched request.

No method of transmission or storage is completely secure. The parent should keep the device locked, avoid sharing the signed-in device, and avoid putting identity documents into optional fields or feedback.

A blocked account, or an account pending deletion, is refused at login.

22. How to request account deletion from the app

This is the in-app path required for a parent who created an account:

  • Open Lil Ummah on the device that is signed in with the account mobile number.
  • Open Parents Zone and answer the parent maths gate.
  • Choose Delete Account.
  • Read the explanation. Type DELETE.
  • Submit the request.

The app sends the signed-in mobile number and the app-instance identifier to the server. The server records a deletion request and marks that account pending deletion. The app then logs out and clears local account data on that device, including the stored phone number, the child profile fields held by the account service, activity, likes, favourites, the local notification list, streak data and the app-instance identifier.

Submitting the request is not the same as finished deletion. Finished deletion happens when an authorised administrator verifies the request and approves it. Our target is to complete a verified request within 7 working days of receipt when verification is completed promptly. Extra checks or holidays can change the timing. This is a service target.

After the account is pending deletion, that mobile number cannot be used to sign in.

23. How to request account deletion from the website

A parent can also submit a request without reinstalling the app, at:

https://www.botcenterprises.com/apps/lil-ummah/delete-account

The form asks for the Indian mobile number used in Lil Ummah and the word DELETE. The browser sends that number to our server function. If the service is configured, the parent receives a reference identifier. Keep that reference.

A website request does not, by itself, prove ownership, because this version has no OTP. It does not lock the account. It does not sign the app out and it does not erase data stored only on the phone. Staff must not approve a website request on the typed number alone. Before approval, an administrator records a verification method and the system requires the request to be marked verified and matched to the account.

If many requests are sent for the same number in a short time, the server can refuse further requests for a while.

The same deletion outcome described in section 20 applies after a verified approval. The target timing is the same 7 working days after verification.

24. What deletion does not do

  • It does not cancel a future Google Play subscription, because this version has no Play subscription. When billing exists, the parent will also need to cancel in Google Play.
  • It does not delete a detached financial record before the legal retention period ends.
  • It does not delete the audit fields listed in section 20.
  • It does not delete learning content we created, such as videos and quizzes, because that content is not the parent’s personal data.
  • It does not control copies a parent exported themselves, or backups made by the phone’s own backup system outside Lil Ummah.
  • A website request does not wipe the app’s local storage. Use the in-app deletion path, or uninstall the app, to remove local data.

25. Rights of the parent

Under the DPDP Act, the parent, as the data principal for the account data, may:

  • Ask for a summary of the personal data we hold on the server about the account, and the processing described in this notice.
  • Ask for correction of personal data that is inaccurate or misleading, or to complete data that is incomplete. Optional profile text that exists only on the phone can be edited or cleared in the app without a server request.
  • Ask for erasure, using the deletion paths in sections 22 and 23. Erasure is subject to the legal retention of a detached financial record and the audit fields described above.
  • Withdraw consent by stopping use and requesting deletion. The account may stop working once it is marked pending deletion.
  • Nominate another person to exercise these rights if the parent dies or becomes unable to exercise them, as the DPDP Act provides. There is no separate nomination screen in this version. Send the nomination request from Parents Zone feedback, or email contact@botcenterprises.com, and include enough detail for us to identify the account without putting a child’s identity documents in the message. We may need to confirm the parent’s authority before we record a nominee.
  • Make a grievance to us, using section 26.
  • Complain to the Data Protection Board of India, as provided under the DPDP Act and the rules under it, after using our grievance path or as the law otherwise allows.

We may need to confirm that the requester controls the account before we disclose or change server data. Because there is no OTP, we will not disclose the account to a person who only types the mobile number on the website. We may ask the requester to use the signed-in app, or another check that an administrator records, before we act.

We do not charge a fee for a reasonable rights request. We can refuse a request that is abusive, repetitive, or impossible to match to an account. We will say if we refuse.

Our target is to acknowledge a privacy request promptly and to respond within 15 days. A deletion that needs ownership verification follows the 7 working day target after verification, which can sit inside or beside that response window. If a request is complex, we will tell the parent why more time is needed.

26. Grievance redressal

A parent who has a complaint about how Lil Ummah handles personal data can:

  • Send feedback from Parents Zone in the signed-in app, after the parent gate. Include the words “privacy complaint” and, if you have one, the deletion reference identifier.
  • Use the Help and Support page: https://www.botcenterprises.com/apps/lil-ummah/help-support
  • Use the Contact page: https://www.botcenterprises.com/contact

You can also email contact@botcenterprises.com for website contact or support@botcenterprises.com for Lil Ummah app support, write to No. 1, S/O She Husain She Abbas, Main Road, Hatrun, Balapur, Akola, Maharashtra 444109, India, or call +91 9765684174. That address, phone number and the listed email channels are grievance contacts for BOTC ENTERPRISES. Please include the mobile number used in the app only if you are the parent, plus a short description of the issue. Do not send copies of government identity cards unless we specifically ask for a narrower proof and explain why.

We aim to acknowledge the complaint promptly and to resolve it within 15 days of understanding the request. If we cannot complete a deletion until ownership is verified, we will say what is still needed.

A parent may also approach the Data Protection Board of India under the DPDP Act.

27. Google Play Data safety

This section is the same set of facts, arranged for the Google Play Data safety form. The form must be filled to match this notice and the app.

Data collected by Lil Ummah and sent off the device:

  • Phone number. Collected. Required for the account. Purpose: account management, security, and fraud prevention (one install at a time, and blocking duplicate or pending-deletion accounts). Not used for advertising. The user can request deletion.
  • App-instance identifier. Collected. Generated by the app, not a hardware ID and not the advertising ID. Purpose: account management and security. Not used for advertising. Removed from the server account when a verified deletion is completed, and cleared from the deletion record after completion except as part of audit fields that no longer contain the identifier.
  • Feedback contents, and the optional parent name and optional contact number included in that feedback. Collected only if the parent submits feedback. Purpose: app functionality and developer communications. Not shown to other users. Not used for advertising.
  • Account and trial status fields listed in section 5. Collected. Purpose: app functionality. Not used for advertising.

Data that stays on the device and is not collected by our servers as a profile:

  • Child display name, avatar and age group.
  • Parent name, parent contact, city or state text, and child class, except where the parent name and contact are included in a feedback message the parent sends.
  • Likes, favourites, streaks, local notification list, and search text.

Data not collected:

  • Precise or approximate location.
  • Contacts, photos, videos of the child, microphone, SMS, calendar.
  • Financial card, UPI or bank details.
  • Email address, in this version.
  • Advertising ID, crash logs, and analytics events.
  • Health, religion as a stored profile field, or political opinions. The learning catalogue may include Islamic educational material. Watching that material is not stored by us as a religion field on the account.

Sharing:

  • The data collected above is processed by Supabase on our instructions.
  • Bunny.net receives the video path and the connection data needed to stream the video, not the child profile and not the phone number in the token request.
  • We do not sell data. We do not share data with advertising partners. We do not use data for cross-context behavioural advertising.

Security and deletion:

  • Data is encrypted in transit using HTTPS.
  • Parents can request deletion in the app and at the website URL in section 23, without reinstalling, for the website path.
  • Deletion is completed after verification, not instantly at the moment the form is submitted. The notice explains what is deleted and what audit or tax records can remain.

Ads:

  • The app does not contain ads. The Data safety and ads declarations should say that the app does not use advertising.

Target audience:

  • The app is made for children with a parent account. The Play Console target-audience answers should include children. The declarations must match this notice, including that we do not use the advertising ID and that we do not show ads.

28. Families and children on Google Play

Lil Ummah is a children’s educational product. The parent is expected to install it and to hold the account.

Practices that matter for Google Play’s Families rules, as implemented in this version:

  • No advertising SDK and no ads in the app.
  • No collection of the Android advertising ID.
  • No sale of personal data.
  • No public user profiles and no social features between children.
  • Parent gate before Parents Zone, feedback, deletion and the subscription information screen.
  • Policy, terms, help and deletion pages open from the app to this website.
  • Optional child details are kept on the device rather than in the server account profile.
  • The server stores the parent mobile number and the app-instance identifier in order to run the account. That collection is disclosed here and at login, before the number is sent.

A parent should supervise use. The app does not replace parental care.

29. Third-party services named in this notice

  • Supabase, for the database and server functions.
  • Bunny.net, for video delivery.
  • The website at https://www.botcenterprises.com, for publishing these pages.
  • Google Play, for distribution of the Android app, under Google’s policies. Google Play Billing is not active in the purchase flow described here.

We do not load social-network plugins, ad networks, or analytics SDKs in the app.

30. If there is a security incident

If we become aware of a personal-data breach that affects a Lil Ummah account and the law requires us to notify a parent or the Data Protection Board, we will notify in the manner and time the DPDP Act and its rules require. We may also use the in-app feedback channel or a published contact address if we need to reach a parent and it is lawful to do so.

31. Changes to this notice

If we change what we collect or why we collect it, we will update this page and change the “Last updated” date. The updated page applies when it is published on this website. If a change requires fresh consent under the DPDP Act, we will ask the parent before we rely on that new purpose. In particular, before a version that turns on Google Play Billing, we will update this notice and the Subscription and Refund Policy so they state the real product, the price source, renewal, cancellation through Google Play, and what purchase status we receive from Google.

The agreement box at login links to this page. A parent should review it when the date changes.

32. Contact

Data fiduciary: BOTC ENTERPRISES.

Product: Lil Ummah.

Privacy requests and grievances:

  • In the app: Parents Zone, after the parent gate, using feedback. Write “privacy request” or “privacy complaint”, and include a deletion reference identifier if you have one.
  • Help and Support: https://www.botcenterprises.com/apps/lil-ummah/help-support
  • Contact: https://www.botcenterprises.com/contact
  • Account deletion: https://www.botcenterprises.com/apps/lil-ummah/delete-account

Postal address: No. 1, S/O She Husain She Abbas, Main Road, Hatrun, Balapur, Akola, Maharashtra 444109, India. Phone: +91 9765684174. Udyam Registration Number: UDYAM-MH-02-0104814. For website contact, email contact@botcenterprises.com; for general company enquiries, email info@botcenterprises.com; for Lil Ummah app support, email support@botcenterprises.com. Do not send a child’s identity proof in the first message.

This notice does not create a customer-support promise beyond the privacy rights and the service targets stated above.

33. Related pages

Terms and conditions:

https://www.botcenterprises.com/apps/lil-ummah/terms-and-conditions

Subscription and refund policy:

https://www.botcenterprises.com/apps/lil-ummah/subscription-and-refund-policy

Those pages describe the service rules and the current state of payments. If they differ from this privacy notice on a privacy question, this privacy notice is the statement of what data we handle.