Last updated: 7 September 2026
This Privacy Policy applies to Drumpling ("the App") and explains how information is processed when you use the App.
The App does not require you to create an account. Drumpling does not ask for or intentionally collect your name, email address, phone number, or other contact information through the App.
Drumpling does not operate a backend for storing your generated drum loops, saved content, or App settings.
Generated loops, saved content, preferences, usage limits, and similar App data are stored locally on your device.
Microphone audio used by microphone-based features such as the tuner is processed locally on your device. Drumpling does not upload or store microphone audio.
Local App data generally remains on your device until you delete it, clear the App's data, or uninstall the App.
The free version of Drumpling uses Google AdMob to provide banner and rewarded advertisements.
Google and its advertising partners may process information for purposes such as delivering advertisements, measuring advertising performance, preventing fraud, and, where you have permitted it, personalizing advertising.
Depending on your device, location, consent choices, and Google settings, this information may include:
device or advertising identifiers;
IP address;
approximate location;
device and operating-system information;
App interactions;
advertising interactions; and
diagnostic information.
Where required by applicable law, Drumpling uses Google's User Messaging Platform (UMP) to obtain and manage consent for advertising-related processing.
You can review or change available Google privacy choices through the privacy controls provided inside Drumpling.
For more information about how Google processes information, see:
https://policies.google.com/privacy
Drumpling uses Google Analytics for Firebase ("Firebase Analytics") to understand how the App is used and to improve its features, reliability, user experience, and business decisions.
Firebase Analytics may process pseudonymous information such as:
App-instance or installation identifiers;
device and operating-system information;
App version;
country or approximate location derived from network information;
App sessions and interactions;
screens or features used;
diagnostic and technical information; and
purchase, subscription, paywall, and feature-use events.
Drumpling also records limited product-usage events. These may include information such as:
when a groove is generated, saved, previewed, or exported;
when Jam Mode starts, ends, reaches its free-use limit, or encounters an error;
Jam duration;
number of bars played;
number of generated Jam sections or chunks;
tempo;
genre;
time signature;
drum kit;
whether transitions are enabled;
whether the user is using the free or Pro version;
remaining generation credits;
which App feature caused a usage limit or paywall to appear; and
whether a subscription flow was opened or successfully resulted in Pro access.
These events are intended to describe use of App features rather than directly identify you.
Drumpling does not intentionally send Firebase Analytics:
your name or email address;
microphone recordings;
microphone input;
tuner pitch data;
generated MIDI note content;
exported audio or MIDI files;
custom loop names; or
other text that you write yourself.
For users in regions where consent is required, Firebase Analytics is disabled until the applicable Google UMP consent process has resolved and analytics consent has been granted.
Drumpling also provides a "Usage analytics" control under Information → Privacy. You can use this setting to disable Firebase Analytics collection. Changing relevant privacy choices later updates whether analytics collection is permitted.
Declining optional analytics does not prevent you from using Drumpling's core features.
For more information about Firebase and privacy, see:
https://firebase.google.com/support/privacy
and:
https://support.google.com/analytics/answer/11593727
Subscriptions and other Google Play purchases are processed through Google Play. Drumpling does not receive or store your payment-card details.
Drumpling uses RevenueCat to provide, validate, restore, and manage subscription entitlements.
RevenueCat may process information necessary to provide these services, including:
a pseudonymous or anonymous App User ID;
product and subscription status;
Google Play purchase tokens and transaction information;
purchase timestamps;
entitlement information;
last-seen information; and
technical information such as device type and operating system.
Drumpling does not intentionally provide RevenueCat with your name or email address.
RevenueCat acts as a service provider/data processor for subscription-related end-user information processed on Drumpling's behalf.
For more information, see RevenueCat's privacy and GDPR information:
https://www.revenuecat.com/privacy
https://www.revenuecat.com/gdpr
Where applicable data-protection law requires consent for analytics, advertising personalization, advertising storage, or similar optional processing, Drumpling relies on the privacy choices collected through Google's consent system.
You may refuse optional consent without losing access to the App's core functionality, although features that depend on advertising, such as rewarded advertising, may not be available when the required advertising consent or permissions are not provided.
Subscription-related information is processed as necessary to provide, validate, restore, and manage subscriptions and paid App functionality requested by you.
You can change available advertising and analytics privacy choices later through the privacy controls provided in the App.
Drumpling does not sell your personal information.
Information may be processed by third-party service providers used to operate specific App functionality, principally:
Google, for Google Play, AdMob, consent management, and Firebase Analytics; and
RevenueCat, for subscription and entitlement management.
These providers process information according to their respective terms, privacy policies, and applicable data-processing arrangements.
If you choose to share an exported audio or MIDI file, Drumpling provides the selected file to Android's sharing functionality.
The file is then sent only to the application or service that you choose. How that receiving service processes the file is governed by that service's own privacy practices.
Some service providers used by Drumpling may process information in countries outside Finland or the European Economic Area.
Where applicable, those providers are responsible for using legally recognized safeguards for international data transfers as described in their privacy and data-processing documentation.
Depending on where you live, you may have rights concerning personal data processed in connection with Drumpling, including rights to request access, correction, deletion, restriction, or other rights provided by applicable law.
Because Drumpling does not require an account and does not directly collect identifying contact information, some information processed by Firebase, Google, or RevenueCat may be associated only with pseudonymous device, installation, advertising, or transaction identifiers. This can limit Drumpling's ability to identify which records belong to a particular person without additional information.
You may contact Drumpling regarding a privacy request using the contact information below. Where technically possible and legally required, we will assist with requests relating to information processed on Drumpling's behalf.
You can also:
disable Usage analytics through Information → Privacy;
review or change available Google consent choices through Drumpling's privacy controls;
manage or cancel subscriptions through Google Play or Drumpling's subscription-management tools; and
remove locally stored Drumpling data by clearing the App's data or uninstalling the App.
Drumpling is not directed to children under the age of 13, and we do not knowingly collect personal information directly from children under 13.
Where local law requires a higher minimum age for consent to optional data processing, applicable consent requirements continue to apply.
Drumpling limits the information it collects and does not operate a user-account or cloud-storage backend for your generated loops and App content.
Third-party services used by Drumpling maintain their own technical and organizational security measures for information processed through their systems.
We may update this Privacy Policy when Drumpling's features, service providers, or data-processing practices change.
The current version will be made available through the App or the location where this Privacy Policy is published. The "Last updated" date above indicates when the policy was most recently revised.
If you have questions about this Privacy Policy or want to make a privacy-related request, contact:
support@drumpling.com