PRIVACY.TXT

The website loads a self-hosted Umami analytics script to understand aggregate traffic, page usage, and anonymous interaction events such as which stack options are selected in the builder, which commands are copied, and which outbound links are followed. These events do not include the names of projects you build, personal information, or persistent identifiers. The site also displays externally hosted content such as videos, social posts, images, and sponsor information. Requests to those external services are governed by their own privacy practices and may expose ordinary connection information such as an IP address, browser headers, and the requested resource.

Better-T-Stack does not provide user accounts on this website and does not sell personal information. Theme and interface preferences may be stored locally in the browser.

After a project is created successfully, the CLI sends one telemetry event containing selected stack options and basic environment fields: CLI version, Node.js version, platform, and package manager. This information is used to understand which integrations are used and to guide maintenance priorities.

The telemetry payload intentionally omits project names, paths, file contents, secrets, environment variables, nested provisioning options, IP addresses, and persistent user or project identifiers. Aggregate results are published on the analytics page.

When creating a project or adding to one fails, the CLI also sends one anonymous failure event to the same self-hosted Umami instance as the website: the command, how the CLI was driven, the stage that failed, the error class, the package manager and backend when known, and a one-line reason with names and paths replaced by placeholders. Umami derives coarse location from the request IP and a session hash that rotates monthly; the IP address itself is not stored. The event never includes project names, paths, or full error messages, and the same telemetry switch disables it.

Disable CLI telemetry for one command with --disable-analytics or set BTS_TELEMETRY_DISABLED=1. The cross-tool DO_NOT_TRACK=1 convention is honored as well. Either variable can be added to a shell profile when telemetry should remain disabled. Project generation continues to work when telemetry is off.

See the analytics and telemetry documentation for the exact payload, public aggregates, and source-code links.

The project does not currently publish a fixed retention period for CLI events or aggregate website statistics. Because a CLI event contains no persistent user identifier, the event record alone cannot be associated with a specific person. Infrastructure providers may retain operational logs under their own policies.

Questions about this notice can be sent to amanvarshney.work@gmail.com. This notice will be revised when collection or processing materially changes.