Audio is not stored
Event audio is processed as a live stream and turned into text. No audio file is retained afterwards. What is saved is text, not a recording.
Data and security
What happens to what's said at your event.
This page states the facts, including the parts we don't yet cover. It is usually the first thing a procurement conversation asks about.
Text is filed under the event
Source and translated text are stored under that event in your account. You can download or delete them at any time. Deleting an event deletes its transcripts.
Guests hand over nothing
Guests do not sign in, do not need an account, and are never asked for a name or an email address.
How sign-in works
Google sign-in only for now. We never store a password; the session is held in a signed, HttpOnly cookie.
Encryption in transit
All pages and live connections are encrypted over HTTPS and WSS.
Third-party processors
Translation is handled by OpenAI's realtime speech service, and the site and live rooms run on Cloudflare. Your event content passes through these services.
What we do not yet have
Stated plainly so nobody is misled: tlive does not hold SOC 2, ISO 27001 or equivalent certification, and there is no standard process yet for data-residency selection or signing a DPA. If your organisation requires those, talk to us first rather than assuming.
Deleting your account
You can permanently delete your account and its records yourself from the account page.
Let everyone follow your next event.
Sign up and get 30 minutes of translation — enough to run a complete rehearsal of a real event. No credit card.
Try it yourself — it's freeContinue with Google. No credit card required.