The Browser Version Versus the Installed App
Using a service in a browser rather than as an installed app trades one kind of exposure for another. The browser version cannot see your device the way an app can — no persistent background access, no device identifier, no ability to sit resident on your phone — but it operates inside a browser that keeps history, autofill, and cookies, and that history is visible to anyone with your unlocked device. Neither option is simply more private.
Which one is better depends on what you are protecting against, and the two threats are genuinely different.
What the installed app has that the browser does not
Installed software runs with capabilities a web page cannot request.
A stable install identifier, which lets an operator recognise the same installation across sign-outs and account changes. Web tracking can approximate this but it is more fragile and easier to disrupt.
Background execution and push delivery, so the app can contact you when you are not using it. A web page cannot, except through browser notifications you explicitly allowed, which are weaker and easier to revoke.
Deeper permission surface. Camera, microphone, photo library, contacts, local network — an app can request all of these persistently. A browser can request camera and microphone too, but the grant is typically per-site and often per-session, and it does not extend to your photo library or address book at all.
Presence on your device. The icon is on your home screen, the name is in your app list, and it appears in your app-store purchase history. That is a visibility cost, not a data cost, and for this category it can be the one that matters most.
What the browser has that the app does not
The browser accumulates its own record, in places people forget to check.
History and autofill. The URL is in your browsing history, and it will appear as an address-bar suggestion, sometimes prominently, sometimes on a new-tab page as a frequently-visited tile. Typing two letters into the address bar in front of someone else is a real disclosure route.
Cookies and site data, which persist until cleared and which keep you signed in — meaning an unlocked device gives an unlocked session.
Cross-site context. A browser session carries whatever your browser exposes generally: your IP address, your user-agent string, your fonts and screen dimensions, your language settings. This is more than an app reveals about your identity in some respects and less in others, and it is why approximate location does not require any permission at all, as covered in location without the location permission.
Extension access, on desktop. Browser extensions with permission to read page contents can read the page you are on. That is a substantial and frequently overlooked exposure with no equivalent on the app side.
Practical configurations
If you use the web version, a few settings do most of the work.
A private or incognito window solves history and persistent cookies at the cost of signing in each time. On mobile this is one tab away and is probably the right default for this category.
A separate browser profile is the better desktop answer: its own history, cookies, extensions, and autofill, kept out of your main profile entirely. Most desktop browsers support multiple profiles and almost nobody uses them for this.
Decline browser notification prompts. They are the web equivalent of push and they add nothing you need.
Check what is saved in autofill. A password saved in browser autofill for this site is discoverable by anyone with your device unlocked; a password manager with its own lock is better.
If you use the installed app, the equivalent moves are on the phone: narrow permissions, previews off as described in notification previews and your lock screen, and periodic checks of what the app has actually accessed.
Progressive web apps sit in between
An “add to home screen” installation of a web app produces an icon that looks like an app and is still a browser context. It typically gets its own storage bucket, may be excluded from your main browsing history, and can request notifications — but it does not get the deeper device permissions and does not appear in your app-store purchase history.
That combination is often the best of both for this category: the convenience and the reduced visibility, without a full install. It is also poorly signposted, so you may not know whether an app offers one until you look.
What neither version changes
Both send your messages to the same servers. The choice is about what your device and browser reveal and retain, not about what the operator receives — an important boundary, because it is easy to over-credit a browser session with privacy it does not provide.
Both are also equally subject to the operator’s storage and retention decisions, and to whatever the operator’s policy says about training use. If the concern is what happens to conversations after they arrive, the app-versus-browser question is the wrong lever entirely, and the relevant considerations are the ones in what is the best way to evaluate AI companion app data privacy concerns.
Where the browser genuinely wins is anything involving other people having access to your phone, because there is no icon and no resident session to find. Where the app wins is nothing about privacy at all — it wins on features that require device capabilities, which is a fair trade to make knowingly.