We care about your privacy,
and you should too.
A note or a pile of files, sealed in this tab before it leaves. No account, no email, nothing to install.
No account needed
open the page and use it
temp note
Sealed text behind one link. It can burn on first read.
We see: size, expiry, how many times it was opened.
transfer
Files up to 4 GiB, each one sealed, one link opens them all.
We see: exact sizes, times, opens. Never names or types.
members
The public directory of people who chose to be listed.
We see: nothing private: it is a public page.
swap ↗
Coin to coin with no KYC. dy.ing never holds the funds.
We see: pair, amounts, addresses, status.
With an account
a username and a password. no email. create an account
storage
A file manager whose names and contents are sealed.
We see: the shape of your tree, sizes, times, what is shared.
masks
Five addresses that receive mail and seal it on arrival.
We see: each message once, while sealing it. Mail is not end-to-end encrypted.
soon
email
A full mailbox. Not open yet.
We see: everything you send, in transit.
claim /@you
claim a public profile
We see: everything you publish. That is the point of it.
messages
End-to-end encrypted chat by @handle.
We see: who talks to whom, when, and how long each message is.
escrow ↗
Deals between strangers. We hold the funds today.
We see: addresses, amounts, parties. Terms and chat are sealed.
Prefer typing?
every screen has a commandbooting local privacy runtime…
Check us
The key never reaches us
Notes and transfers are sealed here with AES-256-GCM. The key rides in the URL fragment, which browsers never send. Run the self-test.
The primitives are checkable
argon2id, AES-256-GCM and BIP39 run against published reference vectors in your own tab. The terminal does it on every load.
The boundary is written down
What is sealed, what is public and what the server must see, per tool, including where it is not end-to-end.