Privacy Policy
MyScore (the "App") places bowing marks on orchestra parts (PDFs or images) that you open on your device. My scores works without an account, and your score files never leave your device: ensembles share only bowing marks and score details (section 2). This policy explains what data the App handles and where it goes.
1. Data that stays on your device
The following data is stored only on your device. It is not sent to the operator or to any third party.
- Copies of the scores you import (PDFs, or images the App combines into a PDF), and what the App reads from them (positions of staves, measures and notes)
- Bowing marks, drafts and saved versions (for ensemble scores, saved versions are also shared with the ensemble: section 2)
- Settings (language, and for each score its part, time signature and mark style) and whether Premium is unlocked
The App reads scores and assigns bowings entirely on your device, and never uploads score files to a server. Deleting a score in the App, or deleting the App, deletes this data. The operator cannot access it. Depending on your device settings, your device's own backups (such as iCloud or Google backup) may include it. Files you export go only where you choose in the share sheet (for example Files, Photos or a printer).
2. Data sent to third-party services
Ensembles: Firebase Authentication and Cloud Firestore
Only if you use ensembles (My ensembles), the App signs in with an anonymous account (Firebase Authentication, Google LLC, USA); no name, email address or phone number is needed. So that members can share bowings, the following is stored in Cloud Firestore (Google LLC; servers in Seoul, Korea) and is visible only to members of that ensemble:
- Ensemble: name, invite code, and members (anonymous account ID, the name you set if any, role, date joined)
- Shared scores: title, part, page count and page sizes, edition fingerprint (a hash of the file, not the file itself), time signature, who added it and when, and when they confirmed that they lawfully have the score
- Saved bowing versions: bowing positions and directions, the author's anonymous account ID and name, and the time
Score files themselves are never uploaded. On ensemble scores the viewer shows the ensemble name and your name faintly at the bottom of each page, and files you export from an ensemble score carry them on every page. The App draws this on your device and sends it nowhere; an exported file goes only where you choose in the share sheet. If a rights holder reports a score, the operator may block that score or suspend the ensemble, and keeps the record of the report (including the reporter's details and the ensemble and score IDs) for three years.
Purchases: Apple App Store, Google Play, RevenueCat
Premium is a subscription processed by Apple or Google. The App never handles card details. To confirm your subscription (renewal, expiry and free-trial eligibility) and restore purchases, when the App starts and when you open the purchase screen, purchase receipts and transaction details, an anonymous identifier generated by the App, and basic device and app information (such as OS and app version) are sent to RevenueCat (RevenueCat, Inc., USA). No name, email address or other identity data is included.
Usage statistics: Google Analytics for Firebase
To improve the App, usage events are sent to Google Firebase (Google LLC, USA): the screens you open and the features you use (for example running auto bowing, saving a version or opening the Premium screen) as numbers and categories only (which engine or part, the time signature, how many marks, success or failure). Firebase also records the app version, device model and OS, language, approximate region (derived from your IP address), an app-instance identifier and, on Android, the install source reported by Google Play. When you buy Premium, a purchase event with the product and price may also be recorded.
- We never send score titles, file names, score contents or your bowing marks.
- The App does not collect your device's advertising identifier, and this data is not used for advertising or ad personalization.
- If you turn off Send usage statistics in Settings, nothing more is sent.
Error reports: Firebase Crashlytics
If the App crashes or hits an error, a report is sent to Google Firebase (Google LLC, USA) so we can fix it: where in the App's code it went wrong, the device model and OS, the app version, the screens opened just before, and an installation identifier. Reports contain no score files, titles or bowing marks. They are sent only while Send usage statistics is on.
3. Transfers abroad
Except for Cloud Firestore (servers in Seoul), these services process data on servers outside Korea, mainly in the United States. Data is sent over encrypted connections while you use the App.
| Recipient (country) | Data | Purpose | Retention |
|---|---|---|---|
| Google LLC: Firebase Authentication (USA) | Anonymous account ID | Signing in to ensembles | Until you delete your account |
| RevenueCat, Inc. (USA) | Purchase receipts and transactions, anonymous identifier, device and app information | Confirming subscriptions and restoring purchases | Under RevenueCat's policy |
| Google LLC: Firebase (USA) | Usage events (including purchase events with product and price), device and app information, approximate region, app-instance identifier | Usage statistics | Under the Google Analytics data-retention setting |
| Google LLC: Firebase Crashlytics (USA) | Error reports (where in the code, device and app information, recent screens), installation identifier | Fixing errors | Under Crashlytics' data-retention policy |
If you do not want usage statistics and error reports to be sent, turn off Send usage statistics in Settings; every feature of the App keeps working. The transfer for confirming purchases is needed to provide buying and restoring, so it cannot be turned off separately. Ensemble data is sent only when you use ensembles.
4. Your choices and rights
- Usage statistics and error reports: turn them on or off at any time in Settings › Send usage statistics.
- Data on your device: deleted when you delete a score in the App or delete the App.
- My scores needs no account. If you have used ensembles, Settings › Delete account takes you out of every ensemble and deletes your anonymous account. Bowing versions you saved stay in the ensemble's history (with the name you had then) until that score or the ensemble is deleted. For other requests to access, delete or stop processing data, write to the address below and we will help as far as we can.
- Users in the EU and UK: the legal basis is performance of the contract for confirming purchases and for ensembles (Art. 6(1)(b) GDPR) and our legitimate interest in improving the App for usage statistics and error reports (Art. 6(1)(f) GDPR). You have the rights of access, rectification, erasure, restriction and objection, and you may lodge a complaint with the data protection authority in your country.
5. Permissions the App requests
The App asks for no special permissions up front. It reads only the files and photos you choose in the system picker; it does not access the rest of your photo library, or your camera, microphone, contacts or location. On iOS, if you save exported images to Photos, the system asks for permission to add photos, which the App uses only for that.
6. Retention and deletion
On-device data is kept until you delete it or uninstall the App. Data sent to third-party services is kept under each service's policy; usage statistics are deleted according to the Google Analytics data-retention setting. Ensemble data is kept until the score is deleted from the ensemble, the ensemble is deleted or you delete your account; versions you saved stay until that score or the ensemble is deleted. Copyright report records are kept for three years.
7. Children
The App is not directed at children under 14 and does not knowingly collect their personal data.
8. Security
Data sent to third-party services travels over encrypted connections (HTTPS). The App never asks for your email address or phone number. The name you use in ensembles is optional and visible only to that ensemble's members.
9. Changes
Changes will be posted on this page with a new effective date. Significant changes will be announced on this page before they take effect.
10. Privacy officer and contact
Privacy officer: the operator of MyStudio · Email: support@mystudioapps.com