Your data

What pialog stores, where it lives, and how to get rid of it. Please contact me if anything is unclear here.

What's collected

No analytics, no tracking pixels, no advertising, no third-party scripts in the app. Nothing is sold or shared with anyone. There is no "anonymous usage data".

• Your playing, as MIDI. The raw output from your digital piano: which keys you played and when. This is what the whole app is built on — it's how pialog works out which piece you're playing, where you were in it, and which bars gave you trouble.
• Audio recordings, if the microphone box is ticked on the record page. This records your room, so if you sing along it's in there (better not sing your bank details 😉). It's what lets you play a session back as it actually sounded. Without it, playback still works, but pialog renders the MIDI, which sounds noticeably worse. At some point in the future, I may also try building a version of pialog that works from sound alone, for acoustic pianos. In that case I'd use recordings and their paired MIDI to calibrate that.
• The scores you upload and the titles you give them.
• Your email address you use to sign into the account.

Where it lives

pialog runs on Fly.io with recordings and session files in Tigris object storage. Both are infrastructure providers acting on my instructions, and both keep the data in Frankfurt, Germany, and therefore inside the EU. The only other third party is Formspree, which delivers messages from the contact boxes to my inbox.

What I can see

I do not look at your data without you telling me to. Being straight about it: in the current beta-testing infrastructure I could (as the person running the server). I'd rather say that than let you assume otherwise. But I won't open your sessions unless you ask me to. What I do look at without asking is the server's own error log: what broke and where.

I don't listen to your audio recordings. When I debug tracking I only ever need the MIDI (which notes, and when). So there's no reason for me to open the audio, and I don't.

You can report if tracking or sheet rendering came out wrong (directly via buttons in the app), helping me debug and improve. Every "something looks wrong?" link names the session or piece it's about and asks whether I may open that one, so it's your call each time. Say no and I still get your message — I just work from your description instead.

I don't know your password. The one I email you is a starter; the moment you set your own in Settings it stops working.

Data-related Options

At all times, you can download or delete all your session data in the Settings. Data for selected sessions can be deleted from the Practice sessions page. You can also delete audio-only, which leaves your tracking and stats unaffected. Pieces in your library can be deleted directly in the Library. Deleting removes the data from the storage it lives in, not just from view. If you want your account and everything in it gone in one go, just email me and I'll erase it.

Nothing expires on its own — your data stays until you delete it or ask me to. If you stop using pialog, tell me which you'd like: deleted, or kept in case you come back.

Who's responsible

pialog is run by Claudio Heinrich-Mertsching, a sole trader in Germany. I'm the person legally answerable for everything described on this page, and the one to contact about it — by email at kontakt@pialog.de, or through the contact form. The full details are in the Impressum.

The formal bit. I process your account and practice data — including recordings, while the microphone box is on — in order to run pialog for you (Art. 6(1)(b) GDPR: the service you signed up for), and the server's error logs to keep it running (Art. 6(1)(f)). If you think I'm handling your data wrongly, you can complain to a data protection authority.