Privacy

Privacy Policy

This Privacy Policy explains how the Android app GRIMLORE: Profane Truths (package name com.totalmadownage.grimloreprofanetruths) processes data.

Last updated: 30 September 2026

1. Controller

Total Mad Ownage

Heiko Jacobs TMO Consulting

Alte Landstraße 20, 53902 Bad Münstereifel, Germany

Email: grimscribe@grimlore.online

The developer or provider named in the Google Play Store must correspond to the information in this section.

2. Summary

The game does not require a proprietary user account and does not transmit save data to a server operated by the developer. Settings, save data and local high scores are generally stored on the device. Google services are used for advertising, consent management, Google Play Games achievements, in-app purchases and, where applicable, Android backups. These services may transmit data from the device to Google.

3. Local game and settings data

In particular, the app stores the following data locally on the device:

  • save data, checkpoints, progress, high scores and Rogue Run snapshots;
  • earned rewards, unlocked content and markers indicating achievements already submitted;
  • music and sound-effect volume, dictionary selection and validation mode; and
  • the time at which the most recent interstitial advertisement was shown, to limit advertising frequency.

This data is used exclusively to provide game functionality, resume games, retain settings and limit advertising frequency. The app does not transmit it to a server operated by the developer. The legal basis is Article 6(1)(b) GDPR insofar as the processing is necessary to provide the game.

Android backup and device transfer

The app permits Android backup functionality. Depending on the device and Google Account settings, Android may encrypt and back up local app data to the Google Account or Google Drive and restore it following a reinstallation or on a new device. Android or Google controls this functionality. Users can manage backups in their Android or Google Account settings. Further information is available in the Google Privacy Policy.

4. Google Play Games

The app uses Google Play Games Services to check the authentication status of an existing Play Games profile, display the achievements interface and submit earned achievements. Platform authentication may take place in the background when the app starts. This does not create a separate game account.

Google may process gamer identity data (such as gamer name and avatar), a game-specific player ID, technical analytics and diagnostic data, and unlocked achievements. The app currently does not use friends lists, online leaderboards, Play Games cloud saves or server-side Google sign-in.

For users in the European Economic Area and Switzerland, the provider is generally Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Processing takes place to provide the Play Games features activated by the user on the basis of Article 6(1)(b) GDPR and, where consent is required, Article 6(1)(a) GDPR. Profile and gameplay data can be managed and deleted through the Play Games profile or Google Account. The Google Privacy Policy also applies.

5. Advertising and consent management

The app uses the Google Mobile Ads SDK (GMA Next-Gen SDK) to display interstitial advertising. Google User Messaging Platform (UMP) is used to present required privacy information, request consent and provide a way to change privacy choices later. The app initializes advertising only when the UMP SDK permits ad requests.

According to Google, the Mobile Ads SDK may automatically collect and transmit the following data to Google or integrated advertising partners:

  • IP address, from which an approximate location may be derived;
  • interactions with the app and advertisements, such as app launches, clicks and video views;
  • diagnostic and performance data, such as launch time, hang rate and energy usage; and
  • device and account identifiers, particularly the Android Advertising ID, App Set ID and, where applicable, other identifiers linked to an account signed in on the device.

This processing is used to deliver and measure advertising, perform analytics, and prevent fraud and abuse. Depending on region, consent and AdMob configuration, advertisements may be personalized, non-personalized or restricted. Advertising technology providers identified in the consent interface may be additional recipients.

Where required by law, storing information on or accessing information from the end device is based on consent pursuant to Section 25(1) TDDDG, and the subsequent processing of personal data is based on Article 6(1)(a) GDPR. Consent may be changed or withdrawn at any time with future effect under Settings → Privacy choices. Insofar as processing is strictly necessary for security and fraud prevention, it is based on Article 6(1)(f) GDPR; the legitimate interest is the secure and abuse-free operation of the advertising service.

Further information is available in Google’s advertising information and the Google Privacy Policy.

6. In-app purchases through Google Play

Optional digital content is offered through Google Play Billing. Google processes the payment. The app receives the information required to unlock and acknowledge the purchase, in particular the product ID, purchase status and purchase token. The app does not use a proprietary payment backend and does not receive complete payment details such as credit-card or bank-account data.

Google stores and processes transaction data in accordance with the terms applicable to Google Play. The developer may receive transaction-related information in the Google Play Console for billing, support and refunds. The developer processes this data on the basis of Article 6(1)(b) GDPR. The Google Payments Privacy Notice and the Google Privacy Policy also apply.

7. Permissions and services not used

The app does not request permissions in its own manifest for precise location, camera, microphone, contacts, calendar, telephony or local media files. At the time of this Policy, it does not use proprietary web analytics, Firebase Analytics, Crashlytics or a proprietary web service for storing user or gameplay data. Network access is generated by the Google services described above.

8. Recipients and international data transfers

Recipients of the data described in Sections 4 to 6 are Google companies and, depending on advertising choices and configuration, additional advertising technology providers named in the consent interface. Processing may also take place outside the European Union or European Economic Area. According to Google, such transfers are based on applicable adequacy decisions and/or appropriate safeguards such as the EU Standard Contractual Clauses. Details are provided in Google’s privacy information and the notices of the relevant advertising partners.

According to Google, the Google SDKs encrypt the data they transmit while it is in transit.

9. Retention and deletion

  • Local game and settings data remains stored until it is reset in the game, the app data is deleted through Android, or the app is uninstalled. Backup copies may remain for longer in accordance with Google’s backup settings and retention periods.
  • Play Games data and achievements are stored according to the settings and retention rules of the Google Account and can be deleted through the Play Games profile or Google My Account.
  • Google retains purchase and payment data in accordance with statutory retention duties and the Google Play terms.
  • Advertising, consent, analytics and diagnostic data is retained in accordance with the policies of Google and the participating advertising partners. The app does not maintain its own database for this data.

10. Data subject rights

Subject to the applicable statutory requirements, data subjects have the right to access, rectification, erasure, restriction of processing, data portability and objection. Consent can be withdrawn at any time with future effect. Data subjects also have the right to lodge a complaint with a competent data protection supervisory authority.

Requests concerning processing by the developer can be sent to grimscribe@grimlore.online For data processed by Google under its own responsibility, users may additionally use Google’s privacy and account controls or contact Google directly.

11. Children

The game is not specifically directed at children. In the UMP configuration, the app is not identified as an offering for users below the applicable age of consent. If the game is offered to children through Google Play’s target-audience settings in the future, the advertising and privacy configuration and this Policy will be updated before publication.

12. Changes to this Policy

This Privacy Policy will be updated if the app’s features, SDKs, data flows or legal requirements change. The current version is available at this URL.