dbt Wizard CLI data use and telemetry
dbt Wizard CLI collects anonymous product telemetry to improve the AI agent experience, understand usage patterns, optimize performance, and attribute compute costs without capturing your code, queries, prompts, responses, or file contents.
Opt out of client telemetry
dbt Wizard CLI respects the following opt-out mechanisms, checked in order:
- Set
DO_NOT_TRACK=1. - Set
DBT_SEND_ANONYMOUS_USAGE_STATS=false. - Store telemetry consent in
~/.dbt/.user.yml.
Setting any of these disables telemetry from the dbt Wizard CLI client.
What dbt Wizard does not collect
dbt Wizard CLI does not collect:
- Prompt or response content.
- SQL queries, file paths, or dbt node names.
- MCP tool call arguments or outputs.
- Raw API keys or tokens. Identifiers are hashed before transmission.
- Error messages that contain user content. Errors are limited to class or code.
Events collected
Tool telemetry records the tool type, tool name, whether the call failed, and execution time. Tool arguments and outputs are not collected.
Data handling
- Telemetry is transmitted over HTTPS to dbt Labs ingestion infrastructure.
- Events are stored in an internal dbt Labs data warehouse.
- Telemetry is not shared with third parties.
- API keys and tokens are never transmitted in raw form.
- Local development users who opt out with the supported environment variables generate no dbt Wizard CLI client telemetry events.
Related docs
- Install dbt Wizard CLI
- Configure BYOK for dbt Wizard
- dbt Wizard in the dbt platform Data & privacy
- dbt AI FAQs
Was this page helpful?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
0