Privacy

Da Capo is a private chord-sheet library run by one person for himself and a few friends. It is not a business, it shows no advertising, and nothing about you is sold or shared with anyone. This page says plainly what it keeps.

What it stores

Who you are. Your email address, because that is how you sign in and how the invitation list knows you are allowed in. If you sign in with Google, Google tells the app your name, your email address and the address of your profile picture, and is asked for nothing else. Your name is what the people you play with see beside you; the picture is not shown anywhere. The people who manage the invitation list see your email address, when you last had the app open, and how many songs and playlists you have — a number of each, never which ones.

Whether you said you chipped in. The app links to a page of its owner’s for anybody who wants to help with running costs. No payment passes through the app, and it is not told whether anybody gave. If you tell it you did, that mark, and the date it lasts until, are kept with your account, and you can take it back in Settings. Nothing in the app depends on it.

Your library — which songs you have added and when you last opened each, and how you left each one: its key, capo, instrument, whether you simplified the chords, your scrolling speed, the chord shapes you chose, and any corrections you made to its chords. Corrections are yours alone and are never applied to anyone else’s copy.

Your playlists, and for one you share with people you play with: who has joined it, and the key and corrections its members settled on. A song or a playlist you share by link can be opened by whoever has the link, until you stop sharing it.

The songs themselves, once added. A song is held once and shared between the people using this copy, rather than stored again for each of them. Which songs are in your library stays private to you.

Notifications, only if you turn them on: the address your phone or browser gives for sending them, and which ones you asked for. Turning them off removes it.

A request to be let in, if you make one: the name and email address you give and who you say invited you, until it is answered.

What it does not store

No password — signing in is Google, or a link sent to your email. No analytics, no tracking pixels, no advertising identifiers.

Nothing it hears. The tuner and following a song by ear use the microphone while they are on. The sound is worked out on your device and is never recorded or sent anywhere.

Nothing of a jam. While you play together, the others on the list see which song you are on and where in it. That is passed along as it happens and not kept.

Other people’s services

Google’s sign-in button loads on the sign-in page and nowhere else. A song’s video, if you choose to open it, is played by YouTube’s own player, in the mode YouTube offers for not following viewers who have not pressed play; none of it loads until you ask. Neither is given anything from your account.

Where it is kept

With third-party hosting, database and email providers, each with their own privacy terms, on their servers rather than on a machine belonging to whoever runs this copy.

Your phone or browser also keeps a copy of your library, so it works without a signal, and holds any change you make offline until it can be sent. Clearing the site’s data removes that local copy and nothing else.

Getting it deleted

Ask contact@dacapo.tech, and your account and library will be removed. Songs you added stay, because they are not yours alone: a song is held once, for everyone using this copy.

Changes

If this changes, the date at the top changes with it.