Privacy Policy
Choir Trainer (“we”, “the app”) is a web application at choir-trainer.com that helps choir singers learn their parts. It is operated by Elena Shamis, a sole proprietor in Rehovot, Israel, who is the controller of the personal data described here. Contact: info@choir-trainer.com.
The short version: the scores live on the conductor's own Google Drive, not with us. We keep only what is needed to run the service — who belongs to which choir, with which role, and the technical data that lets the app open the choir's folder on the conductor's behalf.
1. Who uses the app
- Choir owners and editors (conductors, accompanists) sign in with their Google account. The owner creates a choir; editors add and correct scores.
- Singers join a choir through an invitation link from its conductor. They do not need a Google account.
2. Data we collect
Owners and editors
- From Google sign-in: your Google account identifier, name, email address and profile picture link.
- An OAuth access token and refresh token for Google Drive, which let the app work with the choir's folder on your behalf. The refresh token is stored encrypted (AES-256-GCM); the key is kept separately from the database.
- Your choirs, your role in each, and records of changes you make (who changed which piece and when).
Singers
- The name and voice part you enter when you first join a choir, the date you joined and when you last opened the app.
- A signed cookie on your device that keeps you signed in to the choir.
- If your choir uses individual payment: the email address you give when paying. It also lets you restore access on a new device.
Everyone
- Anonymous usage statistics: a random identifier of the browser, the time and length of a visit, which pieces were opened and played, and which features were used. They contain no names and no IP addresses, and we use them only to see whether and how the app is used.
- Practice settings (chosen part, volumes, tempo) are kept only in your browser's local storage.
- Our hosting provider records technical request logs (including IP addresses) for security and operations, for a short period.
Payments
Payments are processed by AllPay (Israel). We receive the payment status, amount, date and the payer's name and email. Card details are entered on AllPay's page and never reach us.
3. Google user data and Google Drive
Choir Trainer requests these Google permissions: openid, email, profile and https://www.googleapis.com/auth/drive.file.
- What drive.file allows. The app can see and change only files and folders it created itself or that you opened with it. It cannot see or list anything else on your Drive.
- How we use it. To create a private folder for your choir on your Drive; to save there the scores you add, the corrections you make and, in the future, the performance recordings you upload; and to read these files so that the members you invited can practise with them. The folder is not shared by link. Files are read and written by our server on behalf of the choir's owner, only when a choir member uses the app.
- What we do not do. We do not keep copies of your scores in our database. We do not sell Google user data, do not use it for advertising, do not use it to train or improve generalized AI or machine-learning models, and do not let humans read it, except with your explicit permission, when needed for security or abuse investigation, or when required by law.
- Copies on singers' devices. To open pieces quickly, a singer's browser keeps a cached copy of the pieces of their choir. It is removed when the singer leaves the choir or clears the browser data.
Choir Trainer's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. Score recognition (OpenAI)
When an owner or editor asks the app to recognize a score from a PDF or photo, the pages are sent to the OpenAI API to be read into notes. This happens only on that explicit request. Under OpenAI's API terms, data sent through the API is not used to train OpenAI's models; OpenAI may keep it for a limited time to monitor abuse. The recognized score is saved to the choir's folder on Google Drive.
5. Service providers
| Provider | What for | Location |
|---|---|---|
| Vercel Inc. | Hosting of the website and server functions | USA / global edge network |
| Neon (Databricks) | Database of choirs, members, roles and payments | European Union |
| Google LLC | Sign-in and storage of scores on the owner's Google Drive | Global |
| OpenAI, L.L.C. | Score recognition, only on request | USA |
| AllPay | Payment processing | Israel |
| GitHub, Inc. | Storage of the anonymous usage statistics | USA |
Some of these providers are outside Israel. Data is transferred to them only as needed to run the service and under their data protection terms.
6. How long we keep data
- Account, choir and membership data: while the account or choir exists. When an owner deletes a choir or an account, we delete the related records within 30 days; the files on Google Drive stay with their owner.
- A singer removed from a choir loses access immediately; their name and part are deleted within 30 days.
- Payment records: as long as Israeli tax law requires (currently 7 years).
- Anonymous usage statistics: up to 3 years.
7. Your choices and rights
- You can withdraw the app's access to Google at any time at myaccount.google.com/permissions. The choir's folder and files remain on your Drive.
- Under the Israeli Protection of Privacy Law you may ask to see the personal data we hold about you, and ask us to correct or delete it. Write to info@choir-trainer.com; we answer within 30 days.
- If you believe your data is not handled properly, you may also contact the Israeli Privacy Protection Authority.
8. Cookies and local storage
We use only cookies needed for the app to work: a session cookie for signed-in owners and editors, and a signed cookie that keeps a singer in their choir. Practice settings and cached pieces are stored in the browser. We do not use advertising or third-party tracking cookies.
9. Children
Choirs may include singers under 18. For singers we collect only a name and voice part entered at joining. A choir that includes minors is responsible for obtaining any consent required from their parents.
10. Security
All traffic uses HTTPS. Google refresh tokens are encrypted at rest, sessions are signed, and access to each choir's files is checked on our server for every request.
11. Changes
We may update this policy. The effective date at the top shows the latest version. Significant changes will be announced to choir owners by email or in the app.