OPEN A PAD

one shared text pad the server cannot read — notes for an incident bridge, a negotiation, an interview panel. this page generates the pad key, and it rides the link's #fragment — never the wire.

• the pad key lives only in the link's #fragment — browsers never send it, so the server never holds it
• the document is ONE AES-256-GCM blob sealed in your browser; every save replaces it whole, so yesterday's draft provably no longer exists — not here, not on the server, not anywhere
• a pad dies 24 hours after its last write, in enclave RAM — nothing touches a disk, and the relay is hardware-attested: "blind" is checkable, not marketing

PAD IS OPEN

share this link — the part after # is the pad key and never reaches any server:

#……

KEY MISSING

you need the full link — the part after # is the pad key and never reaches the server. without it there is nothing here to read, and the server can't help: it never had the key either. ask whoever shared the pad to re-send the whole link.

WRONG KEY

this link's key doesn't decrypt this pad's ciphertext — the #fragment got mangled in transit, or it belongs to a different pad. editing is disabled: a save with the wrong key would replace what the others wrote. ask for the link again, sent whole.

NOTHING HERE

this pad never existed, or went 24 hours without a write and was swept. the server can't tell you which — and either way the only ciphertext is gone. pads leave nothing behind; that's the point.