Add VoiceBan to your Home Screen and it runs like a real app — in its own window, with its own storage. That means it keeps you signed in instead of logging you out, and it's the only way to turn on notifications on a phone. We recommend everyone do this.
A normal browser tab can clear its storage on its own — iOS Safari, for example, wipes a website's data after a few days of not opening it. VoiceBan holds your keys in that storage, so when it's cleared, you're logged out and have to restore from your recovery phrase. Installed to the Home Screen, VoiceBan gets its own private, persistent storage that isn't cleared like a browser tab — so you stay signed in.
It also launches full-screen with no address bar, feels instant, and is the only way to receive notifications on a phone (see below). Your keys never leave your device either way — installing just makes the experience solid.
This is the question we get most, so here is the answer plainly: a native app would put a kill switch on VoiceBan, and hand it to two companies. Every app in the App Store or Play Store exists at the pleasure of Apple and Google. They approve it, they review every update, and they can remove it — for policy reasons, for political pressure, or for no stated reason at all. It has happened to social platforms before: apps with millions of users, deleted from both stores in a single weekend.
VoiceBan exists for exactly one reason: no company, court order, or government letter should be able to switch it off. There is no company that owns it, no single server that hosts it, no domain it depends on. Shipping that platform through an app store would rebuild — voluntarily — the one chokepoint the entire architecture was designed to eliminate. A "censorship-resistant network" that can be erased from your phone by a store review team is not censorship-resistant. It's a contradiction.
A store listing also requires a registered legal entity, a named developer account, and update-by-permission — three pressure points on the people who build it. We refuse all three.
So instead, VoiceBan is built as a web app you install straight from the network — the instructions below take 15 seconds. Installed, it has its own icon, its own window, its own storage, and notifications, exactly like a store app. The difference is what's missing: nobody sits between VoiceBan and your Home Screen. Nothing to delist, nothing to revoke, no update that needs anyone's approval.
You must use Safari (Chrome on iPhone can't add web apps).
Once VoiceBan is installed to your Home Screen, it can send you notifications — new messages, replies and mentions — if you allow it. On iPhone this only works from the installed app, never a browser tab (an Apple restriction), which is another reason to install.
Open the installed VoiceBan, go to Settings → Notifications, and allow them when your phone asks. You're always in control — you can turn them off any time in Settings, or in your phone's system settings for VoiceBan.
Is this an App Store app? No — it's a web app you save to your Home Screen. Nothing to download, nothing that can be pulled from a store. That's part of what makes VoiceBan hard to take down — the full reasoning is here.
Will it update? Yes, automatically — it always loads the latest VoiceBan. There's nothing to manually update.
Is my account tied to this phone? Your account is your keys, not the app. Installing just keeps those keys safely stored on this device so you stay signed in. Keep your recovery phrase safe — it's the only way to restore your account on a new device.
Do I still need the browser version? No. After installing, always open VoiceBan from your Home Screen so you stay logged in and can get notifications.