Privacy Policy

Updated 29 September: added in-game support, developer gifts and ranked-run verification, including their retention periods. Closed-test builds may differ as updates roll out.

Last updated: 29 September 2026 · Reinelt Games

This policy describes what information the Roll Blox mobile app ("the app", "we", "us") collects, how it is used, the legal basis on which it is processed, and the rights you have over your data. Roll Blox is developed and operated by Reinelt Games. If you have questions, contact reineltgamesdeveloper@gmail.com.

Request deletion of your Roll Blox account and associated data →

1. Information we collect

• Device identifier. Roll Blox uses a device-specific identifier as the primary key for your in-game account. It is not your IMEI, advertising ID, or any other personally identifying ID on its own.
• Player name. The display name you choose for your game profile. Your player name and submitted Time Crunch scores may be shown on public leaderboards. If you publish a community puzzle, its title, layout, your player name and a public creator identifier are shown to other players.
• Game progress. Levels completed, stars, move counts, Time Crunch scores, challenge progress, fragments and skin unlocks. Build 81 and later also store puzzle-completion fingerprints for creator/community milestones, which Endless variants you played, and which in-game music tracks met a listening goal. These small progress records can be backed up with your linked game save. They do not record microphone audio or music played outside the game. Records from older test versions may also include previously available multiplayer features.
• Community puzzles and moderation. In builds with community publishing, sharing is optional. We store published puzzle layouts, their titles and clear proofs, plus likes, play records, reports, creator blocks and acceptance of the sharing rules. Reports and block lists are private. Search terms are sent to our server to find matching puzzles and are not saved as search history. Drafts stay on your device unless you publish a puzzle; they are not part of cloud progress recovery.
• Optional Google Play Games ID. If you choose to link your account in Settings, we store your Google Play Games user ID so your progress can be recovered on a new device.
• In-app purchase records. If you make a purchase, the receipt is verified with Google Play and a record is stored to prevent abuse. We do not see or store your card or billing details — those are handled entirely by Google Play.
• Optional crash and diagnostic logs. You can turn collection on or off in Settings → Account → Usage & diagnostics. New installations in current closed-test builds default to On; existing saved choices are kept, and older test builds default to Off. This preference does not override a required consent choice. When collection is allowed, Firebase Crashlytics may receive the device model, OS version, app version, installation identifiers and crash stack traces to help us fix bugs.
• Optional in-game support. In builds that include Help & Support, sending a report shares your description, replies, category, game installation/account association, app version/build, device model and operating system, language, display/control/audio settings, equipped skin, mode, difficulty, level, move counts and a bounded puzzle layout where available. Reports contain text and automatic game context only. We do not capture screenshots or attach passwords, sign-in secrets, purchase tokens or unrestricted logs. These private records are held in Supabase and used by Reinelt Games to respond to your request and investigate the issue. Support messages are not included in Firebase analytics events or used for advertising. Choosing to send a support request is separate from the Usage & diagnostics setting.
• Developer messages and gifts. We store messages from Reinelt Games, their eligible recipients and a record of rewards collected by each account. Rewards may include fragments or eligible skins. Collection records prevent duplicate claims and support account recovery. Collected messages disappear from the player inbox; the reward history remains subject to the retention schedule below.
• Ranked-run verification. Updated builds send the sequence of successful Time Crunch moves, elapsed-time summaries and the run identifier when you submit a ranked result. The server reconstructs the generated boards to check the run. We retain a compact assessment and digest with the session, rather than a permanent move-by-move history. Account and app-integrity signals also help protect purchases, rewards and rankings.
• Optional analytics. When Usage & diagnostics is enabled and applicable consent permits it, Google Analytics for Firebase processes device information (such as model, manufacturer and OS version), app-instance identifiers, gameplay events and session activity to help us understand usage, diagnose problems and improve performance. This can include mode and difficulty, level results and retries, menu and editor actions, selected skins and settings, purchase/restore and reward outcomes, and sampled connection and frame-rate measurements. We do not include player-entered names, puzzle titles, draft layouts, passwords or purchase tokens in these analytics events. In build 82 and later, a pseudonymous Support ID can connect permitted analytics and crash reports to an installation for troubleshooting. It is not a sign-in credential. You can turn this off without losing gameplay or purchases.
• Integrity and anti-fraud signals. We use standard device-integrity and anti-fraud checks to detect tampered installations, automated abuse, and cheating. The specific signals used and thresholds applied are not published, in order to preserve their effectiveness.
• Network metadata. Standard server logs (IP address, request timestamps, user-agent) are kept for security, abuse prevention, and debugging.

2. How we use it

• To save and restore your progress across devices.
• To provide online challenges, fragment rewards and account services.
• To run the Time Crunch leaderboard and season rewards.
• To share community puzzles, maintain creator ownership, handle reports and blocks, and moderate content.
• To enforce fair play (anti-cheat checks on submitted scores).
• To verify in-app purchases and grant entitlements.
• To diagnose, fix, and improve the app.
• To respond to your support requests.
• To review security and moderation reports and maintain restricted operational backups.

We do not sell your account data for money. Advertising providers process the data described below; some advertising uses may be considered a sale or sharing under applicable US state privacy laws. Use Ad privacy in the app to access the applicable opt-out choices. We do not use your data to train AI models.

3. Legal basis for processing (GDPR / UK GDPR)

If you are in the European Economic Area, the United Kingdom, or Switzerland, our legal basis for processing your data is:

• Contract. Processing necessary to provide the game itself — saving progress, account services and in-app purchases.
• Legitimate interest. Anti-cheat enforcement, account security and network logs for security.
• Consent. Where required, Google's privacy message gathers consent for advertising and analytics storage. In current closed-test builds, the message's analytics-storage choice also controls optional Firebase analytics and crash-report collection; a declined or unavailable analytics consent signal keeps that collection off. Settings → Account → Ad privacy lets you revisit the available regional choices, and Usage & diagnostics provides a separate off switch. Older test builds require an explicit Usage & diagnostics opt-in. Buying Remove Ads is not the same as withdrawing consent.
• Legal obligation. Tax records related to in-app purchases, where required by law.

4. Third-party services

Roll Blox uses the following third-party services. Each operates under its own privacy policy:

Read how Google uses information from apps that use its services, including Analytics and advertising. Provider information: Google privacy policy, Supabase privacy policy, and Cloudflare privacy policy, and Ollama privacy policy.

Cloud AI processing for internal audit reports was disabled on 29 September 2026. The current daily report uses deterministic checks without sending new reports to Ollama. Earlier reports could include player names and level titles and were not treated as anonymous. Historical processing remains subject to the provider terms linked above; disabling new processing does not itself erase historical provider records.

5. Advertising

Roll Blox uses Google AdMob for automatic interstitial ads and optional rewarded ads. In version 0.5, ad requests wait for Google's User Messaging Platform privacy update and its determination that ads may be requested. Where applicable, the message offers consent, decline and manage-options choices, or US state opt-out choices. Revisit available choices in Settings → Account → Ad privacy. AdMob may process an advertising ID, approximate location inferred from network data and limited device/activity data as described in Google's policies. Android's system advertising controls are also available. Declining personalized advertising does not require an in-app purchase.

Both Remove Ads and No Ads + All Skins remove automatic ads and unlock offline Classic, Laser and Endless after online purchase verification. The bundle includes 76 standard skin presets, excluding ten earned Time Crunch rank skins. Rewarded ads remain optional and online. Time Crunch, including Practice, always requires internet. Purchases do not erase data previously collected by service providers. Optional usage and diagnostic collection is controlled separately.

6. International data transfers

Our hosting, advertising and analytics providers may process data in countries other than your own. Their privacy and data-processing terms describe their international processing arrangements and applicable safeguards. Contact us if you need information about the processing of your account data.

7. Data retention

• Game progress and account data. Kept while your account is active. You can request deletion at any time — your data will be removed within 30 days of a verified request.
• In-app purchase records. Retained as needed to verify entitlements, prevent fraud and meet applicable recordkeeping obligations. Account deletion does not delete purchase history held separately by Google Play.
• Crash and diagnostic logs. Firebase Crashlytics retains crash traces and associated identifiers for 90 days before starting removal from its live and backup systems, as described in Firebase's privacy documentation. Other analytics and diagnostic records follow the relevant service settings and retention policies.
• Support reports and replies. Support reports and their replies are removed after up to 90 days, or 30 days after resolution, whichever comes first, by a daily cleanup. Deleting your game account also deletes its support reports and replies. Restricted operational backups may retain deleted records until those backups expire. Local drafts and a maximum of three unsent reports/replies are kept on the device for up to seven days and pruned when Support is next used. You can discard unsent items in Support, or contact us to request deletion of a sent report without deleting your game account.
• Developer gifts. Unpublished drafts expire after 30 days. Campaign messages and collection history are removed 180 days after the campaign expires by daily cleanup. Collected fragments and skin unlocks remain in ordinary account progress. Account deletion removes its associated claim history.
• Network logs. Retention depends on the hosting service and its configured security and debugging logs. Contact us for information about records associated with your account; we do not promise that every provider deletes every log on the same schedule.
• Community content. Unpublishing removes a puzzle from the public browser. We retain its account-linked record and moderation history while your account remains active. Account deletion also removes your published puzzles, reactions, reports and block list. Copies another player saved as a local draft stay on that player's device.
• Time Crunch results. Scores and season history support rankings, rewards and fair-play checks. Completed run sessions, including compact verification assessments and digests, normally expire after seven days through scheduled cleanup; this does not erase the leaderboard or season result. Account-linked results are covered by account deletion.
• Operational audits. Detailed internal reports and generated Drive audit exports normally expire after 28 days during daily maintenance. Aggregate statistics can remain. Recovery copies are access-restricted, and deletion safeguards must be reapplied before a backup is restored.
• Deletion safeguards. Limited one-way identifiers may be retained to recognize retired installations, prevent deleted progress from being restored and prevent abuse.

8. Security

We use industry-standard measures to protect your data, including:

• HTTPS / TLS for all network traffic between the app and our backend.
• Encryption at rest for our backend database.
• Access controls for private account data, alongside the public leaderboard information described above.
• Server-side verification of in-app purchases and submitted scores.
• No storage of payment card details — payments are handled entirely by Google Play.

No system is 100% secure. If we ever discover a breach affecting your data, we will notify you and the relevant authorities as required by law.

9. Children's privacy

Roll Blox is intended for players aged 13 and over, as declared in our Google Play target audience. If you are a parent or guardian and believe your child has provided personal information through Roll Blox, contact us at reineltgamesdeveloper@gmail.com and we will delete it.

10. Your rights

Depending on where you live, you may have the right to:

• Access the personal data we hold about you.
• Correct inaccurate data.
• Delete your account and personal data. Request account deletion inside the app or by email, even if you no longer have the app.
• Restrict or object to certain processing.
• Receive a copy of your data in a portable format.
• Withdraw consent at any time, where processing is based on consent.
• Lodge a complaint with your local data protection authority.

To exercise any of these rights, email reineltgamesdeveloper@gmail.com. We will respond within the timeframe required by your local law (typically up to 30 days, extendable where the request is complex). There is no fee for exercising your rights.

11. California residents (CCPA / CPRA)

If you live in California, you have the right to know what personal information we collect, the right to delete it, the right to correct inaccurate information, and the right to opt out of any "sale" or "sharing" of personal information. Advertising and analytics providers process information as described in this policy. To exercise your California rights, email us at the address above.

12. Changes to this policy

Policy updates will appear on this page with a revised date. Where additional notice or consent is required, we will provide it before the relevant change takes effect.

13. Contact

Reinelt Games · reineltgamesdeveloper@gmail.com