RoviLoop

RoviLoop Privacy Policy

Last updated: 27 September 2026

This policy explains how RoviLoop: Coding Game for Kids (Android package com.revaltronics.roviloop) handles information. The app is operated by [LEGAL_DEVELOPER_NAME] ("we", "us" or "our"). Privacy contact: [PRIVACY_EMAIL].

At a glance

1. Profiles and information stored on your device

RoviLoop stores player names or nicknames, selected avatars and colours, locally generated profile identifiers, creation/update times, puzzle attempts, stars, block-count records, tutorial completion and settings. This information makes it possible to keep separate progress for up to four local players and resume the game later. Please use a nickname rather than a child's full name.

The game does not upload these profile records to a developer-operated account or cloud-save service. Player names, local profile identifiers and entered text are not included in our custom analytics events or ad requests.

Android backup and device-to-device transfer are enabled for the game's saved data. Depending on your device and backup settings, your backup provider may store or transfer copies of profiles, progress and preferences under its own policies. A restored backup can restore earlier saves and settings. You can manage backups through your device or backup account settings.

2. Optional usage analytics

We use Google Analytics for Firebase to understand which parts of RoviLoop are used and improve the game. Collection is disabled by default. A grown-up can enable or disable Share usage data in Settings → Usage privacy. This choice applies to every local player on that installation; gameplay does not require it.

When enabled, custom events describe screens visited, puzzles started or completed, program runs and stops, retries, hints, completed lessons, player creation or selection, and ad loading or display. Event details are limited to predefined screen names, puzzle/world identifiers, command types, counts, outcomes and numeric error codes. They do not include player names, profile identifiers, ages, entered text or the contents of a child's program.

Google Analytics also processes app-instance identifiers, device and app information, and session/activity information. This information is not necessarily anonymous. The integration disables advertising-ID collection, advertising personalization and advertising-related consent categories for Analytics.

Turning sharing off stops future Analytics collection and resets Analytics data on the device. Events discarded while sharing is off are not later replayed. Turning sharing off does not automatically delete information previously received by Google. Restoring default game settings also turns usage sharing off.

3. Advertising and advertising privacy

RoviLoop uses Google AdMob for banner ads on selection screens and interstitial ads at certain completed-puzzle transitions. Ads do not interrupt an active puzzle. The Android TV version does not initialize AdMob or display ads. The current game has no in-app purchases.

Ad requests are configured for child-directed treatment, a general-audience content rating and non-personalized advertising. The app removes Android advertising-ID and Ad Services advertising-ID, topics and attribution permissions. We do not attach player names, progress, custom targeting or our own user identifiers to ad requests.

Non-personalized ads still involve data processing. Google's Mobile Ads SDK may process IP addresses (including approximate location inferred from them), app and ad interactions, performance/diagnostic information and permitted app/device identifiers, such as an app set identifier, depending on the SDK configuration. Google uses this information for ad delivery, measurement, service operation and fraud prevention. Removal of advertising-ID access does not mean that every form of technical identifier is absent.

Google's User Messaging Platform checks applicable advertising privacy requirements and manages relevant privacy choices. Where available or required, these controls can be opened in Settings → Ads & privacy, behind the grown-ups gate. Optional usage sharing and advertising privacy are separate controls.

4. Voice hints

If voice hints are enabled, RoviLoop passes game-provided hint text to the device's selected Android text-to-speech service. The app does not record speech or request microphone access. The speech service may process text locally or online according to its settings and provider's privacy policy. Voice hints can be disabled in Settings.

5. Children and parental choices

RoviLoop is designed for children. It does not provide public profiles, chat, user-to-user messaging or a requirement to disclose a child's real name, email address, date of birth or location. Advertising uses the child-directed configuration described above, and optional usage sharing starts off.

Parents or guardians can manage or delete local profiles, reset progress, leave optional analytics disabled, and contact us about information associated with their child's use. Please do not send a child's full name or other unnecessary personal details in a support request. If you believe personal information about a child has been provided to us inappropriately, contact [PRIVACY_EMAIL] so we can investigate and address it.

6. Providers, support and disclosures

Google processes information through AdMob, the User Messaging Platform and, when enabled, Google Analytics for Firebase. Android backup and text-to-speech providers may separately process information as explained above. We do not operate a data marketplace or sell player profiles. Advertising-related processing by Google is described in this policy and is not excluded by that statement.

If you contact us, we receive your email address and whatever information you choose to include, and use it to respond and resolve the request. We may disclose information when legally required or necessary to protect users, investigate abuse or secure the service, subject to applicable law.

For more information, see the Google Privacy Policy, How Google uses information from apps, Firebase privacy information, and Google Mobile Ads data disclosures.

7. Retention and deletion

Local profiles and progress remain until you delete them, clear the app's storage or uninstall it. To delete a profile and its progress, use Settings → Manage players and the profile's delete control. Resetting progress clears puzzle records but does not delete the profile. Clearing storage removes all local players and settings. Backup copies may remain with your backup provider and may be restored; manage those copies separately through the provider's controls.

Our Google Analytics event/user-data retention setting is [ANALYTICS_RETENTION_PERIOD]. Aggregated reports may be retained separately from event-level information. Advertising and privacy-choice records are retained according to Google's applicable policies and service requirements. Support correspondence is retained while needed to handle the request and meet applicable legal obligations.

You can ask us about access, correction or deletion using [PRIVACY_EMAIL]. We do not hold server-side copies of local player profiles, and a nickname alone cannot identify an Analytics app instance. We will explain what can be located or deleted and any necessary verification, without asking for unnecessary information about a child. Disabling Analytics, deleting a local player or uninstalling the app does not by itself erase data previously processed by Google.

8. Security and international processing

Local saves use Android app-private storage. Google Mobile Ads encrypts data in transit using TLS. No storage or transmission system can guarantee complete security. Google and other device-service providers may process information on servers outside your country under their applicable privacy and data-transfer terms.

Depending on your location, you may have rights to access, correct or delete personal information, withdraw consent, object to or restrict certain processing, request portability, or complain to a privacy authority. Contact us to make a request. Available rights and any exceptions depend on applicable law.

9. Changes and contact

We may update this policy when the app or its data practices change. The revised policy will show an updated date. Where required, we will provide additional notice or obtain a new choice before materially changing how information is used.

Developer/operator: [LEGAL_DEVELOPER_NAME]

Privacy and parental requests: [PRIVACY_EMAIL]