Privacy Policy

Latest update: 1 Nov 2026

1. Introduction

This Privacy Policy explains how ChatGPT Pro Tools (browser extension) handles your data — on chatgpt.com and, only if you allow it, on claude.ai (section 2). We respect your privacy and are committed to being transparent about our data practices.

2. Data Collection & Usage

Outside of Pro license verification (section 3), optional Cloud Sync (section 4), the AI features you run in the cloud — including the free cloud runs (section 5) — anonymous usage statistics if you say yes to them (section 6) and a message you send us through the support form (below), the extension does not send your data to us or third parties — everything else stays in your browser.

  • Access token – read ephemerally from outgoing ChatGPT requests; never stored or transmitted elsewhere. Needs to get users locale.
  • Locale – read to adapt UI; not persisted beyond session state.

On claude.ai. The extension works on claude.ai only after you allow it there (the Claude tab of the extension's menu → Allow on claude.ai), which asks your browser for access to claude.ai; you can take that access back in your browser's site settings at any time. There it reads your Artifacts pages and, with your own claude.ai session, the list of your artifacts — their titles, descriptions and projects — to sort, count and filter them by folder, and claude.ai's own lastActiveOrg cookie, which tells it which claude.ai organisation is open, so the folders of two Claude accounts never mix. To offer you folders made from your claude.ai projects, it also reads the names, icons and colours of your projects from claude.ai, with your own claude.ai session. All of this stays in your browser, except what Sort with AI sends when you use it: the titles and descriptions of the artifacts it sorts and the names of your projects (section 5). Your folders — their names, icons and colours, and which artifact is in which — are kept in your browser only; the one thing of them ever sent is their names, by Sort with AI when you use it. From claude.ai the extension sends only what it may send from ChatGPT too — anonymous usage statistics if you agree to them (section 6) and a message you send through its Support form (below) — and what Sort with AI sends to sort your artifacts, when you use it (section 5).

The extension contains no third-party analytics or tracking scripts, and we never sell or share your data. It tells us how it is used only if you agree to anonymous usage statistics (section 6) — until you do, and whenever you turn them off, nothing about your use of the extension leaves your browser, except the details a support message carries (below); the one thing our server notes about your use of Pro is the dates of your first and last license check (section 3). (Our website uses two privacy-friendly, cookieless analytics services — Vercel Analytics and Ahrefs Web Analytics — for aggregate visit counts only, never your extension data.)

The support form. If you write to us from the extension's Support form, on ChatGPT or on claude.ai, it sends what you fill in — your email address (filled in from your ChatGPT account; you can change it), a subject, your message and any screenshots or videos you attach — with the extension version, your interface language, whether Pro is active and, from ChatGPT, which ChatGPT layout you have and whether the extension's button showed in ChatGPT's sidebar (from claude.ai, that it came from claude.ai), over HTTPS to our server (gptprotools.com/api/support). The server adds your browser's user-agent (your browser and operating system), the site the message came from and your country (from the connection), and emails it all to our support inbox through our email provider, Resend, so that we can reply to the address you gave. Nothing from the form is written to our databases: your message and its files exist only in that email, which stays in our support inbox like any email you send us. The IP address is held in memory only, to limit how many messages one connection can send, and is never written to our storage. The contact form on our website works the same way; in place of the extension's details it sends your browser's language.

If you uninstall the extension, your browser may open a short feedback page on our website. Its address carries only non-identifying context — the extension version, install date, whether Pro was active, and your browser language — and nothing is recorded unless you choose to submit the survey. A survey you submit is kept with that context and with your browser's user-agent and your country, which our server reads from the request. The one exception is when usage statistics were on (section 6): the address then also carries their random install number, opening the page records that the extension was removed, and a survey you submit is linked to that number. Submissions are anonymous unless you choose to leave your email, and are used solely to improve the product. If you do leave it, the address goes only to our support inbox, together with your answer, so we can reply to you about it; it is not stored with the survey answers and is never used for anything else — no newsletters, no marketing. Screenshots or videos you choose to attach go the same way: only to our support inbox, together with your answer, to help us understand the problem you describe; they are not stored with the survey answers. Please leave out anything you would rather keep private.

3. Pro License Verification

If you purchase a Pro subscription, the extension contacts our license server (gptprotools.com/api/license) to verify and manage your license — one of the cases listed in section 2 where the extension sends data to us. For this it sends:

  • License key – sent to confirm your subscription is active (we check its status with our payment provider, Paddle).
  • ChatGPT account email – sent so a Pro license can be tied to a single ChatGPT account (this stops one key being shared across many accounts). We store only a one-way salted hash of the email against your subscription — never the plain-text address — and use it solely to match your account on later license checks. Deactivating Pro releases this link.
  • A random installation number – also sent with each check; our server does not use or store it.

Each time a license check confirms your Pro is active — on activation, then about once a week — we note the day of that check (never the time) against your license — the record keeps the days of your first and your latest check — so we can see whether Pro is actually working for you; for example, whether a purchase was ever activated. When your license ends, that record is deleted, and the note we keep instead holds no license key, email or account id — only the month the license ended, how many whole weeks it lasted, the plan, and how many days before the end it was last checked. A record left behind for any other reason is deleted at the latest 13 months after the last check.

Lost your key? If you ask us to email your key again — from the extension's Settings or from our pricing page — the address you enter is used only to find your purchase at Paddle, and the key goes to the address Paddle holds for that purchase. The address you enter is not stored: it is held in memory only, as a one-way hash, to limit how often the same address can be asked about, and is never written to our storage or our logs.

Payments are handled by Paddle.com Market Limited (our Merchant of Record); we never receive or store your payment details. When you buy Pro on our website, the checkout also notes which link or page brought you there — for example the extension's upgrade window, or one of our articles — and stores it with your purchase at Paddle; we use it only to learn what helps people decide. Free features send nothing to our server, with four exceptions: the free cloud runs of the AI features (section 5), anonymous usage statistics if you agree to them (section 6), a message you send through the support form (section 2), and an address you enter to have your key emailed again (above).

4. Cloud Sync Pro

Pro users can turn on Cloud Sync to back up and synchronize their extension data — AI tags, notes, highlights, saved messages, prompts, chat summaries, and settings — across devices. It is off by default and only runs after you explicitly turn it on.

  • Encrypted. Your data is encrypted on your device before upload, with a key derived from your license key, and we store only the resulting ciphertext — it is never stored or transmitted in the clear, and a breach of the sync database alone cannot expose it. (Because we issue your license key, this is not zero-knowledge: we could technically derive the key. If we ever offer a user-set passphrase for full zero-knowledge sync, we will say so here.)
  • What is stored. The encrypted blobs are kept on our infrastructure (Neon/Vercel), partitioned by your subscription. Your license key authorizes access; no separate account is created.
  • Your control. Turning sync off stops further uploads. Your data also always stays in your browser, so disabling sync never loses it.

If you never enable Cloud Sync, none of this data is uploaded to us — apart from the names and descriptions of your tags, which a cloud tagging run sends with your chat titles (section 5).

5. Cloud AI and the free cloud runs

The extension's AI features — AI Tags (generating tags, applying them to your chats, and tagging new chats automatically), the Prompt Optimizer and chat summaries — run either on a cloud model or on your device. Each AI button shows where it runs, and you choose: in the cloud, or on this device once you turn on On-device AI (Settings → AI, or "Turn on" in the button's menu; Chrome only). On your device, Chrome's built-in model does the work and nothing is sent anywhere. Turning On-device AI on starts Chrome's one-time download of that model.

Chat summaries. On your device, Chrome's built-in model reads the chat and nothing is sent. In the cloud, when you click Summarize or Update in a chat's Summary tab, the extension sends that chat's title and the text of its messages over HTTPS to our server (gptprotools.com/api/ai/summary), which has Google Gemini write the summary, as described below. An image in the chat is sent only as the mark [image], and an attached file only as its name, in the form [file: name] — never the image or the file itself. This is the one feature that sends the messages of a chat, and it sends them only on that click, only in the cloud. The summary is saved in your browser, attached to that chat, and, with Cloud Sync on (section 4), in its encrypted copy.

Folders on claude.ai. Sort with AI, on claude.ai's Artifacts pages, runs only in the cloud. When you click it, the extension sends the titles and descriptions of the artifacts it sorts — those not in a folder yet — and the names of your folders and of your claude.ai projects, with the language of your claude.ai page, over HTTPS to our server (gptprotools.com/api/ai/folders), which has Google Gemini suggest folders and which artifact goes into each, as described below. Nothing is filed until you have looked the suggestion over and accepted it, and your folders stay in your browser (section 2).

On the free plan. Generate, Apply, the Prompt Optimizer, Summarize and Sort with AI each have one free cloud run per calendar month; tagging new chats automatically runs in the cloud only with Pro. The button's menu says what a cloud run sends before you use it; Sort with AI, which starts on its click, is described above. A free run sends no license key — there is none — and no other identifier, and is handled exactly as described below. To keep free runs from being abused, our server counts these requests and the AI tokens they use per day (two numbers per day for AI Tags, two for the Prompt Optimizer, two for chat summaries and two for Sort with AI) and holds the IP address a request comes from in memory only, to limit how many one connection can make; the address is never written to our storage. Separately, for our own bookkeeping, it keeps a daily total of how many cloud AI calls each feature made, on the free and on the Pro plan, and what they cost — totals only, with nothing attached to any user or request.

With Pro. The cloud runs every AI feature without limits for normal use — a monthly fair-use limit, set far above it, stops abuse such as a leaked license key (Terms, section 5) — and it is where each button starts; you can move any button but Sort with AI to your device.

  • What is sent. Only the text each feature needs: for tagging, your chat titles and the names and descriptions of your tags; for the optimizer, the prompt you ask it to optimize, with the tone, length and any extra context you set; for a summary, that chat's title and the text of its messages (images and attached files only as the marks above), with the length and style you pick; for Sort with AI, the titles and descriptions of the artifacts it sorts and the names of your folders and claude.ai projects, with the language of your claude.ai page, so that new folders are named in it. With Pro, also your license key: it verifies your subscription, and what the call cost — an amount in cents, nothing about what was sent — is added to that subscription's total for the month, which the fair-use limit is checked against. Your chat messages are sent only for a summary you ask for — tagging works from titles alone.
  • Processed by Google Gemini. Our server passes that text to the Google Gemini API, which generates the result — the tags, the rewritten prompt, the summary or the suggested folders — and returns it. Google does not use it to train or improve its models; under its terms for paid API use it keeps requests and responses for a limited time, solely to detect and prevent abuse of the service and for any required legal disclosures. Google's handling is governed by its own API terms.
  • Not stored, not reused. We do not save your titles, descriptions, folder names, prompts or chat messages — or the results made from them — to any database, we do not log their contents, and we do not use them for anything other than returning your result. Each request is processed in memory and discarded as soon as the response is sent.

Nothing is sent while a button runs on your device. A cloud run sends its text only when you click the button — Generate, Apply or Optimize — when a run you started picks up again after a page reload, or, with Pro tagging new chats in the cloud, when a new chat gets its title. A summary sends a chat's messages only when you click Summarize or Update, and Sort with AI sends only when you click it.

6. Anonymous usage statistics (only if you agree)

To learn which features work for people and where the extension breaks, the extension asks whether you want to share anonymous usage statistics — in the welcome tour after you install it, or once in the Chat Workspace. They stay off until you say yes, and you can change your answer at any time in Settings → Privacy or in the extension's menu. One answer covers the extension everywhere it works: on ChatGPT and, if you allowed it there, on claude.ai. In Firefox, statistics also need Firefox's own permission for "technical and interaction data". Firefox ticks it by default when you install the extension; we do not take that as a yes, and the extension still asks you. If the permission is off when you say yes, Firefox asks you to confirm. Turning it on yourself in Firefox's add-on settings (Add-ons and themes → ChatGPT Pro Tools → Permissions and data) also counts as a yes. Nothing is sent while the permission is off, or until you have said yes.

  • What is sent. Which of the extension's features you use and whether they worked — for example "opened the Chat Workspace", "exported a chat as PDF — failed, rate limited", "reached the free limit of 7 chats" — how far the welcome tour got, which features you turn on or off in Settings, and errors in the extension's own code; on claude.ai, how you use folders — for example "made a folder", "ran Sort with AI", "moved an artifact into a folder", "showed one folder" — with how many folders you have. When ChatGPT refuses a request for coming too often, the event also says how many requests the extension had sent in the minute before and how many ChatGPT tabs were open; a failure carries ChatGPT's error code (for example 404); and when a button of ours fails to appear, the event names the kind of ChatGPT page it was — a chat, a project, the home page — never its address. Each batch also carries the extension version, which ChatGPT layout you have (or that it comes from claude.ai), whether you are on the free plan or Pro, your browser's language and the day you installed. Our server adds your browser and operating system (from your browser's standard user-agent) and your country (from the connection); the IP address is held in memory only, to limit how many requests one connection can make, and is never written to our storage.
  • What is never sent. Your conversations, chat or project titles, tag names, prompts, notes, highlights, folder names, artifacts or their titles, or anything else you type; your email or license key; chat or project ids and web addresses. Every event is a short code from a fixed list, and our server discards anything that is not.
  • A random install number. When you say yes, the extension creates a random number for this installation, so we can see what happened in what order — for example, that an export failed three times before the extension was removed. It is not linked to your ChatGPT account, your email, your license or anything else we hold. If you uninstall while statistics are on, the feedback page records the removal (section 2).
  • Turning them off. Switch off "Anonymous usage statistics" in Settings → Privacy, or "Usage statistics" in the extension's menu: the install number and any statistics not yet sent are deleted from your browser at once, and nothing more is sent. In Firefox, turning the permission off in Firefox's add-on settings does the same.
  • Use and storage. Used only to find problems and improve the extension — never sold, never shared, never used for advertising. Kept on our infrastructure (Neon/Vercel) for 90 days, then deleted automatically.

7. Data Retention & Your Rights

We hold the little data we do have only as long as it serves the feature you turned on:

  • Cloud Sync data – your encrypted blobs stay on our infrastructure while your Pro subscription is active. They are removed from active storage the moment you unlink your ChatGPT account (Settings → Unlink), held aside for 30 days in case you re-activate the same key on the same account, and permanently deleted after that. While they are held aside they are readable by no one — not by another account, not by anyone holding your license key. They are deleted outright, with no 30-day wait, when your subscription ends, when a different ChatGPT account claims the license, and whenever you ask us to delete them. They are encrypted with a key derived from your license key, so they are unreadable to us regardless.
  • Cloud AI (including the free cloud runs) – nothing to retain: the titles, descriptions, folder names, prompts and chat messages sent to the cloud are processed in memory to generate your result and are never written to our storage or logs. The free runs' daily counts are two numbers per day for each feature — requests and tokens — with nothing attached to them. For each Pro subscription the server keeps one number, what its cloud AI cost this month, which starts over when the month turns. The daily cost totals described in section 5 hold no personal data and are kept for our accounts.
  • Email hash – the one-way hash used to bind a license to one ChatGPT account is kept only while that binding exists; unlinking Pro or cancelling your subscription releases it.
  • License check dates – the dates of your first and last license check (section 3) are kept while your license is active, and deleted when it ends or, at the latest, 13 months after the last check; the note kept after the end holds no license key, email or account id.
  • Usage statistics – kept 90 days from when they reach us, then deleted automatically. Because the install number is not linked to you, we cannot look your statistics up by your name or email; turning them off (section 6) stops them, and what we already have expires on its own.
  • Payments – handled and retained by Paddle under its own policy, together with the note of which page led to the purchase; we never receive or store your payment details.

Wherever you live, you can ask us to access, export, or delete any data associated with you, and we will act on it. You can also remove most data yourself at any time: turning off usage statistics deletes the install number from your browser and stops them, turning off Cloud Sync stops uploads, Unlink in Settings releases the email binding and takes that account's synced data out of service, deleting it permanently after 30 days (sooner on request), and uninstalling the extension erases all local data from your browser. To make a request, use the contact form.

8. Changes to This Policy

We may update this Privacy Policy from time to time, especially as we add new features. We recommend reviewing this page periodically. Your continued use of the Extension constitutes your acceptance of any modifications.

9. Contact Us

If you have any questions or concerns about this Privacy Policy, you can contact us through the contact form on our website.