Telemetry

The varlock CLI collects anonymous telemetry data about usage to help us understand how the tool is being used and to make it better. Participation is optional, and you may opt-out at any time.

What We Collect

We track general usage information, and the environment in which varlock is being used. Specifically we collect anonymous information about:

• Which varlock command is being invoked
• Version and settings for varlock, Node.js, and any plugins
• General system/machine information
• Anonymous user + project ID

How to Opt Out

You can opt out of analytics in two ways:

Using the CLI

Run the following command to permanently opt out:

npm

npm exec -- varlock telemetry disable

yarn

yarn exec -- varlock telemetry disable

pnpm

pnpm exec -- varlock telemetry disable

standalone binary

varlock telemetry disable

This will create/update a configuration file saving your preference at ~/.varlock/config.json.

You may re-enable telemetry by running varlock telemetry enable

Using an Environment Variable

You can also opt out temporarily by setting the VARLOCK_TELEMETRY_DISABLED environment variable:

export VARLOCK_TELEMETRY_DISABLED=true

This will disable analytics for the current session only, which is useful in CI/CD pipelines, or while running a specific command.

Privacy

• All analytics data is completely anonymous
• No personal or sensitive information is collected
• Data is only used to improve the product
• You can opt out at any time
• Analytics are handled by PostHog, a privacy-friendly analytics platform

Data Usage

The anonymous usage data helps us:

• Understand which features are most used
• Identify areas for improvement
• Make informed decisions about future development
• Prioritize bug fixes and new features

If you have any questions about our analytics or privacy practices, please start a discussion on GitHub.