ES
GitHub
Documentation

DOC / 27 / OPERATE

Voluntary telemetry

Control a disabled-by-default, local-only usage journal with an exact field allowlist and user-owned deletion.

In this guideVoluntary telemetry
Getting startedProject structureCLI referenceDeveloper loopIncremental buildsRouting and pagesRust viewsEvents and foldsSchemas and snapshotsHyphae verified syncTyped contentBrowser runtimeDOM ownershipNative runtime previewPortable deploymentFull-stack betaOpenSDK previewComponents and languagesBrowser framework conformanceTooling protocolCompatibility and deprecationAdaptive assetsArtifact trustRelease trustPerformance evidenceErrors and diagnosticsVoluntary telemetryBuild and deployCrates and APILicensing and policy

Disabled means absent

PliegoRS telemetry is disabled by default. Installation, scaffolding, checking, development, and building do not create telemetry state or make telemetry network requests. No environment variable, manifest, installer flag, or account can silently enable it.

shell
pliego telemetry status
pliego telemetry enable

Exact bounded allowlist

An enabled journal retains at most 64 events. Every event contains only a local sequence, one of install/new/check/dev/build, coarse Unix day, CLI version, operating-system platform, and CPU architecture.

Preview and export locally

shell
pliego telemetry preview
pliego telemetry preview --format json
pliego telemetry export --output ./pliegors-telemetry.json

Preview shows the exact report shape. Export creates a new local file and refuses to overwrite an existing path. Neither command uploads data.

Stop and delete under user control

shell
pliego telemetry disable
pliego telemetry disable --delete-local

Disabling stops collection; --delete-local also removes the bounded local state. Re-enabling requires another deliberate command. Corrupt or unsupported state fails closed and cannot enable collection.

Complete telemetry contract