Files
johnmalek312 201cb25488 chore: move current docs into v4/ directory for versioned structure
Move all root-level doc pages (overview, quickstart, features, concepts,
guides, sdk) into docs/v4/ to match the versioning pattern used by
v1/v2/v3. Update docs.json navigation and all internal cross-references
to use /v4/ prefix. Fix broken anchor link in app-cards.mdx.
2026-02-09 16:44:45 +11:00

46 lines
1.5 KiB
Plaintext

---
title: 'Telemetry'
description: 'Configure anonymous telemetry'
---
# Why We Need Telemetry
Telemetry helps us:
- Identify which features are most used and need improvement
- Prioritize bug fixes and new features based on real usage
- Ensure Droidrun works well across different environments
<b>We do not collect any personal or sensitive data.</b> All telemetry is strictly anonymized and used only to improve the framework for everyone.
If you have questions or concerns, please reach out on [GitHub](https://github.com/droidrun/droidrun) or review our privacy policy.
---
# Toggling Telemetry
Droidrun collects <b>anonymized</b> usage data to help us understand which features are most valuable and where improvements are needed. This data is <b>never</b> used for advertising or tracking individuals, and is only used to make Droidrun better for the community.
## How to Disable Telemetry
You can disable telemetry at any time by setting the following environment variable:
```bash
export DROIDRUN_TELEMETRY_ENABLED=false
```
Add this line to your shell profile (e.g., `.bashrc`, `.zshrc`, or `.profile`) to make it persistent across sessions.
## How to Enable Telemetry Again
To re-enable telemetry, set the environment variable to `true`:
```bash
export DROIDRUN_TELEMETRY_ENABLED=true
```
<Note>
Telemetry is currently controlled only by the `DROIDRUN_TELEMETRY_ENABLED` environment variable. While a `telemetry.enabled` config option exists in the configuration schema, it is not currently used by the telemetry system.
</Note>
---