Privacy policy

Skriptum — macOS privacy information / Datenschutz

Updated September 13, 2026 · Skriptum 1.0 · Deutsch · English

ROWPOP — iPhone and iPad

ROWPOP has app-specific privacy information covering local gameplay, Apple purchases and Game Center, Google AdMob, Firebase Analytics, Crashlytics and Remote Config, your choices and your rights. Read the full notice in English or Deutsch. Contact ROWPOP Support for help.

Habinity — iPhone and Apple Watch privacy information

Habinity helps you build routines, record check-ins and reflect on your progress. This section describes Habinity 1.0 and the services actually used by this release. Read it together with the controller, website, international-transfer and rights information on this page. The other providers in the shared service directory are not automatically used by Habinity.

Your device, habits and journal

You can start without creating a Habinity account. Your identity statement, chosen areas, habit names and schedules, reminders, check-ins, streaks, achievements, preferences and onboarding draft are stored on your device. Optional mood records, journal entries, tags and voice memos are also stored locally. These records provide the features you select and let you resume your routines. Habinity does not operate a separate server that receives your private habit or journal database.

Saved journal edits and new voice recordings are encrypted by the app using AES-GCM, with keys stored in the Apple Keychain. Older local recordings are migrated to encrypted storage when they are synchronised or exported. Microphone access is requested when you choose to record a voice memo. Recordings are not sent to a transcription or cloud AI service. If a required encryption key is unavailable, an encrypted entry cannot be opened until the key becomes available; the app does not replace it with a plaintext cloud copy.

Apple Health and sensitive information

Apple Health is optional. With your permission, Habinity reads supported step count, sleep, mindful-session, water-intake and active-energy information on the device to recognise relevant habit check-ins. You can choose the permitted data types in Apple's permission interface and change access in the device's Health privacy settings. With a separate Apple Health write permission, Habinity can save the measured active intervals of a mindful focus-timer session as mindful minutes. An ordinary check-in without a measured session does not invent a health measurement.

The app separately asks for explicit consent before processing health-related mood and journal information or using its health features. You can withdraw this consent in the app's privacy settings and manage or delete existing records separately. Where health information is processed, the applicable consent condition is Article 9(2)(a) GDPR, alongside Article 6(1)(a). Giving permission to read Apple Health is separate from choosing any other sharing feature. Health information is not used for advertising, tracking or data brokerage.

Apple Health values, mood records and health-related habits are excluded from Habinity's personal iCloud projection and Family sharing. The exclusion covers habits linked to Apple Health and habits in fitness, mindfulness, sleep or nutrition areas, together with their check-ins. Mood associations and check-in notes are not uploaded through personal sync. Device backups and Apple's own Health or iCloud settings are separate platform features. See Apple's Health App privacy information.

Optional personal iCloud sync

Personal iCloud sync is off until you explicitly enable it. When enabled with an available Apple account, Habinity uses Apple's private CloudKit database to synchronise eligible general habits, including their names, schedules, icons, check-in dates and streak information. Your local identity profile, mood records and the health-related records described above are not included.

Journal entries remain local by default, including existing entries. You must additionally select the per-entry option to sync a general note. Notes with mood tags or links to health-related or unknown habits are excluded. This option is intended for general notes: do not include medical or other health information in notes you choose to sync. An eligible note's associated voice memo can be included.

Selected personal record contents and voice files are encrypted by Habinity with AES-GCM before upload. When you enable sync, the necessary keys can synchronise through Apple's iCloud Keychain so that your other devices can decrypt them. The same Apple account, available keys and platform configuration are needed for recovery. Apple still processes the technical account, connection and storage information needed to run iCloud. This personal encryption arrangement does not describe Family sharing.

Turning sync off stops new uploads and keeps your local data. It does not by itself erase copies already in iCloud. A change of Apple account pauses sync and requires a new choice for that account. Requested cloud deletions may need the original Apple account to be connected again before they can finish.

Apple Watch, widgets and reminders

The companion Apple Watch app exchanges habit information and check-ins with your paired iPhone using Apple's WatchConnectivity framework. This paired-device exchange is distinct from personal iCloud sync. Widgets and supported system actions use the app's shared on-device storage to show or update your routines. They do not send your journal or voice recordings to a Habinity server.

If you allow notifications, habit and trial reminders are scheduled on the device and can display relevant habit or subscription information. You control notification permission and previews in device settings. Apple's CloudKit notification service can also signal changes to enabled cloud records; Habinity does not use a separate marketing-push provider.

Family and shared routines

Family sharing is optional and asks participants to confirm that they are at least 16 and agree to the sharing disclosure. You can create or join one group with up to six participants through an Apple CloudKit share invitation. You explicitly select eligible general habits to share. Other participants can see your chosen display name, the selected habit's name and icon, streak and current-day check-in, and predefined emoji reactions. Do not include health or other sensitive information in shared names. Journals, voice memos, mood records and health-related habits are not shared with the group.

Family records are stored in Apple's CloudKit sharing service and are accessible to invited participants. They do not use Habinity's additional private-journal encryption. You can change the selected habits, leave the group or, as owner, delete it. Changes and removal requests are queued if the service is unavailable and are retried; already shared information can remain visible until Apple confirms the change. Copies independently made by another participant are outside the app's deletion controls.

Coaching, diagnostics and purchases

Coaching uses local templates or, on supported devices when available, Apple's on-device Foundation Models framework. The identity context and streak information used for a suggestion are processed on the device. Habinity does not send your journal, health records or coaching context to an external AI provider.

Habinity has no advertising, cross-app tracking or third-party behavioural analytics SDK. Optional MetricKit diagnostics, such as launch, memory and crash information, are handled locally by the app; this release has no telemetry upload endpoint. Apple's own platform diagnostics and sharing settings are separate. Contacting support or opening this website involves the correspondence and website processing described below.

Apple handles purchases, payment details and subscription billing. Habinity uses StoreKit to verify product and transaction identifiers, purchase dates, expiry, refunds and entitlement status so that it can unlock or restore Pro. Habinity does not receive your payment-card details and does not use RevenueCat or a separate purchase backend. You can manage or cancel subscriptions through your Apple account. Deleting local or cloud app data does not cancel a subscription. Apple's standard licensed application agreement applies to the app.

Retention, deletion and your rights

Local records remain until you delete them or remove app data, subject to your device's storage and backup controls. The app offers data export and deletion controls in its privacy settings. Deleting a journal entry also removes its local voice file and queues removal of any synchronised copy. Removing all Habinity data records cloud and sharing deletion requests before clearing local content. If offline, keep the app installed and reconnect the relevant Apple account so queued requests can finish. The app reports pending cloud deletion; encryption keys required for cleanup are retained until those deletions are acknowledged.

Removing the app alone does not necessarily erase iCloud records, device backups, Apple purchase records or copies you exported or shared. A file exported through the system share sheet goes to the destination you select, which has its own storage and privacy arrangements.

Providing the local app and requested purchase benefits is based on Article 6(1)(b) GDPR. Optional personal sync and Family sharing are based on your choices and consent under Article 6(1)(a); you can withdraw consent for future processing through their controls. Health-related consent is explained above. Necessary security processing can rely on Article 6(1)(f), and legally required records on Article 6(1)(c). This policy is information, not a consent request. Apple processes platform information under its own Privacy Policy; its services can involve processing outside the EU/EEA as explained in the general transfer section.

For support or privacy requests, contact Fabio Blankenhorn, Konfora Apps, at hallo@konfora.de and identify Habinity. Please send only information needed for your request. We may not hold a copy of information that exists only on your device or in your private Apple storage. The rights and supervisory-authority information below apply.

Larply — iOS privacy information

Larply creates AI images and videos from text, selected photos and templates. This section describes Larply 1.0 and identifies the services actually used by the app. The other services in this directory are not automatically part of Larply.

Accounts and authentication

Supabase provides Larply’s account service, database and file storage in Frankfurt, Germany. We process your account identifier, email address, optional display name, login records, credit balance and subscription status to provide your account and purchases. You can sign in with Apple, an email code, or an email address and password. Apple may provide a private relay email address if you choose Hide My Email. Credentials and session tokens are handled by Apple or Supabase; the app stores its session in the iOS Keychain.

Login and confirmation emails are sent using Resend in its EU region, from login@go.konfora.de. Resend processes the recipient address, message and delivery information. Open and click tracking are disabled for this sending domain. Login codes expire after ten minutes. Contact and support remain available at hallo@konfora.de.

Your prompts, photos and generated media

When you request a generation, Larply sends your prompt, chosen reference photos, selected settings and the required file links through its backend to fal, which runs the configured ByteDance Seedance and Seedream models. Larply shows a disclosure before your first generation. Only submit content you are entitled to use, including permission from people shown in reference photos. Cloud generation is optional; selecting a photo in the iOS photo picker does not give Larply access to your whole photo library.

Prompts, generation settings, job identifiers, status and credit usage are associated with your account so that jobs can resume and completed work can appear in your library. Uploads in Larply’s storage are scheduled for deletion after seven days. Generated result files are scheduled for deletion after thirty days; save anything you want to keep to Photos or Files before it expires. The cleanup job runs periodically, so deletion is not guaranteed at an exact minute. Account records and job metadata can remain until account deletion. Provider copies and technical logs follow the providers’ own retention rules.

Purchases

Apple handles the payment. Larply does not receive your payment-card details. Its backend verifies App Store transactions and processes product and transaction identifiers, dates, subscription expiry, refunds and an app-account identifier to deliver credits, restore purchases and prevent duplicate fulfilment. Subscription benefits and unused credit balances are separate: an expired subscription does not by itself erase unused paid credits.

A backend endpoint hosted by Vercel in Frankfurt verifies the digital signatures on Apple’s purchase notifications before Larply processes them. These signed notifications can contain the purchase identifiers, app-account identifier and subscription information described above. This endpoint does not receive your prompts, photos or generated media.

Storage on your device and sharing

Larply keeps app settings, your session, generation history and cached media on your device. Exporting to Photos or Files creates a copy under your device’s storage controls. Content you share through the system share sheet goes to the destination you select. Those exported or shared copies are not deleted by removing the Larply account.

Deletion and your choices

Use Profile → Delete account to delete your Larply account, stored uploads and results, generation records and credit records from the active service. For an Apple-linked account, the app may ask you to authenticate with Apple again so that the backend can revoke Apple’s authorization. Removing the app alone does not delete your cloud account. Account deletion does not cancel an Apple subscription: manage or cancel it in your Apple account’s subscription settings. Provider backups, operational logs and any records required by law follow their applicable retention periods.

Purposes, recipients and rights

Providing your account, requested generations and purchased benefits is based on Article 6(1)(b) GDPR. Necessary security and abuse prevention are based on Article 6(1)(f), and legally required recordkeeping on Article 6(1)(c). Where a separate consent is required for a particular operation, that consent is collected in context; this notice is not itself consent. Larply does not embed advertising, behavioral analytics or cross-app tracking SDKs.

See Supabase’s Privacy Policy, Resend’s Privacy Policy and Apple’s Privacy Policy. International processing may occur, including when media is generated by fal and its model infrastructure. EU hosting of the account database does not mean every operation stays within the EU. The sections on international transfers and your rights below also apply. Contact Fabio Blankenhorn, Konfora Apps, at hallo@konfora.de for requests concerning Larply.

Dock Out — iOS and Android privacy information

This section describes Dock Out version 1.0, currently being prepared for release. It supplements the shared information below about support, international transfers and your rights. Other providers listed on this page are not automatically used by Dock Out.

Progress, preferences and game features

Dock Out requires no game account. Level progress, earned coins, onboarding completion and music, sound, haptic and reduced-effect preferences are stored on your device. Local records support continued play and your chosen settings. This version has no game-operated cloud save, player chat, purchases or subscriptions. Game coins have no cash value.

Audio, graphics and the tutorial are included in the app. Playing does not send your inputs to an AI service. Haptic effects use the device's feedback capabilities. Dock Out does not request access to contacts, microphone, camera or precise location.

Advertising and your choices

Dock Out uses Google AdMob for optional rewarded videos and interstitial advertisements between levels. A rewarded offer identifies its benefit before you choose to watch it. Declining a rewarded offer does not stop ordinary play.

The advertising SDK may process IP addresses, approximate location derived from connection information, device identifiers, advertising views and interactions, and diagnostic or performance data. Purposes include ad delivery and measurement, advertising personalisation where permitted, and fraud prevention. Non-personalised ads can still involve personal data.

Google's User Messaging Platform (UMP) updates the advertising consent status at startup. The app requests advertisements only when the SDK permits it. Where required, a consent form presents the available purposes, providers and choices. You can reopen required advertising privacy options from Settings; changing them discards previously loaded advertisements before new requests. Choosing to watch an ad is separate from consenting to data processing.

Consent can be withdrawn for the future through the applicable privacy controls. Where consent is required, the relevant legal basis is Article 6(1)(a) GDPR and, where applicable, Section 25(1) TDDDG. The consent message, not this policy, records your choices. Device and platform privacy settings may provide additional controls. See Google's Privacy Policy and Google's advertising information.

Analytics, support and retention

This release configuration does not initialise GameAnalytics or AppLovin MAX. Google advertising diagnostics remain part of the processing described above. Apple's and Google's platform diagnostics and store records are separate from the game's local save.

Local data remains subject to your device's storage and backup controls. Removing local app data does not erase records already held by advertising or platform providers; backups may retain separate copies. Provider retention depends on the relevant service and purpose. Contact us for information relevant to your request.

Opening support or privacy links involves the website processing described below. If you email hallo@konfora.de, include Dock Out and enough information to explain your request. Support does not automatically receive your saved progress. The controller, transfer information and rights described on this page apply to Dock Out; contact Fabio Blankenhorn, Konfora Apps, at the address above for privacy requests.

Yokai Road — privacy information

This section explains the data processing for version 1.0 of Yokai Road on iOS, which is currently being prepared for release. Read it together with the sections on website visits, contact, international transfers and your rights in the Konfora Apps privacy policy. The other providers in that website's service directory are not automatically used by Yokai Road.

Who is responsible

Fabio Blankenhorn, Konfora Apps, Heppstr. 17, 72760 Reutlingen, Germany. For privacy requests and support, contact hallo@konfora.de and identify Yokai Road. Do not send passwords or payment-card details.

Intended audience

Yokai Road is intended for players aged 13 and over. The content age rating displayed by your app store is separate and may differ by region and operating system. The game does not ask for an age or date of birth and has no separate age-selection screen. Advertising uses age-restricted treatment. Optional gameplay analytics is controlled through the shared Google privacy message.

Online progress, accounts and community features

Players receive a guest account through Google Firebase Authentication. The authoritative game progress is stored in Cloud Firestore and processed by Cloud Functions in Frankfurt, Germany. This includes equipment, heroes, currencies, progression, battles, rewards, pending decisions and the times required for daily or return rewards. The game retains a local cache and a journal of pending decisions so that an interrupted connection does not duplicate a reward or lose a confirmed decision. Music, sound and vibration preferences remain on the device.

You can optionally link an email address and password in Settings to recover the same account on another installation. Firebase Authentication processes the email and authentication credentials; passwords are not stored in the game's Firestore documents or sent to RevenueCat. A guest account that has not been linked may become inaccessible after local account data is removed. Signing into another account switches progress; it does not merge two accounts.

Clans, rivals, rankings and chat connect real players. Other players can see your generated game name, clan membership, contributions, ranking and the game statistics needed for those features. Chat sends only the game's predefined replies. You can block or unblock players and report messages. Reports include the reported message and the involved account identifiers and are available to authorised moderators, who can remove a message or restrict community features.

Google Firebase App Check and Apple's App Attest help verify that requests come from the game. Service requests and operational logs can include account or request identifiers, IP addresses and technical request information. These checks and the server's booking records help prevent unauthorised access, duplicate rewards and abuse. Providing accounts, progress and requested community features is based on Article 6(1)(b) GDPR; necessary service security and abuse prevention on Article 6(1)(f). See Firebase's privacy information. The general policy's international-transfer information also applies to provider processing outside Germany.

Test builds use a separate test economy and separate game accounts. Test purchases do not credit production progress.

Purchases and subscriptions

Apple handles App Store purchases and the payment details you supply to the store. Yokai Road uses RevenueCat to check purchases and subscriptions, restore access and determine which benefits are available. This processing can occur when the game checks your entitlements, including at startup, as well as when you purchase or restore.

Relevant data includes your Firebase game account identifier, product and transaction identifiers, purchase history, entitlement status and technical device information. The game uses the same account identifier with RevenueCat to assign and restore purchases. An optional account email is not sent to RevenueCat by the game. A generated account identifier can still distinguish a customer and is not a promise of anonymity.

The game keeps server-side booking records so that a transaction does not grant the same consumable twice. Providing the game and requested purchase benefits is based on Article 6(1)(b) GDPR; necessary fraud prevention on Article 6(1)(f), and legally required recordkeeping on Article 6(1)(c). RevenueCat also uses purchase information for purchase and subscription reporting in its dashboard. See RevenueCat's Privacy Policy and Apple's Privacy Policy.

You can manage or cancel an App Store subscription through your Apple account. Deleting the game or game account does not cancel a subscription. Game progress and store entitlements are different records; restoring a purchase does not by itself restore a deleted game account.

Optional rewarded advertising and privacy choices

Yokai Road uses Google AdMob directly for optional rewarded advertisements. The game tells you the offered benefit before you choose to watch a video. For server-side reward verification, the game sends its account identifier and a single-use reward request identifier to AdMob; Google sends a signed callback to the game server, which confirms and books the reward.

Google AdMob is configured with age-restricted treatment for teens and a maximum ad content rating of G. Google UMP presents the applicable privacy message before advertising is requested and provides access to privacy choices from Settings. The same message also covers Google Analytics storage. Advertising delivery can involve connection IP addresses, ad views and interactions, diagnostics, performance measurement and fraud prevention. Non-personalised advertising does not mean that no personal data is processed.

The game does not request Apple App Tracking Transparency permission or use advertising identifiers for cross-app tracking.

Where consent is required, the relevant processing is based on that consent and can be withdrawn for the future through the applicable privacy controls. The applicable consent message identifies the advertising purposes and participating providers before you make your choices. This page does not itself grant consent. See Google's advertising information and Google's Privacy Policy.

Notifications and reviews

If you allow notifications, Yokai Road schedules local reminders using the device's notification service. The game does not upload a server-push token for those reminders. You can manage notification permission through the device settings.

The game may offer Apple's native review interface. Apple handles submitted reviews through its platform. Opening that interface does not give the game your App Store account or a copy of your review.

Gameplay analytics

The new version uses Google Analytics for Firebase to understand game usage and improve gameplay. The Google privacy message provides the applicable choice for analytics storage together with advertising privacy choices; there is no separate analytics prompt or switch. Analytics collection starts disabled and is enabled only after Google reports an allowed analytics-storage choice or that consent mode does not apply. Missing, denied or unconfigured signals keep collection off. You can review or withdraw your choice through Settings → Privacy choices. In the EEA, the legal basis for optional analytics is consent under Article 6(1)(a) GDPR and, where applicable, Section 25(1) TDDDG.

Firebase Analytics can process app-instance identifiers, app and device information, sessions, approximate geographic information, automatically detected in-app purchase events and usage events, such as completed battles, equipment choices and claimed rewards. These identifiers are pseudonymous, not a guarantee of anonymity. The game does not supply Firebase account IDs, emails, chat text, passwords, receipts or command payloads to Analytics. It disables Analytics advertising storage, advertising user data and personalised-ad signals; the iOS Analytics integration omits IDFA support and disables IDFV collection. See Firebase privacy information and how Google uses information from partner apps. Analytics processing is separate from the Frankfurt game database and may involve international transfers described in this policy. PostHog is no longer an active integration.

Diagnostics, support and websites

Opening the privacy or support website involves the website processing explained in the general Konfora privacy policy. If you contact support, the information you choose to send is used to address your request. Support requests are handled separately from the game database; authorised operational access may be used when needed to investigate your account or request.

Retention, requests and your rights

Game profiles remain while the account is active. Chat history is removed after 30 days, reports and moderation audit records after 180 days, temporary rival caches after one day, and unneeded reward requests after two days. These periods are enforced by the next successful scheduled cleanup. Full command responses are removed or reduced after 30 days; a small replay marker can remain while needed to protect the current game revision. Minimal pseudonymous purchase-booking keys and account-deletion markers are retained to prevent old transactions or deleted accounts from being restored as new rewards. These records do not contain an email, raw account identifier or full receipt.

You can request account deletion in the game’s Settings. Linked accounts require the password again. The server immediately prevents further use of the account and then removes the profile, community records and other direct account references, requests deletion of the RevenueCat customer, and deletes the Firebase Authentication account. Failed cleanup attempts are retried. The app also stops Analytics and resets its local analytics data and app-instance identifier. This local reset does not itself erase data already transmitted to Google. References within other players’ historical command responses and operational logs can remain within their applicable retention periods. Purchase and subscription records that Apple must retain, and records independently processed by advertising providers, are subject to those providers’ arrangements and applicable legal requirements.

Turning Analytics off stops future collection on this device and resets local Analytics data. Google Analytics is configured to retain event and user data for two months, without resetting the retention period when a user returns. This setting does not apply to most aggregated standard reports. Earlier transmitted records remain subject to these settings and applicable erasure rights. The game does not set a Firebase account ID as an Analytics User-ID. Separate privacy requests can be sent to our contact address. Any records from earlier PostHog test builds remain covered by their original consent and can be addressed through support; removal of an integration is not evidence that historical provider records were erased.

Firestore point-in-time recovery retains versions for seven days; daily backups expire after 14 days. Deleted data can remain in those protected backups until expiry. Recovery procedures must reapply deletion records before a restored database is used. Local records and device backups remain subject to the device's storage controls. Deleting one record does not delete every provider's copy.

For a request about data processed for Yokai Road, contact hallo@konfora.de. Include enough information to identify the app and request. Additional information may be needed to locate a purchase-related record; do not send passwords or full payment details. If information exists only on your device, we may not hold a copy of it.

The general Konfora privacy policy explains the applicable rights of access, correction, erasure, restriction, portability, objection and withdrawal, and how to complain to the competent supervisory authority. For information about a particular provider record or retention arrangement, contact us and identify the app and request. The shared sections on this page explain international transfers and provider information.

Sweetdoku — iOS and Android privacy information / Datenschutz

Updated September 30, 2026 · Sweetdoku 1.0 for iOS and Android · Deutsch · English

Deutsch

Diese Angaben beschreiben Sweetdoku 1.0 für iOS und Android. Verantwortlich ist Fabio Blankenhorn, Konfora Apps, Heppstr. 17, 72760 Reutlingen, Deutschland, hallo@konfora.de. Die übrigen Anbieter im allgemeinen Verzeichnis dieser Seite werden dadurch nicht zu Diensten von Sweetdoku.

Spielstand und Einstellungen

Sweetdoku benötigt kein Konto. Levelfortschritt, Münzen, gesammelte Süßigkeiten, Tagesrätsel-Serie, Tutorial-Status sowie Einstellungen für Ton, Musik, Vibration, Auto-X und Farbmuster werden nur auf deinem Gerät gespeichert. Es gibt keinen Cloud-Spielstand und keinen Chat. Münzen haben keinen Geldwert und können nicht ausgezahlt werden. Musik, Grafiken und Rätsel sind in der App enthalten; Spielen überträgt deine Eingaben an keinen Server. Die App fragt keine Kontakte, kein Mikrofon, keine Kamera und keinen genauen Standort ab.

Einwilligung beim Start

Beim Start zeigt Sweetdoku über die User Messaging Platform (UMP) von Google eine Einwilligungsabfrage an, sofern das für deine Region erforderlich ist (z. B. im EWR, im Vereinigten Königreich und in der Schweiz). Du kannst zustimmen, ablehnen oder einzelne Zwecke und Anbieter auswählen. Die Abfrage gilt für Werbung (Google AdMob) und für die Analyse (Google Analytics for Firebase). Deine Auswahl kannst du jederzeit unter Einstellungen → „Privacy Options" ändern oder widerrufen. Rechtsgrundlage ist deine Einwilligung nach Art. 6 Abs. 1 lit. a DSGVO und § 25 Abs. 1 TDDDG.

Werbung (Google AdMob)

Sweetdoku zeigt Anzeigen über Google AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Irland): freiwillige Videos mit Belohnung (z. B. ein zusätzlicher Tipp oder mehr Münzen) und gelegentlich Vollbildanzeigen zwischen Leveln. Das Werbe-SDK kann dabei IP-Adresse, daraus abgeleiteten ungefähren Standort, Geräte- und Werbekennungen, Informationen zu Anzeigen und Interaktionen sowie Diagnose- und Leistungsdaten verarbeiten, um Anzeigen auszuliefern und zu messen, Betrug zu verhindern und – soweit du eingewilligt hast – Anzeigen zu personalisieren. Ohne Einwilligung werden, soweit zulässig, nur nicht personalisierte oder eingeschränkte Anzeigen angefordert; auch diese können personenbezogene Daten verarbeiten. Anzeigen sind auf Inhalte beschränkt, die für alle Altersgruppen geeignet sind. Auf iOS erklärt Sweetdoku zunächst kurz, wofür die Werbe-ID genutzt wird, und fragt dann über Apples App-Tracking-Transparenz (ATT) um Erlaubnis. Nur wenn du „Erlauben" wählst, darf Google AdMob die Werbe-ID (IDFA) für personalisierte Werbung und deren Messung verwenden; du kannst das jederzeit unter iOS-Einstellungen → Datenschutz & Sicherheit → Tracking ändern. Die Einwilligungsabfrage für den EWR, das Vereinigte Königreich und die Schweiz gilt unabhängig davon. Weitere Informationen: Datenschutzerklärung von Google, Wie Google Werbung nutzt.

Analyse (Google Analytics for Firebase)

Um das Spiel zu verbessern, nutzen wir Google Analytics for Firebase (Google Ireland Limited). Die Datenerfassung ist standardmäßig ausgeschaltet und wird erst aktiviert, wenn die Einwilligungsabfrage dies erlaubt (in Regionen ohne Einwilligungspflicht nach dem Start). Erfasst werden pseudonyme Nutzungsdaten wie eine zufällige App-Instanz-ID, Gerätemodell, Betriebssystem- und App-Version, Sprache, ungefähre Region, Sitzungen sowie Spielereignisse (Level gestartet und gelöst mit Größe, Dauer, Fehlern und genutzten Tipps, Tutorial abgeschlossen), Anzeigenereignisse und Kaufereignisse (gekauftes Produkt; auf Android erfasst Firebase dabei automatisch auch Preis und Währung). Wir erfassen keine Namen, E-Mail-Adressen oder Freitexte. Ereignisdaten werden von Google nach 2 Monaten gelöscht; zusammengefasste Berichte können länger bestehen. Wenn du ablehnst oder widerrufst, wird die Analyse ausgeschaltet.

Fehlerdiagnose (Firebase Crashlytics)

Auf iOS und Android nutzen wir Firebase Crashlytics (Google Ireland Limited), um Abstürze zu untersuchen und die Stabilität zu verbessern. Berichte können Stacktraces, technische App-Zustände, App-/Build- und Betriebssystemversionen, Geräteinformationen, pseudonyme Installations-/Sitzungskennungen sowie letzte Analytics-Ereignisse vor einem Absturz enthalten. Wir setzen keine persönliche Nutzerkennung in Crashlytics. Die automatische Übermittlung ist standardmäßig deaktiviert und folgt derselben Datenschutzauswahl im Spiel wie Analytics. Bei deaktivierter Übermittlung können Fehlerinformationen lokal auf dem Gerät verbleiben und bei späterer Aktivierung gesendet werden. Deine Auswahl kannst du über die oben beschriebenen Datenschutz-Optionen ändern. Firebase beginnt nach 90 Tagen mit der Löschung der Absturzdaten und zugehörigen Kennungen. Weitere Informationen: Datenschutzhinweise von Firebase.

In-App-Käufe

Sweetdoku bietet optionale In-App-Käufe an: „Werbung entfernen" (einmalig; schaltet die Vollbildanzeigen zwischen Leveln ab, freiwillige Videos mit Belohnung bleiben verfügbar), ein einmaliges Starterpaket und Münzpakete. Bezahlt wird ausschließlich über den App Store von Apple bzw. Google Play. Die Zahlungsdaten verarbeiten Apple bzw. Google in eigener Verantwortung; wir erhalten keine Zahlungs- oder Kontodaten. Die App erhält vom Store eine Transaktionskennung und speichert gekaufte Inhalte und diese Kennungen lokal auf deinem Gerät, damit Käufe nicht doppelt gutgeschrieben werden und „Werbung entfernen" wiederhergestellt werden kann (Einstellungen → „Restore Purchases").

Für die Kaufabwicklung nutzt die App das Unity In-App Purchasing SDK (Unity Technologies ApS, Niels Hemmingsens Gade 24, 1153 Kopenhagen, Dänemark). Es übermittelt bei Kaufvorgängen technische Daten an Unity: Produkt, Preis und Währung, Transaktionskennung und Kaufstatus, eine zufällige Installations-ID, auf iOS die Kennung für Anbieter (IDFV), Gerätemodell, Betriebssystem, App-Version, Sprache und Region. Werbe-IDs werden dabei nicht übermittelt. Rechtsgrundlage ist die Vertragserfüllung (Art. 6 Abs. 1 lit. b DSGVO) und unser berechtigtes Interesse an einer sicheren, fehlerfreien Kaufabwicklung (Art. 6 Abs. 1 lit. f DSGVO). Unity kann Daten auch in den USA verarbeiten; die Übermittlung erfolgt auf Grundlage der Standardvertragsklauseln der EU-Kommission. Weitere Informationen: Datenschutzhinweise von Unity.

Übermittlung in Drittländer, Speicherdauer, Rechte

Google kann Daten auch in den USA verarbeiten. Google LLC ist nach dem EU-US Data Privacy Framework zertifiziert; ergänzend gelten die Standardvertragsklauseln der EU-Kommission. Lokale Spieldaten bleiben auf deinem Gerät, bis du die App löschst. Das Löschen der App entfernt keine Daten, die Google bereits verarbeitet hat; hierzu gelten die Löschfristen von Google. Deine Rechte (Auskunft, Berichtigung, Löschung, Einschränkung, Datenübertragbarkeit, Widerspruch, Widerruf der Einwilligung und Beschwerde bei einer Aufsichtsbehörde) findest du unter Ihre Rechte. Anfragen bitte an hallo@konfora.de mit dem Hinweis „Sweetdoku".

Web-Version

Sweetdoku gibt es auch als Browserspiel auf CrazyGames. Diese Web-Version enthält weder Google AdMob noch Firebase noch In-App-Käufe; dort gelten die Datenschutzhinweise von CrazyGames (crazygames.com/privacy-policy).

English

This information describes Sweetdoku 1.0 for iOS and Android. The controller is Fabio Blankenhorn, Konfora Apps, Heppstr. 17, 72760 Reutlingen, Germany, hallo@konfora.de. Other providers in the shared directory on this page are not used by Sweetdoku unless named here.

Progress and settings

Sweetdoku requires no account. Level progress, coins, collected sweets, the daily puzzle streak, tutorial status and your sound, music, vibration, Auto-X and colour-pattern settings are stored only on your device. There is no cloud save or chat. Coins have no cash value and cannot be cashed out. Music, graphics and puzzles are included in the app; playing does not send your inputs to a server. The app does not request contacts, microphone, camera or precise location.

Consent at startup

At startup Sweetdoku uses Google's User Messaging Platform (UMP) to show a consent message where required for your region (for example in the EEA, the United Kingdom and Switzerland). You can accept, decline or choose individual purposes and vendors. The message covers advertising (Google AdMob) and analytics (Google Analytics for Firebase). You can change or withdraw your choice at any time under Settings → "Privacy Options". The legal basis is your consent under Art. 6(1)(a) GDPR and Section 25(1) TDDDG.

Advertising (Google AdMob)

Sweetdoku shows ads through Google AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland): optional rewarded videos (for example an extra hint or more coins) and occasional full-screen ads between levels. The advertising SDK may process your IP address, approximate location derived from it, device and advertising identifiers, ad views and interactions, and diagnostic and performance data to deliver and measure ads, prevent fraud and — where you consented — personalise ads. Without consent only non-personalised or limited ads are requested where permitted; these can still involve personal data. Ads are limited to content suitable for all ages. On iOS Sweetdoku first explains briefly what the advertising identifier is used for and then asks for permission through Apple's App Tracking Transparency (ATT). Only if you choose "Allow" may Google AdMob use the advertising identifier (IDFA) for personalised ads and their measurement; you can change this at any time under iOS Settings → Privacy & Security → Tracking. The consent message for the EEA, the United Kingdom and Switzerland applies independently. See Google's Privacy Policy and how Google uses advertising data.

Analytics (Google Analytics for Firebase)

To improve the game we use Google Analytics for Firebase (Google Ireland Limited). Collection is switched off by default and only starts once the consent message allows it (in regions without a consent requirement, after startup). It covers pseudonymous usage data such as a random app-instance ID, device model, operating system and app version, language, approximate region, sessions, game events (level started and solved with board size, duration, mistakes and hints used, tutorial completed), ad events and purchase events (the product bought; on Android Firebase also records price and currency automatically). We do not collect names, email addresses or free text. Google deletes event data after 2 months; aggregated reports may be kept longer. If you decline or withdraw consent, analytics is switched off.

Crash diagnostics (Firebase Crashlytics)

On iOS and Android we use Firebase Crashlytics (Google Ireland Limited) to investigate crashes and improve stability. Reports can include stack traces, technical app state, app/build and operating-system versions, device information, pseudonymous installation/session identifiers and recent Analytics events before a crash. We do not set a personal user ID in Crashlytics. Automatic upload is disabled by default and follows the same in-game privacy choice as Analytics. Crash information may remain locally on the device while uploads are disabled and be sent if collection is later enabled. You can change your choice through the privacy options described above. Firebase starts deleting crash data and associated identifiers after 90 days. See Firebase's privacy information.

In-app purchases

Sweetdoku offers optional in-app purchases: "Remove Ads" (one-time; turns off the full-screen ads between levels, optional rewarded videos stay available), a one-time starter pack and coin packs. Payment is handled exclusively by Apple's App Store or Google Play. Apple and Google process payment data as independent controllers; we receive no payment or account details. The app receives a transaction identifier from the store and stores purchased content and these identifiers locally on your device so that purchases are not credited twice and "Remove Ads" can be restored (Settings → "Restore Purchases").

To process purchases the app uses the Unity In-App Purchasing SDK (Unity Technologies ApS, Niels Hemmingsens Gade 24, 1153 Copenhagen, Denmark). During purchases it sends technical data to Unity: product, price and currency, transaction identifier and purchase status, a random installation ID, on iOS the identifier for vendor (IDFV), device model, operating system, app version, language and region. Advertising identifiers are not sent. The legal basis is performance of a contract (Art. 6(1)(b) GDPR) and our legitimate interest in secure, error-free purchase processing (Art. 6(1)(f) GDPR). Unity may also process data in the United States; transfers rely on the European Commission's Standard Contractual Clauses. See Unity's privacy information.

International transfers, retention, your rights

Google may also process data in the United States. Google LLC is certified under the EU-US Data Privacy Framework; the European Commission's Standard Contractual Clauses apply in addition. Local game data stays on your device until you delete the app. Deleting the app does not erase data Google has already processed; Google's retention periods apply. Your rights (access, rectification, erasure, restriction, portability, objection, withdrawal of consent and complaint to a supervisory authority) are described under Your rights. Please send requests to hallo@konfora.de and mention "Sweetdoku".

Web version

Sweetdoku is also available as a browser game on CrazyGames. The web version contains neither Google AdMob, Firebase nor in-app purchases; CrazyGames' privacy policy applies there (crazygames.com/privacy-policy).

Candy Cheeks — iOS and Android privacy information / Datenschutz

Updated September 26, 2026 · Candy Cheeks 1.0 for iOS and Android · Deutsch · English

Deutsch

Diese Angaben beschreiben Candy Cheeks 1.0 für iOS und Android. Verantwortlich ist Fabio Blankenhorn, Konfora Apps, Heppstr. 17, 72760 Reutlingen, Deutschland, hallo@konfora.de. Die übrigen Anbieter im allgemeinen Verzeichnis dieser Seite werden dadurch nicht zu Diensten von Candy Cheeks.

Spielstand und Einstellungen

Candy Cheeks benötigt kein Konto. Levelfortschritt, Münzen, Leben und Booster, das Album, die Tagesbelohnung, der Tutorial-Status sowie Einstellungen für Ton, Musik, Vibration, Farbenblind-Modus und Tempo werden nur auf deinem Gerät gespeichert. Es gibt keinen Cloud-Spielstand und keinen Chat. Münzen haben keinen Geldwert und können nicht ausgezahlt werden. Bilder, Level und Musik sind in der App enthalten; Spielen überträgt deine Eingaben an keinen Server. Die App fragt keine Kontakte, kein Mikrofon, keine Kamera und keinen genauen Standort ab.

Einwilligung beim Start

Beim Start zeigt Candy Cheeks über die User Messaging Platform (UMP) von Google eine Einwilligungsabfrage an, sofern das für deine Region erforderlich ist (z. B. im EWR, im Vereinigten Königreich und in der Schweiz). Du kannst zustimmen, ablehnen oder einzelne Zwecke und Anbieter auswählen. Die Abfrage gilt für Werbung (Google AdMob), Analyse (Google Analytics for Firebase) und Absturzberichte (Firebase Crashlytics). Deine Auswahl kannst du jederzeit unter Einstellungen → „Datenschutz“ ändern oder widerrufen. Rechtsgrundlage ist deine Einwilligung nach Art. 6 Abs. 1 lit. a DSGVO und § 25 Abs. 1 TDDDG.

Werbung (Google AdMob)

Candy Cheeks zeigt Anzeigen über Google AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Irland): freiwillige Videos mit Belohnung (z. B. doppelte Münzen, ein zusätzliches Leben oder ein Booster) und gelegentlich Vollbildanzeigen zwischen Leveln. Das Werbe-SDK kann dabei IP-Adresse, daraus abgeleiteten ungefähren Standort, Geräte- und Werbekennungen, Informationen zu Anzeigen und Interaktionen sowie Diagnose- und Leistungsdaten verarbeiten, um Anzeigen auszuliefern und zu messen, Betrug zu verhindern und – soweit du eingewilligt hast – Anzeigen zu personalisieren. Ohne Einwilligung werden, soweit zulässig, nur nicht personalisierte oder eingeschränkte Anzeigen angefordert; auch diese können personenbezogene Daten verarbeiten. Anzeigen sind auf Inhalte beschränkt, die für alle Altersgruppen geeignet sind. Auf iOS fragt Candy Cheeks nicht nach der Tracking-Erlaubnis (App-Tracking-Transparenz) und nutzt die Werbe-ID (IDFA) nicht. Weitere Informationen: Datenschutzerklärung von Google, Wie Google Werbung nutzt.

Analyse (Google Analytics for Firebase)

Um das Spiel zu verbessern, nutzen wir Google Analytics for Firebase (Google Ireland Limited). Die Datenerfassung ist standardmäßig ausgeschaltet und wird erst aktiviert, wenn die Einwilligungsabfrage dies erlaubt (in Regionen ohne Einwilligungspflicht nach dem Start). Erfasst werden pseudonyme Nutzungsdaten wie eine zufällige App-Instanz-ID, Gerätemodell, Betriebssystem- und App-Version, Sprache, ungefähre Region, Sitzungen sowie Spielereignisse (Level gestartet, gewonnen, verloren oder abgebrochen; Booster-Nutzung; Tutorial-Schritte; Tagesbelohnung; Album; geänderte Einstellungen), Anzeigenereignisse (z. B. angesehene Anzeigen; über die Verknüpfung mit AdMob erfasst Firebase dabei automatisch auch den geschätzten Anzeigenumsatz) und Kaufereignisse (gekauftes Produkt und Transaktionskennung; auf Android erfasst Firebase dabei automatisch auch Preis und Währung). Wir erfassen keine Namen, E-Mail-Adressen oder Freitexte. Ereignisdaten werden von Google nach 2 Monaten gelöscht; zusammengefasste Berichte können länger bestehen. Wenn du ablehnst oder widerrufst, wird die Analyse ausgeschaltet.

Absturzberichte (Firebase Crashlytics)

Stürzt die App ab, kann ein Absturzbericht an Firebase Crashlytics (Google Ireland Limited) gesendet werden. Er enthält Gerätemodell, Betriebssystem- und App-Version, den technischen Fehlerverlauf und eine zufällige Installationskennung. Auch Crashlytics ist standardmäßig ausgeschaltet und folgt deiner Einwilligung. Absturzberichte werden nach 90 Tagen gelöscht.

In-App-Käufe

Candy Cheeks bietet optionale In-App-Käufe an: Münzpakete, ein einmaliges Starter-Paket, ein Rettungs-Paket und „Keine Werbung“ (einmalig; schaltet die Vollbildanzeigen zwischen Leveln ab, freiwillige Videos mit Belohnung bleiben verfügbar). Bezahlt wird ausschließlich über Google Play bzw. den App Store von Apple. Die Zahlungsdaten verarbeiten Google bzw. Apple in eigener Verantwortung; wir erhalten keine Zahlungs- oder Kontodaten. Die App erhält vom Store eine Transaktionskennung und speichert gekaufte Inhalte und diese Kennungen lokal auf deinem Gerät, damit Käufe nicht doppelt gutgeschrieben werden und „Keine Werbung“ wiederhergestellt werden kann (Android automatisch beim Start, iOS unter Einstellungen → „Käufe wiederherstellen“).

Für die Kaufabwicklung nutzt die App das Unity In-App Purchasing SDK (Unity Technologies ApS, Niels Hemmingsens Gade 24, 1153 Kopenhagen, Dänemark). Es übermittelt bei Kaufvorgängen technische Daten an Unity: Produkt, Preis und Währung, Transaktionskennung und Kaufstatus, eine zufällige Installations-ID, auf iOS die Kennung für Anbieter (IDFV), Gerätemodell, Betriebssystem, App-Version, Sprache und Region. Werbe-IDs werden dabei nicht übermittelt. Rechtsgrundlage ist die Vertragserfüllung (Art. 6 Abs. 1 lit. b DSGVO) und unser berechtigtes Interesse an einer sicheren, fehlerfreien Kaufabwicklung (Art. 6 Abs. 1 lit. f DSGVO). Unity kann Daten auch in den USA verarbeiten; die Übermittlung erfolgt auf Grundlage der Standardvertragsklauseln der EU-Kommission. Weitere Informationen: Datenschutzhinweise von Unity.

Übermittlung in Drittländer, Speicherdauer, Rechte

Google kann Daten auch in den USA verarbeiten. Google LLC ist nach dem EU-US Data Privacy Framework zertifiziert; ergänzend gelten die Standardvertragsklauseln der EU-Kommission. Lokale Spieldaten bleiben auf deinem Gerät, bis du die App löschst. Das Löschen der App entfernt keine Daten, die Google bereits verarbeitet hat; hierzu gelten die Löschfristen von Google. Deine Rechte (Auskunft, Berichtigung, Löschung, Einschränkung, Datenübertragbarkeit, Widerspruch, Widerruf der Einwilligung und Beschwerde bei einer Aufsichtsbehörde) findest du unter Ihre Rechte. Anfragen bitte an hallo@konfora.de mit dem Hinweis „Candy Cheeks“.

Web-Version

Candy Cheeks gibt es auch als Browserspiel auf CrazyGames. Diese Web-Version enthält weder Google AdMob noch Firebase noch In-App-Käufe; dort gelten die Datenschutzhinweise von CrazyGames (crazygames.com/privacy-policy).

English

This information describes Candy Cheeks 1.0 for iOS and Android. The controller is Fabio Blankenhorn, Konfora Apps, Heppstr. 17, 72760 Reutlingen, Germany, hallo@konfora.de. Other providers in the shared directory on this page are not used by Candy Cheeks unless named here.

Progress and settings

Candy Cheeks requires no account. Level progress, coins, lives and boosters, the album, the daily reward, tutorial status and your sound, music, vibration, colour-blind and speed settings are stored only on your device. There is no cloud save or chat. Coins have no cash value and cannot be cashed out. Pictures, levels and music are included in the app; playing does not send your inputs to a server. The app does not request contacts, microphone, camera or precise location.

Consent at startup

At startup Candy Cheeks uses Google's User Messaging Platform (UMP) to show a consent message where required for your region (for example in the EEA, the United Kingdom and Switzerland). You can accept, decline or choose individual purposes and vendors. The message covers advertising (Google AdMob), analytics (Google Analytics for Firebase) and crash reports (Firebase Crashlytics). You can change or withdraw your choice at any time under Settings → "Privacy". The legal basis is your consent under Art. 6(1)(a) GDPR and Section 25(1) TDDDG.

Advertising (Google AdMob)

Candy Cheeks shows ads through Google AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland): optional rewarded videos (for example double coins, an extra life or a booster) and occasional full-screen ads between levels. The advertising SDK may process your IP address, approximate location derived from it, device and advertising identifiers, ad views and interactions, and diagnostic and performance data to deliver and measure ads, prevent fraud and — where you consented — personalise ads. Without consent only non-personalised or limited ads are requested where permitted; these can still involve personal data. Ads are limited to content suitable for all ages. On iOS Candy Cheeks does not ask for tracking permission (App Tracking Transparency) and does not use the advertising identifier (IDFA). More information: Google Privacy Policy, How Google uses advertising.

Analytics (Google Analytics for Firebase)

To improve the game we use Google Analytics for Firebase (Google Ireland Limited). Collection is switched off by default and only starts once the consent message allows it (in regions without a consent requirement, after startup). It covers pseudonymous usage data such as a random app-instance ID, device model, operating system and app version, language, approximate region, sessions and game events (levels started, won, lost or quit; booster use; tutorial steps; daily reward; album; changed settings), ad events (for example ads viewed; through the AdMob link Firebase automatically also records the estimated ad revenue) and purchase events (product bought and transaction ID; on Android Firebase automatically also records price and currency). We do not collect names, email addresses or free text. Google deletes event data after 2 months; aggregated reports may be kept longer. If you decline or withdraw consent, analytics is switched off.

Crash reports (Firebase Crashlytics)

If the app crashes, a crash report may be sent to Firebase Crashlytics (Google Ireland Limited). It contains the device model, operating system and app version, the technical stack trace and a random installation identifier. Crashlytics is also off by default and follows your consent. Crash reports are deleted after 90 days.

In-app purchases

Candy Cheeks offers optional in-app purchases: coin packs, a one-time starter pack, a rescue pack and "No Ads" (one-time; switches off the full-screen ads between levels, optional rewarded videos stay available). Payment is handled exclusively by Google Play or Apple's App Store. Google or Apple process payment data under their own responsibility; we receive no payment or account details. The app receives a transaction ID from the store and stores purchased content and these IDs locally on your device so purchases are never credited twice and "No Ads" can be restored (on Android automatically at startup, on iOS under Settings → "Restore purchases").

For purchase processing the app uses the Unity In-App Purchasing SDK (Unity Technologies ApS, Niels Hemmingsens Gade 24, 1153 Copenhagen, Denmark). During purchases it sends technical data to Unity: product, price and currency, transaction ID and purchase status, a random installation ID, on iOS the identifier for vendors (IDFV), device model, operating system, app version, language and region. Advertising IDs are not sent. The legal basis is the performance of a contract (Art. 6(1)(b) GDPR) and our legitimate interest in secure, error-free purchase processing (Art. 6(1)(f) GDPR). Unity may also process data in the United States; transfers are based on the European Commission's Standard Contractual Clauses. More information: Unity privacy notice.

International transfers, retention, your rights

Google may also process data in the United States. Google LLC is certified under the EU-US Data Privacy Framework; the European Commission's Standard Contractual Clauses apply in addition. Local game data stays on your device until you delete the app. Deleting the app does not erase data Google has already processed; Google's retention periods apply. Your rights (access, rectification, erasure, restriction, portability, objection, withdrawal of consent and complaint to a supervisory authority) are described under Your rights. Please send requests to hallo@konfora.de and mention "Candy Cheeks".

Web version

Candy Cheeks is also available as a browser game on CrazyGames. The web version contains neither Google AdMob, Firebase nor in-app purchases; CrazyGames' privacy policy applies there (crazygames.com/privacy-policy).

Kip & Timbo — iOS and Android privacy information / Datenschutz

Updated September 26, 2026 · Kip & Timbo 1.0 for iOS and Android · Deutsch · English

Deutsch

Diese Angaben beschreiben Kip & Timbo 1.0 für iOS und Android. Verantwortlich ist Fabio Blankenhorn, Konfora Apps, Heppstr. 17, 72760 Reutlingen, Deutschland, hallo@konfora.de. Die übrigen Anbieter im allgemeinen Verzeichnis dieser Seite werden dadurch nicht zu Diensten von Kip & Timbo.

Spielstand und Einstellungen

Kip & Timbo benötigt kein Konto. Levelfortschritt, Sterne, Münzen, Leben, Booster, Fanclub, Tagesgeschenk, Tutorial-Status sowie Einstellungen für Musik, Sounds, Vibration, Bewegung und Sprache werden nur auf deinem Gerät gespeichert. Es gibt keinen Cloud-Spielstand und keinen Chat. Münzen haben keinen Geldwert und können nicht ausgezahlt werden. Die App fragt keine Kontakte, kein Mikrofon, keine Kamera und keinen genauen Standort ab.

In-App-Käufe

Kip & Timbo bietet optionale In-App-Käufe an: „Werbung entfernen“ (einmalig, auch als Paket; schaltet die Vollbildanzeigen zwischen Leveln ab, freiwillige Videos mit Belohnung bleiben verfügbar), ein einmaliges Starterpaket, Münzpakete, Booster-Pakete, das Rettungsangebot nach einem verlorenen Level und das Knacken der Sparmuschel. Bezahlt wird ausschließlich über den App Store von Apple bzw. Google Play. Die Zahlungsdaten verarbeiten Apple bzw. Google in eigener Verantwortung; wir erhalten keine Zahlungs- oder Kontodaten. Die App erhält vom Store eine Transaktionskennung und speichert gekaufte Inhalte und diese Kennungen lokal auf deinem Gerät, damit Käufe nicht doppelt gutgeschrieben werden und „Werbung entfernen“ wiederhergestellt werden kann (Einstellungen → „Käufe wiederherstellen“).

Für die Kaufabwicklung nutzt die App das Unity In-App Purchasing SDK (Unity Technologies ApS, Niels Hemmingsens Gade 24, 1153 Kopenhagen, Dänemark). Es übermittelt bei Kaufvorgängen technische Daten an Unity: Produkt, Preis und Währung, Transaktionskennung und Kaufstatus, eine zufällige Installations-ID, auf iOS die Kennung für Anbieter (IDFV), Gerätemodell, Betriebssystem, App-Version, Sprache und Region. Werbe-IDs werden dabei nicht übermittelt. Rechtsgrundlage ist die Vertragserfüllung (Art. 6 Abs. 1 lit. b DSGVO) und unser berechtigtes Interesse an einer sicheren, fehlerfreien Kaufabwicklung (Art. 6 Abs. 1 lit. f DSGVO). Unity kann Daten auch in den USA verarbeiten; die Übermittlung erfolgt auf Grundlage der Standardvertragsklauseln der EU-Kommission. Weitere Informationen: Datenschutzhinweise von Unity.

Einwilligung beim Start

Beim Start zeigt Kip & Timbo über die User Messaging Platform (UMP) von Google eine Einwilligungsabfrage an, sofern das für deine Region erforderlich ist (im EWR, im Vereinigten Königreich und in der Schweiz nach dem IAB-Transparency-&-Consent-Framework). Du kannst einwilligen, nicht einwilligen oder einzelne Zwecke und Anbieter auswählen. Die Abfrage gilt gemeinsam für Werbung (Google AdMob) und Analyse (Google Analytics for Firebase); vor deiner Entscheidung werden keine Anzeigen angefordert und keine Analysedaten erfasst. In US-Bundesstaaten mit eigenen Datenschutzgesetzen kannst du dem Verkauf bzw. der Weitergabe deiner Daten für Werbung widersprechen. Deine Auswahl kannst du jederzeit unter Einstellungen → „Datenschutz-Einstellungen“ ändern oder widerrufen. Rechtsgrundlage ist deine Einwilligung nach Art. 6 Abs. 1 lit. a DSGVO und § 25 Abs. 1 TDDDG.

Tracking-Erlaubnis auf iOS (App Tracking Transparency)

Auf iOS erklärt Kip & Timbo zuerst in einem kurzen Hinweis, wozu die Werbe-ID (IDFA) genutzt wird, danach fragt iOS mit dem System-Dialog nach deiner Erlaubnis („Deine Daten werden verwendet, um dir relevantere Werbung zu zeigen.“). Nur wenn du erlaubst, darf Google AdMob die IDFA für personalisierte Werbung und Messung verwenden. Du kannst die Erlaubnis jederzeit in den iOS-Einstellungen unter Datenschutz & Sicherheit → Tracking ändern.

Werbung (Google AdMob)

Kip & Timbo zeigt Anzeigen über Google AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Irland): freiwillige Videos mit Belohnung (zusätzliche Perlen, ein Leben, doppelte Münzen, ein doppeltes Tagesgeschenk, eine Video-Truhe im Shop oder ein Booster) und gelegentlich Vollbildanzeigen zwischen Leveln (frühestens ab Level 25, mit Mindestabständen). Banner gibt es nicht. Das Werbe-SDK kann dabei IP-Adresse, daraus abgeleiteten ungefähren Standort, Geräte- und Werbekennungen, Informationen zu Anzeigen und Interaktionen sowie Diagnose- und Leistungsdaten verarbeiten, um Anzeigen auszuliefern und zu messen, Betrug zu verhindern und – soweit du eingewilligt hast – Anzeigen zu personalisieren. Ohne Einwilligung werden, soweit zulässig, nur nicht personalisierte oder eingeschränkte Anzeigen angefordert; auch diese können personenbezogene Daten verarbeiten. Anzeigen sind auf Inhalte bis zur Einstufung „PG“ (elterliche Begleitung empfohlen) beschränkt. Weitere Informationen: Datenschutzerklärung von Google, Wie Google Werbung nutzt.

Analyse (Google Analytics for Firebase)

Um das Spiel zu verbessern, nutzen wir Google Analytics for Firebase (Google Ireland Limited). Die Datenerfassung ist standardmäßig ausgeschaltet und wird erst aktiviert, wenn die Einwilligungsabfrage dies erlaubt (in Regionen ohne Einwilligungspflicht nach dem Start). Erfasst werden pseudonyme Nutzungsdaten wie eine zufällige App-Instanz-ID, Gerätemodell, Betriebssystem- und App-Version, Sprache, ungefähre Region, Sitzungen sowie Spielereignisse (Level gestartet, gewonnen oder verloren mit Level, Welt, Versuchen, Dauer, Schüssen und Sternen; verdiente und ausgegebene Münzen; Tutorial begonnen und abgeschlossen; Einstellungen geändert), Anzeigenereignisse (angefragt, gezeigt, abgeschlossen, geschätzter Werbeerlös), Kaufereignisse (gekauftes Produkt, Preis und Währung, Transaktionskennung) und deine Einwilligungsentscheidung. Zusätzlich speichern wir wenige Nutzereigenschaften: Spielprofil, ob bereits ein Kauf stattfand, Leistungsstufe des Geräts, zugeteilte Testvariante und Installationstag. Wir erfassen keine Namen, E-Mail-Adressen oder Freitexte. Ereignisdaten werden von Google nach 2 Monaten gelöscht; zusammengefasste Berichte können länger bestehen. Wenn du ablehnst oder widerrufst, wird die Analyse ausgeschaltet.

Absturzberichte (Firebase Crashlytics)

Damit das Spiel stabil läuft, nutzen wir Firebase Crashlytics (Google Ireland Limited). Stürzt die App ab oder tritt ein technischer Fehler auf, wird ein Bericht übertragen: Fehlerverlauf (Stack-Trace), Gerätemodell, Betriebssystem- und App-Version, eine zufällige Crashlytics-Installations-ID, die Firebase-Installations-ID sowie das gerade gespielte Level und die Welt. Werbe-IDs werden dafür nicht verwendet. Crashlytics wird nach deiner Entscheidung in der Einwilligungsabfrage eingeschaltet, unabhängig von deiner Auswahl; Rechtsgrundlage ist unser berechtigtes Interesse an einer fehlerfreien App (Art. 6 Abs. 1 lit. f DSGVO). Google löscht Absturzdaten nach 90 Tagen. Du kannst jederzeit per E-Mail an hallo@konfora.de widersprechen.

Spieleinstellungen aus der Ferne (Firebase Remote Config und A/B Testing)

Spielwerte wie Schwierigkeit, Belohnungen oder Werbeabstände können wir über Firebase Remote Config (Google Ireland Limited) anpassen und in Varianten testen (Firebase A/B Testing). Dazu ruft die App beim Start die aktuelle Konfiguration ab; dabei werden die Firebase-Installations-ID und technische Verbindungsdaten wie die IP-Adresse verarbeitet. Die zuletzt geladene Konfiguration wird auf deinem Gerät gespeichert. Rechtsgrundlage ist unser berechtigtes Interesse an einem gut abgestimmten Spiel (Art. 6 Abs. 1 lit. f DSGVO). Die Auswertung von Testvarianten nutzt die Analysedaten nur, wenn du der Analyse zugestimmt hast.

Übermittlung in Drittländer, Speicherdauer, Rechte

Google kann Daten auch in den USA verarbeiten. Google LLC ist nach dem EU-US Data Privacy Framework zertifiziert; ergänzend gelten die Standardvertragsklauseln der EU-Kommission. Lokale Spieldaten bleiben auf deinem Gerät, bis du die App löschst. Das Löschen der App entfernt keine Daten, die Google bereits verarbeitet hat; hierzu gelten die Löschfristen von Google. Deine Rechte (Auskunft, Berichtigung, Löschung, Einschränkung, Datenübertragbarkeit, Widerspruch, Widerruf der Einwilligung und Beschwerde bei einer Aufsichtsbehörde) findest du unter Ihre Rechte. Anfragen bitte an hallo@konfora.de mit dem Hinweis „Kip & Timbo“.

Web-Version

Kip & Timbo gibt es auch als Browserspiel. Die Web-Version enthält weder Google AdMob noch Firebase noch In-App-Käufe. Auf Spieleportalen (z. B. Poki, CrazyGames) gelten zusätzlich deren Datenschutzhinweise.

English

This information describes Kip & Timbo 1.0 for iOS and Android. The controller is Fabio Blankenhorn, Konfora Apps, Heppstr. 17, 72760 Reutlingen, Germany, hallo@konfora.de. Other providers in the shared directory on this page are not used by Kip & Timbo unless named here.

Progress and settings

Kip & Timbo requires no account. Level progress, stars, coins, lives, boosters, the fan club, the daily gift, tutorial status and your music, sound, vibration, motion and language settings are stored only on your device. There is no cloud save and no chat. Coins have no cash value and cannot be cashed out. The app does not request contacts, microphone, camera or precise location.

In-app purchases

Kip & Timbo offers optional in-app purchases: "Remove Ads" (one-time, also as a bundle; turns off the full-screen ads between levels, optional rewarded videos stay available), a one-time starter pack, coin packs, booster bundles, the rescue offer after a lost level and cracking the piggy clam. Payment is handled exclusively by Apple's App Store or Google Play. Apple and Google process payment data as independent controllers; we receive no payment or account details. The app receives a transaction identifier from the store and stores purchased content and these identifiers locally on your device so that purchases are not credited twice and "Remove Ads" can be restored (Settings → "Restore purchases").

To process purchases the app uses the Unity In-App Purchasing SDK (Unity Technologies ApS, Niels Hemmingsens Gade 24, 1153 Copenhagen, Denmark). During purchases it sends technical data to Unity: product, price and currency, transaction identifier and purchase status, a random installation ID, on iOS the identifier for vendor (IDFV), device model, operating system, app version, language and region. Advertising identifiers are not sent. The legal basis is performance of a contract (Art. 6(1)(b) GDPR) and our legitimate interest in secure, error-free purchase processing (Art. 6(1)(f) GDPR). Unity may also process data in the United States; transfers rely on the European Commission's Standard Contractual Clauses. See Unity's privacy information.

Consent at startup

At startup Kip & Timbo uses Google's User Messaging Platform (UMP) to show a consent message where required for your region (in the EEA, the United Kingdom and Switzerland under the IAB Transparency & Consent Framework). You can consent, not consent or choose individual purposes and vendors. The message covers advertising (Google AdMob) and analytics (Google Analytics for Firebase) together; before you decide, no ads are requested and no analytics data is collected. In US states with their own privacy laws you can opt out of the sale or sharing of your data for advertising. You can change or withdraw your choice at any time under Settings → "Privacy settings". The legal basis is your consent under Art. 6(1)(a) GDPR and Section 25(1) TDDDG.

Tracking permission on iOS (App Tracking Transparency)

On iOS, Kip & Timbo first explains in a short message what the advertising identifier (IDFA) is used for; iOS then asks for your permission with its system dialog ("Your data will be used to show you more relevant ads."). Only if you allow it may Google AdMob use the IDFA for personalised ads and measurement. You can change this at any time in the iOS Settings under Privacy & Security → Tracking.

Advertising (Google AdMob)

Kip & Timbo shows ads through Google AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland): optional rewarded videos (extra pearls, a life, double coins, a doubled daily gift, a video chest in the shop or a booster) and occasional full-screen ads between levels (not before level 25, with minimum gaps). There are no banners. The advertising SDK may process your IP address, approximate location derived from it, device and advertising identifiers, ad views and interactions, and diagnostic and performance data to deliver and measure ads, prevent fraud and — where you consented — personalise ads. Without consent only non-personalised or limited ads are requested where permitted; these can still involve personal data. Ads are limited to content rated up to "PG" (parental guidance). See Google's Privacy Policy and how Google uses advertising data.

Analytics (Google Analytics for Firebase)

To improve the game we use Google Analytics for Firebase (Google Ireland Limited). Collection is switched off by default and only starts once the consent message allows it (in regions without a consent requirement, after startup). It covers pseudonymous usage data such as a random app-instance ID, device model, operating system and app version, language, approximate region, sessions, game events (level started, won or lost with level, world, attempts, duration, shots and stars; coins earned and spent; tutorial started and completed; settings changed), ad events (requested, shown, completed, estimated ad revenue), purchase events (product bought, price and currency, transaction identifier) and your consent choice. We also store a few user properties: game profile, whether a purchase was made, device performance tier, assigned test variant and install day. We do not collect names, email addresses or free text. Google deletes event data after 2 months; aggregated reports may be kept longer. If you decline or withdraw consent, analytics is switched off.

Crash reports (Firebase Crashlytics)

To keep the game stable we use Firebase Crashlytics (Google Ireland Limited). If the app crashes or a technical error occurs, a report is sent: the error trace (stack trace), device model, operating system and app version, a random Crashlytics installation ID, the Firebase installation ID and the level and world being played. No advertising identifiers are used for this. Crashlytics is switched on after your decision in the consent message, whatever you chose; the legal basis is our legitimate interest in an app that works (Art. 6(1)(f) GDPR). Google deletes crash data after 90 days. You can object at any time by email to hallo@konfora.de.

Remote game settings (Firebase Remote Config and A/B Testing)

We can adjust game values such as difficulty, rewards or ad spacing with Firebase Remote Config (Google Ireland Limited) and test variants of them (Firebase A/B Testing). The app fetches the current configuration at startup, which processes the Firebase installation ID and technical connection data such as the IP address. The last configuration is stored on your device. The legal basis is our legitimate interest in a well-balanced game (Art. 6(1)(f) GDPR). Test variants are only evaluated with analytics data if you consented to analytics.

International transfers, retention, your rights

Google may also process data in the United States. Google LLC is certified under the EU-US Data Privacy Framework; the European Commission's Standard Contractual Clauses apply in addition. Local game data stays on your device until you delete the app. Deleting the app does not erase data Google has already processed; Google's retention periods apply. Your rights (access, rectification, erasure, restriction, portability, objection, withdrawal of consent and complaint to a supervisory authority) are described under Your rights. Please send requests to hallo@konfora.de and mention "Kip & Timbo".

Web version

Kip & Timbo is also available as a browser game. The web version contains neither Google AdMob, Firebase nor in-app purchases. On game portals (for example Poki or CrazyGames) their privacy policies apply in addition.

PulsePace — iPhone & Apple Watch privacy information / Datenschutz

Updated September 15, 2026 · PulsePace 1.0 · Deutsch · English

Foldpix — Image converter / Bildkonverter

Datenschutz auf Deutsch · Privacy in English