Privacy Policy for Rotation Game

Effective date: November 19, 2026

RouSoftware ("we," "us," or "our") provides Rotation Game. This policy explains how information is handled when you use the Android app and the rotate.lol website.

Information stored on your device

Rotation Game does not require an account. Your saved progress and preferences, including scores, answer statistics, response times, streaks, achievements, daily workout progress, theme and reminder settings, and whether ads have been removed, are stored locally on your device. When usage analytics is enabled, gameplay events such as answer statistics, response times and workout outcomes are also transmitted to Firebase as described below. Explicit question reports can include related gameplay details.

Local data is removed when you clear the app's data or uninstall the app, subject to any backup or restore features provided by your device or operating system. This does not delete information already sent to Google or Firebase.

Advertising

The app uses Google Mobile Ads, also known as AdMob, to show interstitial ads and optional rewarded ads that let you continue a game. The Google Mobile Ads SDK may automatically collect and share information such as:

Google uses this information for advertising, analytics, and fraud prevention. Where required, the app asks for advertising consent before requesting ads. You can review or change your consent from Settings > Ad privacy choices when that option is available. You can also manage or delete your advertising ID in Android settings. Non-personalized or limited ads may still involve data processing needed to deliver ads, measure their performance and prevent fraud.

Buying or restoring Remove ads stops the app from requesting or displaying interstitial and rewarded ads. It does not turn off usage analytics or delete information previously collected by Google.

For more information, see Google's Privacy Policy and Google Mobile Ads data disclosure.

Measuring our ads on Instagram and Facebook

We advertise Rotation Game on Instagram and Facebook. To learn which of those ads lead to installs and to players, the app includes the Meta SDK from Meta Platforms. The app sends Meta an event when the app opens (Meta counts the first one as the install) and when you finish your first workout. With each event the SDK sends device information such as the device model, operating system, app version and IP address, an app-specific ID created by the SDK and, on Android, the advertising ID. Scores, answers, purchases and other gameplay are not sent to Meta.

The SDK stays off unless usage analytics is on in Settings and Google's consent check reports that no consent law applies where you are. If the check places you in the European Economic Area, the United Kingdom or Switzerland, it does not start. Events are sent with Meta's Limited Data Use option, which Meta applies in US states with their own privacy laws. Turning usage analytics off stops further events and asks Meta to limit its use of data already sent. You can reset or delete your advertising ID in Android settings.

Meta uses this information to measure and deliver our ads and, under its terms, to improve its advertising products. See Meta's Privacy Policy.

Usage analytics and crash reports

Usage analytics is enabled by default and can be disabled from Settings > Usage analytics. This setting is separate from advertising consent and the Remove ads purchase. We use Firebase Analytics to understand gameplay and Firebase Crashlytics to diagnose errors in release builds.

Question events include the game mode, difficulty, correctness, answer choice, active response time, and a compact code that can recreate the generated question. We also record app starts, screen visits, workout starts and exits, question loading and generation times, ad display and revenue callbacks, purchase and restore outcomes, and controlled test assignments. These measurements help us understand repeat use, question quality, performance, and monetization. Analytics may also collect automatic app lifecycle and purchase events and approximate location derived from IP addresses.

Crash reports can include stack traces, error messages, application state, recent app interactions, and device and app metadata such as model, operating system and app version. Firebase services use identifiers such as Analytics app-instance IDs, Firebase installation IDs, Crashlytics installation IDs and session IDs. We do not ask for a name, email address or account for this collection, but these identifiers mean the data should not be treated as fully anonymous. Advertising ID collection and advertising personalization are disabled for our Analytics configuration; this does not control AdMob's separate data processing.

Turning usage analytics off disables Analytics and Crashlytics collection, resets Analytics data on the device and deletes unsent crash reports. It does not delete data already uploaded. This switch does not disable all Firebase services or Google SDK processing. Explicitly submitted question reports and the technical information needed to provide those services are handled separately.

For details about SDK data handling, see Google Analytics data disclosure and Firebase Android data disclosure.

Gameplay configuration

When usage analytics is enabled, Firebase Remote Config downloads settings for gameplay and controlled tests. Its requests can include country, language, time zone, operating system and platform versions, app and SDK information, and Firebase installation identifiers. Turning usage analytics off stops new Remote Config fetches and returns future quizzes to the default configuration.

Question reports

The Report question button sends only reports you explicitly submit, even when usage analytics is off. Reports contain the issue category, a reproducible question code, question and answer context, difficulty, timing details, submission timestamps, app version, and platform. The report payload does not include a complete question, screenshot, free-text message, name, email address, account, or Analytics app-instance identifier. Google may process network and technical information needed to receive the submission.

We store reports in Cloud Firestore to investigate generation and display issues. Offline reports are saved on your device before upload and retried on subsequent app launches. The pending copy is removed after a successful upload. Turning off usage analytics does not cancel reports you have already submitted or queued.

Purchases

The optional Remove ads purchase is processed by Google Play. Google handles your payment information under its own privacy policy. Rotation Game receives purchase status and verification information needed to unlock or restore the purchase, but we do not receive your full payment card details. The unlocked status is also stored locally on your device.

When usage analytics is enabled, purchase and restore events can be sent to Firebase, including the product, price, currency and outcome. Our custom analytics events do not include purchase receipts, verification tokens or transaction identifiers.

Notifications and time zone

If you enable the daily reminder, Rotation Game asks for notification permission, reads the device time zone, and schedules a local notification at the time you choose. Your chosen reminder time is stored and used on your device. You can disable reminders in the app's settings or revoke notification permission in Android settings. Remote Config may separately receive time zone information as described above.

Daily challenge in the app and on rotate.lol

The daily challenge, in the app and on the rotate.lol website, does not ask for a name, email address or account. When you first open it, Firebase Authentication creates an anonymous user ID and keeps it on your device (in the app's storage, or in your browser's storage on the website) so our server can recognize your run when you come back. The app and the website have separate IDs. Clearing the app's or the site's data gives you a new ID and a new streak.

For each day you play, including past days from the archive, we store in Cloud Firestore, under that ID, which questions you were sent, the answers you gave, whether they were right, the points and answer times, and when each question was sent and answered. This record is what lets the server time and grade your run. It is deleted automatically about 35 days after the day it belongs to, or after you played it if that is later.

We also keep a small player record under the same ID with your current and best streak, the number of days played and the score and number of right answers for up to the last ten years. Runs finished on their own day are added to daily totals (how many players finished, how many got each question right and how scores are spread) that do not contain your ID. These totals are what the "you beat N% of players" line is computed from and are public on the site. Archive runs are compared with those totals but not added to them.

In the app, the daily challenge's own records are sent to our server whether or not usage analytics is on, since the server grades every answer. When usage analytics is on, the app also records daily challenge events such as starts, finishes and scores in Firebase Analytics, as described above.

To see how many people visit and play, the website uses Google Analytics for Firebase, the same service the app uses. It stores two Google Analytics cookies (_ga and _ga_FE8WLJ38EF) in your browser so that later visits from the same browser count as one visitor. They last up to two years after your last visit. If your browser is set to a European time zone, or hides its time zone, the site asks before it loads Google Analytics, and it loads nothing for analytics unless you choose Allow. Your answer is kept in your browser, and clearing the site's data asks again. Google Analytics receives the pages you open, the site that linked you there and any campaign tags in the link, your browser and device type, and an approximate location derived from your IP address. It also receives the game's own events. These are starting a day, whether each answer was right, its points and how long it took, finishing and the score, sharing, saving the result image and tapping the app links. Google signals and advertising personalization are off for the website, and it sets no advertising cookies. You can block these cookies in your browser settings or install the Google Analytics opt-out add-on.

Google's servers that host the site and run its functions receive your IP address and browser information as part of each request. The site may use Firebase App Check with Google reCAPTCHA to tell browsers apart from automated scripts, in which case reCAPTCHA processes information about your browser and device under Google's terms. The Play Store links on the site carry a tag saying they came from rotate.lol, so we can count installs from it.

To have your daily challenge records deleted, write to ege@rousoftware.com with the date and score of one of your runs, and say whether you played in the app or on the website. We will find and delete the records that match. Daily totals stay as they are, since they cannot be traced back to you.

Sharing and security

We do not sell your personal information. Google handles information to provide advertising, consent management, app distribution and purchases. Meta receives the install and in-app events described under "Measuring our ads on Instagram and Facebook". Firebase processes analytics, crash reports, gameplay configuration and submitted question reports. We may export Analytics events to Google BigQuery for historical analysis and produce aggregate reports. These exports are separate from your saved local progress.

Firebase and Google Mobile Ads encrypt transmitted data using HTTPS or Transport Layer Security. Access to stored question reports is restricted: app users can submit validated reports, but cannot read other reports or delete them through the app. Google services handle information under their applicable terms and Google's Privacy Policy.

Retention and deletion

Analytics event data follows the retention settings configured for the Analytics property. Exported Analytics data in BigQuery is stored separately and is subject to its own storage and retention settings; deleting or expiring data in Analytics does not automatically delete an exported copy. Crash reports follow Firebase Crashlytics' retention practices. Submitted question reports are retained for investigating issues and improving question generation and display. The app does not set an automatic expiry date for those reports.

Clearing app data, uninstalling, disabling usage analytics or buying Remove ads does not automatically delete previously uploaded data. The app has no account to delete, and apart from the daily challenge records described above, no automatic server-side deletion feature. For questions or requests concerning retention or deletion, contact ege@rousoftware.com. Because reports do not contain account details and analytics uses app-specific identifiers, we may be unable to identify which stored records belong to you without further information. Do not send payment details or other sensitive information with an inquiry.

Children's privacy

Rotation Game is not specifically directed to children under 13, and we do not knowingly collect personal information directly from children. If you believe a child has provided personal information to us, contact us so we can address the concern.

Changes to this policy

We may update this policy when the app or applicable requirements change. We will update the effective date at the top of this page when we do.

Contact

For privacy questions, contact RouSoftware at ege@rousoftware.com.