Security
Last updated: 3 November 2026
TeamTalk is a hosted service. Your content is encrypted on the way to our servers and encrypted again while it is stored there, under a key that belongs to your team alone. Our servers hold those keys, so this is not end-to-end encryption. This page sets out exactly what that does and does not protect.
How it works
- Every connection between the app and our servers uses TLS.
- Each team has its own data key. Message text, captions, transcripts, translations, link previews, channel and team names, folder and file names, and board content are stored encrypted with it (AES-256-GCM). Each value is bound to its team and to the record it belongs to, so it cannot be decrypted with another team’s key or moved to another record.
- The team keys are stored only in encrypted form. They are unlocked by a master key kept in a separate key-management service, which never hands that master key out.
- If the key-management service is unavailable, TeamTalk stops serving content and shows “temporarily unavailable”. It never falls back to storing or serving unencrypted content.
- Photos, videos, voice recordings and files are stored in Amazon S3 under Amazon’s storage encryption, not yet under your team’s key.
What this protects against
- A stolen database, backup or disk snapshot. It holds only encrypted content and encrypted keys.
- One team’s data reaching another team through a bug or a wrong query. Content sealed under one team’s key does not open under another’s.
- Someone browsing the database directly. What they see is ciphertext.
- Deletion you can rely on. When an owner deletes a team, its key is destroyed. From that moment its content cannot be recovered by anyone, including from backups.
What this does not protect against
- Someone inside TeamTalk with access to the running service. The service decrypts content to deliver it, so such a person could read it.
- A legal demand served on TeamTalk. We hold the keys, so we can be compelled to decrypt.
- A complete compromise of our servers, including the key-management service.
What is not encrypted
The service needs some information in readable form to work: who belongs to which team and channel, roles, display names and nicknames, phone numbers, message identifiers and timestamps, which messages have been read, reactions, and the language a voice message was recorded in.
To deliver features, our servers decrypt content and pass it on:
- Notifications carry the sender, the channel and the start of the message to Google Firebase Cloud Messaging and Apple, who therefore see that text.
- Translation and transcription run on our own machine, which holds the text or recording only while it is being processed.
- Link previews are fetched by our server from the site you linked to.
Deleting a team
Deleting a team removes its content from the service immediately and destroys its encryption key within a minute of the owner confirming. Copies of that content may still sit in our backups for a while, but without the key they are unreadable, to us as much as to anyone. We do not promise when those copies are physically erased; we promise that they cannot be decrypted.
What TeamTalk is not
TeamTalk is not end-to-end encrypted and is not a zero-knowledge service. If you need a service whose operator cannot read your messages, TeamTalk is not the right tool.