Privacy policy
Last updated: 11 November 2026
talat is a meeting transcription app that runs entirely on your device. This policy explains what data we collect and what we do with it.
The app
By default, all audio recording, transcription, speaker identification, and summarisation happens locally on your device using on-device models. In this default mode, none of this data is sent to us or to any third party, and we can’t see your recordings, transcripts, speakers, or notes.
Three optional features can send meeting content off your device. All are off unless you turn them on in Settings:
- A cloud LLM provider of your choice, which receives the meeting being summarised (covered next).
- Sync, which moves your meetings between your own devices through our server. They’re end-to-end encrypted, so we can’t read them (see “Sync” below).
- Remote MCP access, which lets your AI (such as ChatGPT or Claude) read your meetings through our server, encrypted in transit (see “Remote MCP access” below).
talat includes no third-party analytics and no behavioural tracking. Nothing watches which features you use or what you click.
The app does send us a small diagnostic ping: on launch, periodically while it's open, and at a few key moments like finishing onboarding or activating a licence. It carries a random per-install id (not derived from your hardware), the app version and platform, how far you got in onboarding, and your licence or trial status. It never includes your recordings, transcripts, or anything else about your meetings, and it goes only to our own servers.
Third-party cloud LLM providers
You can choose to use a third-party cloud LLM for better summarisation on longer meetings instead of an on-device model. You choose the provider, you supply your own API key, and you send data to them directly. For these providers, we're not involved in that relationship: we don't proxy requests, don't see your API keys, and don't receive any data.
When you use a cloud provider, their privacy policy governs how they handle your data. Make sure you're comfortable with it.
Sync
Sync is optional and off by default. When you turn it on, your meetings travel between your own devices through our server. They’re end-to-end encrypted before they leave your device, so the server can’t read them.
The server keeps:
- Encrypted messages between your devices, until every device they are for has collected them, or they expire. A recording from your phone is kept for an hour at most. Everything else expires after 30 days. An upload that never finishes is deleted after a day.
- Which devices are in your sync group, and each one’s last-seen time, for the list of your devices.
- Your licence’s id, to count your sync groups against your licence, and the date your group’s sync access runs to, so sync stops for a licence that is no longer active.
- Whether each phone recording was collected or expired, for 7 days, so your phone can tell you.
- Your IP address, for up to 4 hours, to limit how often it can call the server.
- Logs of refused requests and delivery problems, such as an upload that never finished, a message nobody collected, or a pairing that didn’t complete. Your devices and sync group appear in them only as short pseudonymous tags. The logs contain no meeting content and no IP addresses, and are kept for 7 days.
While sync is on, the app asks our licence server every few days for a short-lived sync pass and shows it to the sync server. The pass carries your licence’s id and when the pass expires, and nothing else. Your email address never reaches the sync server.
Voice prints never leave your device, encrypted or not.
Remote MCP access
Remote MCP access is off by default. When it’s on, your AI can read your meetings through our server while talat is open. It’s read only, and meetings you’ve turned off for the assistant stay hidden.
Meetings pass through our server encrypted in transit, and their content is never logged or stored.
The server keeps:
- A random id for your computer and a fingerprint of its key.
- Each AI you’ve linked: its name, when you linked it, and fingerprints of its access tokens. Unused tokens expire after 60 days. Revoking one in Settings stops it at once.
- Link codes, for 10 minutes.
- Your IP address, for a minute, to limit how many codes it can try.
- Logs of what happened, such as a link or an answered request. They name the tool but hold no content, codes or IP addresses, and are kept for 7 days.
Once your AI has read something, its own privacy policy applies.
Google account integration
talat can optionally connect to a Google account so your upcoming meetings appear inside the app. This integration is opt-in: nothing is read from Google unless you explicitly connect an account from Settings.
When you connect a Google account, talat requests two narrowly-scoped, read-only permissions from Google:
https://www.googleapis.com/auth/calendar.calendarlist.readonly- to list the calendars on your account, so you can choose which ones to use with talat.https://www.googleapis.com/auth/calendar.events.readonly- to read upcoming events from the calendars you’ve chosen.
talat also requests the standard openid and email scopes so your connected account can be labelled in Settings with your email address. All four scopes are read-only: talat cannot write to your calendar, create or modify events, or access other Google data.
talat’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. The next section spells out what that means in practice.
How your Google data is protected
Because everything stays on your device, the protection picture is unusually simple. We use the following measures to safeguard data obtained via Google’s APIs:
- Encrypted in transit. Calendar data is fetched from Google over HTTPS (TLS), the encrypted transport required by Google’s APIs. Your operating system handles the connection; nothing of ours sits in between.
- OAuth tokens encrypted at rest. Your Google sign-in is stored in your operating system’s secure credential store (macOS Keychain on macOS, Credential Manager on Windows), which encrypts credentials at rest using keys tied to your user account. Tokens are never stored in plain files on disk.
- Calendar data scoped to your user account on disk. The calendar data talat caches locally is held in talat’s application data folder, which your operating system protects with per-user file permissions. If you have full-disk encryption enabled (FileVault on macOS or BitLocker on Windows, both on by default on modern installs), the cache is encrypted at rest along with everything else on the disk.
- Limited use. We have no servers that receive your calendar data; Google is the only network party involved. We never share your calendar data with other third parties, use it for advertising, or use it to train AI or ML models.
- Revocable at any time. Disconnecting from Settings revokes talat’s access on Google’s side and deletes the locally-cached calendar data from your device.
Microsoft account integration
talat can optionally connect to a Microsoft account (Outlook.com, or a work or school Microsoft 365 account) so your upcoming meetings appear inside the app. This integration is opt-in: nothing is read from Microsoft unless you explicitly connect an account from Settings.
When you connect a Microsoft account, talat requests these permissions through Microsoft Graph:
Calendars.Read- to list your calendars and read upcoming events from the ones you’ve chosen.offline_access- so talat can keep syncing without asking you to sign in again each time.openid,emailandprofile- so your connected account can be labelled in Settings with your email address.
All of these are read-only: talat cannot write to your calendar, create or modify events, send mail, or read your mailbox. As with Google, calendar data goes straight from Microsoft to your device over HTTPS, your sign-in is kept in your operating system’s secure credential store, and we never share your calendar data, use it for advertising, or use it to train AI or ML models.
Disconnecting from Settings deletes talat’s saved sign-in for that account from your device and stops syncing it. Microsoft doesn’t let an app remove its own access, so it keeps listing talat as an authorised app until you remove it at account.microsoft.com (personal accounts) or myapps.microsoft.com (work or school accounts).
Licence validation
If you've bought a licence, the diagnostic ping described above also serves as a licence check: it confirms your licence hasn't been refunded or revoked, and if it has, the app reverts to the free trial. We need this to protect our business. The licence id it sends is opaque: a one-way hash, not your payment details or email.
The website
This website uses PostHog for basic analytics: how many people visit, how many download the app, and which channels lead people to us. PostHog stores an anonymous identifier in your browser’s local storage (not a cookie). If you arrive via a campaign or a directory listing, we note where you came from. We don’t track across devices, share this data, or build advertising profiles.
We use PromoteKit for our affiliate programme. If you arrive at this site via an affiliate link, PromoteKit sets a cookie (lasting 60 days) so the affiliate can be credited if you purchase talat. The cookie contains no personal information: just a referral identifier.
We use Google Ads conversion tracking to help us optimise our marketing. The Google tag is loaded only when a conversion is about to fire (when you click a download button, or when you land on the payment confirmation page) and sets a single conversion-linker cookie (_gcl_au) so the conversion can be attributed back to the original ad click. We do not enable Enhanced Conversions (so no email or other personal information is sent to Google), and we do not use Google Ads for remarketing or cross-site tracking.
Purchases
Payments are processed by Stripe. When you buy talat, Stripe collects your email address (they require it) and billing address. We receive your email so we can send you a licence key. We don't sell, share, or do anything with your email address. We never see or store your payment details.
Data we store
If you buy talat, we store your email address and opaque licence identifier.
Third-party services
- Stripe - payment processing. See Stripe's privacy policy.
- PostHog - first-party website analytics. See PostHog's privacy policy.
- PromoteKit - affiliate referral tracking. Sets a single cookie (60-day expiry) when you arrive via an affiliate link. See PromoteKit's privacy policy.
- Google Ads - conversion tracking, scoped to download clicks and purchase confirmation only (see “The website” section above). See Google’s privacy policy.
- Resend - transactional email (licence delivery). See Resend’s privacy policy.
- Google - Calendar API, only if you opt in to connect a Google account (see the “Google account integration” section above). See Google’s privacy policy.
- Microsoft - Microsoft Graph calendar API, only if you opt in to connect a Microsoft account (see the “Microsoft account integration” section above). See Microsoft’s privacy statement.
- Cloudflare - runs our backend (licensing, sync and this website) and our DNS. See Cloudflare’s privacy policy.
Changes to this policy
If we change this policy, we'll update this page. We won't make changes that weaken your privacy without making them obvious.
Contact
If you have questions about this policy or how talat handles your data, email us at hello@talat.app, or DM us on Bluesky or X.