Skip to content

README says "No Telemetry" but analytics are enabled by default without consent #481

Open

Description

@EmanueleCell4

Hi, thanks for opcode.

The README's security section says "Local Storage: All data stays on your machine" and "No Telemetry: No data collection or tracking" (README.md:383-384). At commit d1ca30a the app ships PostHog analytics that are on by default:

  • posthog-js is initialised with a project key and https://us.i.posthog.com (src/lib/analytics/index.ts:30-31), before the first render (src/main.tsx).
  • When nothing is stored yet, the consent defaults are enabled: true, hasConsented: true (src/lib/analytics/consent.ts:25-29), so events are sent without the user opting in.
  • The consent dialog components exist but are not rendered anywhere; the only way to stop it is a toggle in Settings.

Either the README or the default should change. Suggested fix: default to enabled: false, hasConsented: false, show the existing consent dialog on first launch, and update the README to describe what is collected.

Found while testing Elliot, a tool I'm building that checks docs against code.

Activity

  1. chirag127 commented on Nov 22, 2026

    @chirag127

    Additional source-level findings at c24004d, to complement this report and the existing opt-in PR #482 (not a duplicate issue):

    • src/main.tsx also mounts PostHogProvider with an API key from Vite environment variables and capture_exceptions enabled. If those variables are configured, that independent initialization must be removed or consent-gated as well; changing ConsentManager defaults alone does not cover it.
    • AnalyticsService.setScreen() calls posthog.capture without checking consent. Gate this path consistently with track() and identify().
    • Moving resource monitoring behind a startup-only consent check leaves first-run opt-in without monitoring until restart. Monitoring should follow enable/disable transitions; deleteAllData() should stop monitoring and opt the SDK out before resetting it.
    • If persisted consent is malformed, clear the in-memory settings as well as returning disabled defaults. Require actual boolean true for both enabled and hasConsented, rather than truthy values.

    A local regression suite covering the entrypoint with a mocked PostHog SDK, disabled/invalid storage, opt-in/out and data deletion passes 15 tests (66 assertions) after applying these guards. The suite initially exposed four failures in malformed-consent and lifecycle handling. This is source and mocked-SDK evidence, not live desktop network validation; native desktop verification remains incomplete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions