No account
Lyt has no account and no login. The app identifies your device with an anonymous UUID: a random id that is not tied to your name, your email, your Apple ID or anything else about you.
Recording and transcription in the EU
Recording happens locally on your device. Only when a recording needs to be processed is the audio sent to Lyt's backend (Cloudflare Workers) and on to AssemblyAI, which does the transcription in the EU (Dublin). The audio does not leave the EU during transcription. Lyt's server never stores the audio file, and at AssemblyAI both the audio file and the transcript are deleted the moment Lyt has fetched the result. Audio processed in the EU is also exempt from model training at AssemblyAI. Your meetings are not used to train AI models.
Transcript and feedback may sit briefly (up to 24 hours) in a temporary queue storage until they are delivered to your app. After that they are deleted.
Coach feedback: Lyt's engine or your own key
The coach feedback can be generated in two ways. With Lyt Plus it runs on Lyt's own Anthropic agreement, and AI content is still not trained on by the provider. If you instead choose your own key (Anthropic, OpenAI or Azure), the feedback is generated under your own agreement with the provider: Lyt only passes it on, and the key is never logged or stored server side. None of the providers train on API content. The feedback is AI generated and is marked as such in the summary.
Connected meeting tools
You can connect Lyt with your meeting tools so transcripts arrive on their own. The connections work differently, and the difference matters for where your data is:
- Microsoft Teams: the access lives solely on your own device (in the Keychain), and Lyt reads transcript files from your OneDrive.
- Zoom and Google Meet: Lyt's backend stores access and refresh tokens encrypted (Cloudflare KV) and receives or fetches your meeting transcripts. They are delivered to the app on your device and deleted from the server on collection, and after 7 days at the latest.
Specifically about Google data
Lyt's use of data from Google APIs follows Google's API Services User Data Policy, including the Limited Use requirements. In the wording Google requires:
"Lyt's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements."
Email delivery (optional)
If you choose to get summaries by email, they are sent via Resend. That only happens if you have entered an email address in the app yourself. You can remove it again at any time.
No tracking
The app contains no analytics, no telemetry and no tracking. There is nothing to turn off.
Deletion
Lyt has a delete endpoint that removes all data tied to your device on the server. If you have questions, or want to be sure everything is gone, write to mail@martinibsen.dk.
Who is behind it
Lyt is developed and operated by Martin Ibsen, Danish business registration no. (CVR) 34303320, Kaløvej 81, 8543 Hornslet, Denmark. Martin Ibsen is the data controller for the processing described here.