Privacy policy

Lilt is published by an individual developer, not a business, in the United Kingdom. It keeps your tunes on your device, holds no accounts of its own, shows no ads, and runs no analytics. Nothing you keep in Lilt reaches the publisher. If anything here is unclear, write to support@lilttunes.com.

Your tunes stay on your device

Your library – tunes, variants, tags, favourites, tunebooks, and sets – is kept in a database inside the app's own private storage on your device. It is never sent anywhere unless you switch on sync, described next.

Sync: a copy in your own Google Drive

If you sign in and switch sync on, Lilt keeps a copy of your library in a file in your own Google Drive, in its app-data folder (drive.appdata). That folder is hidden: it does not appear in your Drive file list, and only Lilt can read it. The copy goes there and nowhere else – not to the publisher, and not to any other service.

The sync file holds your library, plus two small pieces of housekeeping:

• your device's model name (for example, ‘Pixel 8’) as a readable label, and a random id this install generated for itself, so that two devices can tell their writes apart;
• a record of which writes each device has seen, so a lost write is noticed rather than silently dropped.

A fingerprint of your device (a SHA-256 hash of its Android id) never leaves the device. It serves one purpose: if the app's data is copied onto a second device, the copy notices, gives itself a fresh id, and re-syncs safely instead of confusing the two devices' writes.

Lilt also reads your Google account's email address from Drive and shows it on the Sync screen, so you can see which account is syncing. It is not sent anywhere.

When you choose ‘Unlink this device’, Lilt asks Google to withdraw its access (the token revoke call goes to Google) and forgets the account on the device. ‘Remove synced data and unlink’ does the same and also deletes the sync file and its previous copy from your Drive. Your library on the device is untouched either way.

Importing from TheSession

When you search TheSession, open a tune link, or fetch a member's tunebook, Lilt sends your search term, the tune or member number, or the link to thesession.org and shows you what comes back. Apart from sync, that request is the only thing the app sends by itself. When you choose Share or save an export, the file goes to the app or place you pick, and nowhere else. Tunes you keep are stored in your own library, each with its TheSession link as its source.

What Lilt never does

• No accounts of Lilt's own: there is nothing to sign up for.
• No ads, and no analytics or tracking of any kind.
• Nothing is sent to the publisher. The only network calls the app makes are to thesession.org (when you import), to Google Drive (when you sync), and to Google (to sign you in, and to withdraw access when you unlink).

Backups and deleting your data

Android's cloud backup is switched off for Lilt. Uninstalling the app removes your library from that device, though Android can copy app data to a new device during a device-to-device transfer. The copy in your Google Drive is separate: uninstalling does not touch it. To remove that too, choose ‘Remove synced data and unlink’ on the Sync screen before you uninstall, or delete the app's hidden data in Google Drive afterwards.

Children

Lilt has no accounts, no ads, no profiling, and no content of its own. The only things that leave the device are the sync copy and the TheSession requests described above, so there is nothing in the app a child could use differently from an adult.

Changes to this policy

If Lilt starts handling data in a new way, this page will be updated to say so before the app changes. The date of the last change will be shown here. Last changed: not yet published.