> For the complete documentation index, see [llms.txt](https://docs.timeinpixels.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timeinpixels.com/nobe-omniscope/settings-and-preferences/usage-analytics.md).

# Usage analytics

Usage analytics are available in **OmniScope 1.11.54 and later**.

OmniScope includes optional usage analytics that help us understand how the application is used. Analytics are **off by default**. No analytics identifier is created and no analytics events are queued or sent unless you choose **Share usage data**.

## Why OmniScope Needs Analytics

OmniScope supports many scopes, source types, layouts, QC workflows, and hardware configurations. Feedback and support requests are valuable, but they do not show how the whole product is used. Aggregate usage patterns help us:

* Prioritize improvements to the features and workflows people use most.
* Understand which scopes, sources, and QC tools need continued attention.
* Make better decisions about where to spend development and testing time.
* See which application versions, operating systems, and GPU backends are active in the field.

Analytics describe **which features are used**, not the media or project you are working on.

## Choosing Whether to Share

When OmniScope asks for permission, select **Share usage data** to opt in. Select **Don't share** or close the dialog to leave analytics disabled.

<figure><img src="/files/pjGrXrlLLJOWI0pcoBlO" alt="OmniScope usage analytics consent dialog"><figcaption><p>Analytics are optional and remain off unless you choose to share usage data.</p></figcaption></figure>

You can change your choice at any time:

1. Open **Preferences**.
2. Select the **Settings** tab.
3. Open **Privacy & analytics**.
4. Turn **Share usage analytics** on or off.

Turning analytics off stops collection immediately and discards events that have not yet been sent.

## What Is Included

Only a fixed, predefined set of event types and properties can be shared:

| Category                | Included data                                                                                                                         |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Application lifecycle   | Installation or update events, session start, clean session end, and session duration                                                 |
| Feature usage           | Selected application actions and whether they were invoked by a button, dial, or dial press                                           |
| Scopes and sources      | Scope type created or changed, and input source type connected                                                                        |
| Layouts                 | Whether the applied layout is the default layout slot and how many scopes it contains                                                 |
| QC                      | QC check family, whether a run started or finished, and the aggregate number of issues found                                          |
| Application environment | Current and previous application version, operating system, GPU backend, build type, license tier, and whether the license is a trial |
| Delivery information    | Event timestamp, short queueing delay, and a count of events that could not be delivered                                              |
| Installation identifier | A randomly generated identifier used to group events from the same OmniScope installation                                             |

The installation identifier is persistent, so the data is **pseudonymous rather than anonymous**. It is not based on your hardware and is not linked to your license, account, name, or email address. Analytics events are processed on servers in the EU.

## What Is Not Included

Analytics never include:

* Video, images, audio, frames, or pixel values.
* File paths or media file names.
* Source names, layout names, or QC preset names.
* Network addresses, stream URLs, or device serial numbers.
* QC report contents, marker text, action parameters, or anything you type.
* Your name, email address, license key, account details, machine name, or hardware identifier.
* A stored IP address or a location derived from it. Your IP address is discarded during processing.

Analytics do not upload log files or replace crash reporting. Events are sent in small background batches and are not stored as an offline analytics history on your computer. Delivery is best-effort, so events can be lost if OmniScope is offline, crashes, or is forced to quit before a batch is sent.

## Installation Identifier and Support

When analytics are enabled, the random installation identifier appears under **Preferences > Settings > Privacy & analytics**. Use **Copy** to place it on the clipboard. The same identifier is also written to the local OmniScope log. Support can associate a report with its analytics only if you deliberately provide that identifier or send the log containing it.

Select **Reset installation identifier** to start a new identifier. This prevents future events from being associated with the previous identifier, but it does not delete analytics that were already sent.