Your music stays yours.

Leggio stores the data required for the app's functionality in its private Android sandbox, including:

• Song title, artist, key, BPM, chords, lyrics, and display settings;
• Imported PDF documents, chord images, cover art, and source URLs;
• Setlists, folders, song ordering, and live performance preferences;
• Theme, language, notation preferences, local Pro status, and backup archives.

This content is not uploaded to any remote server and the developer has no remote access to it. Files are protected by the standard Android sandbox security model.

In production releases, Leggio utilizes Google Firebase Crashlytics to catch unexpected crashes. Leggio does not use Firebase Analytics.

Crash reports include crash stack traces, app version, device specifications, and OS version. Leggio never attaches song contents or personal names.

You can turn off crash reporting at any time via Settings → Privacy & Diagnostics.

To group reports coming from the same installation, Crashlytics generates a random installation identifier. It is not tied to your name, your Google account or any other app, and it disappears when you clear the app storage or uninstall Leggio.

From Settings → Report a problem you can send me something that is broken, or an idea. It leaves only when you press Send, and along with the text you wrote it carries:

• the kind of report (problem or idea) and the date;
• the version and build number of Leggio;
• the device model, the Android version and the app language;
• your email address, only if you choose to leave it.

These are the details I would have to ask for in a reply, and without them a report cannot be closed. Leggio does not attach songs, setlists, files or the list of what you keep in your library. The text is yours to write: please avoid putting anything in it you would rather not share.

Reports are stored in Google Cloud Firestore, in a European Union data centre, and I am the only one who reads them. To write, the app opens an anonymous Firebase Authentication session: it is not an account, it asks you for nothing, it is not linked to your name or your Google address, and it is deleted automatically after thirty days.

Once the report goes through you see a report code. If you want it deleted, write to privacy@leggio.app quoting that code.

The leggio.app website does not use tracking cookies, analytics, or user accounts. It is hosted via Cloudflare strictly for CDN routing and DDoS protection. The homepage reads the language your browser asks for and opens the matching translation. The only cookie stored holds the language you choose by hand, so that choice is kept on your next visit. It contains nothing else.

If you email support@leggio.app or privacy@leggio.app, your email and message contents are processed solely to respond to your inquiry.

.leggio backup archives contain your repertoire and preferences. They are standard ZIP archives with checksum validation and are unencrypted. Treat exported backups as personal documents.

Inside the app, Factory reset (Settings → Backup and Restore) deletes songs, setlists, folders, imported files and preferences, but deliberately keeps your backup archives so a mistake never costs you your library. Delete those archives from the backup list, or use Clear storage in Android Settings to remove everything at once. Uninstalling the app has the same effect.

Backups you exported yourself stay entirely under your control in the folder or service where you saved them. Leggio cannot reach them and never receives a copy.

Android Auto Backup is enabled and may copy your .leggio archives into your own Google account, the same way the system backs up other apps. Those copies belong to your Google account, not to Leggio, and you can manage or disable them from the Android backup settings.

Step-by-step deletion guide →

Processing needed to provide the features you use is based on performance of the service (Art. 6(1)(b) GDPR). Security and technical diagnostics are based on legitimate interest (Art. 6(1)(f) GDPR). Reports you send from the app are based on your request for a reply and on the legitimate interest in fixing defects and improving Leggio (Art. 6(1)(b) and (f) GDPR).

Depending on the feature you use, data may be processed by Google Play, Google Firebase (Crashlytics for diagnostics, Firestore and Authentication for reports), Cloudflare, MetaBrainz and Ultimate Guitar, under their respective linked policies.

Under GDPR Articles 15-22, you have the right to request access, rectification, erasure, and restriction of your data by contacting privacy@leggio.app.