Telemetry Policy#

Note: Telemetry is not active yet. It will be enabled soon, and consent will be requested during installation.

Telemetry in Juice is designed to be transparent, limited in scope, and fully under user control. It is implemented using the open-source project Zest.

Juice includes optional telemetry functionality that is disabled by default and requires explicit opt-in. When enabled, telemetry collects only minimal, high-level technical information to help improve stability and usability. It does not collect personal data, experimental results, measurement data or hardware-related information and it will always remain possible to opt out at any time.

Telemetry does not affect any functionality, does not restrict features and can be fully disabled without impact. Juice remains fully usable with telemetry disabled. This will always be the case.

Note: Juice does not require consent to data collection for normal use, and data collection is not a prerequisite for its core functionality.

Frequently Asked Questions#

Why does Juice include optional telemetry?

Telemetry provides usage signals that support the ongoing maintenance and improvement of Juice. The data may be used to:

  • Assess feature adoption at a high level

  • Identify opportunities to improve usability and stability

  • Support informed decisions about future development priorities

Will the results be shared with the community?

Yes. Aggregated results and high-level insights will be shared periodically via the community platform.

What metadata is collected when telemetry is enabled?

When telemetry is enabled, Juice collects limited, high-level technical information, including:

  • Package name and version

  • The version of the OS and python runtime version

  • High-level usage events (for example, invocation of major features or commands)

  • An anonymous installation identifier used to distinguish unique installations

The installation identifier is generated locally and is not associated with individuals or organizations. The following data is not collected:

  • Personal identifiers

  • User names

  • Environment variables

  • File contents

  • Experiment or measurement data

  • Hardware identifiers or hardware-level data

Telemetry behavior is fully controlled through configuration and can be reviewed, enabled, or disabled by users or system administrators at any time. For more information, please have a look at here.

Is any personal or sensitive data collected?

No. Telemetry in Juice is intentionally scoped to avoid collecting:

  • Personal data

  • Experiment data

  • Measurement results

  • Hardware-specific information

  • Environment or system configuration details

Telemetry data is not intended to identify any individual users or organizations.

Can telemetry be disabled?

Yes. Telemetry is:

  • Disabled by default

  • Explicitly opt-in

  • Fully disable-able

Users who choose not to enable telemetry retain access to all core functionality without restriction.

Does telemetry affect Juice functionality?

No. Telemetry does not:

  • Enable or disable features

  • Restrict functionality

  • Impact performance-critical code paths

Juice behaves the same whether telemetry is enabled or disabled.

How is telemetry implemented?

Telemetry is implemented using the open-source project Zest. This design choice ensures that all telemetry logic is explicit, transparent, and easy to review. For more details, see the Zest documentation.

``