Last updated: 11 October 2026
Dripluma is published by Berkcan Aşkın. For privacy questions, data requests and game support, contact berkcanaskin03@gmail.com.
This policy describes the current Android and iOS version of Dripluma. The game keeps your progress on your device. You can manage optional gameplay statistics, crash reporting and rewarded videos separately.
Age and your choices
Dripluma is intended for players aged 13 and older. On first launch, we ask you to choose an age range, without asking for your date of birth. You can continue without providing your age. Your age range and choices are stored on your device; we do not add your age range to gameplay statistics events.
If you select an age below 18 or do not provide your age, optional gameplay statistics, crash-report sending and ad requests remain off. These options also start off for players aged 18 and older. Adults can turn each option on separately or play with all options off.
Changing these choices does not automatically erase the local records described below or data previously sent with your permission.
Game data kept on your device
To let you continue playing, the game saves level progress, completed levels and stars, virtual gems and support tools, selected appearances, acknowledged tutorials and the current round state on your device. Sound, vibration, age range, privacy and notification choices are also saved locally.
The current version has no game account, sign-in system, server-side progress storage or cross-device cloud save. There are no real-money in-app purchases; gems are virtual game currency. The game does not request access to your contacts, photos or precise location.
Your operating system's backup and restore features may separately manage local app data.
Optional gameplay statistics
If you enable “Gameplay statistics”, we use Firebase Analytics to understand level difficulty and how the game is used. Our gameplay events are limited to:
- Level number and whether a round is a tutorial or resumed game.
- Round result, moves, remaining time, stars and virtual gems earned; failure caused by time or water.
- Completion of an explanation of a new game mechanic.
- Hint, extra-time and water-support use; the game item and amount of virtual gems spent.
- Extra time granted after a rewarded video.
- App foreground activity and app version; whether an interstitial was shown, closed, failed or unavailable, and the level number.
Analytics may also process app-instance identifiers, app version, device and operating-system information, sessions and usage information. General location, such as country or region, may be derived from an IP address; this does not use the device's precise-location permission.
We do not add a name, email address, free text, a complete puzzle layout or a raw device identifier to these gameplay events. However, the service can process its own technical identifiers and network information. We do not claim that all of this data is anonymous. The current configuration does not permit Analytics data to be used for ad personalization.
Optional crash reports
If you enable “Crash reports”, reports are sent to Firebase Crashlytics to help find and fix crashes. They may contain stack traces and error messages, app version and app state at the time of the error, technical information such as device model, operating system and memory, and installation and session identifiers. If gameplay statistics are also enabled, some usage events may be associated with a report to help understand what happened before the error.
When you enable crash-report sending, sending may begin. Turning it off takes effect on the next app launch; close and reopen the game for the new setting to apply. Crash information may remain pending on the device while report sending is off. If you later enable sending, previously pending reports may also be sent. Turning the option off does not automatically delete reports already sent or still stored locally.
Interstitials, rewarded videos and ad choices
The current development version uses Google AdMob test ads. Live ad units are not connected. A full-screen interstitial may appear at a result departure or retry after every three attempts ended by a win, loss or explicit restart. If no ad is ready, the game continues. An interstitial does not grant extra time or gems. Choosing to watch a rewarded video for +20 seconds after time runs out is a separate, optional action and is not required to play the game.
In the current version, both ad formats are loaded only for players who select the 18-or-older age range and when Google's consent status permits requests. Google's ad-consent screen is shown where required. Rewarded videos also require their separate local preference; turning that preference off does not disable interstitials. Current ad requests are configured as non-personalized. A non-personalized or test ad can still involve data processing.
AdMob and its consent service may process your IP address and derived general location, app or device identifiers, ad impressions and video interactions, app and ad performance, error information and consent choices. Available identifiers depend on the device, operating system and permission settings. These data can be used to deliver ads, apply choices, measure the service and prevent abuse.
Where Google's ad privacy-options entry is required, use Settings (Ayarlar) → Privacy (Gizlilik) → Manage ad choices (Reklam tercihlerini yönet) to reopen Google's form. Enabling gameplay statistics does not grant ad consent.
The current iOS configuration does not request the IDFA advertising identifier for tracking across other companies’ apps or websites. It therefore does not present Apple’s ATT tracking-permission prompt. If we add a feature that uses an advertising identifier or cross-app tracking, we will provide the necessary explanation and permission flow separately. Analytics or notification permission does not grant tracking permission.
Optional reminder notifications
After initial setup, we ask whether you would like one daily puzzle reminder. If you choose to enable it, your phone presents its notification-permission prompt. The default reminder is scheduled for 19:00 each day in your phone’s local time. Reminders are created locally on your device; this feature does not use a remote push-notification server, APNs registration or Firebase Messaging. The reminder choice and schedule are kept on your device.
Use Settings (Ayarlar) → Notifications (Bildirimler) to turn reminders off. You can also change notification permission in your phone’s settings. You can play without granting permission. Operating-system settings such as silent mode, Focus, notification summaries and power management may affect delivery time.
When you contact support
The email address, message and any attachments you send to our support address are processed to respond to your request. Correspondence is handled through an email service. Turning off data options in the game does not automatically delete a support message you chose to send.
Service providers and processing locations
For services you enable, we use Google's Firebase Analytics, Firebase Crashlytics, AdMob and ad-consent services. An email service handles support correspondence. These providers process data to deliver their services, and processing and storage may take place outside your country.
Relevant provider information: Google Privacy Policy, Firebase privacy and security information, and Google advertising technologies.
Retention
Local progress and preferences are kept while the app data remains on your device. We do not promise a fixed number of days for pending local crash reports.
Retention of Analytics user-level and event-level records is managed through the linked Google Analytics service's data-retention settings. Aggregated statistics reports may not be subject to the same time limit. See Google Analytics retention information.
Google states that, after retaining Crashlytics stack traces and associated identifiers for 90 days, it begins removing them from live and backup systems. This does not mean every copy is deleted by the end of day 90. See Crashlytics retention information.
We do not state a single universal deletion period for ad and consent-service records. Google's retention information describes periods that vary by data type and processing purpose. Support correspondence is kept for the time needed to resolve and follow up on a request and maintain necessary records.
Changing choices and making data requests
Age range and optional choices are collected during initial setup. In Settings (Ayarlar) → Privacy (Gizlilik), you can change your age range and your gameplay-statistics, crash-report and video-for-extra-time choices. Press Save and continue (Kaydet ve devam et) to apply a change. When required, use Manage ad choices (Reklam tercihlerini yönet) on the same screen to open Google’s form. Turning off gameplay statistics stops the game's new statistics events. Crash reports follow the restart behavior explained above. Turning off rewarded videos stops new video requests; if a video is already open, this does not mean it will immediately close. Changes to preferences do not automatically erase data already processed.
You can remove local data using the app-data deletion options offered by your device. This also removes your level progress, gems and saved choices. On iPhone, offloading an app while retaining its data is different from deleting it with its data. You may need to manage operating-system backups separately.
For information, correction, deletion or other privacy requests, contact berkcanaskin03@gmail.com. Because the game has no account, an email address alone may not identify your technical records. We will ask only for additional information needed to assess your request and explain what action we can take. Your rights and the process that applies may depend on where you live and applicable rules. You may also contact the relevant data-protection authority.
This website
We do not add analytics, advertising code, tracking cookies or external fonts to these support and privacy pages. These pages are hosted on Cloudflare Pages. Cloudflare may process your IP address and technical request information to deliver the content and maintain security; see the Cloudflare Privacy Policy. External provider links take you to services with their own privacy practices.
Changes
We will update this policy if our services or data practices change. Where a new optional data purpose requires an explanation and choice, we will provide these in the app. Contact the address above if you have questions.