fwd

Blog

Why the fwd web app can’t be used to get into your account

Short answer: knowing your email address isn’t enough. A browser joins your fwd account only when you let it in, from one of your devices or with your recovery key, and it holds the same end-to-end encryption as the apps. Every release of the web app is signed, and your browser refuses one that isn’t.

On November 16, 2026, fwd started working in any browser, at app.usefwd.io: on a work computer that blocks extensions, a friend’s laptop, or the browser on an iPhone. A web page asks for more trust than an app you installed, so this is what I built into it, and where its limits are.

The worryWhat fwd does
Someone signs in with your emailThey get nothing: a new browser needs one of your devices, or your recovery key, to join
A borrowed computer keeps your historyHistory and its keys stay in memory, never written to that computer
You forget to sign outChoose 15 minutes, 1 hour or 8 hours, and its access ends when the time is up
The page’s code is changedEvery release is signed; your browser runs only signed releases
A script sneaks onto the pageNo third-party scripts and no analytics; a strict content policy

Your email isn’t a key

When you open app.usefwd.io on a computer, the browser makes its own encryption keys and shows a code: a QR code, and the same code as 56 characters. On its own, that code lets nothing in. One of your devices has to approve it: scan it with fwd on your phone, or type it into fwd on another device. On a phone, it works the other way round: the phone’s browser scans an invite your other device shows, and you approve it there. Either way, you pick how long the browser may stay, the approving device shows that time and can change it, and then it signs the change to your account with its own key.

Every fwd device checks that signed list of devices for itself, so a device the server slipped in without that signature would be refused by your devices. fwd’s server can’t add one, and neither can someone who only knows your email address. The one other way in is your recovery key, the key you saved when you set fwd up, together with a sign-in code sent to your email.

You choose how long it stays

  • 15 minutes, 1 hour or 8 hours: a temporary browser. It can send and receive, and nothing else: it can’t add or remove devices, rename them, delete forwards or change your account. fwd’s server holds it to that. When its time is up, the server ends its access at once, and the next of your devices to sync removes it from your account.
  • Until removed: a browser like your other devices, until you remove it.
  • Ending it sooner: End now on that browser, or remove it from one of your other devices. A removed browser erases its keys and, if the page is open, says it was removed within a second or two.

Nothing useful stays on that computer

The web app keeps your history, the keys that open it, your devices’ names and the pictures you’ve opened in memory only, and fetches them again each time you open the page. What it does store in the browser is its own keys and sign-in, the checked list of your devices, its settings, any files waiting to be sent and a copy of the web app’s code, and none of that opens your history. Close the tab, or let the time run out, and there’s no history on that computer for anyone to read. Files save and links open only when you tap them.

The code is signed

This is the hard part with any encrypted web app: the page’s code comes from the server each time you visit, so a changed file could, in principle, read what you type. fwd’s answer is signing.

  • Every release is signed: it lists every file with its fingerprint, and that list is signed with a key kept on my own machines, never on the servers that host the page.
  • Your browser checks: once a browser has used the web app, it runs only releases whose signature and every file check out, and it never goes back to an older one. A file that doesn’t match is refused, and fwd keeps the release it already has.
  • You can see it: Settings › About shows “Verified release of” and its date, and says so if an update couldn’t be verified.

A strict page, with nothing else on it

app.usefwd.io runs only fwd’s own code. Its content policy blocks scripts from anywhere else, scripts written into the page, and other sites framing it. There are no analytics on it and no third-party scripts at all. A browser kept until removed also asks for your fingerprint, face or PIN, through a passkey, before it approves a device, removes one, makes a new recovery key or deletes your account, on a computer that has one of those.

What it can’t protect against

  • The first visit: the checking starts once your browser has used the web app, so the very first page is taken as the server sends it.
  • A browser that can’t run the checks: the checking lives in the page’s service worker, so a browser that doesn’t run service workers gets the page without it.
  • The checker itself: the browser itself replaces the service worker when the server sends a new one. Signing stops a changed file from slipping in; it isn’t a defence against the server deliberately replacing the checker.
  • A computer that isn’t yours: your employer’s software, or the browser’s other extensions, can see what the page shows. Use a short time there.

For the strongest protection, use the apps on your own devices: their code is installed once from the store or a signed download, not sent with each visit. The web app is for the times you can’t: a locked-down work computer, someone else’s laptop, or an iPhone while there’s no fwd app for it. The security page has the details, and the help page shows how to add a browser.

Related guides

Sources

Checked on November 16, 2026.

Get in early.

Your devices are about to start talking again. Join the waitlist for early access to the private beta.

No spam: just your invite and the occasional update.

Or follow along on r/usefwd ↗: progress updates, feature requests and a direct line to me.

← All posts