Brolly Wonder Privacy Policy

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 have accounts and are never asked for an email address or a telephone number. 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 by them when they sign in, described next.

Grown-up sign in and cloud backup

Parent setup. After the adult gate, a parent or guardian enters their name and mobile number and taps Continue. These contact details are saved on the device with a random local profile identifier. This setup works without a cloud connection.

A grown-up has to be present first. Before the app asks for any mobile number it asks a multiplication question that a young child is not expected to answer. The number cannot be entered until that question is answered correctly. The same question already guards the Parent Dashboard.

Cloud identity. Existing authenticated sessions continue to use the same Supabase account. For a new local profile without evidence of an earlier cloud identity on this device, the app can create a Supabase anonymous account when the service is available. The anonymous account supplies a session; the name and mobile do not prove ownership of an account. Accounts are not looked up, merged or restored by matching these details.

No verification message or password. This version does not send verification SMS or calls, request verification codes, or collect or store a password. The mobile number is unverified parent contact information. The app does not send marketing calls or messages to it. Existing server account records are not automatically deleted or rewritten.

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. Name and mobile alone cannot restore access after actual sign-out, session revocation, clearing app storage, reinstalling or changing devices. Earlier cloud records remain stored unless deleted, but may be inaccessible without a separately established recovery method. 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 synchronisation while retaining the session; 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 does not request the Android advertising ID. The permissions that would let the app read a resettable advertising identifier — com.google.android.gms.permission.AD_ID and android.permission.ACCESS_ADSERVICES_AD_ID — are removed from the app when it is built, so the installed app cannot request one.

How advertisements are configured. Every ad request made by Brolly Wonder is configured for a child audience:

• requests are tagged as child-directed;
• requests are tagged as directed to users below the age of consent;
• 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.

Brolly does not sell children's personal information.

Optional app and learning analytics

Brolly Wonder uses Google Firebase Analytics as an optional app-usage analytics service to help improve the learning experience. Analytics is OFF by default and controlled by a parent or guardian. In an Android build configured for Analytics, a parent or guardian can opt in or opt out using "Share optional app usage analytics" in the Parent Dashboard, after completing the parent gate. 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. Declining does not affect authentication, cloud backup or play. Supabase remains the application's authentication, session and cloud-data system.

When enabled, 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, which are not linked to Supabase accounts. Contact us about privacy requests. More information is available in Google's Privacy Policy and Firebase privacy and security information.

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. A child never registers an account, is never asked for a telephone number, and never sees the sign-in form: a multiplication question a young child is not expected to answer stands in front of it, and the account belongs to 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, below the age of consent, "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; that infrastructure has not yet been decommissioned and older versions may still use it. 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. Requests made that way are completed within 30 days.

We do not retain a copy of a deleted account beyond the periods stated here, other than where we are required to keep records by law.

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 transfers use HTTPS, and database access rules restrict profile and progress rows to their authenticated owner. 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.

9. Contact us

For questions, concerns, or requests concerning this Privacy Policy or Brolly Wonder, contact: