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.

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

We will never collect any of your config files or environment variables.

You can opt out of analytics in three ways:

Run the following command to permanently opt out:

npm exec -- varlock telemetry disable

yarn exec -- varlock telemetry disable

pnpm exec -- varlock telemetry disable

vlx -- varlock telemetry disable

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

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

export VARLOCK_TELEMETRY_DISABLED=true

This could be set in a specific terminal session, while running a specific command, in a Dockerfile, or in a CI/CD pipeline.

You can also opt out at the project level by creating a .varlock/config.json file in your project root with the following content:

{
  "telemetryDisabled": true
}

• 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

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.