neumascan

← neumascan

Privacy Policy

This English version is a translation for your convenience. Only the German version is binding; where the two differ, the German version prevails.

Controller

Lorenz Kutschka und Alexander Muhr, Untere Teichstraße 38a, 8010 Graz, Österreich (Austria), [email protected]

Analytics with Google Analytics, only with your consent

We use Google Analytics 4 (measurement ID G-39TQ4LN1J9) by Google Ireland Limited to understand which pages are used. This happens only if you have agreed (Art. 6(1)(a) GDPR). Without your consent the Analytics script is not loaded at all: Google Analytics then sets no cookies and receives no data.

If you agree, Google Analytics sets cookies and processes your shortened IP address as well as information on page views, device and approximate location. Data may also be transferred to the USA. You can withdraw your consent at any time, with effect for the future, through the “Cookie settings” link in the page footer.

In that case we also measure how the conversion is used: that a file was chosen (image or PDF, size in kilobytes, whether by picking, dragging or the sample button), the result of the resolution check, start, success, cancellation or failure of the recognition including the number of lines, measures and the duration, as well as downloads, playback and transposing, plus sign-up and sign-in including the sign-in method (Google, Apple or email). Your sheet music image itself is not sent to Google Analytics, only these figures about the process. Without your consent none of this is collected and nothing is stored in between.

Ads on Google, measured only with your consent

We run ads in Google Search (Google Ads by Google Ireland Limited). If you reach us through such an ad, Google appends a click ID to the link, and the link names the campaign. Our website passes the click ID on to our own links when you follow them; it stores nothing in your browser for this, and without your consent Google learns nothing about your visit to us.

Only if you agree do we measure whether our ads lead to purchases (Art. 6(1)(a) GDPR): the website then tells Google that you have consented. Google Analytics reads the click ID and may store it in a cookie. Through the link between Google Analytics and our Google Ads account, Google Ads learns that a purchase followed the click, with amount and currency, without your name and without your sheet music image. Data may also be transferred to the USA. You can withdraw your consent at any time, with effect for the future, through “Cookie settings” in the page footer. Our cookie notice calls this measurement “marketing”; “improve neumascan” there means the analytics with Google Analytics.

We do not use personalised ads or remarketing: we pass no audiences to Google Ads and tell Google that your data must not be used for that purpose. If you agreed when our notice named only Google Analytics, your consent stays limited to analytics; we then send nothing for measuring the ads.

Regardless of your choice, we note in our own system, not at Google, on your user ID that you came through an ad (source “google-ads” and the campaign); see “Where you came from”.

Beyond that we use no marketing tools and embed no content from advertising networks. The fonts are hosted locally on our server; no data is transferred to Google for them.

Videos from YouTube, only once you press play

On some pages we show short explainer videos from our YouTube channel. When you open the page you only see a preview image that lies on our own server; YouTube is not contacted and learns nothing about your visit. Only when you press play does the page load the YouTube player (Google Ireland Limited) in privacy-enhanced mode (youtube-nocookie.com). Google then receives your IP address, information about your browser and device, the address of our page and the fact that you are watching the video. YouTube may set cookies or similar storage in your browser, and data may be transferred to the USA. If you are signed in to Google, Google can link the view to your Google account.

The legal basis is your consent, which you give by clicking play (Art. 6(1)(a) GDPR, § 165(3) of the Austrian Telecommunications Act, TKG 2021); a notice about this stands right below every video. Without the click none of this happens. What Google does with the data is described in Google’s privacy policy. If you have agreed to Google Analytics, we also count which video was started on which page.

Hosting and server logs

The website is delivered through Cloudflare (Cloudflare, Inc.). In doing so Cloudflare processes technical access data (IP address, time, requested resource, user agent) to provide and protect the service (Art. 6(1)(f) GDPR, legitimate interest in secure, fast operation). We ourselves do not evaluate these logs any further.

Processing of uploaded sheet music photos

Measuring the staff line spacing (pre-check) and cutting out the lines run entirely in your browser; the image does not leave your device for this. A page is only stored and recognized once you start a scan or add it to a scan in your library (Art. 6(1)(b) GDPR, providing the service you requested).

Storage with Firebase in Frankfurt. For scans we use Firebase, a Google service that processes the data on our behalf (Art. 28 GDPR). The database (Cloud Firestore), the file storage (Cloud Storage) and our server functions (Cloud Functions) run in the Google Cloud region europe-west3 in Frankfurt am Main. For a scan we store the original photo of the page (for a PDF, the image of the page created in your browser), the images of the individual lines cut out of it and prepared for recognition, a reduced preview image of each page, the recognition result, your corrections in the score editor (the corrected result and a change log with time, place, and before and after), the spots you closed with “Looks right”, the transposition you set, the file name as the title, times, the order of the pages and the state of the recognition, as well as the identifier of your account or your guest sign-in that the scan belongs to. In the library a page is already with us as soon as you add it to a scan, even before you start the recognition; if you remove it again or cancel, we delete it together with its images.

Your instrument. If you choose an instrument for transposing in the score editor, we remember it with the time of the choice on your account (in Firebase, as above); new scans of a single part then open already transposed for it. As a guest, your browser keeps it (see “Storage in your browser”) until you create an account or sign in. “Original” in the score editor and “Reset” in the settings delete it. The legal basis is providing the service you use (Art. 6(1)(b) GDPR); it is deleted with your account.

Counter of recognized pages. To detect abuse and cost spikes, we count per account (or guest identifier) and month how many pages were recognized. At more than 100 pages in a month the neumascan team receives a notification with your email address; nothing is blocked (Art. 6(1)(f) GDPR, legitimate interest in protection against costs from abuse). The counter is deleted with your account.

Recognition by an AI model. Our server function sends the prepared images of the lines, not the whole photo, to OpenRouter, Inc. (USA), which forwards them to the provider of the AI model. There they are turned into music notation text; we store the result with the scan.

With this transfer, processing takes place in a third country (USA). Please therefore do not upload photos on which personal data is visible (for example handwritten names or dedications on the sheet); they are not needed for recognizing the music.

Photographing pages with your phone

When you add pages, the computer can show you a QR code. It contains a random code that is valid for 30 minutes and can only be redeemed once; we store only a check value (hash) of it. If you open it on your phone, the capture page signs the phone in to Firebase in the background with an anonymous identifier, separate from a sign-in you may already have there, and allows it for these 30 minutes to put pages into exactly this one scan. The phone can neither see nor change other scans. The pre-check runs in the phone’s browser; a page is stored as described above. We delete expired codes daily (Art. 6(1)(b) GDPR).

Sharing sheet music

You can share a piece that has been read completely via a link. For this we store a random code, the title of the piece, your first name from your account (if Google or Apple provides it; we never show your email address), when the link was created and whether it was withdrawn, how many people accepted it and their user IDs. Whoever opens the link sees the title, your first name and the recognised music — not your original photo and nothing of your other scans (Art. 6(1)(b) GDPR).

Proof. Before sharing for the first time you confirm that the scan comes from a public-domain original. We store this confirmation with the time, your user ID, the scan and the version of the text. It stays stored even if you delete the scan — for three years, so that we can defend against third-party claims; after that we delete it automatically (Art. 6(1)(f) GDPR — legitimate interest in investigating infringements).

Own copy. If someone saves a shared piece to their library, a separate copy of the recognised music is created in their account. It remains until that person deletes it — even if you withdraw the link or delete your scan. We record which link the copy came from and from whom (your first name).

Reporting. Whoever reports a shared piece sends us the reason and, if given, a text and an email address for questions; we also store the link, the scan, the user ID of the person who shared it and — if signed in — that of the reporter. The report is sent by email to the neumascan team (via Resend, see below). We use it only to review and answer it and delete it automatically three years after the report (Art. 6(1)(f) GDPR). If it is justified, we block the link and delete all copies.

“Scan finished” email through Resend

For every scan in your library, “Let me know when it’s done” is preselected: we send you an email to the address of your account as soon as all pages are recognized, with the title of the scan, its state and a link to it. It is sent from [email protected] through Resend (Plus Five Five, Inc., USA), which works on our behalf (Art. 28 GDPR); it is sent from the EU (Ireland). According to Resend, it stores the content and delivery log of the email in the USA and deletes them after 30 days. The transfer to the USA is based on the EU-U.S. Data Privacy Framework, in which Resend participates, and the EU standard contractual clauses. The legal basis is providing the service you use (Art. 6(1)(b) GDPR); if you untick the box on the scan, you get none.

The link in this email carries a marker: if you open the scan through it, we note that once, with the time, on the scan, to understand whether the email helps. We do not measure whether you open the email. The legal basis is our legitimate interest in improving the service (Art. 6(1)(f) GDPR); the note is deleted with the scan.

Notification when neumascan reads music with several staves. Until neumascan could read pages with several staves (piano, choir, full score), you could sign up when uploading such a page so that we would write to you as soon as it worked. There are no new entries any more. For those who signed up we store with Firebase (see above) the email address you gave, your language and the time, together with your account. We write to you about this once, through Resend as above, and delete the entry with that email. The legal basis is your consent (Art. 6(1)(a) GDPR); you withdraw it by writing to us. The entry is also deleted with your account.

Emails after you create your account

Welcome. Once you have created an account and confirmed your address (Google and Apple confirm it for you), we send you one welcome email with the first steps. It is part of the service you use (Art. 6(1)(b) GDPR).

Tips and offers, only with your consent. If you tick “Send me tips and offers from neumascan by email (unsubscribe any time)” when you create your account or in your settings, we write to you occasionally, in the first week for example if you have not scanned anything yet, or with a short question about what would make you scan again. The box is never ticked in advance. For this we store with Firebase (see “Account and sign-in”) on your account whether you agreed, the time and the version of the text you agreed to, every consent and every withdrawal as a history so that we can show when you allowed what, and which of these emails has already been sent so that none arrives twice. Which email fits follows from when you created your account (and confirmed your address) and how many scans you have started. The legal basis is your consent (Art. 6(1)(a) GDPR).

Withdrawal. You can withdraw your consent at any time, with effect for the future: through the unsubscribe link in each of these emails (also with one click in your mail program where it offers that), in your settings, or with an email to [email protected]. After that you get no more tips and offers; emails that are part of the service remain.

Sending. These emails are sent through Resend, as described above under “‘Scan finished’ email through Resend”. We do not measure whether you open an email: no tracking pixel. Only the link in the email that reminds you of the waiting rest of a piece carries a marker: if you open the scan through it, we note that as described above. All other links carry no marker. If you reply, your reply arrives in our mailbox [email protected] (see “Contact by email”). If you delete your account, we delete the consent, its history and the sending notes with it.

Sheet music by email on the Christmas pages

What we store. On the Christmas pages (the overview, the pages for each instrument and for each song) we email you the sheet music you want to download. For this we store with Firebase (see “Account and sign-in”) your email address, the page and its language, the instrument and the sheet music you asked for, the time, your currency and, as under “Where you came from”, only the name of the source you came through. To limit abuse, we count requests per IP address and hour; we store the IP address for this only in unrecognizable form (as a hash value). When you submit the form and when you open the link, App Check with reCAPTCHA (see below) checks that the request comes from our website.

The email with the link. Right after the form we send you an email with a link that is valid for 30 days. It is part of your request (Art. 6(1)(b) GDPR). When you open the link, we note that your address is confirmed, and your browser remembers on this device that it downloads the sheet music without the form, together with the identifier of your request (see “Storage in your browser”). If you then scan your own sheet music or buy something on this device, we note this identifier on the scan and on the purchase, to understand whether the emails help (legitimate interest, Art. 6(1)(f) GDPR).

Tips and offers, only with your consent. Below the address is the box “Also send me tips and offers from neumascan (unsubscribe any time)”, never ticked in advance. If you tick it, your consent only takes effect once you open the link in the email. Then we write to you a few times, for example two and five days later, about how you can listen to your own sheet music and rewrite it for your instrument, and occasionally with an offer. If you have scanned something yourself in the meantime, these emails stop. We store when you consented and to which version of the text, as a history with every withdrawal, and which email has already been sent. The legal basis is your consent (Art. 6(1)(a) GDPR).

Clicks. The buttons in these emails go through neumascan.com/api/m: there we count which button in which email was clicked, and send you on. We do not measure whether you open an email: no tracking pixel. The emails are sent through Resend, as described under “‘Scan finished’ email through Resend”; if you reply, your reply arrives in our mailbox [email protected].

Withdrawal and deletion. You can unsubscribe at any time, with effect for the future: through the unsubscribe link in each of these emails (also with one click in your mail program where it offers that) or with an email to [email protected]. Without consent (no box ticked, never confirmed, or unsubscribed) we delete your address with everything that belongs to it 37 days after your last request or after you unsubscribe: the 30 days the link is valid, plus one week. What remains are numbers without an address (how many requests per page, language, instrument and week). With consent we keep the address until you unsubscribe.

Retention, quality control and deletion

Guest scans are scans without an account, for example your first scan in the library without signing in. We keep them for 90 days: original photo, images of the lines and recognition result. After that a daily clean-up run deletes the guest scan together with all images automatically. If you create an account or sign in before then, it belongs to your account from then on and is no longer deleted automatically.

Scans in your library stay stored until you delete them, one by one in the library or all together by deleting your account in the settings. All data of the scan including the original photos is deleted then, also for quality control, and a recognition that is still running is stopped.

Quality control. Members of the neumascan team who are cleared for this (administrators) can view guest scans and scans in libraries to check how well the recognition works on real pages and to find and fix errors (Art. 6(1)(f) GDPR, legitimate interest in reliable recognition). Other users never see your scans unless you share a piece via a link (see “Sharing sheet music”); there is no public library, and shared pieces are blocked for search engines.

No training. We do not use your photos and scans to train AI models.

If you want a guest scan deleted before the 90 days are over, write to us at [email protected] and give the file name and the approximate time of the scan so that we can find it.

Account and sign-in

For accounts we use Firebase Authentication by Google. You sign in with Google, with Apple or with email address and password. We store your email address, a user ID, the sign-in method and the times of sign-up and last sign-in; for Google and Apple also the identifier of your account there and, if the provider transmits them, your name and profile picture. Firebase stores your password only as a hash value; we cannot see it. When you sign in with Google or Apple, that provider’s privacy terms apply to the processing there.

Emails to confirm your address, to reset your password and to change your address are sent from [email protected] through Resend (see “‘Scan finished’ email through Resend”); the link in them is created by Firebase. If our sending is disrupted, Firebase sends them on our behalf. The notice to the previous address after a change is sent by Firebase.

Guests. The library also works without an account: when you open it, the page signs you in in the background with an anonymous guest identifier so that your scans and your allowance belong only to you (likewise on the page for invited testers). This identifier contains no information about you as a person. Whether you have already started a scan as a guest is remembered by your browser (see “Storage in your browser”). We delete guest scans 90 days after they were created. If you create an account or sign in, the guest identifier is linked to your account or your guest scans move to it.

Visits. If you open one of our pages from outside, we count a visit: one number per day, page and type of device (computer, phone or tablet). For this we set no cookie, store nothing in your browser and use no user ID; we do not store your IP address for it (for the server logs see “Hosting and server logs”). The legal basis is our legitimate interest in understanding how many visitors a page has (Art. 6(1)(f) GDPR).

Steps while scanning and buying. From “New scan” to the score editor we note on your user ID which steps you took (for example page uploaded, sample seen, listened, transposed, purchase window opened, plan chosen, account created), with the time, the page of ours you came from, and the type of device. This shows us where the path does not work well. The legal basis is our legitimate interest in improving the offer (Art. 6(1)(f) GDPR); the notes are deleted with your account.

Questions after a purchase. If you answer our short questions after a purchase (what you need the music for, what you mostly scan, which instrument you play, how often you need new music), we store the answers on your account. They are voluntary; the instrument preselects your tuning when transposing, the rest we use to improve the offer (Art. 6(1)(f) GDPR). They are deleted with your account.

Where you came from. When you open the library for the first time, we note once on your user ID through which source you came to neumascan: only its name (for example “instagram”, “google” or “direct”) and, if the link carries one, a short campaign note (for example the identifier of a video), never the full address of the page you came from. For this the website reads the details in the link and your browser’s referrer when the page is opened and passes the source on to our own links when you follow them; it stores nothing in your browser for this. We also note whether you were on a computer, a phone or a tablet, recognized by your browser’s identifier, without the device model or other characteristics. This shows us which paths lead to scans and purchases. The legal basis is our legitimate interest in understanding how people find neumascan (Art. 6(1)(f) GDPR). The note stays as long as your user ID exists; if you delete your account, we delete it too.

Invite friends. Through “Invite friends” (in the library and in the settings) you create, with an account, a personal invitation link with a random code that we assign to your account. If someone new comes to neumascan through it, their source reads “einladung” (invitation) and this code (see “Where you came from”). If that person buys for the first time within 14 days, we credit pages to both of you and send you an email; you do not learn who bought, and in the settings too you only see numbers (how many signed up through your link and how many bought). The legal basis is, for you, carrying out the invitation offer you use (Art. 6(1)(b) GDPR), and for the invited person our legitimate interest in assigning invitations and crediting the gift (Art. 6(1)(f) GDPR). If you delete your account, we delete your code too.

According to Google, Firebase Authentication runs exclusively in data centres in the USA; Google is certified under the EU-U.S. Data Privacy Framework. The legal basis is providing the account and the guest scan that you request (Art. 6(1)(b) GDPR). Your account exists until you delete it in the settings.

Purchases and payment through Stripe

Purchases and credit. For every account we store with Firebase (see above) the purchase data: which purchases there were (piece purchase, Pro subscription or page pack, time), the state of Pro (identifier at Stripe, state, billing month, cancelled or not), the credit of purchased pages, how many scans in the current month have already received the free part and how many pages have already been recognized in the current month and on the current day; for every page of a scan we note how many pages it counted, so that a failed page is credited back. After a purchase the identifier of your customer account at Stripe is added. This is necessary for the contract (Art. 6(1)(b) GDPR) and is deleted with your account, except for what we have to keep for tax and accounting (below).

Where the offer was opened. If you open the purchase window or the checkout, we note which offer, from where (for example the score editor or the pricing page), for which scan and on which type of device (computer, phone or tablet, as above), to understand which hints help and whether buying works well on every device. The legal basis is our legitimate interest in improving the offer (Art. 6(1)(f) GDPR); the note is deleted with your account.

Payment through Stripe. If you buy a piece, take out Pro (both also as a guest) or buy a page pack, you pay on a page run by Stripe (Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland). Stripe processes your name, your email address, your billing address, your payment details (for example card number and expiry date or bank details) and the details of the purchase (offer, amount, time). You enter your card details directly with Stripe; they never reach neumascan. We do not see the full card number, at most the card brand and the last four digits. Stripe tells us whether a payment succeeded. With Pro, Stripe stores your payment method for the monthly charge until Pro ends. If you buy as a guest, Stripe also tells us the email address you give there: we send the link to your scan to it once (through Resend, as above under “‘Scan finished’ email”), because without an account it otherwise only lies in the browser in which you paid. With the link you bring it into an account, also on another device.

The legal basis is performance of the contract (Art. 6(1)(b) GDPR) and our legal duty regarding tax and accounting (Art. 6(1)(c) GDPR): we keep invoices and accounting records for seven years under the Austrian Federal Fiscal Code (§ 132 BAO). Stripe may also transfer data to Stripe, Inc. in the USA; this is based on the EU-U.S. Data Privacy Framework, in which Stripe participates, and the EU standard contractual clauses. The Stripe privacy policy also applies to the processing at Stripe.

Withdrawing. If you withdraw through “Withdraw from contract”, we store your details (contract, name, email address and, if you give them, purchase date and note) with the time of receipt, send you a confirmation of receipt by email and notify the neumascan team, which checks the refund. Against abuse we count withdrawals per IP address and hour; we store the IP address for this only in unrecognizable form (as a hash value). The legal basis is performance of the contract and our legal duty to confirm the withdrawal (Art. 6(1)(b) and (c) GDPR); we keep it like accounting records.

Cancelling. If you cancel through “Cancel contracts here”, we store your details (contract, name, email address, type and time of the cancellation) with the time of receipt and send you a confirmation by email. We keep cancellations like accounting records (Art. 6(1)(b) and (c) GDPR).

Protection against abuse: App Check with reCAPTCHA

Every recognition causes costs. So that programs cannot call the service past our website, the database, file storage and server functions require proof from Firebase App Check with every access that the request comes from our website. For this the page loads reCAPTCHA Enterprise by Google, only when you start a scan or use your library, not when you merely open a page and not for signing in alone. You do not have to click anything.

For this, reCAPTCHA evaluates information about your browser and your device (hardware and software data) as well as your IP address and sets a cookie that is necessary for this (“_GRECAPTCHA”). Google processes this data as our processor and, according to Google, not for personalized advertising; data may be transferred to the USA.

This happens regardless of your decision about Google Analytics, because we cannot offer the recognition without this protection. The legal basis is our legitimate interest in protecting the service and its costs against automated abuse (Art. 6(1)(f) GDPR).

Storage in your browser

Without your consent, neumascan stores in your browser only what is needed for the respective function (§ 165(3) TKG 2021):

The Google Analytics cookies and the cookie holding the click ID of an ad are only added with your consent, those of YouTube only when you play a video (see above).

Contact by email

When you write to us, we process your details to answer the request (Art. 6(1)(b) or (f) GDPR).

Your rights

You have the rights of access, rectification, erasure, restriction of processing, data portability and objection. To exercise them, contact [email protected]. You can also delete scans and your account yourself at any time (see above). You can also lodge a complaint with the Austrian data protection authority (dsb.gv.at).

Last updated: 20 November 2026. This policy describes the current technical state and is developed further together with the service.