DrumSide is a drum practice app. This page explains what it collects, what stays only on your phone, why we use each piece of data, how long we keep it, and the rights you have over it.
Effective 1 November 2026 · Applies to the DrumSide app on Android and iOS
DrumSide is developed and published by Bastien Oger, an independent developer based in France. He is the data controller for the personal data described in this policy, within the meaning of the EU General Data Protection Regulation (GDPR).
For any question or request about your data, write to drumsideapp@outlook.com (see Contact).
DrumSide works fully offline out of the box. Only the features below use a network connection, and each is optional.
| If you use… | We collect | Stored |
|---|---|---|
| Just practicing, no profile | Nothing leaves your phone, apart from crash reports and anonymous usage counts (below) | device only |
| Creating a profile | Email address, display name, password (stored hashed), or your Google account ID, name, email and profile photo if you sign in with Google | Firebase Auth |
| Practice tracking, Studio patterns (no profile, or backup turned off) | Levels, streaks, saved grooves and fills, tempos, favorites | device only |
| Account backup (with a profile, on unless you turn it off) | A copy of your practice data: saved items, tempos, Studio patterns, practice minutes, levels and streaks, practice settings, and a random ID for the phone that made the backup | Cloud Firestore |
| Sharing to the Community | The pattern itself, your display name, votes you cast | Cloud Firestore |
| Reporting a shared pattern | The pattern ID, the reason you give, your account ID (never shown to other users) | Cloud Firestore |
| DrumSide Premium | An app user ID, subscription status and purchase history. Never your card or payment details | RevenueCat |
| Practice reminders | Nothing sent anywhere. Reminders are scheduled locally by your phone | device only |
| Crash reports (on unless you turn them off in You → Send crash reports) | When the app crashes or hits an error: what went wrong and where in the app's code, the phone model, Android or iOS version, app version, free memory and disk space, and a random installation ID. Never your name, email, account or what you play | Firebase Crashlytics |
| Anonymous usage counts (on unless you turn them off in You → Send anonymous usage counts) | A +1 on shared daily totals for all users together, at most once a day or once per install for each step: opened the app, practised, finished onboarding, first practice, first completed session, saw the Premium page, started Premium, came back 1, 7 or 30 days after installing. No account, no device or installation ID, nothing you play. Only the totals are stored | Cloud Firestore |
All data sent from the app to our services is encrypted in transit (HTTPS/TLS).
Everything you'd use without creating a profile works with no network access at all.
Without a profile, we can't read this data, back it up, or recover it if you lose your phone. Uninstalling the app deletes it.
With a profile, DrumSide backs this data up to your account (Cloud Firestore), so it comes back when you sign in on a new phone or after reinstalling. Only your account can read the backup. You can turn backup off in Profile → Backup; the data then stays on your phone only. Deleting your account deletes the backup.
A profile is optional. It lets your Premium subscription and community activity follow you if you change phones.
Signing up with email stores that email address, a display name you choose, and a securely hashed password, handled by Google's Firebase Authentication. Signing up with Google shares your Google account's name, email and profile photo with us.
We use this only to identify your account, show your display name on grooves you share, and send account email (verification, password reset). We never send marketing email.
The Community tab lets drummers share grooves and fills and vote on them. Sharing something makes it visible to every DrumSide user.
Under the GDPR, every use of personal data needs a legal basis. These are ours.
| Purpose | Legal basis |
|---|---|
| Creating and running your account, signing you in, account email | Performance of our contract with you (GDPR art. 6(1)(b)) |
| Publishing grooves you choose to share, and your votes | Performance of our contract with you (art. 6(1)(b)) |
| Checking your Premium subscription across devices | Performance of our contract with you (art. 6(1)(b)) |
| Backing up your practice data to your account and restoring it | Performance of our contract with you (art. 6(1)(b)) |
| Crash reports, to find and fix bugs | Our legitimate interest in an app that works (art. 6(1)(f)). You can turn them off at any time |
| Anonymous usage counts, to see whether new users find their way in and come back | Our legitimate interest in improving the app (art. 6(1)(f)). Only totals are kept, with no identifier, and you can turn them off at any time |
| Handling reports, preventing spam and abuse, keeping the service secure | Our legitimate interest in a safe community (art. 6(1)(f)) |
| Keeping purchase records required by tax and accounting rules | Legal obligation (art. 6(1)(c)) |
When you delete your account, your account data, backup, shared grooves and votes are removed from our systems. Requests by email are handled within 7 days.
We don't sell data, and we don't run ads or an analytics service. The only outside services are the ones that make accounts, the community, Premium, crash reports and the anonymous usage counts work. They act as our processors.
| Service | Used for | Their policy |
|---|---|---|
| Google Firebase (Authentication and Cloud Firestore) | Accounts, sign-in, community storage, account backup, anonymous usage totals | policies.google.com/privacy |
| Google Firebase Crashlytics | Crash reports | firebase.google.com/support/privacy |
| Google Sign-In | Signing in with a Google account | policies.google.com/privacy |
| RevenueCat | Subscription status across devices | revenuecat.com/privacy |
| Google Play / Apple App Store | Billing for DrumSide Premium | Google / Apple |
We may disclose account information if the law requires it, or to investigate abuse of the community feature (spam, harassment, impersonation).
Google and RevenueCat may process data in the United States and other countries outside the European Economic Area. These transfers are covered by the safeguards those providers offer, such as the EU–U.S. Data Privacy Framework and the European Commission's Standard Contractual Clauses.
Wherever you live, you can use these rights. If you're in the EU or UK, the GDPR guarantees them.
Profile → Account → Delete account removes your sign-in, email, display name, shared grooves and votes from our systems. You can also ask by email. See the account deletion page for details.
Open it from the Community tab and choose Remove. It disappears from every user's app.
Uninstalling DrumSide removes all on-device data. We never received it, so there's nothing for us to delete.
We answer rights requests within one month.
DrumSide is for a general audience learning drums and is not directed at children under 13. We don't knowingly collect personal data from children under 13. In France, if you're under 15, ask a parent or guardian before creating a profile (in other countries, check your local age). If you believe a child has created an account, contact us and we'll delete it.
Account data is stored with Firebase's standard encryption in transit and at rest. No method of transmission or storage is perfectly secure, and we can't guarantee absolute protection.
If this policy changes, we'll update the date at the top of this page. For significant changes, we'll also tell you inside the app.
Questions about this policy, or a request about your data: write to the developer directly.
drumsideapp@outlook.com
Bastien Oger, France