Privacy Policy

Last updated: 2026-07-31

What we collect

By default, Claudictive collects nothing. The app runs entirely on your machine. No telemetry, analytics, or crash reports are sent without explicit opt-in.

What stays on your machine

• Conversation transcripts (in %APPDATA%/Claudictive/transcripts/)
• Session metadata (game name, duration, message counts)
• Settings (hotkeys, preferences)
• Debug logs (rotating, capped at 1MB)

Changes Claudictive makes to your Claude Code setup

To connect the overlay to your existing Claude Code sessions, Claudictive writes into your own Claude Code home directory (~/.claude/). Specifically:

• Hook scripts, and hook registrations in settings.json, so tool-approval prompts can be answered from inside a game
• A status line entry, so the overlay can show what your session is doing
• A marked section in your global CLAUDE.md, so a new Claude Code session knows to pick up where your in-game session left off
• A handoff file describing your last in-game session, which is consumed and cleared when read

Claudictive also reads files from the project directory of the session you are working in, because that is what you are asking Claude about. None of this leaves your machine.

You can reverse all of it: open the desktop hub, go to Settings → Privacy & Data, and use Remove Claude Code integration. Do this before uninstalling, since uninstalling the app cannot clean up files outside it.

What goes to Anthropic (Claude API)

Your messages are sent to Anthropic via the Claude API using your own API key. Anthropic's privacy policy applies to that data. Claudictive does not see, intercept, or store your API key beyond passing it to the local Claude Code CLI process.

What goes to Riot Games (if applicable, future feature)

Game-state detection (e.g., reading in-game / queue / lobby state via Riot's API for League of Legends or Valorant) is a planned opt-in feature. If and when it ships, Claudictive will query the Riot API only for match state and only with your explicit permission. Data will not be stored, aggregated, or transmitted anywhere except your local machine.

Opt-in analytics (v0.2.0+)

Analytics are off by default. We ask you once during onboarding (a checkbox you can leave unchecked) and you can flip the toggle any time in Settings > Privacy & Data.

What we collect when you opt in:

• An anonymous install ID (random hex, never tied to your name, email, or API key)
• Event names from a fixed allowlist (e.g., message_sent, game_injected, onboarding_step_completed)
• Counts and durations (e.g., "session lasted 24 minutes", "message was in the medium length bucket")
• App version, OS, current game name

What we never collect (even with analytics on):

• Message content - what you type to Claude, what Claude responds
• API keys (Anthropic, OpenAI, etc.)
• File paths, project directory names, code content
• Your name, email, username, machine name
• Usernames from games or other apps

Where the data goes: our Cloudflare D1 database. Never sold, never shared with third parties. Used only to improve the product. You can request deletion of your install ID's data by emailing hello@claudictive.com.

Opt-in crash reports (v0.2.0+)

Also off by default. When the app crashes, we send a sanitized stack trace (file paths replaced with [path], UUIDs truncated, API keys redacted) so we can fix the underlying bug. The sanitization happens client-side before anything leaves your machine.

Bug reports

When you submit a bug report, you choose explicitly whether to attach logs or transcripts. Nothing is included without your check.

Every bug-report submission also includes a small derived summary of your local app state to help us triage faster: app version, OS version, last game played, last session duration in minutes, error and exception counts in the last hour, your analytics + crash-reporting opt-in flags, and a few internal counters (e.g. how many recent sessions did not use the overlay). These are all counts, durations, and categorical values - never message content, file paths, API keys, usernames, or game-specific identifiers. The values are derived from data already on your machine; nothing new is collected just to send.

Data deletion

All Claudictive data lives in %APPDATA%/Claudictive/ on your machine. Open the desktop hub and go to Settings → Privacy & Data, where there are two separate actions:

• Delete my local data - erases conversation transcripts, session history, coding stats, bug reports, queued telemetry and the diagnostic log. Your preferences on that page are deliberately kept, so that turning analytics off is not undone by deleting your data.
• Remove Claude Code integration - reverses the changes described above in your ~/.claude/ directory.

Both are irreversible and ask for confirmation first. You can also uninstall the app and remove the folder manually.

Contact

Questions: hello@claudictive.com