Skip to content

Privacy posture chip (RPC route and telemetry state) #152

Description

@truthixify

Tier: S (1-2 days) | Type: ux

Context. Users cannot tell at a glance whether the app is talking to the default public RPC, a self-hosted one, or a proxy, or whether opt-in telemetry is on. All three matter to privacy-conscious users and are currently only visible if you dig into Settings. Note this is distinct from the existing PrivacyBadge / PrivacyTooltip in src/components/, which score per-scan address-reuse via computePrivacyScore in src/lib/privacy-score.ts (a receive-flow signal). The new chip is a header-level infra posture, not a per-scan score, so we give it a distinct component name.

Scope.

  • Header chip PrivacyPostureChip labeled "Privacy: strict / relaxed" reflecting: no telemetry AND non-default RPC vs anything else.
  • Click opens a dropdown listing the actual RPC hosts per chain, telemetry state, and a "review" link to /privacy.
  • Zero network calls from the chip; reads local config only.
  • Design tokens follow the existing chip pattern in NetworkChip.tsx.

Acceptance.

  • Chip updates live when RPC or telemetry toggles change
  • Dropdown host list is copyable
  • Never leaks the RPC URL to any telemetry endpoint
  • Contrast passes AA in both themes
  • Named and placed to avoid confusion with the existing PrivacyBadge (per-scan score)

Files. src/components/PrivacyPostureChip.tsx (new), src/components/Header.tsx, src/lib/telemetry.ts, src/pages/Privacy.tsx.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave programdemoAuto-created for Wave 8dripsFunded via Drips Networkhelp wantedExtra attention is neededprivacyPrivacy-specific workstellar-waveAuto-created for Wave 8uxUser experiencewave-8Auto-created for Wave 8

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions