Privacy policy
Statim has no server for your account or your messages. Your account is a recovery phrase on your device, there is no sign-up, and the developer operates nothing that your messages, keys or contacts pass through. This page is the complete account of what leaves your device, and to whom.
What the developer receives
Three things, all anonymous.
The first is performance data, through Expo's expo-observe library. It
reports how long the app took to start and to move between screens, plus the
host name of the slowest network request made during launch. For this app that
is a messaging relay, or your own blockchain endpoint if you set one. It carries no
account, name, address or message content, and it is not linked to you.
The second is a count of how many devices are running each version, which follows from the update check described below. It is a number on a dashboard, with no way back to a person.
The third is usage statistics, which you can turn off. Unless you do, the app sends the developer's own statistics server (Umami, at stats.laibe.cc) the name of the screen you are on, from a fixed list (such as "Chats", "Chat" or "Settings: Privacy"), with Statim's version, your operating system, the kind of device and its screen size, and the app's language: at launch, on each new screen once it has stayed a second, and when the app comes back after 30 minutes or more away; never while it is behind other apps, before you have set up an account, or while it is locked. It never sends anything you write or read, nor which chat is open or who is in it. The App Store and Google Play list this as product interaction and a device identifier, used for analytics and not linked to you.
Each count carries an id made from a random number kept on your device for this alone, hashed with the month, so the id changes every month and one month cannot be matched with the next. That random number is replaced with a new one within 12 months. It cannot be tied to your account, keys, contacts or messages. On an iPhone it is kept in the keychain, so it survives deleting and reinstalling the app, and is still replaced within 12 months.
The statistics hold no network address and no location: the app sends a fixed placeholder (127.0.0.1) where the address would be. The request itself still comes from your network address: it reaches stats.laibe.cc through Cloudflare, and the server's access log keeps it for a short time, as with this website's visits. The statistics are kept for 25 months, then deleted.
They are on by default, for every account on the device at once, and only released builds send them. Turning off Share anonymous usage statistics in Settings → Privacy stops them at once and deletes the random number, keeping only a record on your device that you turned them off. Turning it back on sends nothing by itself, and the next count makes a new random number.
That is the entire list. There is no third-party analytics SDK, no advertising, no crash reporter that captures what you write, and no push service run by the developer. Notifications are generated on the device, except the iPhone notifications your computer sends through your own iCloud, described below.
What leaves your device, and who sees it
Messages
XMTP, Nostr and Status carry end-to-end encrypted messages. Relay operators
see ciphertext and routing metadata: that two parties are communicating, roughly
when, and from which network address. Nostr relays additionally never learn who
sent a message, only who receives it. You choose the relays under Settings →
Protocols. Status goes through Status's own nodes unless you give it a Status
node of your own there. Starting a Nostr chat with a name such as
[email protected] asks example.com for the public key behind it, so that
site sees the name you looked up and your network address.
Telegram is different, and only active if you sign in. Telegram chats are not end-to-end encrypted: Telegram's servers hold and can read them, exactly as with the official app. Signing in sends your phone number to Telegram, and the app identifies itself with the API ID and hash you registered yourself. The Telegram database on this device is encrypted with its own key in the keychain and is deleted when you sign out or erase the account.
Matrix is only active if you sign in. Messages go to the homeserver you name. Rooms with encryption on are end-to-end encrypted with Olm and Megolm; the homeserver still sees who talks to whom and when. If that homeserver runs a bridge to another network, the bridge decrypts what it relays, on the machine where it runs. Signing in sends your Matrix ID and password to the homeserver once; the app then keeps only a session token, and the SDK's local store (history, keys, downloaded media) is encrypted with its own key from the keychain. Both are deleted when you sign out or erase the account.
On a computer, Statim can run that homeserver itself. It answers only on the computer and, once you connect your phone, on your own Tailscale network, and it talks to no other Matrix server. The first time you turn it or a bridge on, the app downloads that program from GitHub and checks it against a hash the app ships with. The server's database, the bridges' logins and their copies of your chats stay in the app's data folder on the computer. The app does not encrypt them itself, so they rely on the computer's disk encryption. They are deleted when you erase the account. Tailscale's HTTPS certificates put the computer's name on your tailnet in public certificate logs.
Money
Blockchain reads and transactions go from your device to a public endpoint for
that network, or to one you set with /rpc. That endpoint sees which addresses
you look at and which transactions you send.
Token balances are read from that same endpoint. On EVM chains the app asks each contract on a token list bundled with it; on Solana it asks the node what the address holds. No third party is told what you own, and no key is involved.
/trade asks LI.FI for a quote, which shows LI.FI your address,
the tokens and the amount. It works without an account; a LI.FI key you enter
yourself only raises how often you may ask. The transaction is signed on your
device and broadcast through the blockchain endpoint like any other. Releasing a
token to a LI.FI route is usually a signature rather than a transaction, either
the token's own permit or Uniswap's Permit2, and neither reveals more than the
trade already does.
If you save an LCX Liberty DEX key in Settings → Trades, a swap that stays on
one chain also asks LCX Liberty DEX for a quote, and the
app uses whichever quote guarantees you more. That request goes straight from
your device to swap-api.lcx.com and shows LCX your address, the tokens and the
amount. Nothing passes through Statim. Unlike LI.FI, LCX needs an account: you
sign in at dex.lcx.com to create the key. Without a key nothing is sent to LCX.
Bridges between EVM chains, their status checks and token lookup go to LI.FI
either way. A trade on an LCX route cannot use those signatures. When LCX's
router may not yet spend the token, the app approves it for the exact amount in
a transaction of its own, then sends the swap.
On Solana, /trade asks Jupiter at api.jup.ag. A quote
shows Jupiter the tokens and the amount; confirming the trade also shows it your
Solana address, because Jupiter puts the transaction together for it. Jupiter
needs no account and no key. The transaction is signed on your device and sent
through your Solana endpoint.
A trade between Bitcoin and Ethereum or Base goes through
THORChain. Its quotes come from a public THORChain node
at gateway.liquify.com, which sees the assets, the amount and the address the
trade pays out to, along with your network address. An Ethereum token you name
by its symbol is still looked up through LI.FI. The deposit itself is an
ordinary transaction from your device, through your Bitcoin indexer or your
blockchain endpoint, and like every THORChain swap it is public on both chains.
Prices come from a public market data endpoint (Binance's, by default; /marketapi
changes it) with no account and no identifier attached. After /marketapi chainlink,
they are read instead from Chainlink's price feeds on Ethereum through your
Ethereum endpoint, so no exchange learns which markets you watch; that endpoint
sees which feeds are read.
A hardware wallet signs on the device. A Ledger talks to the app over Bluetooth
or USB and a Keystone over QR codes, with nothing in between. A Trezor request
travels as a connect.trezor.io link that the phone hands to the Trezor Suite
app; if Trezor Suite is not installed, the link opens Trezor's website instead,
which then sees the request.
Links and attachments
Link previews fetch the page behind a link directly from that site, to show its title, description and picture. For YouTube it fetches the small oEmbed response instead of the page. This means the site sees your network address when the message arrives, not only if you tap it. It is on by default and Settings → Privacy turns it off. Results are cached on the device for a week so the same link is not re-fetched as it scrolls past.
Links, phone numbers, email addresses, places and wallet addresses are
recognised on the device with no request at all. A wallet address found in a
message is looked up through the blockchain endpoint you already use, exactly as
/balance would. So is a transaction in a message: an Ethereum transaction hash
goes to every EVM chain's endpoint at once, to find the chain it is on, and a
Solana signature goes to the Solana endpoint when the wallet has Solana switched
on.
GIF search uses KLIPY, and only if you enter your own key for it.
AI
AI is off until you turn it on in Settings → AI, and each command runs only when you type it or tap its chip. With Automatic, the model and the translator are the ones built into your device (Apple Intelligence and Apple Translation, or Gemini Nano and Google's ML Kit) and the text never leaves it. ML Kit downloads a language from Google the first time you translate into it, which shows Google your network address and nothing else.
If you choose your own server or Anthropic in Settings → AI, the text of each request goes to that server: what you rewrite or translate and, for summaries and reply suggestions, the recent messages of that chat, including other people's in a group. Translation also falls back to that server when the device has no translator for a language. The address and the key you enter stay on this device.
Suggest replies on open is a separate, optional setting in Settings → AI. When enabled with your TypeSafe API key, opening an eligible DM or group, or receiving a new message while it is open, sends up to 20 recent messages to TypeSafe's Jev to decide whether you need to reply. This includes other participants' messages and happens even when your reply model runs on the device. If a reply is needed, your selected model receives recent messages to write a suggestion. You review and send it yourself. The TypeSafe key stays with your account's other keys on this device and is sent only to TypeSafe.
Highlight chats needing a reply is another optional setting. It loads recent history for chats visible in the chat list and sends up to 20 recent messages to TypeSafe for the badge decision, without marking the chat read. This does not generate or send a reply.
Suggest follow-ups separately allows Jev to check recent messages once your latest sent message has gone unanswered for at least 24 hours. The check runs while you view the list or chat. If a follow-up is useful, your selected model prepares a suggestion when you open the chat; nothing is sent for you.
Suggest useful AI actions separately sends recent messages and your device language to TypeSafe to recommend a summary or translation for the open chat. The selected model or translator runs only when you tap the suggested chip. Automatic Jev checks run only while Statim is in the foreground and unlocked.
Notifications from your computer
iOS stops Statim soon after you leave it, so an iPhone can hear about new messages from Statim on your computer instead. It is off until you turn it on in two places: Notify my iPhone on the computer and Notifications from your computer on the iPhone.
Turning it on opens Apple's sign-in in your browser on the computer. Your password stays between you and Apple. Statim receives a token that opens only its own space in your iCloud and keeps it in the vault on that computer; Apple replaces the token with each request.
For each message that would notify on the computer while its window is in the background, the computer saves a note in the private iCloud database of your Apple Account. The note holds which chat it is, the chat's name and up to 300 characters of the message preview, encrypted with a key derived from the account's recovery phrase. Next to it is a tag, derived from the same phrase, that names the account without revealing its address. Apple stores the note and wakes your iPhone with it through its push service. Apple can see that your Apple Account uses Statim, when notes arrive, how large they are and the tag, but it cannot read them. The developer has no access to your private iCloud database.
The iPhone decrypts the note itself, with the key it derives from the same recovery phrase, and fetches nothing else. The computer deletes each note about five minutes after saving it. Turning the feature off deletes the notes that are left and signs the computer out of iCloud.
App updates
On iPhone and Android, the app asks Expo's update service (u.expo.dev) at
each launch whether a newer version of its own code exists, and uses what it
finds from the next launch. That is how a fix reaches you without waiting for
an app store review.
The request says which platform, which release channel and which build; Expo sees the network address it came from, as any server does. It carries no account, address, phone number or anything from your conversations.
The desktop app checks GitHub instead, and replaces itself only after verifying a signature.
What is never sent
There is no last-seen and no typing indicator. The protocols carry no presence and the app does not add a side channel to broadcast one. Read receipts are off by default and symmetric: with them off you do not see the other person's either. Your address book is read on the device to suggest who to invite and is never uploaded.
What stays on your device
Your recovery phrase and keys, in the system keychain, optionally sealed behind Face ID or the device passcode. For a hardware wallet account, that is the chat key seed its wallet's signature produced, never the wallet's own key. On an iPhone that hears from your computer, the key that opens those notes also sits in a keychain group shared with Statim's notification extension. Message history, in an encrypted database per account. Downloaded media, in per-account directories. Preferences, per account. The random number behind the usage statistics, with the date it was made, or, once you turn them off, only the record that they are off, in the same vault as the keys. On an iPhone that is the keychain, which outlives the app, so the number survives deleting and reinstalling it, until it is replaced within 12 months.
Deleting your data
There is no server-side account to delete, because there is none to begin with. Settings → Erase this account removes the keys, the databases, the media and the settings from this device, signs out of Telegram and Matrix if they were connected, and stops notifications from the computer for that account. It does not delete anything held by those networks, and it does not affect the recovery phrase you wrote down. The same phrase restores the same account later.
Messages already delivered to relays or to other people are beyond the developer's reach, as they are with any messenger. Usage statistics already sent cannot be picked out and deleted, because nothing ties them to you; they are deleted after 25 months.
This website
statim.laibe.cc counts visits with Umami, which the developer runs on the developer's own server. It sets no cookies, and its statistics hold no network address. Each page view records the page, the referring page, browser, operating system, device type, screen size, language, and the country, region and city looked up from the network address. A click on a download link also records which platform's file it was. Page views are grouped into visits by an identifier derived from the address and browser that changes every month.
Each count reaches that server through Cloudflare, and the server's access log keeps the request with its network address for a short time, to run and protect the service. That log is capped by size rather than by a number of days. The site itself is served from the developer's own server, also through Cloudflare, and its access log is kept the same way.
On its own, the app asks the site only for Statim's own sticker pack, and that request is not counted as a visit. A guide link opened from the app loads the page in a browser view, where it counts as a visit like any other.
Children
The app is not directed at children and collects nothing that would identify anyone, of any age.
Changes
This policy is a file in a public repository, so every change to it is a visible commit. Material changes will be noted in the app's release notes.
Contact
Open an issue at github.com/alaibe/statim/issues. For anything security-sensitive, use the private route in SECURITY.md instead.
Last updated 2026-11-20.