ClaudeGate — A microscope on AI CLI data-capture prompts

See which parts of your conversation get uploaded before you click feedback.

Problem

AI CLIs frequently pop a 'give us feedback' prompt, and it tends to appear right when the transcript is long and potentially sensitive. Clicking it authorizes capturing the whole conversation, but that is buried in the terms and never shown in the UI. Users authorize by simply not dismissing the dialog.

Solution

A local intercept/explainer: when you are about to click feedback, it highlights potentially captured sensitive fragments (paths, keys, internal code, customer names) and suggests alternatives like manual redaction or local tickets. It can be a browser extension or CLI plugin, and also audits what has already been submitted.

Users

Engineers using AI CLIs over client code, developers with compliance duties, and outsourcing teams.

MVP

Detect common AI CLI feedback buttons and dialogs; scan and highlight sensitive fragments before submission; generate a redacted summary before sending; export a local feedback log; a short privacy comparison sheet.

Revenue

Free personal tier plus per-seat team subscription with compliance audit logs, unified policies, and offboarding cleanup; paid integrations with existing DLP suites.

Why now

AI CLIs are adding feedback and telemetry en masse, yet users have near-zero awareness of when they authorize capture. Good timing to own the 'privacy prompt layer for AI tools' mindshare.