Where the note actually lives.

The link is the storage

What you write is compressed and encoded into the URL fragment — the part after the # character. Browsers never send the fragment to a server, by design: it exists purely for the page you already have loaded to read. That single fact is what makes an accountless, serverless note possible at all, rather than a clever trick layered on top of one.

It also means there is nothing to expire, nothing to lose in a breach, and nothing the site hosting this editor can read, even in principle — the note never arrives here as a request; it only ever exists in the browser tab that has the link open.

Markdown, rendered safely

The editor renders Markdown live as you type, on a debounce so it stays smooth on a long note. The same rendering pipeline runs when you open someone else's shared link, which matters for a reason a private note does not have to consider: that note's text is arriving from a link you did not write, so it is sanitised against an explicit allowlist before it is ever shown, the same way a browser extension or a mail client sanitises HTML from an untrusted source.

What this means in practice

A few consequences follow directly from the fragment-storage design.

• A very long note produces a very long link. The size meter warns before a link gets long enough that some chat or email clients start truncating or wrapping it.
• There is no edit history and no multi-device sync — the link you have is the only copy, until you send a new one.
• The note works fully offline once the page has loaded, because there is no server round-trip in the writing or reading path to begin with.