Product data information updated
A product data guide for the Windows Overwolf build
Use this guide to understand the data choices in the current Windows Overwolf product. The website privacy notice separately covers browsing this site. Website widget examples use illustrative data; your real PC controls run in the Windows app.
Usage collection depends on the production build's Mixpanel configuration and the Usage analytics setting. Technical error reporting depends on its Sentry configuration. The sections below explain what each path does and where to manage your choices.
Keep your workspace and files locally
Your saved settings bring the workspace back across launches, and local captures can continue into your preferred editing or sharing tools. Keep a backup of the information and footage you value.
Choose the phone's useful sections
Pair on a trusted reachable LAN, then select the companion modules on the PC. Share the readings and controls that help your routine and unpair when you want to revoke phone access.
Manage usage collection in Settings
Find Usage analytics in General > Privacy and choose whether to contribute selected feature-usage events. Technical error reporting follows the separate path explained below.
A saved workspace and local files you can use
| Data | Local workflow | Useful action |
|---|---|---|
| Settings, profiles, notes and tasks | Saved locally by the app so your workspace can return across launches. | Keep a separate copy of information you need before clearing app data or reinstalling. |
| Screenshots and video captures | Saved files in the capture workflow's local image/video destinations. | Open and verify the actual saved file; use your own backup or sharing workflow. |
| Incident reports | Local report files can contain recent readings, your note and available process information. | Review the report and its contents before sending it to support or another service. |
| Phone pairing | A saved local credential supports paired access across app restarts. | Use explicit unpairing when you want to revoke that access. |
Local capture files let you watch a saved play, open it in a separate editor or choose where to share it. Incident files keep available performance context for closer review. When sharing either file, check its contents: clips can contain voices or account names, and reports can contain your note, readings and selected process information.
Clearing settings, deleting a saved file and revoking a companion credential are different actions. Back up files you care about and use the control for the data you actually want to remove. A local cleanup does not automatically erase events already held by a reporting provider.
Choose the information your paired phone can receive
The browser companion uses selected modules on a reachable local network. Its snapshot can include available performance values, volume, timer and stopwatch readings, capture state, brightness controls, network information, selected media titles and a bounded process list. Module switches determine which sections are shared.
The companion snapshot does not send the whole saved state. Notes, task contents and recording paths are not included. Media titles and process names can still be revealing, so review those modules deliberately. Read the companion feature for the controls available on that surface.
Usage events help improve the product, with a setting you can change
When configured in a production Overwolf build and enabled, SysCubes uses Mixpanel for selected feature-usage events. Usage analytics is on by default. A random analytics identifier is saved locally across launches to connect those usage events.
| Included context | Excluded from custom usage events |
|---|---|
| Fixed feature/action names, success or failure, app release and occurrence time. | Note/task text, report contents, file paths and raw error messages. |
| Numeric game/profile IDs, UI language, supported Windows/Overwolf version values and capability availability. | Media metadata, process details and actual hardware/performance readings. |
| Selected durations and layout counts; Mixpanel IP-based approximate location enrichment is enabled. | User-entered names, exact control levels and custom raw IP or coordinate properties. |
| Once, on the first launch of a new install: the download link's campaign labels (for example google and cpc), the install channel and whether an Overwolf account is signed in. | Overwolf account names, account and machine IDs, and ad click identifiers. |
Automatic UI capture, automatic pageview tracking and session replay are disabled. Alongside the selected event data, Mixpanel can receive standard connection and device information; IP-based approximate location enrichment is enabled.
Open Settings > General > Privacy > Usage analytics to turn usage collection off. This drops pending usage events and clears the initialized Mixpanel identity. Turning it on again starts a fresh identity. For a question about earlier provider-held data, use the product contact below.
Technical error reporting follows a separate path
Configured production Overwolf builds use Sentry to report technical errors. SysCubes removes attached user and request fields and disables the trail of preceding actions. Exception details, stack information, the app release and the affected app window can still be part of an error report.
Crash reporting is separate from the Usage analytics switch. For a question about the reporting configuration in your build or earlier provider-held data, include your build version when contacting support.
Manage the data choice that matters to you
| Your choice | What to use | What it affects |
|---|---|---|
| Stop future usage analytics | Usage analytics in Settings > General > Privacy. | Mixpanel usage collection; separate from crash reporting and phone access. |
| Share less with the phone | Phone Companion module switches. | The selected snapshot sections and allowed controls. |
| Revoke paired phone access | The explicit PC stop-and-unpair action. | The saved shared companion credential, including access by other paired phones. |
| Choose capture audio | The capture workflow's System audio and Microphone switches. | Audio requested for future capture; verify a saved test clip. |
| Review a diagnostic report | Open the saved report before sharing it. | Your decision to share its readings, note and available process information. |
| Remove or share a local file | Open the actual destination and use your chosen file workflow. | That local file; separate from provider events or paired credentials. |
Before a gaming session, choose Record or Replay, check System audio and the optional Microphone input, and play a short saved sample. Use capture documentation for the recording path and incident reporting for saved performance context. Keep the files you want and choose their next destination yourself.
Provider information and product data questions
Overwolf supplies the runtime and platform integrations. Mixpanel and Sentry provide separate reporting services when configured for a build. Their policies explain their own services. For SysCubes-specific retention or deletion questions, contact the product support address with the relevant build and data flow.
Overwolf platform privacy information · Mixpanel privacy information · Sentry privacy information
For a product data question, contact syscubes@gmail.com. Include your build version, the relevant feature or data flow and what you want to understand. Review any attachment before sending it.
Common product data questions
Which SysCubes data stays local, and which can be shared?
Settings, notes, capture files and incident files have local storage workflows. The enabled phone companion shares selected data on your LAN. Configured production builds can also send usage events to Mixpanel and technical error reports to Sentry. Review each control for the data flow you want to manage.
How do I turn off usage analytics?
Open Settings > General > Privacy and turn Usage analytics off. This stops Mixpanel usage collection, drops pending usage events and clears its stored identity when initialized. A later opt-in starts a fresh identity. Crash reporting and phone pairing have separate controls and configuration.
Does the Usage analytics switch disable crash reporting?
No. Crash reporting is a separate Sentry integration when configured in a production Overwolf build. Error reports can include technical exception details, stack information and the app release. SysCubes removes attached user and request fields and disables the trail of preceding actions. General settings distinguishes crash reporting from usage analytics.
Does the phone receive my notes or recording folder paths?
The companion snapshot uses a selected-data allowlist rather than sending the whole app state. Notes, task contents and file paths are not included in that snapshot. Enabled modules can share other information, such as media titles, process names, PC readings and control status. Review the switches before sharing access.
Does closing SysCubes forget a paired phone?
Closing the app stops its live connection while preserving the pairing credential. Use Stop companion and unpair on the PC to revoke the shared credential for all paired phones. To add another phone while keeping existing access, use the fresh pairing code displayed after a successful pairing.
Does deleting a local clip erase previously sent analytics?
Local files, companion credentials and provider-held events are different data stores. Deleting a clip removes the selected local file; it does not itself request deletion from a reporting provider. Ask the public support contact about a specific data request. Provider retention and deletion depend on the relevant account configuration and policies.