This policy explains what Use Multiple Chat AI at Once (also listed as Chat with Multiple AI) collects, why, and what you can do about it. It covers the browser extension and the three web pages we host for it: the welcome page, the rating page and the uninstall page.
It is short because the extension collects little. Everything below describes what the code actually does.
- Your prompts, your templates, the files and web pages you attach and the answers you receive never reach us. What you send goes only to the AI services you choose.
- We count installs, ratings and uninstalls, and how long an installation lasted.
- We identify an installation, not a person. There is no account and no login.
- Our pages run analytics automatically, but only when the extension itself opens them at one of those moments. We do not ask for consent first, and we do not show advertising.
What stays on your device
The extension stores the following in your browser and never sends it to us:
- Prompt templates and the draft you are editing, in the browser's local database. For an attachment they keep only a reference — the address of a web page, or a pointer to a file on your disk — never a copy of its contents.
- Your settings. Some settings are stored in the browser's synchronised storage, which means your browser may copy them between your own signed-in profiles. That is the browser's mechanism, not a transfer to us.
- A random identifier for the installation and the moment it was installed (see below).
Clearing the extension's data from its settings removes this local data. It does not remove anything from the analytics services or from our web pages' cookies — those are described further down.
What the extension does on web pages
The extension is declared with access to all websites. It needs that access for three things: to work with whichever AI services you choose, to show its button on the pages you open, and to read a web page you attach to a prompt. What it does depends on the page.
On AI service pages
On the pages of the AI services configured in the extension, when you send a prompt, it:
- puts your prompt into the input field and attaches your files;
- reads your own message in the conversation to confirm the prompt was actually sent. It does not read the assistant's replies — the code has no selector for them.
On any other web page
- The extension button. A small button at the edge of the window opens the extension. It lives in its own isolated element and does not read, change or send the content of the page. You can turn it off in the extension's settings.
- The page menu. When you right-click a page, the extension's menu items offer to attach that page's address to a prompt. Nothing is taken from the page unless you choose one, and then only its address is added. You can turn these items off in the extension's settings.
Web pages you attach to a prompt
When you attach a web address and send the prompt, the extension fetches it. An address that leads to a file is downloaded; an address that leads to a web page is opened in a visible tab, and the extension reads the text of that page. Both use your existing session with that site, so a page that requires you to be signed in is read as you would see it. The tab stays open so you can check what was read.
The downloaded file or the page text goes, together with your prompt, only to the AI services you selected. It is not stored beyond that send. Files you attach from your disk are read at the moment you send, in the same way.
Your tabs
The extension reads the addresses and titles of your tabs, which is a consequence of the tab permission, and uses them locally to route the prompt and to reuse a tab that is already open.
None of this is transmitted to us.
Reading the clipboard is an optional permission. It is requested separately and works only if you allow it.
Once your prompt is in a service's input field, that service receives it and handles it under its own privacy policy. We are not a party to that exchange.
What our web pages collect
Three pages are hosted on this site: the welcome page shown after installing, the rating page, and the uninstall page the browser opens when you remove the extension.
This privacy page is not one of them. It loads nothing from any third party and carries no analytics at all.
The three pages measure only an opening the extension makes at a moment in the life of an installation: when it is installed, when you rate it, and when you remove it. The extension marks such an opening with the installation context it puts in the page's address (see “How the pages know anything” below). A page opened any other way — from a bookmark, from a shared link or by typing its address — loads no analytics and sends nothing to Google Analytics or Yandex Metrica.
Lifecycle events
The three pages send three events to our own Google Analytics property:
| Sent with the event | What it is |
|---|---|
| Installation identifier | A random UUID created for this installation in this browser profile. It is not tied to an account, and a reinstall creates a new one |
| Event name | extension_install, extension_rating or extension_uninstall |
| Extension language | The interface language you selected |
| Extension version | The version installed |
| Installation month | The month of installation in UTC, for example 2026-09, or unknown |
| Rating | 1–5, only if you rated the extension |
| Rating at uninstall | 1–5, not_rated, or unknown |
| Lifetime | How many days the installation lasted, as a fractional number, and whether that number could be measured at all |
| Page address | The address of the page itself, without query string or fragment |
We do not send Google Analytics a user ID. We do not send the exact installation date or the exact time you rated — only the derived month and duration.
Google Analytics adds its own standard fields to these requests, such as the page title, the browser language, a session identifier, timing values and technical tag fields. Like any web request, it also reveals your IP address and browser information to Google.
In that property, enhanced measurement, Google signals and advertising personalisation are switched off, and advertising consent flags are set to denied.
Visit statistics
The same three pages run a Yandex Metrica counter, under the same rule as Google Analytics. Each measured opening records one page view with the page's address (without query string or fragment), the page's name and the interface language.
The counter also receives the same lifecycle events as the table above, under the same
rules and with the same values: extension_install, extension_rating
together with a second goal naming the number of stars, and extension_uninstall. The counter receives
no user ID and no installation identifier in any form.
The service adds its own technical fields and its own visitor identifier to these requests. Like any web request, the counter also reveals your IP address and browser information to Yandex.
The counter records clicks on outbound links and how long you spend on the page. Its other recording features are switched off in the page's own code rather than left at the service's defaults: there is no click map, so where you move or click on the page is not recorded, and there is no session recording (Webvisor) and no e-commerce tracking.
How the pages know anything
The extension opens these pages itself, and registers the uninstall address with your browser
in advance. It passes what the page needs in the fragment of the address — the part after
#: the installation identifier, the installation time, the extension's version,
name and language, its store identifier, and your rating. Browsers do not send the fragment to
the server. The page reads it once and strips it, together with any query string, from the
address bar before any analytics start, and only the values described in this section are then
sent.
Nothing in that fragment describes you. The name in it is the extension's own name, not yours.
To avoid counting the same event twice, each page keeps a short record in the site's local storage of which events it has already sent for that installation.
Other things the pages load
The pages load web fonts from Google, and the rating and uninstall pages embed a Google Form. Those requests go to Google and are visible to it. Anything you choose to type into the form is handled by Google Forms and by us as the form's owner. The pages are served by GitHub Pages, which sees ordinary web server request data. Ratings of 4 or 5 open the extension's Chrome Web Store page, which then applies its own policies.
What we never collect
Your prompts, your templates, the contents of your files and of the web pages you attach, the answers from AI services, the addresses of your conversations, your name, your email address and your account details are not part of anything we collect. There is no code path that sends them.
This does not make the collection anonymous. A random identifier is a pseudonym, and the analytics services still see your IP address and browser details.
Why we collect it
To know how many people install the extension, how they rate it, how many remove it and how long they keep it. We use that to decide what to fix and what to build next.
We do not use it for advertising, profiling or automated decisions about you, we do not sell it, and we do not combine it with data from other sources.
Legal basis
Where the GDPR applies, we rely on our legitimate interest in understanding how the extension is used and improving it. Our pages do not ask for your consent before the analytics start; you can prevent the collection by blocking cookies or scripts for this site, or by not opening the pages. You may object to this processing by writing to the address at the end of this policy — please read the limits in “Your rights” first.
Cookies and storage
- Google Analytics sets its own cookies in your browser. We do not change their lifetime; the service's default for its identifier cookie is two years, and your browser may shorten it.
- Yandex Metrica sets its own cookies and identifiers.
- Our pages use the site's local storage for the short record of already-sent events.
- The extension uses your browser's extension storage, as described above.
You can block or delete all of these from your browser's settings. Blocking them does not break the extension.
Who receives the data
- Google — Google Analytics, Google Fonts and Google Forms.
- Yandex — the Metrica counter.
- GitHub — hosting for the pages.
- The Chrome Web Store — when you install the extension or open its store page.
These companies process data on servers that may be outside your country.
How long it is kept
In our Google Analytics property, event and user data are retained for 14 months, and the retention period restarts when a new event arrives for the same installation. Data that has already been aggregated into reports is not necessarily removed when the underlying events expire.
Yandex Metrica keeps visit data according to its own terms. Data on your device stays until you clear the extension's data, clear the site's data, or uninstall.
Your choices
- Uninstall the extension. Collection stops. Removing it opens the uninstall page once, which sends the uninstall event.
- Clear the extension's data from its settings. This removes the local data and replaces the registered uninstall address with one that carries no installation context.
- Clear this site's cookies and local storage in your browser.
- Block cookies or scripts for this site, or use a content blocker.
- Do not grant the optional clipboard permission.
- Turn off the extension button or the page menu items in the extension's settings.
- Install Google's official Analytics opt-out browser add-on, if you prefer to stop Google Analytics across sites. It affects only what Google Analytics receives. The Yandex Metrica counter is a separate script and keeps recording the page views and lifecycle events described above, so to stop everything these pages collect, block cookies or scripts for this site instead.
Your rights
If you are in the EEA, the UK or another jurisdiction with similar law, you have the right to ask for access to your personal data, and for its correction, deletion or restriction, and to complain to your supervisory authority.
There is a practical limit you should know about. The only identifier we hold for the analytics data is a random UUID generated in your browser. We have no way to connect it to your name, your email address or your device, and you have no way to prove a given UUID is yours. We therefore cannot locate “your” records on request. What we can do is explain exactly what is collected — this policy is that explanation — and you can remove the local identifier yourself by clearing the extension's data or uninstalling it.
Requests: chatwithmultipleai@gmail.com.
Children
The extension is not directed at children under 13. We do not knowingly collect personal information from them. If you believe a child has provided us with personal information through our feedback forms, write to the address above and we will delete it.
Security
The pages are served over HTTPS and the analytics requests are encrypted in transit. The data we hold is limited to what this policy lists. No transmission over the internet can be guaranteed to be completely secure.
Changes to this policy
If what we collect changes, this page changes with it, and the date at the top is updated. Material changes will be described here rather than made silently.
Questions: chatwithmultipleai@gmail.com