// OPENBOX DOCS

Privacy

What OpenBox does and does not collect, and how its data stays on your machine.

Privacy

OpenBox is designed so your library, saves, and metadata never leave your machine unless you explicitly trigger something. This page says exactly what that means and where the boundaries are.

What OpenBox does not do

  • No telemetry. No analytics beacons, no crash reports, no usage statistics are sent anywhere. There is nothing to opt out of.
  • No account. There is no OpenBox account, no login, no license key. Downloading the AppImage or cloning the repository is the entire installation.
  • No cloud library. Library data lives in library.json on your machine. The local server binds to 127.0.0.1 only and every API request must carry a per-launch token, so the window (or tab) you open is the only client.
  • No hidden network calls. The app does not phone home at startup. The only scheduled outbound feature is opt-in Deal Radar, which polls https://store.steampowered.com at the interval you set.

What leaves your machine, and when

Most outbound actions are user-initiated and visible in the UI. Deal Radar is the one opt-in scheduled exception:

  • LaunchBox metadata database. Downloading or updating the LaunchBox metadata database fetches the archive from gamesdb.launchbox-app.com and builds a local SQLite copy. OpenBox then matches titles locally against that database, so no game title or library entry is sent for an individual lookup. The download happens when you trigger it — for example after an import, or from the metadata screen.
  • IGDB search. A search you type is sent to IGDB. IGDB API failures surface readable errors.
  • ScreenScraper and SteamGridDB. Metadata and artwork lookups you trigger send the game title, platform, and identifiers to those services under your own account or API key.
  • Gameyfin. Connecting a Gameyfin server sends the configured URL and library requests to that server.
  • RetroAchievements. Your username and API key, plus ROM hashes for matching, go to RetroAchievements when you use that integration. The key is stored locally in a 0o600 file.
  • Steam achievements and playtime. If you configure a Steam Web API key and Steam ID, OpenBox reads achievement and playtime totals from api.steampowered.com. The request carries those identifiers, not your library files.
  • EmuMovies. Media downloads authenticate with your EmuMovies credentials.
  • Netplay lobby. Opening Online play fetches RetroArch's public HTTPS lobby listing. No credentials are sent, and RetroArch itself makes the room connection.
  • Webhooks. If you configure webhooks, event deliveries go to the URLs you specify, signed with your HMAC secret. Destinations are validated against loopback and local address rules before anything is sent.
  • Statistics sync. If you enable it, play statistics sync to a local folder you choose (for example a Syncthing folder). You control the destination.
  • Deal Radar. If you enable it (deals_enabled), OpenBox queries https://store.steampowered.com for the app ids on your watchlist at deals_poll_hours (default 168). Requests and redirects are restricted to that host. No Steam account, cookies, library, or play history are sent. Disable the feature to stop the poll; the Rust 3.0 server currently polls only on Refresh now because the scheduled hook is not wired.
  • Update checks. Settings > Check for updates queries the GitHub releases API. It is read-only.

What is stored locally

The data directory (~/.local/share/openbox-game-launcher on Linux, %LOCALAPPDATA%\openbox-game-launcher on Windows, ~/Library/Application Support/openbox-game-launcher on macOS, or OPENBOX_DATA_DIR) holds the library, settings, media, backups, save archives, themes, plugin installs, credentials, and the rotating diagnostic log. Credentials are stored owner-only (0o600). Optional tokens for IGDB, ScreenScraper, SteamGridDB, Gameyfin, and RetroAchievements are kept out of the public settings view and exposed to the browser only in masked form. The diagnostic log redacts tokens, passwords, and API keys, but it can contain game names and local file paths, so review it before sharing it.

See Interfaces and data for the full file layout and Configuration for environment variables and persisted settings.

The website

This documentation site is a static export served from GitHub Pages. It has no analytics scripts, no cookies, and no tracking. The hero links to Downloads, where the versioned install.sh script pins the release public key and verifies the AppImage's SHA-256 checksum and Ed25519 signature before installing; Installation covers every platform.

Reporting a concern

If you find behavior that sends data without a user action, or a credential that is stored too broadly, report it through the security policy rather than a public issue.