Your media activity stays local by default

Local first

What Opal stores

Settings, session state and watch history are stored on your computer. Watch history and session data use a local SQLite database you control. Removing the app's local data removes Opal's copy of that information.

When Opal connects to the network

Opal makes network requests when you ask it to check releases, use a connected server, search an enabled source, stream media, fetch metadata or subtitles, use Trakt sync, or access another explicitly enabled online feature. Those providers receive the network information needed to answer the request and apply their own privacy terms.

Plugins and sources

Opal ships with no content sources enabled. Plugins can run code and contact third-party services, so install only sources you trust and review their behavior independently. Opal does not turn a third-party plugin into a private or first-party service.

Browser and LAN features

Opal Connect communicates with the desktop app to deliver its browser actions. The LAN web interface and phone remote intentionally make Opal reachable to devices on your local network while enabled; use them only on networks you trust.

Website data

This static website has no Opal account flow. Interactive download widgets request public release information from GitHub, which means GitHub receives a request from your browser. Hosting infrastructure may retain ordinary access and security logs.

Verify the implementation

Opal is open source. You can inspect the application, website and issue history in the public repository. Privacy bugs should be reported through the repository's issue tracker without including personal media data.