Frequently asked questions.
For anything not covered below, contact us at hello@talat.app.
The basics.
Is talat really private?
Yes. Audio capture, transcription, speaker identification, and summarisation (by default) all happen on your computer using on-device models. We have no server that receives or stores your meeting content, which means we can’t see your recordings, transcripts, or notes even if we wanted to. The privacy policy has the full breakdown.
Does it work offline?
Yes. Transcription and summarisation both run on your computer out of the box; neither needs an internet connection (aside from a periodic background licence check). You may choose to use a cloud LLM for summarisation, but talat doesn’t need it.
Where is my data stored?
Locally, on your computer, alongside any audio recordings you’ve chosen to keep. None of it ever syncs or uploads anywhere.
Can you see my transcripts?
No. None of your meeting content ever leaves your machine, unless you’re using a cloud LLM to summarise it or pointing one at talat’s MCP server. In both of those cases, we still cannot see your data.
What data do you actually collect?
If you’re just trying talat out, nothing. If you buy a licence, your email address (so we can send you the licence key) and an opaque licence identifier used to validate the licence is still active (e.g. hasn’t been refunded). That’s it. The privacy policy lists everything in one place.
Procurement, legal, and the boxes they tick.
Are you SOC 2 certified?
No. SOC 2 is designed to give you assurances about how a vendor handles your data on their servers: access controls, breach notification, incident response, and so on. We don’t have servers that handle your meeting data. Transcription, storage, summarisation (with a local model) and speaker matching all run on your computer. There’s nothing on our side for SOC 2 to audit, so the certification doesn’t map onto what we do. If your procurement checklist is asking whether this vendor is ever in a position to mishandle your data, the answer is no, because we’re never holding it in the first place.
What about GDPR?
Most of what GDPR addresses doesn’t apply to us because we don’t process your meeting data. talat runs on your computer, which is already under your legal and physical control; the audio, the transcript, the notes, and the summaries are all yours, where you’d expect them to be. The only personal data we hold is your email address and licence identifier, covered by the privacy policy.
Separately: recording a meeting can trigger participant-notification requirements under GDPR and similar regimes elsewhere, regardless of which tool you use. That responsibility sits with whoever is doing the recording rather than with us. We’re exploring an API you’ll eventually be able to hook into so you can pipe recording notifications into whatever system you use; it’s on the roadmap, not live yet.
Do you have a DPA?
A data processing agreement covers how a processor handles data that belongs to a controller. Because we’re not a processor of your meeting data (none of it flows to us), a traditional DPA doesn’t map onto the relationship. The architecture removes the need for most of what a DPA is designed to cover; if your legal team wants to discuss it further, contact us at hello@talat.app.
What about data residency?
Data resides on your computer. talat doesn’t store your meeting data in any cloud region, because it doesn’t store your meeting data in the cloud at all. If you run a local LLM for summaries, that stays on your machine too.
What happens if I turn on the cloud LLM?
Summarisation is optional. The default is a local model, but you can switch to a cloud provider (OpenAI, Anthropic, and others) using your own API key. When you do, your transcript goes directly from talat to that provider over a direct connection; we don’t proxy the request and we don’t see the data.
Once your data is with the cloud provider, it’s covered by their terms, not ours. The same applies if you wire talat up to an external tool via MCP, or pipe transcripts into any other third-party service; that relationship is between you and that provider, and our “nothing leaves your machine” promise stops at the handoff. If you’d rather avoid that entirely, stick with a local model and no third-party integrations.
What if talat the company goes away?
Because everything runs on your computer, the app you installed keeps working. Your database, recordings, and notes stay exactly where they are. Updates would stop, but there’s nothing on our side whose disappearance would take the product with it.
Practical questions.
Do I need a browser extension or meeting bot?
No. There’s nothing extra to install alongside talat, and no meeting bot to invite. Calendar integration isn’t required either (although we’re considering adding it in future to help with things like speaker identification).
Does it work on Windows?
Yes. Windows 10 and 11 are both supported. macOS still needs an Apple Silicon chip (M1 or newer).
How it's sold.
Can I use my licence on more than one computer?
Yes. A talat licence is tied to you, the individual, rather than to a particular computer, so use it on whichever of your machines you like - personal or work. The only expectation is one licence per person.
Is talat a one-off purchase?
Yes, talat is a one-off purchase, not a subscription. During pre-release the price is $49, and every future update is included for life. After 1.0 the base price (still to be confirmed) will include one year of application updates.
Do you offer volume pricing?
Yes, starting at five seats. Email us at hello@talat.app with roughly how many seats you’re looking for and we’ll put together a quote.
Do you have an enterprise plan?
Yes. See talat for enterprise for the full capability menu (managed deployment, compile-time policy enforcement, custom builds, customer-hosted licensing, support under contract) and how pricing is shaped. To start a conversation, email nick@talat.app directly.