Privacy

What stays on your device.
And what doesn't.

Last updated: May 25, 2026. This policy is written in plain English on purpose. If anything is unclear, that's a bug — please tell us at divykairoth@gmail.com.

Tally is a Chrome extension that reads your Claude (claude.ai) usage data so you can see, in real time, how much of your rate-limit window is left and how many messages you can expect to send before hitting it. It also lets you, on demand, hand off a Claude conversation to ChatGPT, Gemini, or Grok.

This policy explains exactly what data Tally touches, where it goes, and what it does not do.

What Tally reads

Tally fetches data from three endpoints on https://claude.ai, using your existing browser session cookie — exactly as the Claude web app does:

  1. GET /api/organizations — to get your organization ID.
  2. GET /api/organizations/{id}/usage — to get the current 5-hour and 7-day usage percentages and reset timestamps.
  3. GET /api/organizations/{id}/chat_conversations/{convId} only when you explicitly click a destination button in the popup. This returns the message history of the chat you're on.

Tally never reads, transmits, or stores your Claude session cookie itself. The browser handles cookies; Tally just makes same-origin fetch calls from a content script.

What Tally stores locally

In chrome.storage.local (your browser, on your device, never synced to any Tally server):

KeyContentsWhy
tally:historyUp to 20 recent percentage-deltas after Claude messages, tagged with the model usedTo estimate "messages left" based on your own usage patterns
tally:billingDaily-quota counter + (if activated) your Polar.sh license keyTo enforce the 2-free-sends-per-day cap and unlock Pro
tally:onboardedBooleanSo the welcome screen only opens once
tally:pendingSnapshotThe conversation being handed off, with a 90-second TTLRead by the destination injector on the target site, then deleted

What Tally does NOT do

When you hand off a conversation

If you click ChatGPT, Gemini, or Grok in the popup, this is the data flow:

  1. Tally fetches your active conversation from claude.ai (same-origin, same cookies your browser already sent).
  2. Tally formats it as Markdown in your browser's memory.
  3. Tally writes the Markdown to chrome.storage.local under tally:pendingSnapshot with a 90-second time-to-live.
  4. Tally opens a new tab to the destination site.
  5. A content script on that destination site (chatgpt.com, gemini.google.com, etc.) reads the pending Snapshot, pastes it into the destination's chat input, and immediately deletes the storage entry.
  6. The destination LLM then receives the conversation — at that point, their privacy policy applies, not ours.

The Markdown never leaves your machine except via the deliberate paste into the destination's input field. We do not send it to any Tally server.

Polar.sh integration

If you upgrade to Pro:

Tally never sees your card details, billing address, or any payment information. That stays between you and Polar.

Help form

If you submit the help form inside the extension, the message and email you provided are sent via Formspree (formspree.io/f/xvzyzbza) and arrive in divykairoth@gmail.com. Only what you type — no automatic data collection.

Open source

Tally's source code is public at github.com/kairothq/tally. You can audit every line at any time.

Changes

If we ever change what data Tally touches, this policy will be updated and the date at the top will move forward. Material changes will be flagged in the extension's update notes.

Contact


← Back to Tally · Pricing