Privacy notice
Last updated: 16 October 2026
This notice explains what OnPitch does with your personal data, why, and what you can do about it. It is written to be read, not to be survived — if anything here is unclear, ask us and we will fix the wording.
Who is responsible
| Contact | support@onpitch-music.com |
| Service | OnPitch, at https://onpitch-music.com |
We are established in Latvia, so we need no Article 27 representative in the EU. We are not required to appoint a Data Protection Officer — we are not a public authority, we do not process personal data on a large scale, and we process no special categories of data — so we have not appointed one. Write to support@onpitch-music.com and a person will read it.
The short version
- We store your email address, and the songs you analyse. Nothing else about you.
- Your microphone is only ever recorded when you press record. In the tuner, the sing-along and the practice room it is analysed inside your browser and never uploaded, recorded or stored. In Record Studio, which exists to record you, the takes are yours, and they are now saved to your account so they are there on your other devices. See The microphone — this is the one section worth reading in full.
- The audio file you upload is deleted as soon as the analysis finishes. The separated tracks stay until you delete the song.
- There is no advertising, no analytics and no tracking of any kind. We set no cookies, which is why you have never seen a cookie banner here.
- You can have everything erased. Email us and we will do it within one month.
- You can complain about us to the Latvian Data State Inspectorate, whose details are at the end.
What we collect
Your account
| Email address | To identify your account, to check it is really yours when you sign up, and to send you password resets |
| Password | We never see it. Sign-in happens directly between your browser and our authentication provider, which stores only a cryptographic hash. It never passes through our servers |
| An account identifier | A random identifier that links your songs to you |
| Your plan and monthly usage count | To apply the free-plan limits — and, when we have given you a plan for a while, the date it ends |
| A request for a paid plan, if you make one | That you asked, which plan and when. We answer it by writing to your account's email address — nothing is copied anywhere else to do that |
| Your measured vocal range, if you use the practice room | Two note names and the date measured |
| Your progress in Learn guitar, if you are signed in | Which lessons you have finished, which step of each you reached and when, and the lesson you were last in — so the course carries on where you left off on any device. Nothing you play is recorded or sent |
The songs you analyse
- The name of the file you upload. This is free text that you control, and it is the one field that could contain your name or anyone else's if you name your files that way.
- The audio itself, while it is being analysed.
- The separated tracks produced from it, so you can play them back.
- What we worked out about the song: its key, tempo, chord changes, and the pitch curve for the voice. These are measurements of the recording, not of you.
- Its duration, its size on disk, and when you added it.
A recording can contain other people. If you upload a rehearsal, a lesson or a live take, somebody else's voice or playing may be on it, and a recognisable voice is personal data about that person. Two things are worth being exact about. We never try to work out who anyone is — nothing here identifies or verifies a speaker, nothing compares one recording against another, and no recording is ever used to build a profile of a voice. And it is your upload: when you submit a recording of other people, you are the one deciding to, which is why our terms ask you to have their agreement first. If you are on a recording somebody else uploaded and you want it removed, write to support@onpitch-music.com and we will deal with it — and you have every right in Your rights over that audio, not a lesser set. We cannot write to such a person to tell them we hold it, because we have no idea who they are or how to reach them, which is one of the situations the GDPR accepts as a reason not to; this notice is the public account instead.
A photo of a tab, when you ask the app to read one
In the Android app, Photo existing tab takes a picture of a tab written on paper and turns it into a tab you can edit. What happens to that picture, in order:
- It is taken by your phone's own camera app, which hands the app that one picture. The app never looks through your photo library.
- It is re-saved on your phone before it is sent, which removes the hidden data a phone writes into a photo — including the location where it was taken. A close-up is also made smaller; a whole page held upright is instead cut into up to four strips between its tab lines, so the reader can see every number. The strips are the same picture, in pieces.
- It is sent to our server and passed on to an AI model that reads it: Google's Gemini, reached through OpenRouter (both named under Who else is involved). The model sends back the strings, frets and bars it can see, and the song's title and artist when they are written on the page.
- Nobody keeps it. We do not store the photo: it exists on our server only for the seconds the reading takes. The request asks OpenRouter to use only providers that keep nothing and do not use what they are sent for training. The copy on your phone is deleted once it has been read.
- What comes back is offered, not saved. You see the photo beside what was read, and the tab is only kept if you choose to keep it — after which it is an ordinary tab of yours, like any other.
The reading is made by a machine and it makes mistakes — most often with numbers written between the lines rather than on them. Check every note before you play from it.
Technical data
- Your IP address is seen by our servers and by our hosting providers, as it is by every website you visit. We record it in a log line only when a request is refused for asking too often — see Keeping the service working.
- Our servers keep ordinary request logs, which include IP addresses and the paths requested. Our hosting and database providers keep their own logs under their own retention rules.
What we deliberately do not collect
We say this explicitly because the industry norm is otherwise, and because you can verify most of it by inspecting the page:
- No advertising identifiers, no cross-site tracking, no behavioural profiles.
- No analytics — there is no analytics package in this application at all.
- No third-party scripts. No fonts loaded from another company's servers.
- No location data, no device fingerprints, no contacts, no photo-library access.
- No information about other devices on your network.
- No date of birth, no gender, no phone number, no postal address, no profile picture.
Do you have to give us any of this?
No — and the law asks us to say so rather than leave you to infer it.
- The tuner, the practice room and the tab editor need nothing at all. No account, no email, no upload. They work signed out, and offline.
- An account needs an email address and a password, because there is no other way to hand your songs back to you and only to you. Not giving them means not having an account. There is no other consequence, and we will not ask you for anything else in exchange.
- Analysing a song means giving us the recording. There is no way round it — separating a track into its parts is work no browser can do. If you would rather not, do not upload it, and nothing else stops working.
None of it is required by any statute. It is all what the service needs to do the job you asked it to do.
The microphone
This section is deliberately specific, because a microphone is the most intrusive permission this application asks for and because the answer is better than you may expect.
There are two different things here, and the difference is the whole section. Most of what OnPitch does with a microphone is listen and measure. One feature, Record Studio, exists to record you — and it records only when you press record.
Listening: the tuner, the sing-along, the practice room
This audio never leaves your device. Your browser captures it and analyses it in the browser:
- The detection runs as code inside the page, on your computer or phone — the note you are singing, or in the timing drill simply the moment you played something. Nothing is sent to us to be analysed.
- The audio is not recorded. No file is written and no buffer is kept; nothing survives the moment the sound has passed through. What the timing drill keeps is a handful of measurements — when an attack happened and how loud it was — and never the sound itself.
- In the sing-along, the audio goes to your own speakers or headphones if you turn the monitor up, and to nothing else. In the tuner and in the timing drill it goes nowhere at all, not even to your speakers.
- We never receive your voice or your playing from these features, so we cannot store it, share it, lose it, or be compelled to hand it over. There is nothing to hand over.
Recording: Record Studio
This one does the opposite, deliberately, and only when you ask it to:
- Nothing is captured until you arm a track and press record, and it stops when you press stop. The page shows you while it is recording, and your browser shows its own indicator as well.
- A take is saved on your device the instant you stop, so a lost network or a closed tab cannot cost you a performance.
- A take is then uploaded to your account, so it is there on your other devices and survives a cleared browser. It goes straight from your browser to our storage provider (Cloudflare R2, in the EU) without passing through our own servers, and the record of it — its length and its size, never its contents — is held in our database alongside your songs. The copy on your device is removed once the upload is confirmed, so the take exists in one place rather than two.
- So is how the studio is laid out. The track names you type, their levels, mutes and solos, and which recording sits on which track are saved to your account as well, so the studio looks the same on every device you sign into. With each recording go a few facts about how it was made, shown in the clip's Details: when it was recorded, the name your browser gives the input it came through (for example "MacBook Pro Microphone" or the name of an audio interface), its sample rate and the format it was saved in. Which input a device will use for the next recording, and which track is armed, stay on that device.
- Until that upload finishes, the only copy is on your device. If you are offline, or it fails, the take waits on your device and goes up next time. Nothing is lost in between — that is the entire reason it is written down before anything is sent.
- Playing a take needs a connection. It is fetched from your account when you press play. The rest of Record Studio — arming a track, recording, the tuner, the metronome, the tab editor and the practice room — still works with no connection at all.
- A take is yours. We do not listen to it, we do not analyse it unless you ask us to, and we never try to work out who is on it. Delete it and the audio goes with it.
- Everything in How long we keep things and Erasing everything applies to a take exactly as it applies to a song.
If somebody else can be heard on a take — a bandmate, a teacher, whoever is in the room — then what this notice says about recordings containing other people applies here too. A microphone in a room raises the same question as an uploaded file, and we answer it the same way.
What else persists from the microphone: your measured vocal range, and only if you use the practice room's range check. Two note names such as G3 and E5, plus the date, saved in your own browser's storage so that exercises start somewhere you can actually sing. You can clear it from within the app.
Your browser asks for permission before any of this, and you can withdraw that permission at any time in your browser's settings. While a microphone is live, your browser shows its own indicator; that indicator is the browser's, not ours, and it is a more trustworthy signal than any promise we could make.
Please note the boundary. The audio files you upload for analysis are a third case again: those reach our servers because separating a recording into tracks is work no browser can do. They are covered above and in How long we keep things.
Why we process your data, and on what legal basis
One purpose per row, one legal basis per purpose, and where we rely on a legitimate interest we say what that interest is.
| What we do | Why | Legal basis (GDPR Art. 6) |
|---|---|---|
| Create and run your account | You asked us to; we cannot provide the service without it | Performance of a contract, Art. 6(1)(b) |
| Analyse a song you submit and store the result so you can come back to it | This is the service you signed up for | Performance of a contract, Art. 6(1)(b) |
| Read a photo of a tab you take, and offer what was read as a tab you can keep | You asked us to | Performance of a contract, Art. 6(1)(b) |
| Send you an email to confirm your address when you sign up | So an account belongs to a real address that is yours, and nobody can sign up with someone else's | Performance of a contract, Art. 6(1)(b) |
| Send you a password-reset email when you ask for one | So you can get back into your account | Performance of a contract, Art. 6(1)(b) |
| Count how many songs you have analysed and how many tab photos you have had read this month, and how much you have stored | To apply the free-plan limits we publish | Performance of a contract, Art. 6(1)(b) |
| Keep a request you make for a paid plan, and write to you about it | You asked to hear from us about it, before any contract for that plan exists | Steps at your request before entering a contract, Art. 6(1)(b) |
Refuse a sign-up from a temporary-inbox service, or from another way of writing an address that already has an account (name+tag@, or dots in a Gmail address) | Our legitimate interest in not having the free allowance claimed many times over by one person. The address you type is compared with a list of temporary-inbox domains and with the addresses already registered; nothing new is stored, and a refused address is not kept | Legitimate interests, Art. 6(1)(f) |
| Limit how often any one connection can start an analysis, and how many tab photos one account can have read in a day, and log a refused attempt with its IP address | Our legitimate interest in not having our computing capacity taken by automated abuse. Analysing a song costs real money; without this, one script could spend it all | Legitimate interests, Art. 6(1)(f) |
| Keep server logs, and investigate faults and security incidents | Our legitimate interest in a service that works and is not broken into, and yours in the same | Legitimate interests, Art. 6(1)(f) |
| Act on a report that content infringes someone's rights or is unlawful | Our legitimate interest in operating lawfully, and the rights-holder's interest in their work | Legitimate interests, Art. 6(1)(f) |
| Establish, exercise or defend a legal claim | Our legitimate interest in defending ourselves | Legitimate interests, Art. 6(1)(f) |
| Comply with a legal obligation, such as a valid order from a competent authority | We have no choice | Legal obligation, Art. 6(1)(c) |
| Send you news about OnPitch, if you ever ask us to | Only ever with your say-so, and you can withdraw it in one click | Consent, Art. 6(1)(a) |
We do not currently send any marketing email at all. The last row exists so that if we start, the basis is already stated and it is consent.
Where we rely on a legitimate interest, you may object — see Your rights. We will stop unless we can show compelling grounds, and for the abuse-prevention row we generally can, since without it the service would not survive.
No automated decisions. Nothing here makes an automated decision with a legal or similarly significant effect about you. Being told you have used your three free songs is a contractual limit being applied, not a judgement about you, and no profile is built from it.
Who else is involved
Named, not described as "categories of recipients", so you can look each one up.
| Who | What they do | What they see |
|---|---|---|
| Supabase | Runs our database and handles sign-in | Your email address, the hash of your password, your account identifier, your song records including file names, the guitar tabs you write — including anything you type into one, such as the song title, the performer and your own notes — and how your Record Studio projects are laid out: the project names and track names you type, their levels, which of your recordings is on which track, and for each recording when it was made, the name of the input it came through, its sample rate and its format. Hosted in the EU West (Ireland) region |
| Resend | Sends our account emails — the one confirming your address and the password reset | Your email address and the email itself, which holds a link that works once. Sent from its European (Ireland) region. Not your songs, tabs or recordings |
| Cloudflare | Serves the application itself to your browser | As the network in front of us, your IP address, your browser type and which pages you request |
| Modal | Runs the analysis | The audio you upload, while it is being analysed, and the results |
| OpenRouter | Passes a tab photo you take on to the AI model that reads it, and passes the reading back | The photo of the tab, re-saved with its location data removed (a whole page as up to four strips of it), for as long as the request takes. Not your email or any other account detail. We ask it to route only to providers that keep nothing |
| Google (the Gemini model) | Reads the tab in the photo | The same photo, for as long as the reading takes. Requested with no retention and no use for training |
That is the complete list. The last two see a photo only when you use Photo existing tab, and nothing else of yours ever. There is no advertising network, no analytics provider, no customer data platform, no email marketing tool, and no payment processor — because there is nothing to pay for yet. There is also no video or streaming service on this list, and there used to be: until August 2026 the application could fetch audio from a link you gave it, which meant our server contacted that site. It cannot any longer — the capability was removed, not merely hidden — so nothing about your song reaches anyone outside this table.
We will also disclose data if we are legally required to, and we will tell you when we are allowed to tell you.
Sending data outside the EU
Our database and sign-in are hosted in the EU West (Ireland) region, so your account data stays in the European Economic Area.
Cloudflare, Modal, Resend, OpenRouter and Google are United States companies operating global networks, so some processing may happen outside the EEA. Where it does, transfers are covered by the European Commission's Standard Contractual Clauses and, where the provider is certified, the EU–US Data Privacy Framework. You can ask us for a copy of the safeguards that apply and we will send them.
How long we keep things
Concrete periods, including the awkward one.
| What | How long |
|---|---|
| The audio file you upload | Deleted the moment the analysis finishes. If the analysis fails, the file is removed by a clean-up that runs every few hours, once it is old enough that no analysis could still be using it — in practice within a day |
| The separated tracks and the analysis results | Until you delete the song. Nothing removes them automatically — except after a paid plan ends, below. If you want them gone, delete the song, and if you want everything gone, see below |
| Your account and your email address | Until you ask us to delete it |
| Your monthly song count | It resets on the 1st of each month |
| A request for a paid plan | Until your account is deleted. Once answered it is marked answered, and you can ask us to remove it at any time |
| A take you record in Record Studio | In your account until you delete it, or until your account is deleted. Nothing removes it automatically. Until its upload finishes, the only copy is on your device |
| How your Record Studio projects are laid out, and their names | In your account until you delete the project or your account. Deleting a project deletes its recordings too. Also in each browser you have used the studio in, until you clear it |
| Your progress in Learn guitar | In your account until your account is deleted, when you are signed in. Also in each browser you have used the course in, until you clear it |
| The guitar tabs you write | In your account until you delete the tab, when you are signed in. Always also in the browser you wrote them in, until you clear it |
| A photo of a tab you ask the app to read | Not kept. It exists on our server only for the seconds the reading takes, and the copy on your phone is deleted once it has been read. A tab you choose to keep from it is kept like any other tab |
| Your vocal range, your per-song corrections | In your own browser, until you clear them |
| Songs, recordings and tabs over the free limits, after a paid plan ends | Three months from the day the plan ends. Then the newest that fit the free limits are kept and the rest are deleted permanently, with a warning in the app and by email at least 14 days before. Taking up a paid plan again within the three months keeps everything. There are no paid plans yet, so this has not applied to anybody |
| Server logs | Short-lived operational logs. Our hosting and database providers apply their own retention periods, which are described in their own notices |
Erasing everything
Email support@onpitch-music.com and ask. We will confirm it is you, delete your account, your song records, every separated track and analysis file, every guitar tab you have written, and every take you have recorded, and confirm when it is done — within one month, as the law requires, and normally within a few days.
We are honest about why this is not yet a button in the app: deleting the account row does not by itself delete the audio files, and a button that left your recordings behind would be worse than no button. We do it with a tool that removes both, and we check afterwards. A self-service version is on our list.
Anything held only in your own browser — your vocal range and per-song corrections — is yours to clear, and clearing your browser's site data for OnPitch removes all of it.
Your takes are no longer in that category. Since 13 September 2026 they are uploaded to your account, so clearing this browser no longer loses them and erasing your account erases them with everything else. A take still on its way up, which has not yet been uploaded, is the one case where clearing site data would lose it.
Your rights
Under the GDPR you have the right to:
- Know what we hold about you, and get a copy.
- Correct anything inaccurate.
- Erase it — see above.
- Restrict what we do with it while a dispute is resolved.
- Take it with you, in a structured, machine-readable format.
- Object to processing based on a legitimate interest, including at any time.
- Withdraw consent, where we rely on it, without affecting what was done before.
- Not be subject to a solely automated decision with legal or similarly significant effect. As above, we make none.
To use any of them, write to support@onpitch-music.com. We will reply within one month. It is free; we will only charge, or refuse, if a request is manifestly unfounded or excessive, and we will explain why if we ever do. If you ask for a copy, what you get is a machine-readable file — your account details and song records as JSON, and your audio files as they are stored.
One of those rights we are required to put in front of you rather than bury in a list, and it is the right to object. Where we rely on a legitimate interest — the abuse limits, the server logs, acting on a report, defending a claim — you may tell us to stop at any time, and we must stop unless we can demonstrate compelling grounds that override your interests. Write to support@onpitch-music.com and say that you object; you do not have to give a reason or cite anything. And the easy half: we send no direct marketing at all, but if we ever do, an objection to it is absolute — there is no balancing to be done, and we would simply have to stop.
You can also complain to a supervisory authority. Ours is:
Datu valsts inspekcija (Data State Inspectorate)
Elijas iela 17, Riga, LV-1050, Latvia
pasts@dvi.gov.lv — dvi.gov.lv
You may also complain to the authority in the EU country where you live or work.
What is stored on your device
We use no cookies. Nothing here tracks you between sites, and that is why you have not been asked to accept anything. What we do store is strictly necessary to make the app work, which is why it needs no consent:
| Stored as | What it holds |
|---|---|
onpitch.auth.v1 | Your sign-in session, so a reload does not throw you out. Contains access and refresh tokens and your email |
onpitch.session.v1 | A single flag recording that you have passed the front page |
onpitch.tabs.v2 | Any guitar tabs you have written, filed under whichever account wrote them so that signing out does not leave them on screen for the next person. When you are signed in this is a working copy — the tab is also in your account, which is what lets the editor keep working with no connection. Written while signed out, it is here only, and clearing site data will lose it |
onpitch.tabs.v1 | The earlier version of the same store. It is read once, copied into the key above, and then left alone rather than deleted — a second copy of your own work costs a few kilobytes and is worth having |
onpitch.practice.v1 | Your measured vocal range, and which steps of the guitar practice path you have finished |
onpitch.metre.v1 | Per-song corrections, such as moving where the bar starts |
onpitch.chords.v1 | Per-song chord corrections: where you have told us a chord we detected was wrong, and what it actually is |
onpitch.layout.v1 | How you have arranged the screen, such as how tall you have dragged the graph, and whether guitar lessons read each step aloud |
onpitch.metronome.v1 | How you have set the metronome up: tempo, time signature, accents, click sound and level |
onpitch.course.v1 | Your progress in Learn guitar — which lessons you have finished and which step of each you reached — kept separately for each account that signs in on this browser. When you are signed in this is a working copy of what is in your account; signed out, it is here only |
onpitch.record.v4 | How you have set Record Studio up, kept separately for each account that signs in on this browser: which input and how far to shift new recordings for your headphones' delay, and for each of your projects its name, the track names, their levels and mutes, and which recordings are on which track and where along it. When you are signed in this is a working copy of what is in your account. Not the audio |
onpitch.record.v3 | The same settings from before you could have more than one project. Read once, copied into the key above as your first project, and then left alone rather than deleted |
onpitch.record.v2 | The earlier version of the same settings, from before a track could hold more than one recording. It is read once, copied across in the same way, and then left alone rather than deleted |
onpitch.record.v1 | An earlier version again, from before the settings were kept per account. Read once in the same way, and likewise left alone |
onpitch.timing.v1 | How you have set the practice room's timing drill up: the tempo, the count and the click, plus the delay this device was measured to have between playing a sound and the app hearing it. That last one is a property of your speakers and microphone, not of you, and it is what stops the drill telling you that you are late when you are not |
A database named onpitch-takes | The audio you record, while it waits to be uploaded. Every take is written here the moment you stop, so that stopping cannot lose it, and it is removed once the upload to your account is confirmed. A take that has not been uploaded yet — because you were offline, or it failed — stays here until it has. It is the one place on your device that holds audio |
The app also keeps a small offline cache so it can start without a network, and so the tuner, metronome, practice room and tab editor work with no connection at all. That cache holds the application itself, plus up to 30 recent API responses for up to 24 hours. No audio is ever put into that cache — stems are excluded deliberately, and so are takes. onpitch-takes is not a cache: it is a store you filled by pressing record, and nothing evicts it behind your back.
One consequence worth stating plainly, and a larger one since Record Studio: on a shared or borrowed computer, that cache and the storage above outlive your visit, and signing out does not currently clear them. That now includes recordings of you playing or singing. Clear the site's data if the device is not yours.
On the Android app
The Android app is a separate program on your phone, so none of the browser storage above applies to it. What it keeps is kept in the app's own private storage, which no other app can read, and all of it goes when you uninstall the app or clear its data:
| Stored as | What it holds |
|---|---|
| Downloaded songs | The separated stems of any song you open on the phone, so it plays with no connection, together with the server's own reply about that song — its length, which analyses it holds, and the pitch curve. That last one is what lets the app score your singing offline rather than only play the music |
| A decoded-audio cache | The same audio, unpacked into the form the player reads. It is derived from the downloads and is rebuilt if it goes, so the app treats it as disposable and the system may delete it when space runs short |
| Tabs | Any tab you write on the phone, and any tab your account already holds. These now go to your account, exactly as they do on the website, so a tab written on your phone appears in your browser and the other way round. The copy on the phone stays as well, which is what lets the editor keep working with no connection — so clearing the app's data loses only tabs that had not yet reached your account |
| Record Studio | The audio of anything you record, and the arrangement of it — which recording is on which track and where along it. The audio now goes to your account as well, as soon as you stop recording: it is compressed on the phone and sent straight to our storage provider without passing through our servers, and it counts against the same disk allowance as your songs. The phone keeps its own copy too — unlike the website, which deletes its local copy once the upload confirms — because the phone is the device that has to work with no signal. A recording that could not be sent stays on the phone and the studio says so. The arrangement is still on the phone only |
| Your sign-in | Your session, encrypted, so closing the app does not sign you out. It is your email address and the two tokens that prove you signed in — never your password. It is locked with a key kept in the phone's own secure key store, which cannot be copied off the phone, and it is excluded from backups, so it never leaves the device. It stays until you press Sign out, until our side ends the session, or until you uninstall the app or clear its data. Since 20 September 2026 the app asks you to sign in before it will open anything: your songs, your recordings and your tabs belong to your account, and the allowances are counted against it |
| Settings | Whether you chose the light or the dark theme, how tall you have made the singing graph, the metronome's tempo, metre, accent pattern and click volume, the range you measured in the practice room, how Record Studio is set up — the length of count-in you want and which microphone to record from — and, for each speaker or car you have measured it on, the delay between the phone playing a sound and hearing it back, stored under the name the phone gives that speaker (a car's Bluetooth name, for instance). No audio: the range is two note names and a span, which is what every later exercise is pitched against, and the microphone setting is a name, not a recording |
| Corrections you make to a song | Where you said the bar starts, any tempo you set by hand, and any chord you told us the detector got wrong. Kept against that song so you do not have to make the same correction twice. Only on the phone — the website keeps its own and the two do not meet |
The app records nothing except in Record Studio. The tuner, the sing-along — on the song screen and in Car mode — and the practice room open the microphone, read the pitch, and keep no audio at all — the same promise the website makes, and for the same reason: they have no need of it.
Keeping the service working
We limit how often one connection can start an analysis, because a single script could otherwise spend our entire computing budget. When a request is refused for this reason, we write one log line containing the connection's IP address and how long it must wait. That is the only place we record an IP address ourselves, and it exists to tell abuse from a person having a busy afternoon.
How we protect it
Factually, without claiming perfection:
- Everything travels over HTTPS.
- We never see your password. It goes from your browser to our authentication provider, which stores only a hash.
- Access to your data is enforced by the database itself, not only by our application code, so a mistake in our code cannot expose another account's songs — the database refuses.
- Every request for one of your files checks that the file is yours. A request for someone else's is answered exactly as one for a file that does not exist, so an outsider cannot even learn what exists.
- Uploads are capped in size and length, and file paths are validated so a crafted request cannot read anything outside the intended folder.
No system is perfect. If you find a problem, please tell us at support@onpitch-music.com — we would far rather hear it from you.
If something does go wrong. If personal data is lost, altered or exposed, we will contain it, write down what happened, and assess what it means for you. Where there is a risk to your rights, we must and will report it to the Data State Inspectorate within 72 hours of becoming aware — even if the picture is still incomplete, because a partial report on time is worth more than a complete one late. Where the risk is high, we will tell you directly, in plain language, without waiting to be asked. We deliberately do not promise to email you about every incident regardless of severity: that is a promise products make in a privacy notice and then quietly break, and the legal test is the honest one.
Children
OnPitch accounts are for people aged 16 or over, and we do not knowingly create accounts for anyone younger. If you believe a child has an account, tell us and we will remove it.
The tuner and the practice room need no account and collect nothing. The tab editor needs no account either, and used without one it collects nothing; signed in, a tab you write is saved to your account. All of them can be used by anyone.
Changes to this notice
If we change it, we will update the date at the top. If a change materially affects your rights, we will tell you in the app or by email before it takes effect, and we will keep the previous version available so you can see what changed.
Contact
support@onpitch-music.com — for any question about this notice, any of the rights above, or anything you think we have got wrong. A person reads it.
OnPitch is run from Latvia.
Version history
| Version | Date | What changed |
|---|---|---|
| 1.34 | 16 October 2026 | We also count how many tab photos you have had read this month, to apply the monthly allowance each plan has. A number per month, kept with the song count |
| 1.33 | 15 October 2026 | Who is responsible gives the contact address and the service; the rows for a company name, registration number and registered address are removed until the company that will run OnPitch is registered |
| 1.32 | 15 October 2026 | Names Modal as the company that runs the analysis, and the region our database is in, EU West (Ireland) — both were placeholders until now |
| 1.31 | 15 October 2026 | Sign-up refuses temporary-inbox addresses and a second account on the same inbox written another way (name+tag@, or a Gmail address with dots). Added to Why we process your data; nothing new is stored |
| 1.30 | 15 October 2026 | We now ask you to confirm your email address when you sign up, by a link we send to it, and our account emails — that one and the password reset — are sent by Resend, named under Who else is involved |
| 1.29 | 14 October 2026 | You can request Premium or Pro before they can be bought. We keep that you asked, which plan and when, and write to your account's email address about it; a plan we give you for a while has an end date we keep with your plan, after which the free plan's limits apply again |
| 1.28 | 14 October 2026 | The practice room's guitar path remembers, in this browser only, which of its steps you have finished — under the key that already held your vocal range, onpitch.practice.v1. It is a list of step names; nothing you play is kept |
| 1.27 | 14 October 2026 | Record Studio keeps a few facts about how each recording was made — when, the name your browser gives the input it came through, its sample rate and its format — with the project in your account and in your browser, and shows them in the clip's Details. The input's name was previously kept on the device only, and the name of the input a device will use next still is |
| 1.26 | 7 October 2026 | Guitar lessons can be read aloud. Whether you have turned that on is kept with how you have arranged the screen, in onpitch.layout.v1. The recordings are part of the app and nothing about your listening is sent to us. Record Studio also remembers, on this browser, how far to shift new recordings for your headphones' delay |
| 1.25 | 6 October 2026 | Record Studio can hold many projects, each with a name you choose. The names are kept with the projects in your account and in your browser, under a new key, onpitch.record.v4. Deleting a project deletes its recordings from your account and frees their space |
| 1.24 | 6 October 2026 | How long we keep your songs, recordings and tabs when a paid plan ends, written down before any paid plan exists: everything for three months, then the newest that fit the free limits, with the rest deleted permanently and a warning at least 14 days before by email to the address on your account. Added to How long we keep things |
| 1.23 | 30 September 2026 | Learn guitar now remembers your progress: which lessons you have finished and which step of each you reached. It is kept in your browser and, when you are signed in, in your account, so the course carries on where you left off on any device. It is listed under Your account, How long we keep things and What is stored on your device |
| 1.22 | 30 September 2026 | The Android app remembers the delay it measured for each speaker or car it plays to, so the sing-along is timed correctly the next time without measuring again. It is a number of milliseconds kept beside your other settings under the name the phone gives that speaker, and it never leaves the phone. The measurement now listens to the song itself for a few seconds instead of playing clicks; nothing it hears is kept |
| 1.21 | 26 September 2026 | A photo of a whole tab page, held upright, is now sent as up to four strips cut between its tab lines rather than made smaller, so the reader can see every number; a close-up is still made smaller. Either way it is re-saved without its location data and nobody keeps it. What comes back can now include the song's title and artist when the page names them, which name the new tab |
| 1.20 | 25 September 2026 | The Android app can read a photo of a tab written on paper. The photo is taken by your phone's camera app, made smaller and stripped of its location data on the phone, then read by Google's Gemini model reached through OpenRouter — both now named under Who else is involved. Nobody keeps the photo, what is read is offered for you to check rather than saved, and the number of photos one account can have read in a day is limited |
| 1.19 | 24 September 2026 | The Android app now keeps you signed in when you close it. Your session — your email address and the tokens that prove you signed in, never your password — is stored encrypted with a key held in the phone's secure key store, is excluded from backups, and goes when you sign out, uninstall the app or clear its data. It used to be held in memory only, as 1.12 said, so every launch asked for your password again |
| 1.18 | 23 September 2026 | Car mode in the Android app can now listen to you sing against the song, the same way the sing-along on the song screen does: it reads the pitch and keeps no audio. The microphone opens only when you press MIC and closes when you leave the screen |
| 1.17 | 23 September 2026 | The Android app now remembers how tall you have made the singing graph, so it stays the size you chose from one song to the next. It is one number, kept in the app's own storage beside your other settings, and it never leaves the phone |
| 1.16 | 21 September 2026 | The car audio check has been removed from the website, so the screen described in 1.10 no longer exists and nothing on the site asks your phone to cancel the echo of the music. This takes a listening feature away rather than adding one; everything else about the microphone is unchanged |
| 1.15 | 20 September 2026 | Tabs written in the Android app now go to your account, the same way they do on the website, so they appear on your other devices; the copy on the phone stays, which is what lets the editor work with no connection. The app also now asks you to sign in before it will open anything, where it used to let you play songs already downloaded without an account |
| 1.14 | 19 September 2026 | Recordings made in the Android app are now uploaded to your account, so they are on your other devices and survive losing the phone. They go straight to our storage provider without passing through our servers, they count against the same disk allowance as your songs, and erasing your account erases them. Two differences from the website are stated rather than left to be found: the phone keeps its own copy as well, because it has to work with no signal, and a recording that could not be sent stays on the phone with the studio saying so |
| 1.13 | 19 September 2026 | The Android app keeps three more small things, all in the same private storage and all removed with the app: the length of count-in Record Studio should use and which microphone it should record from, and — kept against a song rather than against the app — where you said the bar starts, any tempo you set by hand, and any chord you told us the detector got wrong. None of it is audio, and none of it leaves the phone |
| 1.12 | 18 September 2026 | There is an Android app. It keeps downloaded songs, a rebuildable cache of the decoded audio, any tab you write, anything you record, and your settings — the theme, the metronome's pattern, and the vocal range you measured — all in the app's own private storage and all removed when you uninstall it. Two differences from the website are stated rather than left to be found: your tabs and your recordings are on the phone only — the app does not put them in your account yet — and the app holds your sign-in in memory, so closing it signs you out. The microphone promise is the same on both: nothing is recorded outside Record Studio |
| 1.11 | 15 September 2026 | Record Studio's layout — track names, levels, mutes and solos, and which recording is on which track — is now saved to your account, so the studio looks the same on every device. Supabase is named as holding it, the device-storage table gains the per-account key, and the retention row for a take no longer says it is held only on your device, which stopped being true in 1.8 |
| 1.10 | 15 September 2026 | A car audio check: a test screen that measures how well the sing-along hears you through a phone speaker or a car's Bluetooth. It listens the same way the sing-along does and can ask the phone to cancel the echo of the music. Nothing is recorded, nothing is stored, and nothing is sent to us |
| 1.9 | 14 September 2026 | The practice room gained a timing drill, which listens to you play against a click and draws where each attack landed. It listens the same way the tuner does: nothing is recorded and nothing is sent to us. It also measures, once, how long this device takes between making a sound and hearing it, and keeps that number in your browser |
| 1.8 | 13 September 2026 | Record Studio takes are now uploaded to your account, so they are on your other devices and survive a cleared browser. Says that they go straight to Cloudflare R2 without passing through our servers, that the copy on your device is removed once the upload is confirmed, that playing one needs a connection, and that erasing your account erases them |
| 1.7 | 10 September 2026 | The guitar tabs you write are now saved to your account, so they follow you to your other devices, and the editor still works with no connection. Says what Supabase can see, how long a tab is kept, and that erasing your account erases your tabs |
| 1.6 | 9 September 2026 | Tabs written in this browser are now filed by account, so signing out does not leave them on screen for whoever signs in next. They are still kept in this browser only |
| 1.5 | 9 September 2026 | Corrected: this notice said a take was uploaded to your account. It is not — that is intended and not built, and takes have never left the browser. The recording section, the retention table and the device-storage table now say so |
| 1.4 | 8 September 2026 | Record Studio: the microphone can now be recorded, when you press record. The microphone section is split into listening and recording, because those are different promises. Takes are held on your device and in your account, and what this notice says about other people on a recording now covers a microphone in a room as well as an uploaded file |
| 1.3 | 2 September 2026 | One more thing kept in your browser: the chord corrections you make to a song |
| 1.2 | 1 September 2026 | The note-by-note guitar reading was removed, so its pitch curve is no longer among the things kept about a song. Two of the six pretrained models went with it |
| 1.1 | 17 August 2026 | Whether you have to give us any of this, and what happens if you do not. The right to object stated separately rather than in a list. What we do if there is a data breach, matched to the legal test rather than over-promised. What an export contains. Recordings that contain other people, and their rights over that audio |
| 1.0 | 16 August 2026 | First published |