Privacy Policy
This policy says what Scoreflection does with data about you, why it is allowed to, and what you can tell us to do instead. It is written to be read, not to be survived.
1. The short version
- Much of the app needs no account: the library, playback, the tuner and the two games that only ask you to listen all work without one. The features that listen to you play are the paid Practice plan, and a plan is tied to an account.
- Listening to you play happens on your own device. The sound is not sent anywhere.
- Reading a photo of sheet music does not. That picture is sent to our server, read there, and thrown away β see section 4, which explains exactly what happens to it.
- There are no adverts and no profile of you.
- Nothing you have to consent to is switched on by default.
2. Who is responsible
Scoreflection
Laura Steffan
Erfweiler StraΓe 12
66994 Dahn
Germany
For privacy matters: privacy@scoreflection.com · Imprint
We have not appointed a data protection officer, because the legal conditions for one (Section 38 BDSG) are not met here. The competent supervisory authority is:
Der Landesbeauftragte fΓΌr den Datenschutz und die Informationsfreiheit Rheinland-Pfalz
Hintere Bleiche 34
55116 Mainz
Germany
https://www.datenschutz.rlp.de
3. What we collect, why, and what allows us to
Each row is a purpose. If a purpose does not apply to you β you have no account, you never turned contributions on β then nothing in that row exists for you.
- Your account
- Email address, a password we only ever store hashed, an age band, which version of the terms you accepted and when, and your real name if you joined the forum. Needed to give you the account you asked for — Art. 6 (1) (b) GDPR.
- Signing in with Google or Apple
- If you sign in with Google or Apple instead of a password, the provider confirms who you are and passes us an account identifier, your email address (with Apple, a relay address if you choose to hide yours) and whether it has verified it. We keep the identifier with your account so the next sign-in finds the same account; we do not receive your name, picture, contacts or a password. What Google or Apple process themselves is their responsibility (section 5). The basis is your account — Art. 6 (1) (b) GDPR. You never have to use it: an email address and a password work just the same.
- Keeping the account yours
- Sign-ins and failed sign-in attempts, with the IP address and a description of the device. This is how a break-in is noticed at all, and it is our legitimate interest in a service that is not quietly taken over — Art. 6 (1) (f) GDPR. The IP address and the device description are erased after 30 days; the record that the sign-in happened stays with your account for 13 months (section 7). From those records we also count how many accounts were in use in a week — a number and never a list of who, on the same legal basis: we need to know whether the service is being used at all.
- Paid plans
- Your email address, what you subscribed to and when. Card details are entered at Stripe and never reach us. Necessary for the contract — Art. 6 (1) (b) — and, for invoices, a legal obligation we cannot waive even if you ask — Art. 6 (1) (c) with sec. 147 AO.
- The free week on a new device
- So that each device can try the Practice features without an account for one week only once, the app reads the device identifier the operating system gives it — only once you tap “Start the free week” in the app, never before — and sends it to our server. There it is immediately converted into a value that cannot be turned back into the identifier; only that value, the platform and when the device first appeared are kept — never the identifier itself, and never together with an account. The basis is our legitimate interest in giving the free week once per device — Art. 6 (1) (f) GDPR.
- Unlocking the listening model on your device
- Before the listening model works on a device, and from time to time after that, the app checks with our server that it may use it. Each check carries the device identifier described above and a confirmation from the operating system that the request comes from our unaltered app on a genuine device: Google Play Integrity on Android, Apple App Attest on iOS (section 5). On a paid plan the identifier is only used for that check and not kept. During the free listening trial we keep it, converted in the same irreversible way, together with your account and how much of the trial has been used, so that the trial is given once per device and once per account. Each check is recorded in the same log as sign-ins. The basis is the contract — Art. 6 (1) (b) — and our legitimate interest in keeping the model from being copied and the trial from being collected twice — Art. 6 (1) (f) GDPR. Section 7 says how long each part is kept.
- Orders, cancellations and withdrawals on this website
- When you order a plan, we record who ordered what at which price and when, and which version of the terms applied, and send you the contract confirmation. When you cancel or withdraw through the forms on this website, we store what you declared — name, address, reference, time — and confirm it to you. The request's IP address and device description are kept too, because these forms have to work without signing in and abuse could not be investigated otherwise; they are deleted after 30 days. The basis is the contract and our legal duty to confirm orders, cancellations and withdrawals — Art. 6 (1) (b) and (c) GDPR — and, for the IP address and device description, our legitimate interest in forms that cannot be turned against other people's contracts — Art. 6 (1) (f).
- Reading a photo of sheet music
- The image you send, for as long as the transcription takes. You asked for the transcription, so the basis is the contract — Art. 6 (1) (b). Section 4 says what is and is not kept.
- Which scores the library may show you
- Some scores are public domain in the EU but still protected in the United States. To decide which ones to show, our server looks up the country of the IP address your request comes from, in a database kept on our own server, and also reads the region your device reports. If either says United States, you see only the scores that are public domain there too. The address is used for this one lookup and is neither stored nor passed on, and neither is the country. The basis is our legitimate interest in not making protected works available where they are protected — Art. 6 (1) (f). The country database is “IP to Country Lite” by DB-IP, licensed under CC BY 4.0.
- Practice statistics and practice recordings
- Only if you switch contributions on, and only ever on that basis — your consent, Art. 6 (1) (a). They are not linked to your account; they carry a random installation number instead. You can withdraw at any time in the app's privacy settings, which also erases what was already sent and still carries that number. Withdrawing does not undo what was lawful before you did. If you are under 16, you cannot give this consent on your own (Art. 8 GDPR): only switch contributions on if a parent or guardian agrees.
- Problem reports you send from the app
- When you circle a passage and report that the notation is wrong, or that the app misheard what you played: your description, the bars, the title of the piece, and what we need to see the same thing you saw — app version, device model, screen size and display settings. You choose for each report whether it goes with your account, so that we can ask you a question, or with a random report number that leads nowhere. Fixing a fault you told us about is our legitimate interest — Art. 6 (1) (f) GDPR. Two things travel only if you tick their box in the report, and on no other basis — your consent, Art. 6 (1) (a): a score file of your own, and, for a report that the app misheard you, the last ten seconds of microphone sound. A recording sent with a report is used to find that one fault. It is used to train a model only if you separately agree to that. Section 7 says how long each part is kept.
- The community forum
- Your nickname, your posts, and — held privately, never shown — your real name, so that there is somebody behind every post. The forum itself is the contract — Art. 6 (1) (b); holding the name is our legitimate interest in a community that can be held to account — Art. 6 (1) (f).
- Writing to us
- Your message, your address, and our answer. The contact form and the enquiry form on the page for music schools are the same thing: what you type there — name, address, subject and message — reaches us as an email and is kept like any other correspondence, and nowhere else. Handling your request — Art. 6 (1) (b) and (f); where you are exercising a data protection right, answering it is itself a legal obligation — Art. 6 (1) (c).
- The app waitlist
- If you ask on the waitlist page to be told when the app is available, we keep your email address, whether you asked about Android or iOS, the instruments you ticked, the language of the page and when you signed up — nothing else, not your IP address. The instruments tell us which listeners to finish first; we only ever look at them as a count per instrument. To make sure the address is yours, we first send it one email with a confirmation link. You are on the list only once you have clicked that link, and we note when the email went out and when you confirmed; an address that is not confirmed is deleted after 7 days. After that we use it for one thing: a single email when the app can be downloaded for your phone. No newsletter, and it is never passed on. The basis is your consent — Art. 6 (1) (a). You can withdraw it with one click, with “Take me off the list” in the confirmation email, or by writing to support@scoreflection.com; either way the address is deleted straight away. The list is stored with Cloudflare, in a database held in the EU, and the confirmation email is sent through our mail server at Hetzner (both in section 5); section 7 says how long.
- This website
- Server logs kept briefly to keep the site up and to see attacks — Art. 6 (1) (f). Your light/dark and language choices are stored in your own browser and never sent to us.
- The tuner and the metronome on this website
- The tuner opens your microphone only when you press Start, and the sound is worked out inside the page: nothing is recorded, nothing is sent to us, and no server is involved at any point. Press Stop, switch tabs or leave the page and the microphone is released again. Both tools remember their settings — the reference A, the tuning you picked, the tempo, the beats in a bar — in your own browser, which is the setting you asked for by changing it; nothing else is kept, and none of it reaches us.
- Signing in on this website
- The account page and the door to the community sign you in with your Scoreflection account. To keep you signed in while you move between the two and the forum, the page stores the sign-in — two tokens the server issued and the address you signed in with, never your password — in your own browser. By default that lasts until you close the tab. If you tick “Stay signed in on this device” it stays until you sign out, or for 30 days without a visit. It is stored because you asked to be signed in, which is the service you requested — sec. 25 (2) no. 2 TDDDG, Art. 6 (1) (b) — so it does not ask your permission, and it is used for nothing else.
- Which pages and buttons on this website get used
- A counter goes up: for the page, for the button, for the day, and for the language it happened in. On the first page of a visit a second counter goes up for where the visit came from: one word for the kind of place — a search engine such as Google, a social network such as Instagram, an email, or “direct” when there was none — taken from a fixed list in the page, never the address of the page you came from (anything not on the list counts as “other”), and the country. The country is worked out by Cloudflare, who delivers this website, from the connection, and handed to us as two letters; we neither see nor keep the IP address it used. Nothing is stored on your device for any of it, and the count carries no identifier, no IP address and no clock time — there is no record here that is about you. That is why it does not ask your permission, and it is also why there is nothing in it we could hand back to you or delete on request: we would not know which of the numbers was yours. We want to know which pages explain the app, which ones lose people, and how people find us — Art. 6 (1) (f).
- Which version of a page you were shown
- We sometimes show two versions of a page to find out which one explains things better. This stores which one you were shown, so the page does not change under you on the next visit. It is not shared with anyone, and no profile is built from it. Because it is stored on your device it happens only if you say yes — Art. 6 (1) (a), and sec. 25 (1) TDDDG, which asks separately about storage whatever else allows it. Privacy choices at the foot of every page takes that back as easily as it was given, and refusing changes nothing about how the site works.
- Cookies
- This website sets no cookies. What it keeps in your own browser is listed above: your light/dark and language choice, the settings of the tuner and the metronome, your sign-in when you sign in, your answer to the question about page versions and, only if you said yes, which version you were shown. The community forum sets one cookie, a session cookie that keeps you signed in and protects its forms against misuse; it expires after two hours without use. It is needed for the forum you chose to use — sec. 25 (2) no. 2 TDDDG — and is used for nothing else.
We do not profile you, and no decision with a legal or similarly significant effect on you is made automatically — Art. 22 GDPR.
4. The two models
Two things in Scoreflection are machine-learning models we trained ourselves. They matter to your privacy because they differ in one respect: where they run.
- Scoreflection Listening Model — runs on your device
- Input: the sound of you playing. Output: the notes it believes it heard, and how they line up with the score. The sound does not leave your device to make this happen.
- Scoreflection Score Reader — runs on our server
- Input: a photograph or scan of printed sheet music. Output: a machine-readable score (MusicXML). The image is held only for as long as the transcription runs and is not kept afterwards. A result waiting to be collected is held for at most 30 minutes.
So for listening, the sound of your playing never leaves your phone, and a photograph of a printed page does. What the page shows is printed music, and we never keep the picture. It is not stored, not used to train anything, and not shown to anyone. A finished transcription is also emailed to your own account address, so it reaches your mailbox as well as your app.
Both models can be wrong, and a score they produce is marked as machine-read where the app shows it — that mark is required of us by Art. 50 of the EU AI Act, and it is also just honest. Check anything a model tells you before you trust it.
5. Who else touches any of this
Every company below is bound by a data processing agreement, or is named because it decides something itself and you should know.
- Hetzner Online GmbH
- Hosting of our servers, including the community forum and the score reader, and our email (the mails we send you and the mail you send us). Located in: Germany. Privacy policy.
- Cloudflare, Inc.
- Delivery of this website, protection against attacks, storing the app waitlist, counting how often handed-out links are followed, naming the country a visit to this website came from, and storing our backups, which are encrypted before they leave our server so that Cloudflare cannot read them, in storage located in the EU. Located in: USA, with EU edge locations. Transfer to a third country on the basis of EU Standard Contractual Clauses and the EU-US Data Privacy Framework. Privacy policy.
- Stripe Payments Europe, Ltd. (acting on its own responsibility, not on our instructions)
- Payment processing for paid plans. Located in: Ireland, with transfers to the USA. Transfer to a third country on the basis of EU Standard Contractual Clauses and the EU-US Data Privacy Framework. Card details are entered at Stripe and never reach our servers. Privacy policy.
- DeepL SE
- Translating forum posts and support correspondence on request. Located in: Germany. Submitted text is not used for training. Privacy policy.
- Google Ireland Limited (acting on its own responsibility, not on our instructions)
- Sign in with Google, only if you choose it: Google confirms who you are and passes us an account identifier, your email address and whether Google has verified it. Located in: Ireland, with transfers to the USA. Transfer to a third country on the basis of the EU-US Data Privacy Framework. Privacy policy.
- Google Ireland Limited (acting on its own responsibility, not on our instructions)
- Play Integrity, on Android only, when the app checks that it may use the listening model: Google confirms that the request comes from our unaltered app installed from Google Play on a genuine device. Google learns that our app asked for this check on that device, not who you are. Located in: Ireland, with transfers to the USA. Transfer to a third country on the basis of the EU-US Data Privacy Framework. Privacy policy.
- Apple Distribution International Ltd. (acting on its own responsibility, not on our instructions)
- App Attest, on iOS only, when the app checks that it may use the listening model: Apple confirms that the request comes from our unaltered app on a genuine device. Located in: Ireland, with transfers to the USA. Transfer to a third country on the basis of EU Standard Contractual Clauses and the EU-US Data Privacy Framework. Privacy policy.
- Apple Distribution International Ltd. (acting on its own responsibility, not on our instructions)
- Sign in with Apple, only if you choose it: Apple confirms who you are and passes us an account identifier, your email address (or the relay address Apple creates if you hide yours) and whether Apple has verified it. Located in: Ireland, with transfers to the USA. Transfer to a third country on the basis of EU Standard Contractual Clauses and the EU-US Data Privacy Framework. Privacy policy.
What we do not use:
- No advertising network, and no adverts of any kind
- No automated decision-making with legal effect
We measure two things about this website, and they are not the same kind of thing. The first is a count of how often a page was opened and its buttons used, and of how often the links we hand out were followed. For the first page of a visit it also counts what kind of place the visit came from β a search engine, a social network, an email, or typed in directly β as one word from a fixed list, never the address of the page you came from, and the country the visit came from, which Cloudflare, who delivers this website, works out from the connection; we neither see nor keep the IP address it used. It stores nothing on your device, carries no identifier, no address and no timestamp finer than the day, and there is nothing in it that could be traced back to you β so it rests on our legitimate interest in knowing which pages and links are actually used and how people find them, Art. 6 (1) (f). We compare those counts with the number of people who joined the app waitlist each day and how many named each instrument β the numbers, never the addresses. The second is A/B testing: we sometimes show two versions of a page, and remembering which one you saw does store something on your device, so it happens only if you agree to it and only for as long as you do. That is what the banner asks about, and the link in the footer takes the answer back. We use no third-party analytics service, neither is shared with anyone, and no profile of you is built from either. That describes what is running now rather than promising anything about later; if it changes, this section changes with it, and it changes before the new thing starts.
The app can show you other pieces like the one you are looking at. Those suggestions are worked out from the music itself. They are not worked out from you β not from which scores you have opened, downloaded or rated, and not from what anybody else has done either. Asking for suggestions records nothing and builds no profile of you. That describes what runs today rather than promising anything about later; if it changes, this section changes with it, and it changes before the new thing starts.
If Scoreflection passes to a company
If Scoreflection is continued by a company and your contract passes to it (section 14 of the terms), the data needed to perform it goes with it: your account, your subscription and the billing. The legal basis is Art. 6 (1) (b) GDPR β it is the same contract, only with a different counterparty β and, for anything passing beyond that, our legitimate interest in the service continuing, Art. 6 (1) (f) GDPR.
From that point the company taking over is the controller within the meaning of the GDPR and is bound by this policy. We tell you about the change in text form at least four weeks beforehand, naming the company, and you can then terminate the contract with effect from the date of the change β section 14 of the terms sets out the detail. An account without a paid subscription passes over the same way; if you would rather it did not, you can delete it at any time (section 8).
This does not mean, and does not permit, a sale to an unrelated third party. Were that ever to happen, we would tell you beforehand and you would decide whether your account goes along.
6. Children
Scoreflection is used by children, and most of it is built so that it does not need to know anything about you at all: the sheet-music library, playback, the tuner and the games that only ask you to listen work without an account. Having the app listen to you play and mark your notes is part of the paid plan, and a paid plan belongs to an account. If you are a child, a grown-up in your family sets that up. Even then, the listening happens on your phone.
- Age. Making an account does not ask how old you are. We ask only when you join the community forum, because the forum has an age limit. You can answer with your date of birth, or just your age, or a parent can simply say the account belongs to a child. We store an age band — such as "under 13" or "16 or over" — because that is all we ever need to act on. A date of birth is optional.
- The community forum is for members aged 16 and over. Nothing else in the app is affected by your age.
- Contributions to us — practice statistics or short recordings that help improve the listening — are off until someone switches them on. If you are under 16, a grown-up in your family decides that with you, not you alone.
- If you join the forum we also ask for your real name and keep it private, so that there is somebody behind every post. It is never shown on the forum and never shared — the forum shows only the nickname you choose.
- The sound of you playing is listened to on your own phone, and is not sent to us.
- A photo of sheet music is sent to us to be read, and thrown away straight afterwards. Take pictures of the music, not of yourself or anybody else.
- We show no adverts and use no advertising or tracking services, so nobody is building a profile of you here. We do count how often each page and button gets used, but the count only says that it happened once more — never who it was.
Parents and guardians: you can ask us what we hold about your child and ask us to delete it — write to the address below. Our child safety standards page explains how to report a concern and lists independent advice services.
7. How long we keep things
The periods below are enforced automatically. Most categories are deleted when their period is up. The two you contribute on purpose — practice statistics and practice recordings — are not: what expires there is the connection between the contribution and your device, and once that is gone the contribution stays as part of what the listening model learns from. There is then nothing left in it that points at you, which is also why it can no longer be found and taken back. The period is how long you have to change your mind.
- Your account
- for as long as the account exists
- The converted value of the device identifier for the free week
- for as long as we offer the free week β the entry is exactly what prevents a second week on the same device
- The converted value of the device identifier and how much of the free listening trial it has used, together with your account
- until the device has not checked in for 24 months; if you delete your account, the link to it is removed at once and only the count stays with the device
- IP address and device description in sign-in records and in the record of listening-model checks
- 30 days
- Server logs, which can contain your IP address
- 30 days
- The record that a sign-in, a failed attempt or a listening-model check happened on your account, without the IP address or the device description
- 13 months
- Practice and feature statistics, if you turn contributions on
- connected to your device for 13 months, then anonymised and kept
- Practice recordings, if you choose to contribute them
- connected to your device for 24 months β that is how long you have to take them back. After that the connection is removed and the recording stays in the training set, with nothing in it that points at you
- Which steps of setting up and using the app you reached, if you turn contributions on
- connected to your device for 13 months, then anonymised and kept
- Counts of which pages of this website were opened, which buttons were used and which handed-out links were followed, and of where visits began: the kind of place they came from and the country
- 13 months, and never connected to you at any point β there is no record here that is about a person
- Which version of a page you were shown, if you agreed to that
- on your own device until you withdraw or clear it; what reaches us is the name of the variant in the counts above, and nothing that says it was you
- Signed-in sessions
- 30 days after you last used the app, then you sign in again
- Email confirmation links
- 24 hours, and they work only once
- A photograph of sheet music you send to be read
- the duration of the transcription
- The score read from your photo, while it waits for the app
- until the app collects it, at most 30 minutes; if the app was closed before the scan finished, 7 days in your account, for your devices to collect
- A recording or a score file you attach to a problem report from the app
- until the report is closed, and never longer than 90 days
- A problem report you send from the app: your description, the passage, the app version and the device model
- connected to your account, or to a random report number, for 13 months; after that the report stays, with nothing in it that says who sent it
- Support correspondence
- 36 months
- Your email address on the app waitlist, with the instruments you ticked
- until we have sent the one email telling you the app is available, and never longer than 6 months
- Invoices and the records tax law requires us to keep
- up to 10 years, held at Stripe and by our tax adviser, and outside the reach of a deletion request
- Orders, cancellations and withdrawals you make through this website: what you declared, when, and the address it concerned
- 4 years, as proof of the contract for as long as claims under it can be made; the IP address and device description sent with it, 30 days
- Encrypted backups of all of the above, kept so that nothing is lost if a server fails
- at most 91 days, on servers in the EU. If we ever have to restore one, every deletion made since it was taken is carried out again before the service comes back
You can delete your account yourself, in the app under Account → Delete account, or from this page; it takes effect as soon as you confirm by email, and it cancels any subscription first. Four things outlive the account, and none of them names you afterwards: a score you donated stays in the shared library with the donation no longer attributed to you, a moderation report you filed stays with the report no longer naming you, a problem report you sent from the app stays without your account on it — the recording or score file you attached to it is deleted — and the security records keep that the account existed with your address removed. Invoices stay because tax law says so.
Contributed statistics and recordings are not linked to your account — they carry a random installation number instead. You can erase everything under that number at any time from the app's privacy settings, without waiting for the periods above. Once a contribution has passed its period and lost that number, it can no longer be found — not by you and not by us. And a model that has already learned from a recording cannot be made to unlearn it; what we can delete is the recording.
8. What you can require of us
Under the GDPR you have the right to:
- a copy of what we hold about you, and to know where it came from (Art. 15);
- have anything wrong about you corrected (Art. 16);
- have it deleted (Art. 17) — the account page does this immediately;
- have its use restricted while a dispute is settled (Art. 18);
- get it in a portable, machine-readable form (Art. 20);
- object (Art. 21) — see just below;
- withdraw any consent at any time, with effect from then on (Art. 7 (3));
- complain to a supervisory authority — the one for us is named in section 2 (Art. 77).
Your right to object
Where we rely on our legitimate interest (Art. 6 (1) (f) GDPR), you can object at any time on grounds relating to your particular situation (Art. 21 GDPR). We then stop processing that data unless we can demonstrate compelling legitimate grounds that override your interests, or the processing serves the establishment, exercise or defence of legal claims. An informal message to the privacy address below is enough.
Write to the privacy address below. We answer within a month, and we say so if a request needs longer. We will not charge you for it and we will not make you explain yourself.
9. Contact
- Privacy
- privacy@scoreflection.com
- Child safety
- childsafety@scoreflection.com
- Security reports
- security@scoreflection.com
- Everything else
- support@scoreflection.com
10. Changes to this policy
If we change how any of this works, the policy changes with it and the date at the top moves. If a change matters to you — a new purpose, a new company handling your data, a longer period — we tell you in the app or by email before it takes effect, rather than letting you find it here.