you
Accounts & honesty.
stikk has no accounts of its own — it signs into the ones you already have, on this device. Or mints one that never leaves it.
Not connected on this device.
Not connected on this device.
Not connected on this device.
- 🟢Going live
Not saved — not by us, not by anyone in the middle. When either side disconnects, the messages are gone from both screens; what remains is a line saying it happened, and it dies with the tab. The other person can still keep what they saw.
- 🔵Stored, encrypted (Matrix, XMTP)
Kept by the protocol’s servers in encrypted form so chats survive your phone being off. Keys live on your devices — and an XMTP throwaway identity is nothing but a key on this device, so its backup button is the whole recovery story.
- 🟡Server-readable (Bluesky DMs)
The provider can read what you send. stikk labels this lane loudly — in the composer, on every thread, and on the seam whenever a conversation drops onto it.
Every conversation shows which lane each message rode — the dividers in a thread are lane changes, never decoration.
A personal experiment in user-owned identity and honest retention. stikk is the zip tie, not the wire: conversations ride protocols you already have accounts on, woven into one thread. Invites only pop while stikk is open — push notifications aren’t built yet.
Developer: loopback rehearsal — a two-pane demo of the live machinery in one tab.