Privacy Policy

1. Controller

The controller for the processing of your data is Ron Jan Walkowsky, c/o flexdienst – #20573, Kurt-Schumacher-Straße 76, 67663 Kaiserslautern, Germany (see Imprint). For questions about data protection you can reach us using the contact details given in the imprint. A data protection officer is not required by law.

2. Principle

Our apps work without a user account, show no advertising and include no third-party analytics or advertising libraries. No profiling takes place, and no data is sold or passed on for advertising purposes.

What you enter or achieve in an app stays on your device. If something does leave your device, it is described in the sections below – completely and in detail.

3. What stays on your device

Everything created while using an app is stored locally: settings, saved games, best times, plans, lists, history. This data is not transmitted to us. We have no access to it and do not even learn that it exists.

Details about health, nutrition or training likewise remain solely on your device – they never reach us or any third party, not even in aggregated or anonymised form.

Uninstalling an app deletes all its local data; you can also reset an app's data at any time in your device settings.

4. Notices in the app and anonymous reach measurement

On start-up, our apps ask a server operated by Aynari whether a notice is waiting – about a new version, say, or about a fault. Three things are transmitted: a randomly generated identifier (UUID), which language version you use, and which app it concerns.

The identifier is created on your device the first time you open the app. It is a random string with no connection to your person, your Google account or a device-wide advertising ID. It serves two purposes: a notice you have dismissed should not come back, and we want to be able to count on how many devices an app is opened at all. The transmission is encrypted (HTTPS). Delete the app and install it again, and a new identifier is created – the old one cannot be matched to the new one.

With Minesweeper 3D the game additionally reports how its introductions are used: whether one was offered, declined or started, whether it ran to the end or at which point you skipped it, and whether you opened the rules page. Each time, only that single piece of information is transmitted – without the identifier mentioned above, without a timestamp and without any other identifier. We count how often each answer occurs and do not learn whom it came from. This can be switched off in the game's settings; notices are unaffected.

Not transmitted are saved games, times, streaks, health or training data, search terms or details about your device. The identifier is not passed to third parties and not combined with any further personal data.

How long. An entry is deleted once no request has come from that device for twelve months – along with the record of which notices were dismissed there. Keep using the app and you keep your identifier; otherwise dismissed notices would come back. Only the aggregated daily figures remain, and those can no longer be traced to any device.

Where. Our server is located in a data centre within the European Union. This request transfers no data to a country outside the EU. It is different for Google Play Games – see section 7.

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in being able to deliver current notices and in knowing the reach of our apps in anonymous form. You may object to this processing under Art. 21 GDPR.

5. Access data when connecting

As with any request over the internet, your device technically transmits its IP address to our server, along with the time and the address requested. These details are needed for the answer to reach your device and serve operational security. They are not combined with the identifier described in section 4. We do not put your IP address into any database; what the web server underneath records technically is described in the following paragraph.

Access data. As with any website request, log entries are created on the server – IP address, time, the address requested, the amount of data transferred and whether the request succeeded. They arise for technical reasons, serve operation and defence against attacks, and are neither evaluated by us nor combined with anything else. The log starts afresh each day; entries older than 14 days are deleted. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure operation).

Limiting the event counter. So that nobody can flood this counter with made-up reports, the server accepts only a limited number of them per sender and hour. For this, the IP address is not stored but turned into a check value computed from the address and the current hour (SHA-256), which is deleted after two hours and can no longer be traced to any address. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a service safe from abuse).

6. Notifications and reminders

Reminders – of a training session, an open task, or of the app itself after a longer break – are scheduled and triggered entirely on your device. Nothing goes to us and nothing to third parties; we learn neither whether a reminder appeared nor whether you responded to it.

The operating system asks for permission before the first notification. You can switch reminders off again at any time, in the app or in your system settings.

7. Google Play Games Services

Leaderboards, achievements and the backup of your saved game run through Google Play Games Services. They are optional: without signing in, everything can be used fully; only these services are then missing.

If you do sign in, Google processes your Play Games player ID and the results you achieve – your times or scores for the leaderboards, your progress for the backup. We ourselves receive no data about you: we can see neither who is signed in nor who ranks where.

The controller for this processing is Google Ireland Limited or Google LLC. Their privacy policy applies. You give your consent by signing in (Art. 6(1)(a) GDPR) and can withdraw it at any time by signing out.

8. Purchases through Google Play

Paid content is handled exclusively by Google Play. We receive neither your payment details nor your name or address, but only the information from Google as to whether a purchase exists for your account – which is all an app needs in order to unlock the content bought.

9. Voice input

Voice control is evaluated entirely on your device. Nothing is recorded and nothing is sent to a server – neither to us nor to third parties. The operating system asks for the microphone permission beforehand; without it, only voice control will not work.

10. Permissions

Our apps request only the permissions they actually need: internet access for notices and Google Play Games, vibration for tap feedback (can be switched off), notifications solely for reminders (can be switched off), and the microphone solely for voice control.

Location, contacts, photos, phone state or advertising IDs are not requested by our apps. Which of these permissions an app actually needs is shown before installation in its Google Play listing.

11. Advertising and tracking

Our apps contain no advertising and no third-party trackers or analytics tools. No data is passed to third parties for advertising or marketing purposes. The reach measurement described in section 4 takes place exclusively on our own server; no personal profiles are created in the process.

12. Recipients

Our web host operates aynari.de and the notice server and acts for us as a processor under Art. 28 GDPR: Host Europe GmbH, Gertrudenstraße 30-36, 50667 Cologne, Germany.

Google – for distribution through Google Play and, if you sign in, for Play Games Services. Google also processes data in the USA. The transfer is based on the EU-US Data Privacy Framework or on standard contractual clauses.

13. Retention

Local data remains until you delete it or uninstall the app. The random identifier is deleted on our server once no request has come from that device for twelve months – on your device it lives as long as the installation, and a reinstallation creates a new one. The server logs are deleted after 14 days, the check value of the counter limit after two hours – both described in detail in section 5. Data held in Play Games rests with Google and follows their retention periods; you can view and delete it in your Google account.

14. Your rights

Under the GDPR you have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and the right to object to processing based on legitimate interests (Art. 21). Consent once given can be withdrawn at any time with effect for the future.

Locally stored data you can delete yourself at any time – by uninstalling the app or resetting the app's data in your device settings.

A practical note: since we store no additional details alongside the random identifier, we cannot assign it to a person. For a request for access under Art. 15 GDPR you would have to tell us the identifier yourself – otherwise we are not in a position to identify you (Art. 11 GDPR).

For matters under the GDPR you can reach us using the contact details given in the Imprint. Independently of that, you have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR) – in particular with the authority at your place of residence, your place of work or the place of the alleged infringement.

15. Data security

We use technical measures to protect the data stored locally on your device. Depending on the app this may include encrypted databases or other security mechanisms. Every connection to our server is encrypted end to end (HTTPS).

16. Children

Our apps are not directed at children under 13. We do not knowingly collect personal data from children and do not ask for anyone's age.

17. Changes to this policy

If something changes about our apps or about the legal situation, we adapt this policy. It carries the date of its version at the bottom. Should a change require more than a statement, namely your consent, we will ask you beforehand.

The current version is always available on this page.

As of 29 August 2026