Wondermio: Privacy Policy

Lumisoft Studio is the app’s publisher and the controller for the processing under its responsibility described in this policy. For privacy and parental requests, contact support@lumisoftstudios.com. Apple, Google and RevenueCat explain their respective roles and data practices for their services in their own terms.

No account or exact date of birth is required. An optional nickname, age group or grade, language, avatar and learning preferences, activity results, skill summaries and progress are stored in the device’s database. Lumisoft Studio does not receive that database; child profiles and learning results are not sent to RevenueCat or the ad network. There is no child-to-child chat or social feed.

Settings, last-verified purchase rights and ad-frequency records are also stored locally. The ad counter is shared across the device and contains no child identity. Parent and teacher areas, purchases and external links sit behind a parental gate. That gate does not replace verifiable parental consent where required by law.

Adults can export a backup or report to a destination they choose through the device’s share menu. These files may contain profile and progress information; the recipient’s or cloud service’s policy applies. In-app deletion does not delete exported copies. The device’s own backup settings may also apply.

Teacher QR scanning is available only when an adult opens the feature and grants camera access. Images are processed on the device; the app does not save photos, video or audio, or send QR images or decoded codes to a verification server. The teacher verification service is currently inactive. Microphone and precise-location permissions are not requested.

The Android QR component uses Google ML Kit. On-device image processing does not mean there is no technical telemetry: Google processes device and app information, installation identifiers, API usage events, performance and error metrics to operate and diagnose the service and prevent abuse. This flow is independent of removing ads. Details: Google ML Kit Terms & Privacy

Google Mobile Ads (AdMob) is integrated on both iOS and Android. The iOS 1.0.0 (7) and Android versionCode 12 internal test builds use only Google test ad units. Live ad units are disabled in the current configuration; enabling them in a later release requires separate compliance and device checks. Test ads still connect to Google; a test label does not mean that no data is transmitted.

In a free build with advertising available, every five completed activities across the device create at most one interstitial ad opportunity. An ad may appear at a natural break, such as leaving a result screen: at least five minutes apart and at most three times in the preceding 24 hours. Ads are not shown to the 2–4 age group, in the first session, in the first two minutes after launch or during an activity. There are no banner, app-open or rewarded ads; learning content is not unlocked by watching an ad. An incomplete load is skipped. An ad may load in the background before it is displayed.

Ad requests are marked child-directed, with under-age-of-consent settings, a G content limit and non-personalized requests. The app does not request behavioral ad personalization. Android’s advertising ID (AD_ID) and Privacy Sandbox advertising permissions are removed. On iOS, the app does not request ATT (App Tracking Transparency) permission or ask to use the IDFA advertising identifier. Child profiles are not supplied for ad targeting.

These limits do not eliminate all technical identifiers or data transmission. Google explains that its advertising service can process IP addresses and approximate location inferred from them, app- or developer-scoped device identifiers, ad impressions and interactions, crashes, performance and other diagnostics to deliver and measure ads and prevent fraud. No location permission does not prevent IP-based location estimates. The app’s current configuration and the SDK’s general capabilities are different. Google’s data practices: Google Privacy Policy

RevenueCat verifies and restores monthly and yearly Family Premium and the permanent Remove Ads entitlement. It processes a random customer identifier generated by the SDK, product and transaction information, purchase tokens or receipts, purchase and expiry dates and subscription status. Connections can also involve an IP address, platform, app and operating-system version, store region, language and currency. The purposes are purchase verification, entitlement delivery, synchronizing refunds and renewals, and purchase statistics.

Connections are not limited to pressing a purchase button: status is checked at launch, on returning to the app and during restoration. Previously purchased direct-store entitlements can be synchronized to RevenueCat. Child names, profiles, learning progress and contact details are not supplied as customer attributes. RevenueCat’s automatic advertising/attribution identifier collection and optional diagnostics feature are disabled; this does not stop purchase-data processing. Details: RevenueCat Privacy Policy

Apple App Store / StoreKit handles iOS payments; Google Play Billing handles Android payments. Card numbers and store-account passwords are not sent to Lumisoft Studio. The stores’ payment and account data are governed by their own policies: Apple Privacy Policy and Google Privacy Policy

Family Premium, including a valid trial, prevents new ad requests while active. Remove Ads is a one-time, non-consumable purchase; it does not auto-renew or unlock Premium content. Refunded or revoked entitlements are updated according to the store’s verified status. Use Parent Panel > Restore Purchases with the same store account; this does not restore child progress. Uninstalling the app does not cancel a subscription.

Ad-free access does not delete earlier ad records or disable RevenueCat purchase verification or the Android QR component’s technical processing. There is no separate general usage analytics or crash-reporting service in the app; the SDK processing above is distinct.

Delete profiles and progress through Parent Panel > Privacy and data. The in-app reset preserves purchase rights and ad-frequency limits; it does not erase every technical record or the RevenueCat customer record. Uninstalling can cause local records to be lost; manage device and cloud backups separately.

We keep support emails only as needed to answer the request and meet applicable legal obligations. You can ask us to delete a RevenueCat customer record; we must first identify the relevant record securely. This does not delete store transaction records or cancel a subscription. Retention by Apple, Google and RevenueCat depends on each service’s obligations and policies; we do not promise a single deletion period for every provider.

Where KVKK or GDPR applies, rights may include information, access, correction, erasure, restriction, objection, portability where applicable, and withdrawal of consent. Withdrawal does not affect prior lawful processing. You may complain to the competent data protection authority. Manage local child data in the app; for support or service records under our control, email support@lumisoftstudios.com. We ask only for information needed to verify the request and parental authority; do not send passwords or a child’s photograph.

Purchase verification can rely on providing the service requested by an adult, support correspondence on answering the request, and necessary security and record processing on applicable legal obligations or legitimate interests. Valid consent is separately required where the law calls for it. Where COPPA applies, parents’ rights to review and delete child data and refuse further collection must be respected; exceptions for internal operations do not extend to all advertising. Child-directed ad tags alone do not establish KVKK, GDPR or COPPA compliance or verifiable parental consent.

Apple, Google and RevenueCat infrastructure may process data outside your country, including in the United States. We do not transfer the child’s local learning database to these services; the service and technical data above may be processed across borders. Providers’ privacy documents explain their processing and transfer practices. Applicable transfer requirements and legal safeguards must be met separately; this policy is not itself transfer consent or evidence that a particular safeguard is in place.

Service connections use encrypted transmission. Protect your device and exported files; no storage or transmission method can guarantee absolute security.

We update this page and required notices when data practices change. The date above identifies this version. Significant changes may require additional notices or consent under applicable law. For privacy questions: support@lumisoftstudios.com.