Privacy Policy

Last updated: 2026-09-18

What we collect

By default, Claudictive sends us nothing. No telemetry, analytics, or crash reports are sent without explicit opt-in, and nothing reaches us unless you choose to send it (for example, a bug report).

Two things do leave your machine by default, and neither comes to us: your messages go to Anthropic through your own Claude Code (see What goes to Anthropic), and ads are loaded from Overwolf (see Ads and the Overwolf platform).

What stays on your machine

Claudictive keeps these files in %APPDATA%/Claudictive/:

• Conversation transcripts (in %APPDATA%/Claudictive/transcripts/)
• Session records: game name, duration, message counts, the project folder path, and the ID of the Claude Code session the overlay was connected to
• Settings (hotkeys, preferences, and the install ID described under Opt-in analytics)
• Coding stats shown in the hub
• Copies of bug reports you submitted, and feedback you wrote in the hub (feedback is only sent if you choose to email it)
• Analytics events and crash reports that are queued but not yet sent (for example, while you are offline or after you turn reporting off; they are sent the next time you turn it on)
• A first-launch marker, so the app knows it has run before
• A debug log (capped at 5MB; the oldest part is dropped when it fills up). Your Windows user folder is written as ~ in it, but it can contain project folder names, file paths inside your user folder, and error output from Claude Code

Changes Claudictive makes to your Claude Code setup

Claudictive asks before writing anything to your Claude Code home directory (~/.claude/). The consent screen is step 3 of onboarding, and you can answer or change it later in Settings → Claude Code integration. It lists exactly what Claudictive wants to add. Nothing is written until you choose Allow.

If you allow it, Claudictive writes:

• Hook scripts, and the small status files they exchange with Claudictive, in ~/.claude/hooks/, so tool-approval prompts can be answered from inside a game
• Hook registrations and a status line in ~/.claude/settings.json, so the overlay can show what your session is doing
• Its own instructions file, ~/.claude/CLAUDICTIVE.md
• One import line, @CLAUDICTIVE.md, added to ~/.claude/CLAUDE.md - nothing else in that file is touched
• A handoff file, ~/.claude/overlay-session.md, describing your last in-game session. A hook passes it to the next Claude Code session you start in a terminal, so that session knows what you discussed in game, and then clears it. This means your in-game conversation becomes part of that terminal session's context and is sent to Anthropic by your own Claude Code (see What goes to Anthropic).
• When the overlay takes over a session in a project, the same status line is also added to that project's own .claude/settings.json

If you choose not to allow it, none of the above is written. Overlay chat still works either way - only handing a session back to your terminal, and answering terminal permission prompts from the overlay, depend on saying yes.

If you installed an earlier version of Claudictive, it may already have written some of this without asking. That old content is moved into ~/.claude/CLAUDICTIVE.md the next time you open the app, and you are asked once to confirm you want to keep it.

You can reverse most 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. This does not remove a status line added to an individual project's .claude/settings.json - delete that yourself if you want it gone.

What Claudictive reads on your machine

To find your Claude Code sessions and show them in the overlay, Claudictive reads:

• Your Claude Code conversation transcripts in ~/.claude/projects/, so it can list your sessions and show their messages in the overlay
• The lists of slash commands and skills in your ~/.claude/ folder, so it can offer them in the overlay
• The working folder of each running claude process, so it can tell which projects have a live session
• Files in the project folder of the session you are working in, and a file you pick yourself, because that is what you are asking Claude about

Claudictive does not send any of this to us. The only part that leaves your machine is what goes to Anthropic as part of your conversation: your messages, and any file content Claude reads while answering you.

What goes to Anthropic (Claude API)

Your messages are sent to Anthropic by your own local Claude Code, using whatever login it already has (a Claude subscription sign-in or an API key). That includes any project file content Claude reads while answering, and, if you allowed the Claude Code integration, the in-game conversation handed to your next terminal session. Anthropic's privacy policy applies to that data.

Claudictive never stores your credentials. When it starts the local claude process, it passes on only a fixed list of environment variables that Claude Code needs. If your Anthropic API key or Claude Code login token is set as an environment variable, it is on that list and is passed through to claude; Claudictive does not log or save it.

Claude Code keeps its own transcript of every session it runs, including sessions the overlay starts, in ~/.claude/projects/. Those files belong to Claude Code, not to Claudictive (see Data deletion).

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.

Ads and the Overwolf platform

Claudictive is free and shows ads served by Overwolf's ad SDK. The SDK runs inside the in-game chat panel and the desktop hub pages, which are the same pages that show your conversations. Loading an ad is a network request to Overwolf and its advertising partners, and Overwolf's own privacy policy governs what they collect. Claudictive passes the ad SDK nothing about your conversations, projects or files; it only tells it where to place the ad and what size it is.

Claudictive runs on the Overwolf platform, and Overwolf's privacy policy also covers the platform itself. The app asks Overwolf for the Profile and Streaming permissions because Overwolf's ad SDK requires them for ad targeting under Overwolf's privacy policy. Claudictive's own code does not use them.

Opt-in analytics (v0.2.0+)

Analytics are off by default. Onboarding does not ask about them; the only way to turn them on is the toggle in Settings → Privacy & Data, and you can turn it off again at any time there.

What we collect when you opt in:

• A random install ID, created for this install and never tied to your name, email, or API key. It is shown in Settings so you can quote it if you ask us to delete your data. It is only sent while analytics is on; with analytics off, nothing we receive carries it.
• Event names from a fixed allowlist (e.g., message_sent, game_injected, onboarding_step_completed)
• Counts and categories (e.g., "message was in the medium length bucket")
• App version, your system's user-agent string (which names the app runtime and Windows version), which part of the app the event came from, and the current game name
• Your country, which our server works out from the connection (the IP address itself is not stored with the event)

When you turn analytics off, the app sends any events it already collected while analytics was on, labelled unknown instead of your install ID, plus one final analytics_opt_out event, also without the install ID, and then stops.

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 database, hosted by Cloudflare (see Service providers). Never sold, and not shared with anyone except the service providers named on this page. Used only to improve the product.

Opt-in crash reports (v0.2.0+)

Also off by default, with its own toggle in Settings → Privacy & Data. When the app hits an error, we send the error message and a stack trace so we can fix the underlying bug, together with the app version, your system's user-agent string and the current game name. If analytics is also on, the report carries your install ID; otherwise it carries none.

The report is cleaned up on your machine before it is sent: file paths are replaced with [path], API keys, bearer tokens and named secrets are redacted, session IDs are shortened, and email addresses are reduced to their domain. This is automatic pattern matching, so it cannot promise to catch every personal detail an error message might contain.

Bug reports

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

A bug report contains:

• Your description, exactly as you typed it
• Your email address, only if you fill in the optional email field
• If you ticked them, the end of your debug log and of the conversation transcript (limited in length). These are cleaned up on your machine before sending, the same way as crash reports: file paths become [path], API keys, bearer tokens and named secrets are redacted, session IDs are shortened, and email addresses are reduced to their domain. The words of the conversation itself are sent as they are. The form shows you a preview of what you are attaching.
• Whether logs and a transcript were attached
• Your install ID, only if analytics is on

Our server also stores your country and your system's user-agent string with the report. It does not store your IP address or the page you came from. Cloudflare, which runs our server (see Service providers), sees your IP address when the report arrives, but we do not keep it. To stop spam we store a rate-limit key: a keyed hash of your IP address that changes every day (UTC) and cannot be turned back into the address without our server secret. Reports submitted before [OWNER: date the server change went live] may still include the IP address and referring page they were sent with.

The claudictive.com website

• Waitlist: if you join the waitlist on the homepage, we store your email address, the time you signed up, the page that referred you, and your IP address.
• Contact form and uninstall survey: we store what you enter (message, subject, the reasons you ticked, and your email address - required on the contact form so we can reply, optional on the survey), plus your country and your system's user-agent string, the same way as bug reports. Both forms use Cloudflare Turnstile to block spam, which loads a script from Cloudflare and receives your IP address.
• Fonts: the homepage loads its fonts from Google Fonts, so your browser sends your IP address to Google when you open it. Google's privacy policy applies to that request.

Service providers

Cloudflare hosts the claudictive.com website and the servers the app reports to, and stores our data (analytics, crash reports, bug reports, website form submissions and the waitlist) in its database. As part of serving every request to claudictive.com, Cloudflare receives the IP address it comes from. Cloudflare Turnstile checks website form submissions for spam. Cloudflare's own privacy policy applies to what it processes.

How long we keep data

• Analytics events: kept for 13 months, then deleted automatically
• Crash reports: kept for 90 days, then deleted automatically
• Bug reports, feature requests, contact form messages and uninstall survey answers: kept for 12 months, then deleted automatically
• IP addresses and referring pages stored with reports and form messages sent before [OWNER: date the server change went live]: removed from those records on [OWNER: purge date], or deleted with the record itself once it is 12 months old, whichever comes first
• Waitlist emails: kept until the waitlist closes, plus 30 days, then deleted

Data on your own machine stays until you delete it (see below).

Data deletion

Most 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, feedback, queued telemetry and the diagnostic log. Your preferences on that page (including the install ID) are deliberately kept, so that turning analytics off is not undone by deleting your data.
• Remove Claude Code integration - reverses most of the changes described above in your ~/.claude/ directory (a project's own status line is not included - see that section for how to remove it).

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

Neither action, and not uninstalling either, removes:

• Scratch files (described below)
• Claude Code's own transcripts in ~/.claude/projects/, including those of sessions the overlay started. They belong to Claude Code; delete them there if you want them gone.
• Anything already sent to our servers

Deleting data on our servers: email hello@claudictive.com and include the install ID shown in Settings. That lets us find the analytics events, crash reports and bug reports sent with it. Reports sent while analytics was off carry no install ID, so we can only find them by the email address you entered with them, if any. For the waitlist, contact form or uninstall survey, tell us the email address you used.

Scratch files (v0.6.0+)

If you use the Scratch tab, which lets you chat without opening a project, anything Claude writes during that conversation is saved to ~/.claude/scratch/. Those are your files, not app data, so neither action above deletes them and neither does uninstalling. We deliberately do not remove work you asked Claude to produce. Delete that folder yourself whenever you want it gone.

Contact

Questions: hello@claudictive.com