Privacy Policy

1. What we store, and why

Every item below exists because a feature you asked for needs it. Nothing here is collected for analysis, resale, or advertising.

• Your account: name, email address, and — if you add them — an avatar, cover image, and short bio. Needed because the platform has a sign-in.
• Sign-in sessions: a session token, plus the IP address and browser user-agent of the device that signed in. This is how you stay logged in and how you or we can spot a session you do not recognise. Sessions expire and are deleted.
• What you make and save:favourites, collections, uploads to your drive, and your membership in a teacher's classroom. This is your content; it exists because you created it.
• Your streak and level: a handful of running totals — your XP, your level, your current and longest streak, your total time practised, and the date you last practised. When you finish practising, the length of the run is added to those totals and the run itself is thrown away: we do not keep a record of which piece you played, the tempo you reached, or how well you scored. There is no practice history to hand over, because we never write one.
• Subscription status: if you subscribe, we store which plan you are on and until when.

2. What we do not do

• No third-party analytics. There is no Google Analytics, no Mixpanel, no Meta pixel, and no equivalent in our code.
• No advertising, no ad networks, and no tracking across other websites.
• No selling, renting, or trading of personal data, in any form, to anyone.
• No behavioural profiling and no automated decisions made about you.
• No reporting of your listening or practice history to publishers or rights organisations.
• No marketing email you did not ask for. We send account email only — verification and password resets — plus notifications you switch on yourself.

3. Your microphone and MIDI instrument

Wait Mode listens to you play. That listening happens entirely inside your browser: the audio is analysed for pitch on your own device and is never uploaded, never recorded by us, and never stored. The same is true of a connected MIDI keyboard — we receive the result of the comparison, not the sound. If you use the in-app recorder, the recording is made on your device and is yours; it goes nowhere unless you choose to save or share it.

There is one exception, and it never turns itself on: if we have invited you as a tester and you have accepted, a measurement session sends us the numbers the detection model produces — still not the audio. See section 6b.

4. Live classes

Live sessions are carried by LiveKit, which routes the audio and video between the people in the room. That is what makes the call work. We do not run server-side recording of live sessions.

5. Payments

Paid plans are not open yet, so no payment data exists. When they do open, subscriptions on the web will be handled by Polar as merchant of record; a purchase started inside a mobile app will be handled by Apple or Google and reported to us through RevenueCat, which tells us your account id and what you are entitled to. We will never see or store your card number — what comes back to us is your subscription status, which is what unlocks premium features.

6. Service providers

We keep this list short deliberately. These are the only third parties that touch your data, and each does one job:

• Turso — the database your account and content live in.
• Vercel — hosting. Standard server logs, as any web host keeps.
• Cloudflare R2 — storage for media you upload.
• Resend — sends account email such as verification and password resets.
• LiveKit — carries live class audio and video.
• Polar — subscription billing on the web, once paid plans open.
• RevenueCat — relays mobile in-app purchases to your account. Not switched on yet either.

That is the whole list. We run no error-monitoring or crash-reporting service today; if we ever add one, it appears here before it is switched on.

6b. Microphone measurement programme (QA accounts only)

Some accounts are invited to act as testers so we can measure how accurately note detection works through a microphone. This programme never turns itself on: the account has to be granted the role, and the person has to accept before the first recording.

While a measurement session runs, the device sends us three things: pitch probabilities produced by the detection model, key events from the connected MIDI instrument, and a description of the instrument, room and microphone that the tester writes themselves.

We do not send or store any audio recording. What leaves the device is the numbers the model produced, not sound, and it cannot be turned back into speech from the room.

Testers can see their own sessions and delete any of them at any time; deleting removes both the file and the database record. This data is only used to improve note detection.

7. StageScore (iOS and Android app)

Everything above describes the web platform. None of it applies to StageScore, our sheet-music reader for the music stand:

• No account, no sign-in.StageScore is not connected to your Backing & Score account.
• Nothing is collected. No personal data, no usage logs, no analytics, no diagnostics, no tracking.
• Everything stays on your device.Your PDFs, annotations, bookmarks, jump links, page order, labels, setlists, and preferences live in the app's own storage. Backups are ordinary files you keep and share yourself.
• It works offline. The app makes no network requests of its own. The only outbound action it can take is handing a link you tap in its About screen to your browser or mail app.
• Files. It reads the PDFs you import and records their file timestamps to cache page previews, which stay on the device.

More about StageScore

8. Keeping and deleting your data

Your account data stays for as long as your account does. Ask us and we will send you a copy of it, correct it, or delete it — write to [email protected] and deleting your account removes your personal information from our active databases. Some billing records must be kept for tax purposes, as the law requires of any business.

9. Children

Younger students often learn through a teacher's classroom. If a student is below the age of digital consent where they live, the account should be created and managed by a parent, guardian, or the teacher acting with their permission.

10. Changes to this policy

If we ever start collecting something that is not on this page, this page changes first and we say so plainly. It is a short list on purpose, and we intend to keep it that way.

11. Contact

Questions, requests, or anything that looks wrong on this page: [email protected]. General help lives on our Support page.