Privacy policy






Privacy Policy – Math Kingdom



Privacy Policy

App: Math Kingdom
Package name: com.forebear.mathkingdombuilder
Effective date: 08 Jun 2026

This Privacy Policy explains how Math Kingdom
(“the App”, “we”, “us”, or “our”) handles information when you use
the App.

Math Kingdom is a children’s educational app. Based on the current
version of the App, most information is stored only on the user’s
device and is not sent to our servers.

1. Information We Collect

The current version of the App may store the following data locally on the device:

  • Child profile information such as a profile name and avatar selection.
  • Learning progress, rewards, stars, streaks, and kingdom progress.
  • Parental control information, such as a hashed parent PIN.
  • Basic app state, such as whether onboarding has been completed.

The App currently does not require account creation
and does not ask users to submit email addresses,
phone numbers, precise location, contacts, photos, camera data, or
microphone recordings.

2. How We Use Information

We use locally stored information to:

  • save a child’s learning progress and unlocked content;
  • remember app settings and onboarding state;
  • support parental access controls; and
  • provide the core educational and game-like features of the App.

3. Data Sharing

Based on the current version of the App, we do not sell personal
information and we do not intentionally share user data with
advertisers, data brokers, or external analytics providers.

If we later add online services such as analytics, crash reporting,
cloud sync, sign-in, subscriptions, or customer support tools, we
will update this Privacy Policy before those changes are used in
production.

4. Children’s Privacy

Math Kingdom is designed for young learners. We aim to limit data use
to what is necessary for the App to work.

Based on the current implementation, the App stores progress and
profile data locally on the device and does not knowingly collect
children’s personal information for online use.

Google Play requires children’s apps to provide a privacy policy, and
FTC COPPA guidance requires clear notice about children’s data
practices. See:
Google Play User Data policy
and
FTC COPPA FAQ.

5. Storage and Retention

The data described above is generally stored on the user’s device
using local app storage.

Local data is typically kept until it is removed by the user, the
user clears the app’s storage, or the app is uninstalled.

Some temporary media files may be created on the device during app
playback operations, such as audio handling on certain platforms.
These temporary files are used only for app functionality.

6. Security

We use reasonable steps within the current app architecture to protect
locally stored information. However, no method of storage or
transmission is completely secure.

The current parent PIN is stored in hashed form on the device. This
helps avoid storing the plain PIN directly, but it should not be
treated as bank-grade security.

7. Third-Party Services and SDKs

The current app build includes third-party libraries for core app functions such as:

  • audio playback;
  • text-to-speech;
  • local storage; and
  • animations and UI rendering.

Based on the current codebase, these libraries are used for app
functionality rather than for advertising or user analytics.

8. International Users

If the App is made available in multiple countries, local laws may
give users or parents certain privacy rights. You should review this
policy with legal counsel if you plan to launch broadly or add online
services.

9. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. If we make
material changes, we will update the effective date above and revise
the policy made available with the App and/or on the public policy
page.

10. Contact Us

If you have questions about this Privacy Policy, contact:

Company name: Forebear Productions
Contact email: saurav@forebearpro.com

11. Important Publishing Note

Before using this policy in production, review it carefully and make
sure it exactly matches the live app, the Google Play Data safety
form, and any future SDKs or backend services you enable.



    See How We Can Help!