A private video player with no account: why local-first matters

Most streaming apps want an email address before you press play, and many quietly log everything you watch. A private video player with no account works differently: your library, history and settings stay on your own device, and nobody builds a profile of your viewing. This article explains what "local-first" really means, what a player can and can't keep private, how to read an extension's permissions honestly, and how to check any streaming tool before you trust it.

What your viewing history reveals

Viewing data is more personal than it looks. What you watch, when, and for how long can hint at your language, your schedule, your health worries, your politics and who you live with. When a service stores that data on its servers, it can be:

• Used for ad targeting or sold on in aggregate.
• Exposed in a data breach.
• Requested by others, subject to the law where the company operates.
• Kept long after you stop using the service.

None of that is a reason to panic. It's a reason to prefer tools that don't collect what they don't need.

What "local-first" means for a private video player

A local-first app keeps your data on your device by default and works without a server account. For a video player, that means:

• No sign-up. No email, no password, nothing to leak.
• Your library stays on your device. My List, continue watching, history and settings are saved in your browser's own storage, not uploaded.
• No analytics or telemetry. The app doesn't report what you click or watch.
• You control deletion. Remove items, reset, or uninstall, and the data is gone, because there's no copy elsewhere.

The trade-off is honest: without an account there's no automatic cloud sync between devices. A good local-first player gives you an export and import option instead, so you can move your library yourself.

Better Stream: a private video player with no account

Better Stream is built to be a private video player with no account:

• No account, no telemetry, no content servers. We don't run servers that log what you watch.
• Everything is stored locally using Chrome's extension storage: settings, installed plugins and playlists, My List, continue watching, history and Live TV favorites.
• Backups are yours. Export and import your data whenever you want; nothing is sent to us.
• Manifest V3. Under Chrome's Manifest V3 rules, an extension can only run code included in its reviewed package, not code loaded from a remote server later.

The full details, including what is and isn't collected, are in our privacy policy.

The honest part: what still leaves your device

"Local-first" doesn't mean "no network." A player has to fetch things to play them. When you use Better Stream, your browser connects directly to:

• The sources you add: plugin servers, playlist hosts and stream servers.
• Metadata providers, such as TMDB, for posters, descriptions and artwork.
• Subtitle sources, when you search for subtitles.
• A proxy, only if you choose to configure one.

Like any web request, those services can see your IP address and what was requested, and their own privacy policies apply. Better Stream doesn't sit in the middle and doesn't receive copies. So the privacy of your setup also depends on which plugins and playlists you choose. Our guide to using Stremio addons in the browser safely covers how to vet them.

Data	Where it lives with Better Stream	Who can see it
Account details	None exist	Nobody
My List, history, continue watching	Your browser's extension storage	You
Settings and subtitle preferences	Your browser's extension storage	You
Installed plugins and playlists	Your browser's extension storage	You
Requests for streams and catalogs	Sent directly from your browser	The source you added
Requests for artwork and metadata	Sent directly from your browser	The metadata provider
Usage analytics	Not collected	Nobody

Why the extension asks for access to all websites

This is the question we hear most, and it deserves a straight answer. When you install Better Stream, Chrome warns that it can read and change data on websites you visit. That warning appears because of the host access permission (<all_urls>).

Why it's needed: streams, playlists, manifests and subtitles can live on any server, and you choose which ones. The extension has to be able to fetch from those hosts and, for some sources, set request headers (like a referrer) the source requires before it will serve video. Without broad host access, every new source would break.

What it's used for, and not used for: it's used to fetch the content you request. It isn't used to read your browsing, look at the pages you visit, or collect data.

Here are the other permissions in plain English:

1. storage: saves your library and settings on your device.
2. tabs: opens and manages Better Stream's own player tab.
3. declarativeNetRequest: applies request rules needed for playback (and the optional proxy, if you set one). These are declarative rules, so they don't route your browsing through us.
4. scripting and webNavigation (optional): requested only when you turn on a feature that needs them.

If you'd like to see what Chrome lets you control, Google's guide to managing extensions explains how to change an extension's site access or remove it.

How to check any streaming extension's privacy

Use this checklist on any player, including ours:

1. Read the permissions on the Chrome Web Store listing and in chrome://extensions under Details. Ask whether each one matches what the extension does.
2. Read the privacy section of the store listing, where developers disclose what data they collect and how it's used.
3. Read the privacy policy. Look for plain statements about what's collected, not vague "we may share with partners."
4. Check for an account requirement. If a player needs your email to play a local file, ask why.
5. Look for export and delete options. You should be able to take your data and erase it.
6. Be wary of anything that bundles content. Players that promise free premium movies are often the ones with the worst privacy, and the content is usually unlicensed.

Using a private player on more than one device

The obvious question with no account: how do you move between your laptop and your desktop? With a local-first player, you do it deliberately rather than automatically:

1. Export a backup from Better Stream's settings on the first device.
2. Move the file however you like: a USB stick, your own cloud drive, or an encrypted note.
3. Import it on the second device.

Your library, My List, plugins and settings come across, and no company in the middle ever holds a copy. It takes a few more clicks than automatic sync, and that's the point: you decide when and where your viewing history travels.

A tip: if you share a computer, use separate Chrome profiles. Each profile has its own extensions and extension storage, so each person's history and lists stay separate.

Privacy and legality go together

A private player is about protecting your data, not about hiding what you do. Privacy doesn't make unlicensed content legal, and Better Stream ships no content of its own. Use it with sources you're entitled to: your own media, playlists from your provider, public-domain archives and legitimate plugins. Our FAQ explains how sources work.

Key takeaways

• Viewing history is personal data; the safest data is data that's never collected.
• A local-first, private video player with no account keeps your library and history on your device.
• Local-first still means network requests to the sources you choose. Pick them carefully.
• Broad site access is needed to fetch streams from any host you add; it should never be used to read your browsing.
• Check permissions, privacy disclosures and export options before trusting any streaming tool.

Want a player that respects your privacy and still feels like a proper streaming app, with a full-featured player, Live TV with a program guide and continue watching? Add Better Stream in about a minute, as shown in how it works. Questions about how your data is handled? Contact us and we'll answer them directly.