Privacy and security
Your browser and the app on your computer encrypt everything between them. The Tunnelio server in the middle passes sealed messages along: it can see that they exist and how big they are, never what they say.
How the encryption works
- Pairing. The code the computer app shows lets your browser and your computer prove to each other that they know the same secret without ever sending it (a password-authenticated key exchange, SPAKE2). Out of it comes a pairing key that only the two of them have.
- Each connection. Every time the browser connects, the two make fresh keys for that session (X25519), tied to the pairing key. A key that leaked would not open other sessions.
- Each message. Every message is sealed with AES-256-GCM and numbered, so it cannot be read, changed or replayed on the way.
The server never has the pairing key or the session keys. The full protocol, with the threats it considers, is in the project's specification.
What the server knows
- Your e-mail address and when you created your account and signed in.
- Your devices: the names you gave them, their system and app version, and when they connect.
- Who talks to whom, when, and how big each message is.
- While you are connected, your IP address, used for the limits on attempts. It is not stored.
- For each signed-in session, the browser and system as the browser itself announces them, and when it was last used.
- Two sealed files it cannot open: the list of your paired computers and your preferences.
Whatever sits in front of the server to carry its traffic sees the same, and only ciphertext.
What the server never sees
- Your messages, the answers, and the images and documents you send.
- Which models you use, and your conversations' titles.
- The secret part of the pairing code (8 of its 12 symbols).
- Your password: the browser derives a separate sign-in key from it, and the server keeps only a slow hash of that key.
Where your conversations live
Only on the computer that runs Ollama, in the computer app's own file. Nothing is kept on the server. An anonymous chat is not kept at all.
Tunnelio does not encrypt that file itself, so turn on your system's disk encryption (BitLocker on Windows, FileVault on macOS, LUKS on Linux): a lost or stolen computer then does not give your conversations away.
Your password matters
It seals the list of your paired computers and your preferences. If someone ever got a copy of the server's database, a long password is what keeps those sealed files closed. Use a long one you do not use elsewhere, and consider two-step sign-in.
The limits, plainly
- The web app comes from the server. Your browser runs the code the server sends, and that code sees your password and your conversations. A tampered server could send altered code; this is true of every end-to-end encrypted app that runs in a browser. You can check it: the server publishes the commit its web app was built from, the build is reproducible, and the project's script compares every file it serves with a rebuild of the public code (how).
- The server sees the traffic's shape: who, when and how much, as listed above.
- A paired browser can use the computer. Anyone with access to a browser you paired can chat with your computer. Remove the pairing if a device is lost (see Devices and account).
Check your downloads
Every release publishes the SHA-256 of each installer. How to verify your download shows the one command to run on your system.
Found a problem?
Write to [email protected]. For a security issue, please do not open a public issue: see the project's security policy.