1. Controller and scope
Domenic RauHeinestr. 20/6
75236 Kämpfelbach
Germany
Email: Rau.Onlinebusiness@gmail.com
This notice covers Knobelpause on Android and iOS. The Google features below apply to Android versions offering them. Older Android versions may continue using the previous direct Drive sync. iOS builds offering in-app sync use iCloud; builds without it store progress locally. Processing when visiting this website is explained in the website privacy notice.
2. Playing and local storage
Knobelpause can be played offline without a separate account. The app stores game saves, running games, completions, results, playing times, progress values, and game, display, and input settings locally in app storage on your device, where relevant to the game.
These records provide the game, resume supported games, and display progress. Local storage or access strictly necessary for the game functions you expressly request is based on section 25(2)(2) TDDDG. Where personal data is involved, Article 6(1)(b) GDPR applies because processing is necessary to provide the requested game functions.
The app does not send this game information to me or a player database I operate. Knobelpause does not synchronise progress unless you activate it. Optional Android leaderboards, Google sync and import of older Drive backups are described separately in section 5. The platform distinction below applies to iOS builds offering iCloud sync.
Local data normally stays on your device until deleted using available app functions, device settings, or uninstalling the app. Uninstalling usually removes local app data. Existing operating-system backups may remain independently or restore data on reinstallation.
3. Advertising and technical services
Knobelpause contains no advertising and operates no usage-analytics, advertising-profile or Firebase service of its own. When optional Android Google features are used, Google's Play Games SDK nevertheless processes its own analytics and diagnostics. A blanket statement that no analytics or diagnostic service is integrated therefore does not apply to these Google features. Section 5 explains this; platform reports and TestFlight are described below.
Playing Knobelpause requires no access to contacts, location, camera, or microphone. For optional Android sync, the app uses the network status reported by Android to avoid sync requests when known to be offline and synchronise pending progress when connectivity returns. Knobelpause operates no separate external connectivity-test service. Processing independently performed by Android, Google Play, Apple, or the device manufacturer is separate.
4. App stores and device backups
When buying, downloading, or updating through Google Play or Apple’s App Store, the store provider processes account, payment, device, and transaction data under its own responsibility. Knobelpause does not handle payments itself. As developer, I may receive order/refund information, submitted reviews, and platform technical-quality reports through the respective store.
I use order information where necessary for contract fulfilment or refunds (Article 6(1)(b) GDPR) and legal obligations (Article 6(1)(c) GDPR). The legitimate interest for technical-quality reports and feedback is troubleshooting and supporting the app (Article 6(1)(f) GDPR). Applicable statutory retention duties apply to personal records; other records are needed only as long as their purpose requires.
Depending on device, account, and backup settings, your operating system or backup provider (including iCloud when enabled) may back up, transfer, or restore app data. This is separate from Knobelpause’s own progress sync. Manage these backups in your device or backup provider’s settings.
For Google services in the EEA, the provider is generally Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Processing outside the EU or EEA may occur. Google's Privacy Policy and your device/backup provider's information apply. For Apple services, see Apple’s Privacy Policy.
TestFlight (iOS beta testing)
In TestFlight betas, Apple automatically shares crash and usage data with me; this cannot be disabled in TestFlight. Depending on your invitation and feedback, this may include your name/email, comments, and screenshots. I use these only to test and improve Knobelpause (Article 6(1)(f) GDPR) and delete my copies when no longer needed for that purpose. See Apple’s TestFlight privacy notice for Apple’s processing and retention.
iOS builds offering optional iCloud sync
Where offered by your iOS build, optional sync uses your Apple Account's private CloudKit database for completed progress, results and selected puzzle settings. Unfinished puzzles, layouts and device settings stay local. It is off until enabled; disabling it retains local and existing cloud data. The app does not access other iCloud documents or send these saves to the developer. Apple manages account access and storage; Knobelpause does not receive your Apple password. Builds without the feature store progress locally. This does not introduce Google leaderboards on iOS.
5. Optional Google features (Android)
Optional Google Play Games leaderboards (Android)
You can open leaderboards under Settings → Social → Leaderboards. Ordinary local play does not require a Google Play Games profile. The app initializes Google's Play Games SDK when you explicitly use a Games feature. If you separately enable Play Games cloud sync, later startup/resume may initialize the SDK and restore the existing session without an interactive sign-in request. Google may connect the Play Games profile selected in your Google settings and show its own account or ranking UI.
Submitting scores is a separate choice, off by default on each device. Enabling it stores your choice and the selected Play Games player identifier locally. While it is enabled, opening leaderboards sends eligible, already earned lifetime bests/totals to Google: longest streak, completed-puzzle count, stars, and best ranked results for Pattern Recall, Math Sprint and Sequence Echo. Existing eligible achievements are included. Raw puzzle boards, unfinished games, move histories, layouts and Google Drive access tokens are not submitted to leaderboards. This does not enable cloud save synchronization.
Google receives the scores and processes the associated Play Games identity and technical service information. Rankings can show your gamer name, avatar, score and rank according to your Google profile's visibility settings. Google's SDK also documents automatic analytics and diagnostics for SDK stability and product improvement. Knobelpause has no separate advertising or usage-analytics service. Google's service connections use HTTPS; Google's privacy information describes its own processing and retention. Knobelpause does not provide end-to-end encryption that hides these service data from Google.
Turning score submission off stops future score submissions from this device. It does not delete scores already held by Google, disconnect every other device, or undo Google's SDK initialization in the current app process. You can manage your Play Games profile, game data, visibility and deletion through Google Play Games or your Google account. Google's per-game instructions are available at https://support.google.com/googleplay/answer/9130646. These controls do not promise erasure of all technical data independently retained by Google. Local saves, cloud backups and older Drive backups are separate copies.
Optional Play Games progress sync and existing Drive backups (Android)
Cloud sync is separate from leaderboard submission. Enabling it stores an account-binding marker and sync choice locally and sends eligible completed progress, results/history, statistics, tutorials and explicit puzzle settings to Google Saved Games for your Play Games profile. Existing local and imported progress is merged. Unfinished boards, undo/redo, timers, layouts and general device settings stay local. Sync can run on startup/resume and after eligible changes while enabled; there is no independent always-running background service.
Importing an older Google Drive backup requires a separate explicit action and the drive.appdata permission. The app reads only its own hidden Drive data, confirms the destination profile and merges progress without replacing device settings. Original Drive backups are not changed or deleted. A pending import is not a confirmed Saved Games backup. Disabling sync stops future app-initiated backup requests, keeps local/imported progress and does not delete Google's existing backups or undo SDK initialization in the current process. On iOS, builds offering in-app sync use iCloud; builds without it retain local progress.
Saved Games still requires Google's Drive API internally; retiring Knobelpause's direct Drive sync does not remove every Google storage dependency. Google's SDK data-handling and account-managed deletion information also applies to this flow.
Synced progress/history and older recovery parts remain until removed; the app has no automatic age-based cloud cleanup. Disconnect sync and turn submission off on every device before deleting game data; retained local copies can be uploaded again if you later re-enable the features. Older Drive backups must be managed separately in Google Drive's Manage apps settings. The app has no remote cloud-deletion function and the developer cannot access your private Google storage to erase it for you.
The legal basis for the optional score and progress transfers initiated by Knobelpause is consent under Article 6(1)(a) GDPR. You can withdraw it for future transfers using the separate sync and submission controls. This does not erase earlier data or determine the legal basis for Google's independent service processing. See the existing recipient/transfer and rights sections.
Older versions: direct Google Drive synchronisation
The existing information below continues to apply to older Android versions with direct Drive sync. The new Play Games version uses that access only for an explicitly chosen read-only import; existing backups are retained.
Your choice: Connection and synchronisation activate only when you explicitly choose “Connect Google & enable sync” in Settings and authorise Google access. You can decline or cancel and play completely offline. Declining does not cause repeated automatic sign-in prompts. You can start later in Settings. The purpose and legal basis are the cross-device progress synchronisation you voluntarily choose and consent under Article 6(1)(a) GDPR. Disconnecting withdraws that consent for the future.
Storage and access: The app reads and writes only its own hidden app-data area in your selected Google Drive account. It requests only https://www.googleapis.com/auth/drive.appdata. It receives no general access to other Drive files and does not request your email address or Google profile through a separate profile permission. The developer operates no central player database and receives neither your sync files nor your access token.
Transfer and encryption: HTTPS provides transport encryption between the app and Google Drive; data is not transmitted openly over the internet. Sync files contain structured JSON progress data. Knobelpause does not additionally encrypt their contents with its own key. It therefore provides no end-to-end encryption against Google as storage provider. The hidden app-data area and Google authorisation limit access but do not replace additional content encryption.
Transferred data: completed puzzle/tutorial identifiers, results, stars, playing times and completion histories, including completed-attempt statistics; attempt counters and selected puzzle options. Random installation/attempt and Drive-area association identifiers, version and change metadata support correct merging. These can be personal data when associated with your Google account. They are not advertising or hardware identifiers.
Stays local: running puzzles, boards, notes, undo/redo, hints and timers, layouts, language, sound and general device settings. Completed-attempt statistics do not restore a running puzzle.
Google connection: The app uses Google's Android authorisation through Google Play services. Google processes the selected account association and necessary technical connection, device, app, and access information, including the IP address involved in network connections, for authorisation, security, and service delivery. The app keeps short-lived access tokens only in memory; Google manages its own authorisation/token storage. Existing authorisation can be renewed without a dialog. If renewed consent is needed or the account does not match the stored connection, sync pauses. No separate Knobelpause account is created.
Operation and retention: enabled sync runs on start/resume, progress changes and “Synchronise now”; transmission while the app is closed is not guaranteed. Pending progress, merged data, sync metadata and a backup made before the first import remain local. Cloud progress and history, including older file parts, are retained until deleted; there is no automatic age-based cleanup.
Disconnecting and deleting differ: Disconnect stops further sync on this device and discards the access token. Imported progress, the local backup, and cloud files remain. Disconnect other connected devices separately. You can additionally revoke Google authorisation under Connections in your Google account; revocation does not delete existing cloud files. In Google Drive in a browser, use Settings → Manage apps → Knobelpause → Options → Delete hidden app data to remove the hidden area. Disconnect every device first so it cannot upload again. Uninstalling the Android app does not delete the Drive app-data area. Android → Apps → Knobelpause → Clear storage removes local app data, including imported achievements and backups; this is irreversible and separate from Android/Google backups. I have no remote access to delete your private local or Drive files for you.
Google receives sync data as provider of your chosen account and Drive service. In the EEA, the provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Processing outside the EU/EEA is possible. Google's Privacy Policy and the Google Drive terms explain worldwide processing and retention. Knobelpause uses Google API data only for the described synchronisation, not advertising, sale, profiling, or AI training. Its use and transfer comply with the Google API Services User Data Policy, including Limited Use requirements.
International Google transfers: The described services may involve processing by Google LLC in the USA. Google explains that, within their respective scope, it relies on adequacy decisions, including the EU-US Data Privacy Framework for appropriately certified US companies. Where adequacy decisions do not cover transfers, Google uses standard contractual clauses where needed. Its transfer-framework information explains the applicable grounds, certification, and how to request copies of clauses. This information also applies to the Google Play processing described above and the Gmail mailbox below.
Contact form and email
For support, I process your sender address, message and information you choose to send, using Gmail, to answer your enquiry. The basis is Article 6(1)(b) GDPR for contract-related enquiries, otherwise Article 6(1)(f), with the legitimate interest of providing support. Correspondence is deleted when no longer needed for the enquiry and follow-up, unless legal retention duties or legal claims require storage. Contact is voluntary; sufficient information and a reachable address are needed for a reply. No game save or device report is attached automatically. The website privacy notice explains the shared form, email providers and spam protection.
Your rights
Where the legal conditions are met, you have rights of access, rectification, erasure, restriction and data portability. You may object to processing based on Article 6(1)(f) GDPR on grounds relating to your particular situation. You may withdraw consent for the future without affecting earlier lawful processing. Contact Rau.Onlinebusiness@gmail.com. You may complain to a data protection authority, including the Baden-Württemberg authority.
8. Changes to this notice
The notice is updated when app processing changes. The date above records the last substantive update.