Privacy Policy
Last updated: October 6, 2026
1. Overview
Claude Tuner is a Chrome extension ("the Extension") and web dashboard ("the Dashboard") that monitors your Claude.ai usage metrics and provides analytics. This privacy policy explains what data we collect, how we use it, and your rights regarding that data.
Claude Tuner is not affiliated with, endorsed by, or officially connected to Anthropic, PBC.
Two parts, handled differently. This policy covers two things:
- ① Claude Tuner — the usage Extension and the Dashboard. It collects usage metrics only: usage percentages, reset times, your plan and organization metadata (section 2). Your Claude.ai conversation list (titles and IDs) and the content of your conversations are never sent to or stored on our server.
- ② AI Cross-Check and AI Debate — the Extension's AI comparison feature, also shown at claudetuner.com/multiai. This feature can save the questions and answers you exchange in it to your Claude Tuner account, so you can see them in your other browsers and on the Dashboard. Section 10 describes everything that reaches our server from it.
Scope of our "no conversation content" statements. Wherever this policy says that we do not receive, collect or store the content of your questions, answers or conversations, that statement does not apply to three cases only, all of them in AI Cross-Check (section 10): (1) history sync — while you are signed in to Claude Tuner and have not turned it off, your AI Cross-Check and AI Debate conversations are saved, encrypted, to your account (section 10.2); (2) a conversation or AI debate you explicitly asked to share by pressing Share — that one conversation is uploaded and published at a link (section 10.3); and (3) text you choose to type into the optional note of an AI debate's feedback box (section 10.4) — it is sent as you write it (extra spaces and line breaks are collapsed), so please do not paste conversation content there. None of these cases ever applies to conversations you hold yourself on Claude.ai, Gemini or ChatGPT.
2. Data We Collect
| Data | Purpose | Storage |
|---|---|---|
| Google account email | User authentication & account identification | Server (Cloudflare D1) |
| Google account name | Display name on dashboard (collected only via Google Sign-In, not from Claude.ai) | Server (Cloudflare D1) |
| Google profile picture URL | Avatar display on dashboard (collected only via Google Sign-In) | Server (Cloudflare D1) |
| Claude.ai usage rates | 5-hour and 7-day utilization percentages, including per-model breakdown (e.g., Opus, Sonnet) | Server + Local (chrome.storage) |
| Reset timestamps | Countdown timers for usage window resets | Server + Local |
| Subscription plan | Plan-specific token estimation and recommendations | Server + Local |
| Subscription details | Renewal date, pending plan changes, subscription pause status | Server |
| VAT status (personal Claude / ChatGPT plan) | Whether VAT applies to your personal Claude or ChatGPT subscription (yes/no — for Claude, on the last bill and on the next one), the date it was checked, which of your organizations/accounts it belongs to, and the country of your billing address (country code only, so a verdict is shown only where a business tax ID removes VAT) — determined in your browser from your billing settings; amounts and billing details are not sent. Shown to your team's dashboard admins unless you hide that organization from your team, so they can point out that a VAT-exempt price is available | Server |
| Privacy setting | Whether "Improve Claude" data sharing is enabled in your Claude.ai account | Server |
| Timezone & language | Localized dashboard experience and timezone-accurate reporting | Server |
| Rate limit tier | Internal plan identifier for accurate plan detection | Server |
| Organization membership | Organization name and ID from your Claude.ai account for per-workspace usage tracking | Server |
| Usage-limit reset passes | How many usage-limit reset passes your Claude.ai or ChatGPT account holds, their type (e.g. full, 5-hour, weekly) and expiry dates — read from the same usage response, and handled like your usage rates. The Extension only reads them; it never uses (redeems) a pass — you do that yourself on Claude.ai or ChatGPT. Pass identifiers, names and promotion details are not sent | Server + Local |
| Extra usage & spending | Additional usage allowance, limits, and spending amounts from your Claude.ai account | Server + Local |
| AI Cross-Check history (only while signed in, with history sync on) | Your AI Cross-Check and AI Debate conversations — your questions, the AI answers, debate turns and summaries, a title, which AIs and models took part, and the IDs of the conversations the feature created in your Claude, Gemini and ChatGPT accounts (so you can continue them in another browser). Attached files, generated images and Incognito conversations are never included. Kept so you can see your history in your other browsers and on the Dashboard; your 50 most recent conversations are kept. Encrypted at rest (section 10.2) | Server (Cloudflare R2 + D1), encrypted |
| AI Cross-Check share links (only if you press share) | A conversation or AI debate you held in Claude Tuner's AI Cross-Check and explicitly asked to share by pressing Share (the questions and AI answers shown in the share preview), a title, which AIs answered, and — only if you choose — your name and profile photo. Published at a public link until you delete it (see section 10.3) | Server (Cloudflare R2 + D1) |
| AI Cross-Check sends | When you send a question from the AI Cross-Check page: which AIs and models it went to, the round number, and content-free characteristics of the question — a length range, its dominant script (e.g. Korean, Latin), a line-count range, and whether it contains code or a link. Used to understand what the feature is used for. This record never contains the question itself or the answers; they reach our server only through history sync or a share link (the rows above), and these derived values cannot be turned back into your question. | Server |
| AI Debate statistics | When an AI debate in AI Cross-Check ends: how it ended (concluded, send limit reached, left), its settings (length, moderation, positions and roles, tone, reply length), the number of participants, turns, sends and your own interjections, how many times the moderator asked you something, and how long it ran. Used to see which settings lead to useful debates. No topic and no words — of the AIs or yours — are included. | Server; the same counts and settings, without any identifier of the debate, also go to Google Analytics |
| AI Debate feedback (only if you rate a debate) | Your 👍 or 👎 under a debate's conclusion, the reasons you tick (e.g. "wrong facts", "too long"), and — only if you type one — a short note (up to 500 characters; extra spaces and line breaks are collapsed). Sent with the debate's settings, the model groups that took part (e.g. "Claude / balanced") and the extension version, so we can tell whether changes made debates better. The debate's topic and the AIs' answers are not sent. The note never goes to analytics (Google Analytics receives only the rating and counts); our team is notified of each feedback — including the note, but not your email — through a Telegram message. | Server; operator notification (Telegram) |
| Extension version | Installed extension version for compatibility and debugging | Server |
| Operating system & browser | OS family and generation (e.g., macOS 26, Windows 10/11) and browser brand with major version (e.g., Chrome 152), used to diagnose collection problems specific to an environment. The exact OS patch version is deliberately not collected. | Server |
3. Data We Do NOT Collect
① Claude Tuner (usage Extension and Dashboard)
- Conversations you hold yourself on Claude.ai, Gemini or ChatGPT (on those sites, not through AI Cross-Check) — neither their content nor your conversation list (titles and IDs). We never collect or upload them, and neither history sync nor sharing (section 10) ever reaches them. Inside your browser, the Extension reads the conversation list in Claude.ai's sidebar to show your folders and usage on the page; that list is not sent to or stored on our server. AI Cross-Check reads only the replies to the questions you send from its own page, in your browser (section 5)
② AI Cross-Check and AI Debate
- What you ask and receive in Claude Tuner's own AI Cross-Check (the Extension's AI comparison feature, also shown at claudetuner.com/multiai) is not collected for our own use — only content-free characteristics of a question are recorded (see section 4). It reaches our server only in the three cases of section 10: history sync, which saves your conversations to your own account, encrypted, while you are signed in and have not turned it off (section 10.2); a conversation or AI debate you explicitly ask to share by pressing Share (section 10.3); and a note you type into a debate's feedback box (section 10.4)
- Files you attach to an AI Cross-Check question (images, documents), images the AIs generate, and conversations held with Incognito on — history sync never uploads them, not even their names or how many there were
Neither part collects
- Personal files or documents
- Browsing history on any website
- Passwords or authentication tokens for Claude.ai
- Payment or billing information — card details, amounts paid, invoices or tax IDs (the only billing-related items are the yes/no VAT status and billing country code above)
- Any data from other websites
4. How We Collect Data
The Extension collects usage data by calling Claude.ai's internal usage API endpoint from within your authenticated browser session. This is the same data displayed on Claude.ai's own usage interface. Data is collected:
- Automatically at regular intervals (default: every 5–10 minutes, configurable by server)
- When you visit or return to a Claude.ai tab
- When you manually click the "Collect" button
- At increased frequency when usage is rising rapidly (adaptive boost mode)
- When a 429 (rate limit) response is detected on Claude.ai via the
webRequestAPI — only the HTTP status code is observed, no request or response content is read
The AI Cross-Check page on our website (claudetuner.com/multiai; formerly called Multi-AI Compare) is only a UI shell that embeds the same Extension's own compare page in a frame. The answers reach our server only through history sync (section 10.2) or a share link you create (section 10.3). A question carried in the page address in the URL fragment (the part after #, the form the Extension and our links use) is never sent to a server. If a link puts the question in the query string instead (?q=), it reaches our hosting provider's edge once as part of that request's address before the page moves it into the fragment; we do not store, analyze or forward it. Our analytics for that page record the page address and the referrer without any question. Data handling is otherwise identical to using the feature from the Extension directly. By default, the conversations the feature creates are kept in your own Claude, Gemini and ChatGPT accounts, like any conversation you start on those sites: you can continue them there, and if the page loses its connection to the Extension it can pick a kept conversation up again. If you turn on "Incognito" on the compare page, they are created as temporary chats instead (Claude, Gemini) or hidden from your history when the session ends (ChatGPT), and cannot be resumed. Except for Incognito conversations, the feature also keeps a history of them in your browser. A copy reaches our servers only through history sync (section 10.2) or a share link (section 10.3). Apart from those two, Claude Tuner's servers never receive the question or the answers: the feature's requests to us are the quota/status calls (GET /api/compare/status, POST /api/compare/consume), the per-round outcome and debate statistics (POST /api/compare/outcome, POST /api/compare/debate) and — only if you rate a debate — its feedback (POST /api/compare/feedback, section 10.4), which carry your Claude Tuner sign-in token and no question or answer content, plus a feature-flag fetch from our CDN (flags.json, no account data); model lists come from the providers themselves. With history sync on, the Extension additionally sends and reads your history through /api/compare/history (and the Dashboard reads it through /api/me/compare-history), as described in section 10.2.
Each send does tell our server about the question, without containing any of it: which AIs and models were asked, the round number, and five derived values — a length range (e.g. "200–999 characters", never the exact length), the dominant script of the text (e.g. Korean, Japanese, Latin — read from the prose, with links and code blocks excluded), a line-count range, and two yes/no flags for whether the text contains code and whether it contains a link. We use these to see what the feature is used for. They are computed inside the Extension (for very long texts, from the first 20,000 characters), each one is a value from a fixed published list, and none of them can be reversed into your wording; the code flag is a heuristic based on the shape of the text (fenced blocks, code-like line endings and openings), not on its meaning. We do not collect prompts for our own use — the only question text that reaches our server is your history, saved to your own account while history sync is on (section 10.2), a conversation you explicitly ask to share by pressing Share (section 10.3), and a feedback note you type (section 10.4). The Extension does not read any other conversation on Claude, Gemini or ChatGPT — only the compare conversations it creates for you, and only in your browser.
For AI debates, the Extension also reports how each debate ended and with which settings (section 2), again without a topic or any words. If you rate a debate with 👍 or 👎, that rating, the reasons you tick and the optional note you type are sent to our server (POST /api/compare/feedback); the note never reaches our analytics provider, and our team is notified of each feedback through Telegram (section 11).
5. Claude.ai API Endpoints Accessed
For usage collection, the Extension only accesses the following Claude.ai API endpoints and does not access any conversation, message, or chat-related endpoints. The one exception is the opt-in AI Cross-Check feature (formerly Multi-AI Compare): only when you send a question from the compare page, it creates conversations and reads their replies in your own Claude, Gemini and ChatGPT sessions, in your browser (see section 4). It never reads your existing conversations on those sites, and the question and the replies reach our servers only through history sync (section 10.2) or a share link you create (section 10.3).
| Endpoint | Purpose |
|---|---|
/api/account | Email and privacy settings |
/api/organizations | Organization list and plan detection |
/api/organizations/{id}/usage | 5h/7d utilization rates and the usage-limit reset passes your account holds (read only) |
/api/organizations/{id}/subscription_details | Subscription info and renewal date |
/api/organizations/{id}/paused_subscription_details | Paused subscription check |
/api/stripe/{id}/invoices | VAT status of the personal plan (read at most once a day; only yes/no and the bill date leave your browser) |
/api/stripe/{id}/upcoming_invoice | Whether the next bill of the personal plan includes VAT (read with the invoices above; only yes/no leaves your browser) |
/api/organizations/{id}/address | Billing country of the personal plan (read with the invoices above; only the country code leaves your browser — never the name or street address) |
/api/organizations/{id}/upgrade_to_max | Plan upgrade (with user consent) |
/api/organizations/{id}/downgrade_individual_claude_subscription | Plan downgrade (with user consent) |
/api/organizations/{id}/cancel_subscription_downgrade | Cancel scheduled downgrade (with user consent) |
You can verify this yourself by inspecting the Extension's source code — it is shipped unobfuscated — or by monitoring network requests in Chrome DevTools.
6. Open Source & Code Transparency
Claude Tuner's extension source code is fully open source under the MIT license:
github.com/chaehyun2/claudetuner
- No build step — the source files in the repository are byte-for-byte identical to the Chrome Web Store package. There is no minification, bundling, or obfuscation.
- No conversation access — for usage collection the extension never calls any
/api/chat,/api/messages, or conversation-related endpoint; it only reads usage percentages, reset timestamps and the usage-limit reset passes your account holds (their count, type and expiry). The one exception is AI Cross-Check, which creates and reads only the compare conversations you start from its page, in your browser (section 5). You can confirm this by searching the entire codebase forfetchcalls. - Enterprise audit-friendly — security teams can review the complete source code, compare it against the installed extension, and verify that no data beyond usage metrics is transmitted, apart from AI Cross-Check signals, AI Cross-Check history sync and a conversation you explicitly share — the AI Cross-Check signals in section 2 are derived values (a range, a script name, two flags), and prompt or answer text is sent only by history sync, which the user can turn off (section 10.2), or when the user explicitly asks to share a conversation by pressing Share (section 10.3).
7. How We Use Data
Collected data is used solely to:
- Display real-time usage metrics in the extension popup
- Render historical charts and trends on the web dashboard
- Calculate estimated token usage
- Provide subscription plan recommendations
- Predict when usage limits may be reached
- Enable optional data sharing with users you explicitly authorize
- Show your AI Cross-Check history in your other browsers and on the Dashboard, while history sync is on (section 10.2) — your history is used for nothing else: not for ads, analytics or training any AI model
- Display promotions/ads (targeted only by country and interface language) and measure their performance — impression and click counts, and how many distinct users an ad reached (see §9 for exactly how distinct users are counted)
8. Data Storage & Security
Server-side data is stored on Cloudflare Workers D1 (SQLite), a globally distributed database service; the content of AI Cross-Check conversations you explicitly share (section 10.3) and your synced AI Cross-Check history (section 10.2) is stored in Cloudflare R2 object storage. Synced history — its questions, answers and titles — is additionally encrypted at rest with an application key (section 10.2). All communication between the Extension and our server uses HTTPS encryption.
Local data is stored in chrome.storage.local and remains on your device.
9. Data Sharing
We do not sell or rent your personal data, and we do not share it with advertisers. The extension and dashboard may display ads or promotions (our own or from partners). Ads are targeted only by broad signals — your country and interface language — never by your personal information or the content of your conversations, which we do not collect (apart from the three cases of section 10, which are kept for you, not for us) and never use for advertising. We measure ad performance for statistics only — never to target ads, build a profile, or decide which ad you see. To count how many distinct users an ad reached (and to avoid showing you the same ad too often), our server derives an irreversible hash of your account identifier and uses it solely to de-duplicate those counts. That hash is never shared with advertisers and never used to select an ad. It exists only as a short-lived de-duplication key: it is held for at most 24 hours and then deleted automatically, and it is never written into our analytics store. The measurement data we keep contains only counts by campaign, country, and language, with no personal identifiers. Clicking an ad takes you to the advertiser's website through normal web navigation; the advertiser does not receive your data from us.
The service includes optional data sharing features: you may share your usage data with specific users by email, and if you join a team (organization), your usage data may be visible to team administrators and members. You control your sharing preferences and can revoke access at any time through the Dashboard.
AI Cross-Check conversations: see section 10 for history sync and share links.
10. AI Cross-Check & AI Debate (/multiai)
AI Cross-Check (the Extension's AI comparison feature, also shown at claudetuner.com/multiai) and AI Debate send your question to Claude, Gemini and ChatGPT in your own accounts, from your browser. This section lists every way the content of those conversations can reach our server. Conversations you hold yourself on Claude.ai, Gemini or ChatGPT are never part of any of them.
10.1 In your browser
The compare page keeps a history of your recent conversations in this browser (except Incognito conversations). Its list shows the signed-in account's conversations together with those held while signed out, and keeps the 20 most recent of them; older ones are removed from this browser automatically, without affecting the copy saved by history sync. Another Claude Tuner account's conversations stay in this browser, hidden from the list and counted separately, until that account signs in again. With history sync off, or while you are signed out of Claude Tuner, that history stays only in this browser.
10.2 History sync
While you are signed in to Claude Tuner, history sync saves your AI Cross-Check and AI Debate conversations to your account, so you can view them in your other browsers and on the Dashboard. A conversation is saved only by the browser it was started in; if you continue it in another browser, it is saved from there as a separate conversation. It is on by default, but nothing is uploaded until the compare page has shown you a one-time notice about it, with a switch to turn it off.
- What is saved: your questions, the AI answers, debate turns and summaries, a title, which AIs and models took part, and the IDs of the conversations the feature created in your Claude, Gemini and ChatGPT accounts, so that another browser signed in to the same AI accounts can continue them. Only conversations you start or continue after history sync is available are uploaded; signing in does not upload your earlier history in bulk.
- Never saved: files you attach (images, documents), images the AIs generate, and conversations held with Incognito on for any AI. Not even their names or how many there were are uploaded — only the fact that an attachment was left out, so the conversation can say so.
- How much: your 50 most recently updated conversations. Older ones are deleted from our server automatically.
- Encryption and access: the questions, answers and titles are encrypted at rest with an application key held separately from the storage. This is server-side encryption, not end-to-end encryption: our server decrypts your history to show it to you. Our operators access it only when needed to respond to an incident (for example, a failure affecting your history). Your history is not visible to people you share usage data with or to your team's administrators, and it is never used for ads, analytics or training any AI model.
- Turning it off: you can turn history sync off on the compare page at any time. From then on, your history is kept only in this browser. When you turn it off you can also choose to delete the copy already on our server. History sync is set per browser: if it is still on in another of your browsers, conversations you continue there afterwards are saved again.
- Deleting: deleting a conversation from your history also deletes it from our server. So that another of your browsers cannot upload it again, we keep a deletion marker for it — the conversation's random ID, with no question, answer or title — until you delete your account. Deleting your account — including from the Dashboard settings page — deletes your synced history from our server immediately, not after the 90-day period in section 12, and it is not restored if you sign in again.
10.3 Share links
When you explicitly ask to share a conversation or an AI debate you held in Claude Tuner's AI Cross-Check by pressing Share (never a conversation of yours on Claude.ai, Gemini or ChatGPT themselves), the conversation you selected (your questions and the AI answers shown in the share preview) is uploaded and published at a link on claudetuner.com/c/… that anyone with the link can read. The page is not indexed by search engines, but we cannot control where a link is forwarded. Your name and profile photo appear on the page only if you choose to show them (the default is anonymous); your email address is never shown. Link previews in messengers may display the title and a short excerpt. A share stays available until you delete it — from the share dialog or your list of shared links — and deleting your account does not delete your share links, so please delete any you no longer want public before deleting your account. We may remove shared content that is reported to us or violates our policies. Messengers may keep their own copy of a link preview after deletion.
10.4 Debate feedback note
If you rate a debate and type a note into its feedback box, the note is sent as you wrote it (extra spaces and line breaks are collapsed), together with the rating described in section 2. The debate's topic and the AIs' answers are not sent with it.
11. Third-Party Services
| Service | Purpose | Privacy Policy |
|---|---|---|
| Google Sign-In | Authentication | Google Privacy Policy |
| Cloudflare Workers | Server & database hosting | Cloudflare Privacy Policy |
| Resend | Transactional email delivery (reports, invitations) | Resend Privacy Policy |
| Google Analytics | Anonymous website and extension usage analytics | Google Privacy Policy |
| Telegram | Operator notifications to our team (e.g. AI Cross-Check activity and AI Debate feedback, which may include your account email and the feedback note you wrote) | Telegram Privacy Policy |
12. Data Retention
Usage snapshots are retained on our server for as long as necessary to provide historical trend analysis. You may delete your account and all associated data at any time through the Dashboard settings page — except share links you published, which stay public until you delete them (see below and section 10.3). Upon deletion, a minimal record (email and deletion timestamp) may be retained for abuse prevention and legal compliance.
Local data stored in the Extension can be cleared by uninstalling the Extension or clearing extension data in Chrome settings.
AI Cross-Check share links are kept until you delete them (see section 10.3); account deletion does not remove them. Orphaned links of deleted accounts may be removed by us.
Synced AI Cross-Check history (section 10.2) is limited to your 50 most recently updated conversations; older ones are deleted from our server automatically. Deleting a conversation from your history deletes it from our server, and deleting your account deletes your synced history immediately — it is not kept for the 90-day period described below.
AI Cross-Check usage records, AI Debate statistics and AI Debate feedback (including any note you wrote) that were recorded before you deleted your account are deleted together with it when it is permanently deleted; once your account is marked as deleted, no further debate statistics or feedback are recorded for it. Deleting from the Dashboard first marks the account as deleted (signing in again restores it); the permanent deletion normally happens 90 days later, by a daily clean-up that retries until it succeeds. Operator notifications already delivered to our team through Telegram (section 11) are not recalled.
13. Your Rights
You have the right to:
- Access your data via the web dashboard
- Delete your account and all associated data through the Dashboard settings page (share links you published are deleted separately, from the share dialog or your list of shared links)
- Revoke data sharing permissions at any time
- Turn off AI Cross-Check history sync on the compare page, and delete the copy of your history on our server (section 10.2)
- Opt out of weekly email reports via the Dashboard settings page
- Uninstall the Extension at any time to stop all data collection
14. Children's Privacy
Claude Tuner is not intended for use by children under the age of 13. We do not knowingly collect personal information from children.
15. Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last updated" date. Continued use of the service after changes constitutes acceptance of the updated policy.
16. Contact
If you have questions about this Privacy Policy or wish to request data deletion, please contact:
Email: support@claudetuner.com