Privacy Policy

Last updated 2 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, export, or delete it at any time, or turn history off entirely in Settings.
  • 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 anonymous crash reports” in Settings, Lirrly sends an anonymous install identifier, the app and macOS version, and error details to a server operated by Lirrly's developer. It never sends transcripts, audio, clipboard contents, 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.

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, email the address below and it will be deleted on request.

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

Questions or deletion requests: open an issue on GitHub, or use the in-app feedback form in Settings → Account.