How Spoken handles your recordings
Spoken exists to keep a family's recipes and the voices they came from — so it's worth being straightforward about what that actually involves.
What's recorded and kept
When you record, the audio and a text transcript of what was said are both saved, by default forever — so a session can be re-parsed later if the recipe needs another pass. There's currently no way to delete just the audio for one recording while keeping its recipe; that's a real gap, not a design choice, and it's on our list to fix.
Who processes it
Turning a recording into a recipe means sending the audio to Deepgram for transcription, and the resulting text to an OpenRouter-hosted language model to structure it. Both are third-party services this app relies on — audio does leave the device it was recorded on, briefly, to make the recipe. Nothing is used to train those services' models beyond however they each individually process a normal API request.
Who can see it
Only people on your family's invite list can sign in and browse recipes, sessions, or recordings at all — signing in requires a one-time link sent to an allowed email. A recipe itself stays private unless someone explicitly turns sharing on for it; that creates a public, unlisted link anyone with the URL can view, and it can be turned back off at any time. Turning sharing on never exposes the underlying recording or transcript — only the finished, structured recipe.
Your control
Sign out at any time from the menu. Any recipe you own can be deleted for good, one at a time from its Edit screen or several at once from Home's “Select” mode — deleting a recipe doesn't touch the original recording it came from, if it came from one. Removing a recording, or an account entirely, still needs whoever administers your family's Spoken — that self-serve path isn't built yet.
This page describes the app as it actually works today, not as a legal policy — if anything here changes, this page will too.