Your data stays on your PC

What the app uses

OpenBlade reads the hardware and Windows information its controls need: the laptop model and firmware identity, the installed graphics card and other controller identities, device status, power and battery information, temperatures, fan speeds, display state, audio state, which of your apps are using the GPU, and configured input actions.

The service, tray app, and Session Agent exchange this information locally. Hardware state, profiles, diagnostics, and configured actions are not automatically sent to the project or a remote service.

Update checks

The tray app can request public OpenBlade release metadata from GitHub. Before the first automatic check, you choose Daily or Manual only. In Settings > Updates, choose Every startup, Daily, Weekly, Monthly, or Manual only. Automatic checks run at most once when the tray starts, if the selected interval is due. Failed checks have a retry delay and do not count as successful checks. There is no background polling. Choose Manual only to turn automatic checks off.

On the validated Blade 16 (2025 and 2026) models, the tray can also request published firmware updater versions from that model's official page on mysupport.razer.com. This separate check defaults to Manual only and uses the same interval choices. It covers BIOS, EC, and MCU on both models; the graphics card VBIOS, matched to the NVIDIA adapter actually installed; and, on the Razer Blade 16 (2026), Thunderbolt 5 and the touchpad. To match these components, OpenBlade reads the adapter identity, Windows USB4 root-router property, and touchpad HID descriptor locally. It compares versions only when it can identify both the installed component and the published updater. OpenBlade shows the published versions beside the installed values but does not decide whether an update applies, download an updater, or run one.

The GitHub update request includes no laptop model, firmware, profiles, settings, diagnostics, or hardware state. The Razer request uses a model-specific support URL, but includes no installed firmware values or other hardware state. GitHub and Razer receive the connection data ordinarily needed to answer each request, such as your IP address and request headers, and handle it under their own privacy policies. OpenBlade opens release and support pages in your browser; it does not download or run updates automatically.

What the app stores

OpenBlade stores machine-wide configuration and separate profiles for each Windows user under %ProgramData%\OpenBlade. It stores current-user preferences, bounded diagnostic logs, and crash reports under %LocalAppData%\OpenBlade. These files can contain app versions, device or feature status, error details, and other technical context. OpenBlade redacts known user and machine identifiers from its persistent user-mode logs, but you should still review diagnostic files before sharing them.

The uninstaller keeps profiles and settings for a future reinstall unless you choose to remove them.

Diagnostics and links

Exporting diagnostics saves an archive where you choose. OpenBlade does not upload it. Review diagnostics, profiles, and screenshots before sharing them; they may contain information about your PC.

Experimental-model reports include the source used for support, paused-control status, and up to 32 recent control results. Exports use cached data without contacting the laptop again. Serial numbers and raw HID reports are excluded, and identity redaction applies. See the experimental guide for test reports.

Links in OpenBlade and on this website can open third-party sites in your browser. Those sites handle visits under their own privacy policies.

This website

The OpenBlade website is a static documentation site. The site itself does not use accounts, advertising, analytics, tracking pixels, or cookies. The hosting provider may process standard connection data, such as an IP address and browser request, to deliver and protect the site.

Questions and security reports

For privacy questions, open an issue in the documentation repository. Do not put sensitive information in a public issue. For a security concern or data that should remain private, follow the project's security policy.