Privacy Policy
Last updated: 2026-11-20
What we collect
Before version 0.9.2, nothing is sent by default. The app runs on your machine. Crash reports are sent only if you turn them on. Analytics are off until you turn them on, except that starting with version 0.9.2 the app can start with them on if you are outside the EU and its territories, the EEA, the UK and UK-linked territories, and Switzerland (see Analytics). Our website, claudictive.com, keeps a simple count of visits without cookies - see Website visits. The app shows ads, which are served by Overwolf, not by us - see Ads below.
What stays on your machine
- Conversation transcripts (in
%APPDATA%/Claudictive/transcripts/) - Images you paste into the in-game chat (in
%APPDATA%/Claudictive/pasted-images/), so Claude Code can open them. They go only to your own Claude Code session, like the rest of your message, and are deleted after 7 days. - Game screenshots from the snapshot button in the in-game chat. Claudictive captures your game screen only when you press that button. The picture is added to your message like a pasted image, you can remove it before sending, and once you send it, it is stored and deleted exactly like a pasted image.
- Session metadata (game name, duration, message counts)
- Match summaries (from v0.9.0, in
%APPDATA%/Claudictive/match-summaries.json). When a game closes, Claudictive reads the Claude Code transcripts already on your machine for the time you played and stores what Claude finished: the first line of each of Claude's final replies, the names of the files it changed (not their contents or full paths), the project folder name, file and commit counts, and times. Only your last 30 games are kept. They are shown in the desktop hub and never sent anywhere. Delete my local data in Settings erases them with the rest of your local data. - Settings (hotkeys, preferences)
- Debug logs (rotating, capped at 1MB)
Changes Claudictive makes to your Claude Code setup
Claudictive asks before writing anything to your Claude Code home directory (~/.claude/). The first time you connect the overlay to an existing Claude Code session, a consent screen lists exactly what it 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, which is consumed and cleared when read - 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 - A small Claude Code mod, the live mirror, in
~/.claude/claudictive-mirror/, and that folder's name added toenv.CLAUDE_CODE_PLUGIN_DIRSin~/.claude/settings.json(your own entries there are kept). It lets a message you send in game run inside your open Claude Code session. While it runs, it keeps small per-session files in the same folder: a status file (session id, project folder, model, which Claude Code app, its version), the text of in-game messages on their way into the session, their delivery status, and questions Claude asks you in game with your answers. Message, status and question files are deleted once handled. From v0.9.0 it also keeps a usage file per session (usage.json) for the desktop hub's Live board: how full the context window is, your plan's usage limits and reset times, the session's cost, and the names of the skills it has. Names and numbers only, no conversation text. It gets these from Claude Code itself on your machine, without any extra request, and nothing is sent anywhere. It is on by default once you choose Allow
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.
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 most of it: open the desktop hub, go to Settings → Privacy & Data, and use Remove Claude Code integration. Do this before uninstalling: uninstalling Claudictive on its own leaves these files in place. This does not remove a status line added to an individual project's .claude/settings.json - delete that yourself if you want it gone. It also leaves the ~/.claude/claudictive-mirror/ folder, which does nothing once its entry in settings.json is removed; you can delete it yourself.
What goes to Anthropic
Claudictive works with your own Claude Code: the CLI, VS Code, JetBrains or the desktop app. A message you type in game is delivered into your Claude Code session on your machine. Claude Code then sends it to Anthropic the same way it always does, under your own Claude Code sign-in (your subscription or your API key). Claudictive does not talk to Anthropic itself. Anthropic's privacy policy applies to that data.
Claudictive never asks for, stores, logs or sends your Claude credentials. When it has to start Claude Code for you (for example to reopen a project whose terminal is closed, or for the Scratch tab), it runs your installed Claude Code with your own environment, so a key or token you have set there (ANTHROPIC_API_KEY, CLAUDE_CODE_OAUTH_TOKEN) reaches Claude Code as usual. Claudictive only passes it on.
Ads
Claudictive is free and ad-supported. Ads appear in the desktop hub (not on the Settings, Help, onboarding or consent screens) and at the bottom of the in-game chat panel (not while the chat is collapsed). They are served by Overwolf's ad platform: the ad code is Overwolf's own, loaded from Overwolf. Overwolf's privacy policy covers the data used to show them.
Claudictive does not receive personal data from ads, and sends no ad data to our server. The app only notes in its local debug log whether an ad slot loaded, so we can fix empty slots. That log stays on your machine unless you attach it to a bug report.
Waitlist
Before the public release, claudictive.com had a waitlist form. For each signup it stored your email address, the time you signed up, the page you signed up from, and your IP address. We used it only to tell people about the launch. The waitlist is now closed. To be removed from it, email [email protected].
Analytics
Before version 0.9.2: analytics are off by default. Nothing is sent until you turn them on yourself in Settings > Privacy & Data, and you can turn them off again there at any time.
Starting with version 0.9.2: the last setup screen shows a "Usage stats" card with one switch. Whether it starts on or off depends on where you are. When the card opens, the app asks claudictive.com whether your region requires opt-in. Our server reads your country from the connection, answers only yes or no, and stores nothing from that request. In the European Union and its territories, the EEA, the United Kingdom, Gibraltar, Jersey, Guernsey, the Isle of Man and Switzerland, and whenever the answer is unknown (for example the lookup fails or is blocked), the switch starts off. Everywhere else it starts on. Nothing is saved until you press "Go play", and if you skip setup nothing is saved and nothing is sent. If you skip setup or leave it another way, you later see the same card once in the hub, with the switch off.
If you already use the app with analytics off: after updating to 0.9.2 you see the same card once, in the hub, with the switch off. Analytics turn on only if you switch it on and press Continue. If you already turned analytics on, they stay on. In every case you can change this at any time in Settings > Privacy & Data. Turning analytics off stops sending. The random install ID stays on your machine, and Settings > Privacy & Data shows it, so you can quote it in a deletion request.
What we collect when you opt in:
- A random 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", "a match summary listed 3 tasks in 2 projects")
- App version and current game name
- From 0.9.2, about the chat panel in a game: a random session ID that exists only for that game session and is not stored with your settings and is not reused after that game; how the panel was opened (hotkey, pill click, or an alert such as a question, an approval or a finished task); a coarse range for how far into the game it was opened (such as 0 to 30 seconds or 10 to 30 minutes); whether it was the first open of that game; how long the panel stayed open; and, when the game ends, the game's Overwolf game ID, how long the game ran, how many times the panel was opened and for how long in total. An "open" means the chat panel expanding, not the overlay appearing. These are counts, time ranges and fixed labels only, never what you typed or what Claude answered
- Your Windows display scaling (e.g., 125%) and the game's screen resolution (e.g., 1920x1080), once per game session
- The user agent of the app's built-in browser, cut to 64 characters. This is the field we label "OS": it names your Windows version and the browser and Overwolf versions the app runs on
What our server adds to each event: your country, as reported by Cloudflare, and a daily rate-limit key. We do not store your IP address.
When you turn analytics off: the app sends one last event, analytics_opt_out, so we can count how many people opt out. It carries no install ID. It contains only the event name, the time, which part of the app sent it, the app version and the user agent, and our server adds your country and the rate-limit key as above. After that, nothing more is sent.
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 [email protected].
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.
What a crash report contains:
- The error class, the sanitized error message and the sanitized stack trace
- Which part of the app crashed
- The app version and the user agent of the app's built-in browser (cut to 64 characters, as above)
- The game name, if the report includes one
- Your random install ID, but only if analytics are also on. With crash reports on and analytics off, the report is sent without it
- Added by our server: the daily rate-limit key. Crash reports do not store your country or your IP address
Bug reports
A bug report is sent only when you press send in the hub's bug report form, whether or not analytics are on. You choose explicitly whether to attach the app's recent log or a session transcript. Nothing is included without your check, and both are scrubbed of file paths, keys and similar details before they leave your machine. What you type in the description is sent as you wrote it.
What we store when you send one:
- Your description, and the log or transcript if you ticked them
- Your email, only if you give one, so we can reply
- Whether a log and a transcript were attached
- Your random install ID, only if analytics are on
- The user agent of the app's built-in browser and your country, as reported by Cloudflare
- The daily rate-limit key. We do not store your IP address
A copy of each report also stays on your machine, in %APPDATA%/Claudictive/.
Contact form and uninstall survey
The contact form and the uninstall survey on claudictive.com send something only when you press send. When you uninstall the app, it opens the uninstall survey in your browser; filling it in is optional, and closing the tab sends nothing.
What we store when you send one:
- What you write, and the reasons you pick in the uninstall survey (including a game name, if you type one)
- Your email, only if you give one, so we can reply
- The app version, when the app opened the survey
- Your browser's user agent and your country, as reported by Cloudflare
- The daily rate-limit key
What we do not store: your IP address. It is used only while your message is being received, to run Cloudflare Turnstile (the spam check on the form, which is processed by Cloudflare) and to compute the rate-limit key above.
Submissions go to our Cloudflare D1 database. Never sold, never shared with third parties, used only to answer you and improve the product. To have a submission deleted, email [email protected].
Website visits
When you browse claudictive.com, a small script on our own site counts the visit so we can see which pages people read and how they find us. It sets no cookies and stores nothing in your browser.
What we record:
- The page you opened (for example the home page, this privacy page or a post on our blog)
- Which of our download, Overwolf store or Discord links you click, and on which page, so we can see which blog posts lead to downloads. On a phone this also covers the send-it-to-yourself buttons (email, share, calendar reminder, copy link): we only count the click. Your email address, your contacts and what you share stay in your own apps and never reach us.
- The name of the website that sent you here (for example
www.reddit.com), never the full address of the page you came from - The campaign tags in the link you followed, if it had any (
utm_sourceandutm_campaign) - Whether your screen is mobile or desktop sized
- Added by our server: your country, as reported by Cloudflare, and the daily website key
What we do not record: no cookies, no ID stored in your browser or that follows you from one day to the next, no IP address, and nothing about what you do on other websites. The website key lets us count roughly how many different visitors came on one day. Because it changes every day, it cannot link your visits on different days. It is also separate from the key we store with app data and form messages, so your visits cannot be matched to anything you send from the app or our forms.
If your browser sends Global Privacy Control or Do Not Track, the script sends nothing at all, and our server also stores nothing for a request that carries either signal.
Visit records go to our Cloudflare D1 database and are deleted automatically once they are more than 90 days old. The clean-up runs every so often rather than at an exact moment, so a record can last a little past 90 days before it is removed. Never sold, never shared with third parties, used only to understand how the site is used.
The rate-limit key
Analytics events, crash reports, bug reports, contact messages and uninstall surveys are all stored with a rate-limit key, so we can stop one address from flooding our database. Our server makes it from your IP address and the current date (UTC): it computes an HMAC-SHA256 of the two, using a secret key that only our server has, and keeps the first 32 hex characters. Your IP address itself is not stored.
For an IPv6 address, the key is made from the first half of the address only (the network prefix), because one home or mobile connection is usually given a whole block of IPv6 addresses that share that first half. An IPv4 address is used as it is.
Website visits are stored with a separate website key. It is made the same way, from the same address and date, but with a fixed label for website visits added to the input, so for the same address on the same day it comes out as a completely different value. That is why website visits cannot be matched to app data, crash reports or form messages, even by us.
Because the date is part of the input, both keys change every day, so they cannot link what you send on different days. Without our secret they cannot be turned back into your IP address. Someone who had the secret could check whether a guessed IP address matches a key, which is why the secret never leaves our server and is not part of the app.
Data deletion
Almost all Claudictive data lives in %APPDATA%/Claudictive/ on your machine. The one exception is described under Scratch files below. 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, the diagnostic log and pasted images. 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 most of the changes described above in your
~/.claude/directory (a project's own status line and the inactive~/.claude/claudictive-mirror/folder are left - see that section for how to remove them).
Both are irreversible and ask for confirmation first. You can also uninstall the app and remove the folder manually.
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: [email protected]