Privacy
Written for the person who never signed up and had a wallet made for them anyway.
What is stored
For each handle someone sends to: the platform, that platform’s public numeric user id, the handle, display name and avatar URL as the platform publishes them, the generated wallet address, and the time. For each send: the ticker, amount, an optional note from the sender, and the status.
A wallet can be created for you without you asking
That is the mechanism, not a side effect: someone typing your handle is what brings the wallet into existence. It holds only what is sent to it, it is bound to your account’s permanent id, and it is yours the moment you sign in. If you would rather it did not exist, it cannot be deleted from the chain, but write to us and the record of it here will be.
What the public ledger shows
The home page lists recent sends. Notes are never shown: they are written by one person about another. A handle is shown only after that person has signed in at least once. Until then it is masked, because a wallet made for someone who has never opened the app is not their decision to publish. Wallet addresses and balances are visible on the chain regardless of what this page does.
What cannot be known
Senders are never asked to sign in or connect a wallet, so there is no sender account here to identify. A send is recorded as a request for a deposit address, not as a claim about who paid.
Third parties
Privy holds authentication and wallet key shares. GitHub is queried to turn a handle into a public user id, and X either through its own API or, without a token configured, through FixTweet’s public mirror, which therefore sees the X handles that get looked up. A public RPC endpoint is read for balances. No analytics, no advertising, no tracking cookies.