What ChoralHub stores about you, who can see it, and how you can have it deleted.
Last updated November 7, 2026
ChoralHub is operated by the people named in the footer of this site, who act as the data controller for the account you create.
Your choir's owner and administrators decide who joins the choir and what they can see inside it. For that part, they act as controllers too. If you want your membership of a choir ended, they are the people to ask.
Questions about any of this can go to the contact address in the site footer.
Only what you or your choir enters, and a record of how you use the app, described below. There is no advertising, no tracking across other sites and no analytics profile.
•Account: your email address and an encrypted password, handled by Supabase Auth. We never see your password.
•Profile: your name, voice part, and optionally a photograph.
•Contact and logistics: optionally your phone number, address, height, and whether you have a car. Height and car availability exist because they are used to arrange people on a stage and to organise lifts to concerts.
•Emergency contacts: optionally up to two people to call if something happens to you at a rehearsal or concert: their name, phone number and how they are related to you. Please make sure they agree to be listed.
•Choir activity: your attendance at rehearsals, recordings you upload and any link you add to them, comments you write, and which choirs you belong to.
•Choir fees: if your choir uses it, whether you have paid a fee the choir set (for example a weekly or monthly fee), how much you paid, with an optional note such as "cash", and which price group you are in (for example a student price), or a price of your own on one fee. Your choir's owner or an administrator sets and ticks it. Nothing is paid through the app, and only your choir's owner and administrators see it.
•Activity log: when you sign in, and changes you make such as uploads, edits and deletions. It keeps the service secure and lets your choir's owner see what happened in the choir.
•Games: each time you start one of the games, which game, piece and level you chose, in which choir, and whether you played to the end. We use this only to see whether the games are used. Your best Note Rain result on a piece is kept for your choir's leaderboard.
•Messages from us: we may now and then send you a message inside the app, with a title, a text and sometimes an image. We keep the message, its image and when you closed it, so it is shown to you once. Only you and we can see it.
•Calendar link: if you add your rehearsals to your own calendar, we keep a private link that belongs to you. Your calendar app (for example Google, Apple or Outlook) reads your rehearsals and concerts through it and keeps a copy in your calendar, under that company's own privacy terms. Anyone you give the link to can read them too. You can reset the link at any time, and it is deleted with your account.
•Health and diet: optionally your blood group, known illnesses or medical conditions, medicines you take regularly, allergies, and your diet (for example vegetarian, vegan, gluten-free, or anything you write yourself). This is handled separately, as explained below.
Everything except your email is optional. You can leave any of it blank and use the app.
Blood group, illnesses, medicines and allergies are health data. Under Turkish law (KVKK, Law 6698) they are special category personal data, and under the GDPR they fall under Article 9. Diet can reveal religious belief, which is a special category too. Both laws require consent that is explicit and specific to that data, rather than bundled into a general agreement.
So all of it sits under one consent of its own, separate from these terms. It is off by default, you are asked for it in your own profile, and every field under it is optional.
Withdrawing that consent deletes all of it. It does not merely hide it. You can withdraw at any time by unticking the box in your profile.
It is visible only to you and to the owners and administrators of your own choirs, and only while your consent stands. This is enforced by the database itself, which keeps health data in a separate, locked table, not merely by the app. It is never shown to other singers, never used for anything except emergencies and planning meals and travel, and never shared outside your choir.
You do not have to provide any of it. Nothing in the app stops working if you leave it blank.
Choirs are isolated from one another at the database level, not merely in the interface. A member of one choir cannot read another choir's data even if they try to reach it directly.
•Other members of your choir see your name, voice part, photo and attendance, and, if you play Note Rain at full tempo, your best result on each piece's leaderboard.
•Your choir's owner and administrators also see your contact details and emergency contacts, whether you have paid the choir's fees, and your health and diet information if you have consented. The owner also sees the choir's activity log, including when members sign in.
•Members of other choirs see nothing about you at all.
•We can technically reach the database to operate and repair the service, and do so only for that. We also see who has played which game, to learn whether the games are used; choirs do not see this.
In Supabase, which hosts the database and file storage, and on Vercel, which serves the application. Email is sent through Resend. If a conductor uses the AI assistant (an experimental feature for some choirs), what they write there is sent to Anthropic, together with the names of the choir's pieces and singers and their voice parts, so its Claude model can prepare a draft. Nothing is saved unless the conductor confirms it, and the conversation is not stored in ChoralHub.
When something breaks, a technical error report (what failed, on which page, which browser) goes to Sentry so we can fix it. It carries no account details, IP address or content you entered. If you turn on browser notifications, they travel through your browser maker's push service (Google, Mozilla or Apple), encrypted so that service cannot read them. In the ChoralHub phone app, notifications go through Google Firebase Cloud Messaging (on iPhone, also Apple's push service), which carries the notification's title and short text to your phone. A code for your phone is kept with your account until you turn notifications off, sign out or delete your account. To see which pages are used, Vercel Web Analytics counts page visits anonymously and without cookies. It cannot identify you or follow you to other sites. The video guides under Help are hosted on YouTube. A guide connects to YouTube only when you press play, through YouTube's privacy-enhanced player, and from then on YouTube sees that visit as it would on any site.
These providers process data on our behalf and may store it outside your country, including in the European Union and the United States.
Your profile is kept while your account exists. Delete your account and it goes.
Content you created inside a choir, such as attendance records, recordings and comments, belongs to that choir's history and may remain after you leave it, just as the minutes of a meeting outlive the people at it. Ask your choir's administrators if you want it removed.
If a choir is deleted, its data is deleted with it.
Your game plays, leaderboard results, fee payment records with their amounts, your price group and the messages we sent you are deleted with your account. Activity log entries stay, but they are no longer linked to you.
You can ask what is held about you, correct it, delete it, or object to it being held at all. Most of it you can do yourself from your profile page, which is faster than asking.
Where we rely on your consent, as with health and diet information, you can withdraw it at any time without giving a reason, and withdrawing is as easy as giving it was.
Under KVKK you may also apply to the Turkish data protection authority, and under the GDPR to your local supervisory authority, if you think something is wrong.
Only what is needed to keep you signed in. No advertising cookies, no third-party trackers, no analytics that follow you elsewhere.
If you play one of the video guides, YouTube's player may keep its own data in your browser. Nothing from YouTube loads before you press play.
If this document changes materially, the date at the top changes and you will be asked to read it again. Small corrections that do not change what we do will not interrupt you.