Resources
Everything written down. Including the caveats.
A tool that asks to hold your credentials owes you a straight explanation of what it does with them. These pages are that explanation.
01 / Index
Start wherever your question is
Short answers in the FAQ, the full boundary on the security page, and a human at the end of the support page.
FAQ
The questions that come up before someone trusts a link with a password in it: what expiry really means, what happens when views run out, and what cannot be recovered.
Read it AnswersSecurity model
The trust boundary drawn explicitly — what the server holds, what happens if a link leaks, what an automated reader can reach, and the risks that stay open.
Read it TechnicalSupport
Where to ask a question, how to report a bug, and how to disclose a vulnerability responsibly.
Read it Get helpContact
One form to reach a person, with the subject chosen up front — a bug, a question, a disclosure, or a request to read the source.
Read it Reach us02 / Source
Read the implementation instead
None of the claims on this site require taking our word for it. The code, the threat model and the delivery plan are all readable — ask for whichever one answers your question.
Source
The Rust backend, the browser cryptography, and the test vectors that pin the envelope formats.
Ask for access CodeThreat model
What the server holds, what happens if a link leaks, the guarantees that are considered binding, and the risks that stay open.
Read the threat model SecurityRoadmap
Product scope and delivery status, including which parts are finished and which are still Phase 0.
Ask what is unfinished Roadmap