Privacy
Last updated 11 November 2026
Partsong is built so that your music stays with you. There are no accounts, no cookies and no advertising. This page explains what stays on your device, what leaves it, who handles it and why.
Who is responsible
Partsong is run by Betwixt Limited, a company registered in England and Wales (company number 10573596) whose registered office is at Mandage House, Westerton, Chichester PO18 0PG. Betwixt Limited is the data controller for the little personal data described here. For anything about your data, email bugs@partsong.app.
What stays on your device
When you scan or open music, the photos or PDF pages are read on your device: the music reader runs in your browser and nothing is uploaded to do it. Your scores (photos, the music as read, your marks and settings) are stored in your browser's storage on that device. A few preferences (such as the sound you chose, or that you said "Not now" to installing) are kept there too. Deleting a score in Partsong deletes it from the device; clearing the site's data in your browser deletes everything.
What leaves your device
Scores you share
When you share a score as a link, Partsong encrypts it on your device (AES-GCM) and uploads only the encrypted copy to Partsong's link service, which runs on Cloudflare. The key needed to open it is part of the link itself, after the #, and browsers never send that part to a server. So neither Partsong nor Cloudflare can see the music, the photos or the score's name; only people you give the link to can open it. A link works for a month, and its encrypted copy is deleted within two months of upload. If you want a shared copy removed sooner, email us the link.
When you share from a computer, the song's name is copied with the link so that it shows in your message. That text goes wherever you paste it.
Sending a recording, or using Save as a PDF file, makes a file on your device and hands it to your phone's share sheet or your downloads. Partsong doesn't upload it; where it goes after that is up to you.
Problem reports
If you use Report a problem, your email app opens with a report addressed to us, which you can read and edit before sending. It includes what you write, your device and browser, the app's version, recent errors and messages from the music reader, and, from a score's screen, that score's name and parts. Sent from a score's screen, the score (with its photos) goes with it unless you untick it, and so do the pages Partsong couldn't read when it asks you for them: they're uploaded encrypted to the link service, just like a shared link (above), and the email carries the link, so only someone with the email can open them. The encrypted copy is deleted within two months. Nothing reaches us unless you send the email. We use reports only to fix problems, and delete them when they're no longer needed for that. We may use AI services to help read a report and any score sent with it, find the cause and test a fix.
Usage counts
To see which features get used, Partsong counts visits and actions (such as reading a score, pressing play or sharing) with GoatCounter. It sets no cookies and doesn't identify you. GoatCounter receives your IP address, browser and screen size with each count, uses them to tell visits apart and to find the country, and doesn't store the address. The counts never include your scores or their names; the most they record about a reading is how many pages it had, or, if it failed, the reader's short error message (such as “No staffs found”). Readings and errors are also counted by the kind of device (such as iPhone, Android or Windows) and the version of Partsong, errors with their short message, and so are readings that had to restart because the page was closed, the reader ran out of memory, or the page was reloaded once so the reader could use more of the processor, and the result of a quick check, when you start a scan, that the device can run the music reader, so we can fix the commonest problems. To see whether people come back, once a day the app counts, in broad groups, how many different days it has been used on your device, how long ago it was first used there, and how many scores it holds (such as “day 4–5”, “1–4 weeks ago”, “6–10 scores”). When a score is read, the app also counts, in broad groups, how many scores have been read on your device and on which of its days of use (such as “score 2, day 2–3”). When a score is shared to you, it counts whether it arrived (or why it didn't), whether you added it, and the first time it's played. Those counts are kept on your device; no identifier is sent with them, so they can't be linked together or to you.
Loading the app
Like any website, the services that deliver Partsong see your IP address and browser when they send you its files:
- GitHub Pages hosts the app, the open-source libraries it uses, and the music reader's models.
- Cloudflare runs the link service, used when you share or open a link.
They keep short-lived logs under their own privacy policies. Partsong doesn't receive those logs.
Why (the legal basis)
Usage counts and problem reports are handled on the basis of our legitimate interest in keeping Partsong working and improving it, in ways you'd expect and that don't identify you. Shared copies are stored because you ask for them to be, to provide the link you're sharing.
Where
GitHub, Cloudflare, GoatCounter and the AI services we use for problem reports may handle data outside the UK. Where they do, they rely on the safeguards UK data protection law requires, as set out in their policies.
Your rights
Under UK data protection law you can ask to see, correct or delete personal data we hold about you, or object to how we use it. In practice we hold very little: problem reports you've sent us, and encrypted shared copies we can't open. Email bugs@partsong.app. You can also complain to the Information Commissioner's Office.
Children
Partsong asks for no personal details and is fine for choir members of any age. Younger children should share scores and send reports with a parent's help.
Changes
If what Partsong does with data changes, this page will change first, with a new date at the top.