Liryco is a collaborative lyric-writing app. It was built to keep your work on your device. This page says exactly what data the app handles and where it goes.
Everything you create lives locally on your iPhone:
This data is protected at rest with iOS file protection, readable only after you first unlock the device. Liryco has no server that stores your songs, and we cannot see your lyrics.
If iCloud Drive is enabled, Liryco backs your work up to your own iCloud account — never to a Liryco server. The backup is one file in an iCloud Drive folder named "Liryco", containing your songs, lyrics, version history, notes, profile and your voice-memo audio. It is written only when the content has actually changed, and it is governed by Apple's iCloud terms and your Apple account. Turn it off by disabling iCloud Drive for Liryco in iOS Settings.
When you invite a co-writer, Liryco connects your devices directly over your local Wi-Fi using Apple's MultipeerConnectivity. There is no Liryco server in the middle. While a session is live:
Two optional features send limited data off your device, and only when you actively use them.
api.lirycoapp.com), authenticated with your
account token, which forwards them to Anthropic (the Claude API). Liryco's server
does not store your lyric text — it counts usage against your quota. Anthropic deletes inputs and
outputs within 30 days of receipt, and may retain them for up to 2 years if a request is flagged
by their trust-and-safety systems. Nothing is used to train a model. No API key ships inside the
app. You can withdraw this permission any time in Settings → AI.If you send feedback from the app, the text you type and your app version are sent to the developer so it can be acted on.
Liryco's server (api.lirycoapp.com) and this website run on Cloudflare,
which processes your IP address to deliver them, as any host does. When you create an account or ask
for a password reset, the app runs a Cloudflare Turnstile check in the background to
keep bots out; Turnstile sees the request's network details but no lyric, email or password. The
emails we send you (password resets, and updates if you opted in) go out through Cloudflare's email
service.
Liryco requires an account, on the free tier too. We store your email address and your subscription
standing so the app knows you have access. We use your email to reach you about your account — a
password reset, a problem with your access. We send product news and update announcements only if you
tick "Email me about Liryco updates" when you sign up, and you can turn that off any time in Settings.
We also keep a per-device identifier supplied by iOS (identifierForVendor) so your
signed-in devices can be told apart, and the country your sign-up request came from
— taken from the network by our hosting provider, never from GPS — which we use only as an aggregate
count of where writers are. We never see your
password — it is stored only as a hash. Subscriptions are purchased and billed by
Apple through the App Store; payment details go to Apple and are never seen or
stored by Liryco.
You can delete your account from inside the app: Settings → Delete account. It asks for your password, then permanently removes your Liryco account.
Deleting your account does not cancel your subscription. Apple bills that, and only you can stop it — on your iPhone, under Settings → your Apple Account → Subscriptions. Cancel there first, or Apple keeps charging for an account that no longer exists.
Deleting a session from Recents removes its lyrics, notes and voice-memo audio from your device. Uninstalling the app removes all local data. If iCloud Backup is on, a copy stays in your own iCloud account until you delete it there or turn the feature off in Settings.
You can revoke any of these in iOS Settings at any time.
Liryco is not directed at children under 13, and we do not knowingly collect data from them. The app generates song lyrics on request and does not filter them for language, so it is rated for older audiences on the App Store.
If this policy changes materially, the date at the top changes with it and the new version is published here before it takes effect.
Questions, or a request about your data? Send them from the support page and they reach the developer directly.