Sealed Chat
Talk through this page. Each message is sealed on your device before it leaves, and the history only ever shows sealed text.
The same passphrase on both devices, typed into this exact address, opens the same room. Starting takes a few seconds on purpose, to make guessing slow. If your browser offers to save or fill a password here, decline.
The newest message from the other device opens above by itself and has a coloured border here. Tap any other message to open it instead. Only one is ever open, and this page keeps nothing you open.
How this works, and what it cannot do
- Your message is sealed on this device before anything is sent. The relay that passes messages along is sent only sealed text, and it refuses anything else. This page never sends it your passphrase.
- You are trusting whoever runs this address to serve this page unchanged. They could serve a different page that behaves differently, and this page cannot warn you about that. The original Sealed Message tool can keep a checked copy of itself on your device. This page cannot.
- The passphrase does two jobs. It locks each message, and it decides which room you are in. Both devices reach the same room by typing the same passphrase into this exact address. A different address, even for the same machine, is a different room.
- A short or common passphrase can be guessed, and a room lasts until someone ends it, so a patient guesser gets many tries. Anyone who guesses it lands in your room and can read it. Use a long one, and a new one for each session.
- The page shows how many devices have opened the room. Opening the page in another tab counts as another device. If someone joined before your partner did, the count can look normal, so treat it as a warning sign and not as proof.
- The history shows sealed text only. The newest message from the other device opens by itself in one place, so keep the screen away from other eyes while a session is running. Tapping another message replaces it. This page stores nothing you open. Your phone may still keep a picture of the screen for its app switcher.
- The relay holds the sealed messages in memory until someone presses End session. It writes nothing to disk and keeps no log of requests. If the relay restarts, every open room is lost.
- End session removes the room from the relay, overwrites the relay's stored copy of every message, and clears this device. Those messages were only ever sealed text. The relay cannot scrub the brief working copies it made while passing them along, which its memory reclaims in its own time. The other device clears itself the next time it checks in, or the next time it tries to send. It cannot remove records kept elsewhere that a connection happened, or anything the other person copied.
- The page cannot tell you who wrote a message, because both of you share one passphrase. It only marks what this device sent during this session. The relay could also hold back, repeat or reorder messages. Each opened message shows when it was sealed, which is how you would notice an old one sent again.
- Every sealed message here is an ordinary Sealed Message. To seal or open one by hand, use the original tool, which is blocked from using the network at all: sealed-message.statichost.page
- Always open this address in Safari, Chrome or Firefox itself. The browsers built into apps such as Messenger and Instagram can read what is typed into any page they show. This page refuses to work in the ones it can recognise, but it cannot recognise all of them. A keyboard app with full access can also see what you type, and no page can detect that.
- Only the one script built into this page can run here, and it talks only to the relay that served it. Your browser enforces the first part.