HotTea Web chat

What we can read, and what we can't.

HotTea encrypts your messages, photos and videos on your device, and our server delivers them without being able to read them. The server still sees some information it needs to run HotTea, and encryption has limits. This page explains what is protected, what isn't, and what you can do yourself.

How encryption works

Every HotTea account has a key pair. Its public key is shared through our server so others can encrypt for you. Its private key stays on your devices and in your login file.

When you send something, your device encrypts it before it leaves. Only devices signed in to your account or to the accounts of the others in the chat can decrypt it.

In ordinary chats, our server stores and forwards only this encrypted data, called ciphertext. To deliver it, the server must know who it is for and when it was sent. It has no key to open the content.

What we cannot read

In ordinary chats, the following reaches our server only as ciphertext. Our delivery service has no key to decrypt it:

  • Message text, including edits and replies
  • Live drafts while you type them
  • Photos, Live Photos and videos
  • Voice messages
  • Profile photos
  • Group names and group photos
  • The text of items on your shared to-do list
  • Photos and videos you add to games, such as Picture Puzzle images or Daily Duo photo and video answers

One exception is by design. HotTea runs a few accounts of its own, such as feedback. A message you send to one of them is encrypted for that account, and we read it as its recipient, just as any contact reads what you send them. Profile photos of these accounts are public.

What we can access

Encryption hides content, not the information the server needs to run HotTea. Our server stores or sees the following, so the people who run HotTea can access it.

Data HotTea handles, whether it is end-to-end encrypted, and what our server can access
Data End-to-end encrypted What our server can access
Messages and live drafts End-to-end encrypted Yes Sender, recipients and chat; when a message was sent, edited or deleted; its type, such as text, photo or voice; its size; whether and when it was saved; and that you are typing.
Photos, videos and voice messages End-to-end encrypted Yes Type and file size, when they were uploaded, and whether a view-once item has been opened.
Account End-to-end encrypted No Your username and public key, whether you have a profile photo, your signed-in devices with their names and when they were last active, and the IP address your device connects from.
Contacts, chats and groups End-to-end encrypted No Who chats with whom, message requests and whether they were accepted, blocks and archived chats. For groups: who created them, who is a member or invited, and whether a group has a photo.
Online and read status End-to-end encrypted No Whether you are online, when you were last online, and how far you have read in each chat.
Reactions End-to-end encrypted No Which emoji you reacted with, to which message, and when.
Shared to-do list End-to-end encrypted Partly The text is encrypted. The server sees who added each item and when, and who checked it off and when.
Games End-to-end encrypted Partly Game photos and videos are encrypted. The server can access everything players enter and the results: words, statements, questions and answers, cards, moves, winners and Daily Duo text answers.
Sugar End-to-end encrypted No Your balance and every change to it: daily and Daily Duo rewards, games, Hot Messages, presents and other purchases.
Push notifications End-to-end encrypted No Each notice names the sender's username and has a generic text, such as "New message", or the reaction emoji. Apple and Google deliver these notices.

Game secrets, such as a Picture Hangman word, the lie in Two Truths and a Lie, the thing to guess in 20 Questions, or the cards in poker, are stored encrypted with a key held by our server. That keeps them hidden from the other player until the game reveals them, but it is not end-to-end encryption: the server decrypts them to run the game, so HotTea can access them. Only the photos and videos in a game are encrypted end to end.

Protect yourself

Compare fingerprints

In a chat's options, Verify identity shows one fingerprint for you and one for your contact. Compare both in person or over another channel you trust, not in the HotTea chat itself. If they match, nobody has slipped a different key in between. After your first chat, HotTea remembers your contact's key and stops with a warning if it ever changes. Groups have no Verify identity of their own: HotTea remembers every member's key in the same way. To check a member, compare fingerprints in your chat for two with them.

Secure your devices

Anyone who can unlock your phone or computer can read your chats there. Use a screen lock, keep your system and browser up to date, and turn on App lock in HotTea for an extra PIN or Face ID.

Keep your login file safe

Your login file contains your private key and the recovery credential that signs in to your account. Anyone who has it can sign in as you and decrypt messages sent to your account that they get hold of. Store it somewhere only you can reach, such as a password manager or an encrypted drive, and never send it in a chat or by email.

Review your active sessions

Profile → Settings → Active sessions lists every device signed in to your account. Sign out any you don't recognize. If your login file may have leaked, replace it under Profile → Settings.

Where protection ends

Your contact can keep copies

Once a message is decrypted on your contact's device, they can copy it, take a screenshot or film the screen. No app can reliably prevent that. In a group, the same goes for every member.

Disappearing doesn't erase copies

The 24-hour expiry and view once control what the app and our server keep. They cannot erase screenshots, recordings or other copies someone has already made.

When content expires

Messages, photos, videos and voice messages normally expire 24 hours after our server accepted them, and the server then deletes them. A saved message stays as long as someone in the chat keeps it saved, and expires 24 hours after the last save is removed. Items on the shared to-do list don't expire. They stay until someone in the chat deletes them or the chat is deleted. If you leave a group, the server deletes your messages in it for everyone. If its creator leaves, it deletes the whole group.

A compromised device sees everything

Encryption protects your data in transit and on our server, not on a device that is already compromised. Malware on your device or your contact's, or a modified HotTea app, can read messages once they are decrypted. The web chat is loaded from our server each time you open it, so using it also means trusting the code we deliver.

A leaked key can unlock stored messages

Your account key doesn't change over time. Whoever obtains your private key, for example from a leaked login file, can decrypt ciphertext addressed to your account that they have or can still get, such as saved messages on our server.

Technical details

For readers who want the specifics. The API documentation describes the protocol in full.

Cipher suite

HotTea uses authenticated HPKE (RFC 9180, mode Auth) with DHKEM(P-256, HKDF-SHA256), HKDF-SHA256 and AES-256-GCM. Every message, draft and wrapped key is sealed in a fresh HPKE context with the sender's private key and the recipient's public key. An envelope that opens correctly therefore also shows it was sealed with the sender's key.

A message is sealed twice: once for the recipient and once for the sender's own account, so the sender's other devices can read it too. In a group, it is sealed once for every member, pending invitations included, and once for the sender. The creator seals the group's name and the key of its photo for every member in the same way.

Media keys

Each photo, video or voice message is encrypted with AES-256-GCM under a fresh random 256-bit key and a fresh 96-bit nonce. That media key is then sealed with HPKE for each participant. The server stores the encrypted file and the sealed keys, never the media key itself.

When a view-once item is opened, the server deletes its sealed keys and the encrypted file.

Authenticated routing data

Sender, recipient, chat, content type and message ID are bound to every envelope as additional authenticated data. The server can read this routing data but can't change it: if an envelope is altered or moved to another chat, decryption fails. Encrypted media is bound to its chat, sender, ID and kind in the same way.

Key pinning on first use

The first time you chat with someone, HotTea stores their public key on your device and in your login file. From then on, the app uses only that pinned key. If our server ever returned a different key for that contact, the app would refuse with "Your contact's security key changed." In a group, HotTea pins every member's key the same way, also for members you have never chatted with alone.

This trusts the first key it sees. Comparing fingerprints confirms that this first key really belongs to your contact. A fingerprint is the SHA-256 hash of the public key, shown in groups of four hexadecimal characters.

Forward secrecy

Every envelope is encrypted to the recipient's long-term identity key. As RFC 9180 explains for this kind of use, that offers no forward secrecy for the recipient: whoever later obtains the private key can decrypt all retained ciphertext addressed to it.

Expiry limits how much ciphertext our server keeps. It cannot protect ciphertext someone copied earlier.

Replacing a login file

Replace login file sets a new recovery credential, so old login files can no longer sign in. It also signs out your other sessions and revokes your API keys.

It doesn't change your encryption identity. The private key in an old login file still decrypts ciphertext addressed to your account, so treat content as exposed if an old file leaked.

Key storage on your devices

In browsers, HotTea keeps your keys in an encrypted IndexedDB vault. Its AES-GCM wrapping key is marked non-extractable, so the browser does not hand out the key itself. Anyone with access to your browser profile can still open HotTea there.

On iPhone, your keys are stored in the Keychain and are available only on that device, while it is unlocked.

iCloud recovery

On iPhone, you can turn on iCloud recovery in Settings. HotTea then keeps a copy of your private key, recovery credential, pinned contact keys and profile photo key in your iCloud Keychain, without an active session token. That copy is protected by your Apple account, so secure it accordingly.

Notification metadata

Push notifications are sent through Firebase Cloud Messaging and, on iPhone, Apple's push service. A notice carries the sender's username as its title and a generic text such as "New message", or the reaction emoji, as its body. If several accounts are signed in on one device, it can also name the receiving account. It also carries IDs the app needs to open the right chat.

Message content is never part of a notice. On iPhone, the app can use the message ID to download the encrypted message in the background.

Read the protocol in the API documentation