Brolly Wonder Privacy Policy
Brolly Wonder · Effective date: October 29, 2026 · App version 2.0.3 (version code 7)
Developer: Brolly · Contact: brollysolutions.in@gmail.com · +91 81868 44555
Brolly ("we," "us," or "our") provides Brolly Wonder, a children's educational application. Inside the app the learning world is called WonderVerse; Brolly Wonder is the name of the application itself. This Privacy Policy explains what information the app handles, why it is used, how it is protected, and the choices available to parents and guardians.
1. Information handled by Brolly Wonder
Information stored on the device
Brolly Wonder lets a user enter a player display name and choose an avatar. The app also records learning and gameplay information, including:
- player display name and selected avatar;
- lesson and quiz results;
- learning progress, skill statistics, and activity history;
- time spent on learning activities;
- streaks, levels, stars, coins, badges, and rewards;
- saved mini-game levels and high scores; and
- virtual-pet selections and progress.
This information is used to provide the app's learning experience, show progress in the parent dashboard, and preserve progress between sessions.
Children do not create accounts and are never asked for an email address or a telephone number. A parent or guardian creates the account with their own mobile number, the student’s name and a 4-digit PIN. Player information is held on the device and may also be backed up when a parent cloud session is connected and backup is not paused.
Parents and guardians should encourage children to use a nickname rather than a full legal name. Brolly Wonder does not ask a child for an email address, telephone number, precise location, photograph, contacts, microphone recording, or camera access. The only telephone number the app ever collects is a parent's or guardian's own mobile number, entered when signing up, described next.
Parent setup and cloud backup
Account sign-up and login. A parent or guardian signs up with their own mobile number, the student’s name and a 4-digit PIN, and later logs in with the mobile number and PIN. The mobile number identifies the account. No verification SMS or call is sent, so the number is not verified. When cloud services are available, signing up or logging in starts cloud connection and synchronisation automatically unless backup is paused; there is no separate initial cloud-backup opt-in. Local play works without a cloud connection.
Parent access. The parent contact-details form and Parent Dashboard are accessible without a multiplication challenge. They do not verify age, identity or that an adult is present. Account access still requires the account credentials or an authorised recovery link.
Cloud identity. Signing up or logging in creates or opens a Supabase account identified by the mobile number. The student’s name is stored with that account as a display name. Accounts are not looked up, merged or restored by anything other than the mobile number and PIN entered at login.
PIN and PIN reset. The app does not send verification SMS or calls or request verification codes. The PIN is turned into an account credential that Supabase stores only in hashed form; Brolly cannot read it. Because no code is sent, a PIN can be reset by entering the account’s mobile number and a new PIN, so anyone who knows the number could reset that account’s PIN. A 4-digit PIN is a weak credential; do not reuse a PIN you use elsewhere. The app does not send marketing calls or messages to the mobile number.
Sessions and recovery. The app stores a Supabase session token on the device and refreshes it when possible, so closing and reopening the app normally retains cloud access. The token is a credential and must be protected. After logging out, clearing app storage, reinstalling or changing devices, a parent logs in again with the mobile number and PIN, or resets the PIN as described above. Local progress remains usable while available on the device.
What is stored when backup is connected. Supabase stores the child's player display name, avatar, learning and game progress listed above under the authenticated user ID. A separate parent profile stores the parent's name and unverified mobile number under that same user ID. A local copy is retained and pending parent-profile changes are retried when connected; unavailable cloud services do not block play. Existing verified phone records in the sign-in service and backup rows are preserved. No advertising information is stored in these profile or progress rows.
Offline progress. Lessons and games use the device copy. Existing synchronisation safeguards preserve newer local progress and prevent one account's local save from being uploaded to another account. Cloud synchronisation needs a connection; local setup and play can continue without one. Backup availability is shown in the Parent Dashboard.
Turning backup off. Pause cloud backup stops parent-profile and progress synchronisation while retaining the session; it does not sign out or stop session refresh. Resume cloud backup reuses it when valid. Actual Sign out removes the session on this device after a warning about loss of cloud access, but keeps local progress. Delete cloud data and Delete account are separate actions described in section 5.
Advertising and automatically processed information
Brolly Wonder includes the Google Mobile Ads SDK to display a banner advertisement on the Kingdom Map and an opt-in "Watch Video Ad" rewarded advertisement that a user chooses to start. The app does not display full-screen interstitial advertisements. Optional Firebase Analytics is described separately below. The app does not include a separate attribution or crash-reporting service. Google and its advertising technology may automatically collect or process information such as:
- the device's IP address, which may be used to estimate general location;
- interactions with the app and advertisements, such as app launches, taps, and video views;
- diagnostic and performance information; and
- an app set ID, where permitted — a developer-scoped identifier that is reset when the developer's apps are removed from the device.
Advertising identifier. Brolly Wonder is configured to avoid Android advertising-ID collection. Its Android manifest removes com.google.android.gms.permission.AD_ID and android.permission.ACCESS_ADSERVICES_AD_ID, and Firebase advertising-ID collection is disabled. Google Mobile Ads requests are configured for child-directed treatment, which Google documents as preventing AAID transmission. Permission removal alone does not guarantee identifier behavior on every supported Android version.
How advertisements are configured. Every ad request made by Brolly Wonder is configured for a child audience:
- requests are tagged as child-directed;
- the maximum ad content rating is set to "General"; and
- only non-personalised advertisements are requested, so advertisements are not selected using a profile of the user's interests.
These are technical settings applied to every ad request. They describe how the application is configured; they are not a statement of compliance with any particular law, certification, or programme.
Google states that information collected by the Google Mobile Ads SDK is encrypted in transit. Google may use this information for advertising, measurement, and fraud prevention. Google's handling of information is governed by its own policies. More information is available at Google's Privacy Policy and Google's advertising information.
Google documents app set ID support in the Mobile Ads SDK for reporting and fraud prevention. App set ID is subject to Google Play's restrictions: it must not be used for advertising personalisation or advertising measurement, or linked to personal information or other identifiers for advertising purposes. Brolly's own application code does not read this identifier or link it to parent contact details or child profiles. The advertising and measurement purposes described above are not a statement that every listed data type is used for every purpose. See Google Mobile Ads release notes and Google Play's app set ID requirements.
Brolly does not sell children's personal information.
Optional app and learning analytics
Brolly Wonder uses Google Firebase Analytics as an app-usage analytics service to help improve the learning experience. In an Android build configured for Analytics, analytics is ON by default, and a parent or guardian can switch it off at any time with the “Optional learning analytics” setting in Settings. The app confirms a successful change or shows an error with retry guidance if it cannot confirm the change. Web previews do not send Firebase Analytics events. Turning it off does not affect login, cloud backup or play. Supabase remains the application’s authentication, session and cloud-data system.
When analytics is on, the app sends limited usage measurements: app launches, foreground sessions, screen visits, onboarding steps, game and level activity, completion results, durations and reward events. These event details are restricted to fixed screen, game, category and result labels, reward categories, and bounded level numbers and durations. We do not send parent or child names, phone numbers, email addresses, passwords, one-time passwords (OTPs), Supabase user IDs, authentication tokens or similar credentials to Firebase Analytics. Firebase Analytics may also automatically collect and process a pseudonymous app-instance identifier, device/app and operating-system metadata, language, automatic usage events and general location derived from IP addresses. This information is not completely anonymous. No precise location is requested.
For this Analytics setup, advertising-ID collection and advertising personalisation remain disabled. Automatic screen reporting is disabled; the app sends only the permitted screen labels described above. Advertising storage, advertising user data and ad personalisation consent are denied. We do not use Analytics data for advertising or link Analytics with Google Ads or AdMob through this integration. Existing child-directed ad settings remain separate.
After opt-out is confirmed, Analytics collection is disabled and local Analytics data and its app-instance identifier are reset. If the app cannot confirm that collection is disabled, it tells the parent or guardian and offers a retry; custom gameplay and usage events are paused while the choice is unresolved. Opt-out does not erase data already received by Google. That data is subject to the Analytics property retention settings and Google privacy terms; aggregated reporting may be retained separately. Supabase account/cloud deletion does not automatically delete Analytics records; this integration does not attach Supabase account IDs to Analytics events. The Analytics choice belongs to the installation and is not automatically withdrawn by signing out or deleting a Supabase account. Contact us about privacy requests. More information is available in Google's Privacy Policy and Firebase privacy and security information.
Diagnostic messages
Diagnostic messages can contain a cloud account identifier, the last four digits of a legacy parent phone number, session status, timestamps and limited progress values such as experience points and coins. These console messages are separate from optional Firebase Analytics. Their availability depends on the build and device logging settings; the app does not automatically upload these console messages to a separate diagnostic service. If you choose to send logs to support, those logs may contain this information. Do not send passwords, verification codes or session tokens.
2. How information is used
Information handled by the app is used to:
- operate lessons, quizzes, rewards, and virtual-pet features;
- save and display learning progress;
- provide parents or guardians with an on-device progress dashboard;
- maintain app reliability, security, and performance;
- display and measure advertisements; and
- prevent advertising fraud and abuse.
3. Children's privacy
Brolly Wonder is designed as an educational experience for children. We aim to minimize the information requested from children. The app does not ask children to register an account or provide a telephone number. The parent contact-details form is intended for parents and guardians and is accessible without a multiplication challenge. It does not verify that an adult is present. The cloud account is intended for the parent or guardian. A player display name is stored on the device and may be a nickname.
Advertising providers may process device and usage information as described above. Brolly configures every advertising request for a child audience — child-directed, "General" content rating, and non-personalised only — as set out in section 1.
Parents and guardians should supervise children's use of the app. If you believe a child has provided personal information inappropriately, contact us using the details below. We will review the request and take reasonable steps within our control.
4. Sharing of information
Brolly does not sell or rent personal information. Google may process information through the Google Mobile Ads SDK for advertising delivery, measurement, diagnostics and fraud prevention. Google also processes optional app and learning analytics when enabled as described in section 1. Supabase hosts cloud account sessions, parent profiles and backed-up progress. This version does not send mobile numbers to MSG91 or request verification messages. Earlier app versions used MSG91 (Walkover Web Solutions Pvt. Ltd.) to deliver verification SMS or automated calls; older installed versions may still request that service. Information may also be disclosed when required by law, to protect users or the public, or in connection with a business reorganisation where permitted by law.
5. Data retention and deletion
Locally stored parent contact details, profile identifiers, player and learning information remain on the device until the app's data is cleared or the app is uninstalled, except that confirmed account deletion also clears the local parent profile and account references. Actual sign-out keeps the local parent contact details for convenience but removes the session. Child progress remains separate.
Brolly Wonder excludes its data from Android's own cloud backup and from device-to-device transfer. A child's learning record is not copied to a Google account by the operating system, and it does not follow the user to a new device that way.
A parent or guardian can delete all locally stored Brolly Wonder data through the Android device settings by selecting the app and clearing its storage, or by uninstalling the app.
When cloud backup has succeeded, a copy exists in our database. The Parent Dashboard offers two separate deletion actions for an account with a valid session.
Delete cloud data. Parent Dashboard → Cloud backup → Delete cloud data. Removes the backed-up child progress and pauses backup. The account, parent profile and session are kept so backup can be resumed. Progress on the device is kept.
Delete account. Parent Dashboard → Cloud backup → Delete account. Deletes the authenticated account, its parent profile, and its backed-up child progress, including any legacy mobile number stored with those records. The app removes the local session and parent profile after confirmed deletion. This cannot be undone. Child progress on the device is kept. Entering contact details later does not restore the deleted account.
You can also request account deletion without opening the app, at https://brollysolutions.in/brollywonder/delete-account, or by emailing brollysolutions.in@gmail.com. Include parent contact information to help locate records; a name or mobile number alone does not authorise deletion. Ownership must be established before an account is removed. Contact support for the status and expected completion time of an emailed request.
Deleting active account records does not itself erase service-provider backups or operational logs. Any such retained copies are subject to the applicable service retention and expiry procedures. Contact us for information about retention applicable to your request, including any legal retention obligations.
Clearing the app's storage on the device does not by itself remove the cloud copy, and deleting the cloud copy or the account does not remove the device copy — the two are deliberately separate so that neither action destroys data the parent did not ask to lose.
Advertising information processed by Google is subject to Google's retention controls and privacy policy.
6. Security
We use reasonable measures intended to protect information handled by the app. Parent details and learning information are stored in the app's private storage area on the device. Cloud access uses authenticated Supabase sessions. The app is configured to use encrypted connections, and its database migrations define owner-based access rules for profile and progress rows. Self-reported name and mobile do not authorise access. No method of storage or transmission is completely secure, so absolute security cannot be guaranteed.
7. International processing
Third-party service providers such as Google may process information in countries other than the user's country. Their processing is governed by their privacy terms and applicable legal safeguards.
8. Changes to this policy
We may update this Privacy Policy when the app, its third-party services, or legal requirements change. We will update the effective date at the top of this policy. Material changes may also be communicated through the app or its store listing where appropriate.
Policy revision dated November 3, 2026. Documents release 2.0.3 (version code 7), including sign-up and login with a mobile number, student name and 4-digit PIN (no verification code), PIN reset by mobile number, analytics on by default with an opt-out in Settings, and direct access to parent setup and dashboard, advertising-ID controls and app set ID purposes. Ad configuration uses child-directed treatment without simultaneously enabling the separate under-age-of-consent flag.
Historical policy changes
These entries record earlier releases and are not instructions for the current setup flow.
Changes in the September 30, 2026 version. Parent Name + Mobile setup replaces verification-code entry. Contact details are saved locally and, when available, in a separate cloud parent profile. Existing cloud sessions and user IDs are preserved; new cloud identities use anonymous sessions. This version sends no verification messages and adds no password. Pause, sign-out and recovery limitations are explained above. Optional Android Firebase Analytics support is added with collection off by default, parental controls and restricted event payloads as described above. Historical entries below describe earlier versions, not the current flow.
Changes in the September 28, 2026 version. The verification code is now delivered by SMS first, with the automated telephone call kept as the fallback, and it is sent by MSG91 over India's DLT system — an earlier version named 2Factor.in and described the call as the primary channel. Password sign-in was removed in full. A parent now signs in with their mobile number and a 6-digit verification code every time, and the app no longer asks anyone to create, confirm, store or reset a password; the "create password", "confirm password" and "forgot password" steps are gone, and there is no password stored for any account. Section 1 was rewritten to describe the code-only flow and to record that a sign-in token is kept on the device so that a code is not needed on every launch, and section 5 no longer lists a password among the things account deletion removes. The step order is unchanged: a multiplication question must still be answered before the app asks for a mobile number. Existing accounts were not affected — a mobile number that already had an account signs back into that same account and the same backed-up progress.
Changes in the September 20, 2026 version. A Delete account action was added to the Parent Dashboard, alongside the existing Delete cloud data action, and section 5 now describes both and links the web page for requesting deletion without the app. Full-screen interstitial advertisements were switched off, so the app now serves only a banner on the Kingdom Map and the opt-in rewarded video; section 1 was corrected to match. The banner was removed from the Rewards screen, leaving one advertisement placement per screen. An inaccurate sentence claiming the app was "fully playable with no network at all" was corrected: signing in requires a connection. The full text of this policy is now readable inside the app, under Parent Dashboard → Privacy Policy, as well as at the address above.
Changes in the September 19, 2026 version. Signing in with a grown-up's mobile number became required to use the app, so cloud backup is no longer described as optional. Password sign-in was added: the verification code is now used when the account is created and if the password is reset, rather than every time. A multiplication question must be answered before the app asks for a mobile number. The policy now records that the mobile number is stored alongside the backup row, that a verification SMS may be sent if the call cannot be placed, and that the verification call is placed by 2Factor.in — an earlier version named the wrong provider.
Changes in the August 24, 2026 version. Optional cloud backup was added. It is off unless a parent turns it on, and section 1 describes what is stored, how a parent enables it with their own mobile number and an automated verification call, and how to turn it off or delete it. Sections 4, 5 and 6 were updated to match, and MSG91 was added as the provider of the verification call.
Changes in the August 23, 2026 version. The app no longer requests the Android advertising ID and no longer includes its data in Android's own backup or device transfer; the sections describing those practices were corrected, and the child-directed advertising configuration was described explicitly.
9. Contact us
For questions, concerns, or requests concerning this Privacy Policy or Brolly Wonder, contact:
BrollyEmail: brollysolutions.in@gmail.com
Phone: +91 81868 44555
Address: Metro Pillar No. A689, Dr Atmaram Estates, 3rd Floor, Nizampet X Roads, beside Sri Bhramaramba Theatre, Near JNTU Metro Station, Hyderabad, Telangana 500072, India
This page is the Brolly Wonder Privacy Policy published at https://brollysolutions.in/brollywonder/privacy-policy. The same text is also readable inside the app, under Parent Dashboard → Privacy Policy. Account deletion: https://brollysolutions.in/brollywonder/delete-account. This policy covers the Brolly Wonder app only; the notice for the brollysolutions.in website is at /privacy.