Why promise no opt-out telemetry while telemetry has been on the whole time? Without even a button to turn it off.

I’m frustrated that telemetry appears to have been added and enabled by default without clearly notifying existing users.
T3 Code’s website previously made an explicit promise:

No telemetry
Unless you opt in. Full stop.

That statement appeared on the homepage on May 14th (https://web.archive.org/web/20260514051916/https://t3.codes/) and was later silently removed (https://github.com/pingdotgg/t3code/commit/3bdaa6e10046945ccc08264d2d6f3b81775efcb3). Meanwhile, the telemetry configuration currently defaults to enabled (and has since March 5th) (https://github.com/pingdotgg/t3code/blob/main/apps/server/src/telemetry/AnalyticsService.ts).

Users who installed T3 Code based on an explicit “unless you opt in” promise had a reasonable expectation that no analytics without their knowledge and consent would be sent out. Removing that wording from the website is not a proper notification to existing users.

Expected behavior

Before enabling telemetry or materially changing data-collection behavior, the project should:

• Notify existing users prominently through the application or update process.
• Explain exactly what is collected, when it is collected, and where it is sent.
• Request explicit consent before enabling it.
• Preserve the existing privacy behavior until the user makes a choice.
• Provide an obvious in-app control for disabling it completely.
• Document the opt-out for CLI and headless installations.

Requested resolution

• Disable telemetry by default for users who have not explicitly opted in.
• Add an in-app notice and consent prompt.
• Add a clearly visible telemetry setting.
• Publish the complete telemetry event and property schema.
• Explain when telemetry was introduced, which releases contained it, and whether users were notified.
• Establish a policy requiring prominent advance notice for future privacy or data-collection changes.

Even if the collected information is considered “anonymous,” silently enabling it after publicly promising opt-in telemetry is unacceptable.

Start with apps/server/src/telemetry/AnalyticsService.ts and review commit 3bdaa6e10046945ccc08264d2d6f3b81775efcb3, then trace how telemetry is enabled for application, CLI, and headless users. Done means the requested consent, default-disabled behavior, visible control, event schema, rollout history, and policy documentation are addressed.