Privacy Policy
Last updated 26 September 2026. This policy covers the Lirrly macOS app and lirrly.com.
The short version
Lirrly has no account system, no tracking, and no Lirrly-operated server in the dictation path. Your dictation history and settings stay on your Mac. Your API key stays in the macOS Keychain. We cannot read any of it.
What stays on your device
- Your API key — stored in the macOS Keychain. It is sent only to the transcription provider you configured (Groq), never to us.
- Dictation history — a local file on your Mac. You can search it, copy from it, or delete it at any time, or turn history off entirely in Settings. It keeps the most recent 200 dictations.
- Settings, dictionary, snippets and transforms — local files. Nothing is synced.
What leaves your device
When you dictate, your audio is sent directly from your Mac to Groq for transcription, and the resulting text is sent to Groq for cleanup. This happens with the API key you supplied, under Groq's privacy policy. Lirrly does not proxy, copy, or retain this traffic.
Optional crash reports and feedback
Off by default. If you turn on “Send crash reports” in Settings, Lirrly sends a random install identifier, the app and macOS version, and error details to a server operated by Lirrly's developer. Error details are reduced before they are sent: a provider failure is cut down to its status and error code, and anything shaped like an API key or an email address is stripped out — and the server strips the same shapes again before storing anything. It never sends audio, your history, your clipboard, or your API key. Feedback you type into the in-app form is sent only when you press Send, along with the optional email address you provide. You can turn this off at any time; nothing is sent while it is off.
These reports are pseudonymous, not anonymous: the install identifier (shown in Settings → Account) links your reports to each other, and to feedback you choose to send. That link is what makes deletion possible. The server never stores IP addresses, and keeps error reports for 180 days and feedback for 365 days, after which they are deleted automatically; backups of this data age out within a further 14 days.
The website
lirrly.com is a static site hosted on GitHub Pages. It sets no cookies and runs no analytics. GitHub may log requests as part of serving the site — see GitHub's privacy statement.
Children
Lirrly is not directed at children under 13 and does not knowingly collect personal information from them.
Your rights
Because Lirrly holds no account and stores your content locally, you can exercise deletion yourself: clear history in Settings, remove the Keychain entry, and delete the app. For anything sent via optional crash reports or feedback, ask for deletion through the in-app feedback form (Settings → Account). The form carries this install's identifier, which is what lets the matching reports and feedback be found and deleted — so please don't post that identifier in a public GitHub issue.
Changes
Material changes to this policy will be noted here with a new “last updated” date, and in the release notes of the version that changes behaviour.
Contact
Deletion requests: the in-app feedback form in Settings → Account, which reaches the developer privately. General questions: open an issue on GitHub — issues are public.