The tools include
ffx (and all its subtools),
device_launcher, Fuchsia Snapshot Viewer,
Scrutiny verify routes, and the Fuchsia extension for VS Code. If you disable
analytics, an opt-out event is sent and after that no further analytics will be
sent by the tools to Google until analytics is enabled again. Otherwise, if
analytics is enabled, invocations and usage of these tools will result in data
collection including the following:
- CPU architecture (e.g.
arm64, etc.), kernel name (e.g. Linux, Darwin, etc...) of the system.
- The version of the tool and related Fuchsia environments (e.g. the Fuchsia SDK version).
- Usage of and interactions with features and whether certain features are enabled.
- Whether a tool is invoked in a bot environment (e.g. a CI environment) and whether a tool is invoked by other Fuchsia related tools.
- The event of analytics being enabled or disabled.
- Success, failure, exceptions, errors, and timing of a task performed by a tool.
- Crashes of a tool.
- Operational metrics (e.g. symbolizer will report the number of modules with local symbols for each symbolized stack trace).
- A random unique ID (RFC 4122 version-4 UUID), generated for the current user when the user opts in to analytics.
When collecting data, Fuchsia plans to remove open text (e.g. argument value of
ffx flags) and other types of potentially identifying information (e.g. a full