Server privacy and security

What a Tiny server stores, what the person who runs it can read, and what it does not protect against.

A Tiny server is run by its owner, not by the tinyclient project. Joining one means trusting whoever runs it with what is listed here. This page is about the server; Privacy and security is about the app on your computer.

What the server stores

DataHow it is kept
PasswordsNone. There are none.
AccountsA display name and an optional picture. An email address only if a sign-in provider sent one and the owner chose to keep it. There are no usernames.
PasskeysThe public key, a counter, a label, and when it was made and last used. Recovery codes as hashes.
Sessions, invites, bot tokensOnly a hash of each token. A session has no address, user agent or device name beside it.
Plaintext messagesThe text, in the database
Encrypted messagesCiphertext, with who posted it and when
FilesOne file each on the upload volume, under a random name. A plaintext upload is plaintext on disk; a sealed one is stored as it arrived.
CallsNothing. No recording. A call between two people leaves one line in their conversation saying how it ended.
Audit logWho did what to whom, with any reason they typed
Device namesAn optional label for each device used with encrypted conversations
IP addressesNo table holds one. The call server holds participants’ addresses in memory during a call.

The stack does not encrypt the database or the volumes on disk. That is the host’s to do.

What the operator can read

The person with the database owner role or root on the host can read every plaintext conversation and attachment, any email addresses, the audit log and every abuse report. They can sign in as any member, make themself an owner, and restore an older backup. Reading leaves no trace.

They cannot read the text of an encrypted conversation, the contents, names or types of sealed files, or the audio of an end-to-end encrypted call.

Roles do not change this. A moderator sees what their permissions show in the app; the operator is whoever holds the machine.

What the server always sees

Other members learn who is on the server and, in a call, the host’s public address. They do not learn each other’s addresses from the server.

A Tiny server is not an anonymity system.

Logs and telemetry

Operate and upgrade has the settings.

What is on the network

Retention and deletion

Nothing deletes messages, audit rows or bans by age. There is no auto-delete setting.

WhatKept for
A session30 days unless the operator set otherwise. Not extended by use.
The replay of live events24 hours
An upload never attached to a message1 hour
An invite nobody usedUntil it expires: 7 days unless set
A resolved abuse report90 days unless set, or for as long as an owner holds it

No deletion reaches the database’s write-ahead log, earlier backups, other people’s copies, or a proxy’s logs. Deleted files are unlinked, not overwritten. Restoring a backup brings back what was deleted after it. Backups have no schedule or expiry of their own.

What it does not protect against

The full account

The repository’s docs/privacy/ has the guarantees with the test behind each, the threat model, the data flows, and the open findings. Where those documents and this page differ, the repository is right. Some of them were written before the server had passkeys of its own and still describe sign-in through a provider only.

Edit this page on GitHub