Nextellar telemetry is anonymous, minimal, and opt-in.
- Telemetry is disabled by default until explicitly enabled.
- On first run, Nextellar shows a transparency notice:
Nextellar collects anonymous usage data to improve the tool.You can disable this with --no-telemetry or NEXTELLAR_TELEMETRY_DISABLED=1Learn more: https://nextellar.dev/telemetry
- Users can manage preferences with:
nextellar telemetry statusnextellar telemetry enablenextellar telemetry disable
Preferences are stored in ~/.nextellar/config.json.
- Per invocation:
--no-telemetry - Environment override:
NEXTELLAR_TELEMETRY_DISABLED=1 - Persistent opt-out:
nextellar telemetry disable
Only this payload is sent for scaffold events:
{
"event": "scaffold",
"anonymousId": "random-uuid",
"properties": {
"template": "default",
"language": "typescript",
"network": "testnet",
"wallets": ["freighter", "albedo"],
"packageManager": "npm",
"withContracts": false,
"skipInstall": false,
"success": true,
"cliVersion": "1.0.4",
"nodeVersion": "20.10.0",
"os": "darwin"
}
}Not collected:
- project name
- file paths
- environment variables
- API keys
- user identity
- Telemetry is non-blocking and fire-and-forget.
- Request timeout is 3 seconds.
- Failures are silent and never block scaffolding.
- Offline execution is supported (no errors surfaced to users).