Privacy Policy

Last updated: 24 August 2026

This policy covers the DrumBlocx web app at drumblocx.com (also reachable at drumchops-web.web.app) — the practice tools, the Lessons area, creator subscriptions and the creator studio. The iPad app has its own separate policy.

DrumBlocx is run by Chi Chiu Shum (trading as DrumBlocx), ABN 68 992 572 301, in Brisbane, Queensland, Australia. We handle personal information under the Australian Privacy Principles.

The short version. You can use every practice tool without an account and without giving us anything personal. If you make an account we store your email and what you do in the Lessons area. If you subscribe to a creator, Stripe handles your payment and we never see your card. We do not sell your data, we do not run ads, and we do not use your data for anything except running the service.

1. Using DrumBlocx without an account

The practice tools need no account. Patterns you save are stored in your own browser, not on our servers.

We do count visits, so we know whether anyone is using the thing. Each browsing session adds one row of anonymous counters — a running total for the day, not a record about you. What goes into it:

These are stored as aggregate totals. There is no IP address, no name, and no way to pick an individual out of them.

How we get the country

To work out the country, your browser makes a request to ipwho.is, a third-party IP lookup service, which sees your IP address and returns a country code. We only ever store the country code. If you would rather this did not happen, an ad blocker or tracker blocker will stop it, and the site still works.

What we store in your browser

We do not use cookies. We do use browser storage:

KeyWhat it is
dc_cidA random identifier so we can tell a new browser from a returning one. Not linked to your name, email or account.
dc_countedMarks that this session has already been counted. Cleared when you close the tab.
dc_notrackOnly set if you opt out. See below.
dc_auth_hint, dc_has_lessons, dc_lessons_unreadRemembers that you have an account and whether there is anything unread in Lessons, so the page can show the right thing before it finishes loading.
Practice dataYour saved patterns, favourites and settings, kept in your browser.

Opting out of counting: add ?notrack=1 to any DrumBlocx URL. That browser stops being counted from then on. ?track=1 undoes it.

2. If you create an account

An account is needed for Lessons, subscriptions and the creator studio. We store:

WhatWhy
Email addressSigning in, account emails, connecting you to a teacher or creator
Display nameSo your teacher and creators know who you are
Whether your email is verifiedSome features require it

Passwords are handled by Google Firebase Authentication and we never see them. If you sign in with Google instead, Google tells us your email address, name and profile picture — nothing else, and we do not get access to your Google account.

3. If you use Lessons with a teacher

Lessons connects teachers with their students. When you are linked to a teacher we store: the invitation and the link between you, the practice patterns your teacher sends you, homework notes, your practice activity (sessions, tempos, how long you played) and skill levels your teacher records.

Who can see it: you and the teacher(s) you are linked to. Nobody else — not other students, not other teachers, not other creators.

4. If you subscribe to a creator

Creator subscriptions are paid through Stripe. Your card details go straight to Stripe and never touch our servers — we cannot see your card number.

Because the creator is the merchant of record for the sale, your payment goes into that creator's own Stripe account, and Stripe shares the normal transaction information with them: your email address, the amount, the date, and enough detail to issue a refund. We store which creator and tier you subscribed to, when the current period ends, and a Stripe subscription reference — not your payment details.

If you subscribe to a coaching tier, that creator automatically becomes one of your teachers in Lessons, and section 3 applies. If the creator asks intake questions, your answers are visible to that creator.

5. If you are a creator

Your creator page is public — your display name, handle, bio, picture, banner, genres, levels, and your published tiers and prices can be seen by anyone with the link. Do not put anything there you would not want public.

We store the content you publish: courses, lessons, videos, weekly drops and intake questions. Videos and images are stored in Google Firebase Storage and served to your subscribers through short-lived links.

When you connect Stripe, you deal with Stripe directly — they collect your identity and payout details under their agreement with you. We never see your bank details. We store your Stripe account reference and whether Stripe says you can accept payments and receive payouts.

6. Live video sessions

Live sessions and one-to-one video calls run on Daily.co. When a room is created we store the room reference and who it is for. The call itself — audio, video, anything shared on screen — runs through Daily.co under their privacy policy. We do not record calls.

7. Emails we send

Email is delivered by Resend. We do not send marketing email, we do not sell or share your address, and there is no mailing list to be added to.

8. Who else touches your data

ServiceWhat it doesWhat it sees
Google FirebaseSign-in, database, file storage, server functionsEverything stored in your account
StripeSubscription paymentsYour email, payment details, subscription history
ResendSending emailYour email address and the contents of those emails
Daily.coLive video roomsYour call audio and video while a call is running
ipwho.isCountry lookup for visitor countsYour IP address, at the moment of the request

That is the whole list. There are no advertising networks, no data brokers, no analytics companies, and no third-party trackers on this site.

Where your data lives

Our Firebase project and server functions run in Google's us-central1 region, so your data is stored and processed in the United States, and our other providers may process it in the United States or elsewhere. By using DrumBlocx you consent to your personal information being handled overseas. We choose established providers, but overseas recipients are not always subject to Australian privacy law and we cannot guarantee they will handle it the way an Australian entity must.

9. Children

Drum students are often young, and some are under 16. We collect the minimum needed for the feature to work — an email address and a name — show no ads, do no profiling, and share nothing beyond the linked teacher or creator. A parent or guardian can ask to see or delete a child's data at any time by emailing us. If you are under 18, get a parent or guardian's permission before making an account.

10. How long we keep things

11. Your rights

You can ask us to: show you what we hold about you; correct it; delete your account and its data; or explain something in this policy. Email chiubeat@gmail.com and we will act within a reasonable time — normally under 30 days.

Deleting your account. There is no self-service delete button yet, so email us and we will delete your account and associated data. If you have an active subscription, cancel it first (see the Refund & Cancellation Policy) so you are not charged again. Creators: deleting your DrumBlocx account does not close your Stripe account — do that with Stripe directly.

Unsubscribing from weekly summaries is instant via the link in any summary email.

If you are in the EU or UK, you also have the rights given to you by the GDPR, including the right to object to processing, to get a portable copy of your data, and to complain to your local data protection authority. Our lawful bases are performing our contract with you (running your account and subscriptions), your consent (visitor counting, which you can opt out of), and our legitimate interests (keeping the service secure and working).

12. Security

Traffic is encrypted in transit. Access to stored data is controlled by server-side security rules — students cannot read other students' data, creators cannot read other creators'. Passwords and payment details are handled by Google and Stripe respectively and are not stored on our systems. No system is perfectly secure; if a breach ever affects your personal information, we will tell you and the Office of the Australian Information Commissioner as the law requires.

13. Changes to this policy

If we change this policy in a way that materially affects you, we will email account holders or put a notice on the site before it takes effect. The date at the top always shows the current version.

14. Contact and complaints

Chi Chiu Shum, trading as DrumBlocx (ABN 68 992 572 301) — Brisbane, Queensland, Australia
Email: chiubeat@gmail.com

If you are not happy with how we have handled a privacy matter, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.