What the extension does with page content
To know whether you're on a product page, a component of the extension reads the content of pages you
visit (for example structured product data, the product name, price, and image). This happens locally,
in your browser, and is used only to detect products and to compare the item you're viewing against
offers found elsewhere.
As an additional safeguard, detection is switched off on a curated list of major sensitive sites -
well-known banking, payment, sign-in, webmail, and health services. That list cannot include every
such site, so the protections that always apply are these: detection only reads a page locally to
recognize a product, the on-page prompt appears only on product pages, and a price check runs only
when you start one.
The extension does not modify the pages you visit beyond showing its own small "check price" prompt, and
it does not read page content for any purpose other than the price-comparison feature described here.
What happens when you run a price check
When you start a check, the extension uses the product tab - in your own, already-logged-in session -
for supported search providers and discovery on comparison sites, marketplaces, and retailer searches.
It can use Google Search, Shopping, and Lens; Bing Search, Shopping, and Images; and DuckDuckGo Lite
fallback. It sends generated product or catalog queries and market/language parameters to those sites.
As candidate offers are found, the extension checks their pages in parallel in up to the number of
temporary tabs you choose in Settings. It creates those tabs inactive inside the product's tab group;
they remain visible in Chrome and the side panel, can be opened while the check runs, and close when it
ends. A page that needs attention may be retried in the visible product tab. If worker tabs are
unavailable, checking continues serially in that tab. When the check finishes, the product tab returns
to the page where you started and the temporary group is removed.
The tab activity described above is visible in Chrome. During the same active check, the extension can also make bounded direct GET
requests to candidate retailer/comparer pages and product-image hosts. These requests verify product
identity and current price, discover a retailer's search URL, resolve promising comparer links, recover
strict canonical product evidence, or compute an image fingerprint locally. They contain no Muchita
account or analytics identifier, but the destination receives the requested URL and ordinary connection
data. Muchita AI does not receive a copy of your searches or the pages visited during a check.
Visual search can read up to 12 MB of the product image in your browser and supply those bytes to the
visible Google Lens or Bing Images file input. That image is uploaded to the selected search provider,
not to Muchita. Result cards can also load product images from their hosts and request a retailer icon,
falling back to Google's favicon service with the retailer domain; those image requests use no referrer.
If a search provider shows a "verify you're human" (CAPTCHA) check, the extension surfaces it so you can solve it
yourself and then continues. It never bypasses, evades, or automatically solves these checks.
Price research has no schedule, alarm, or automatic restart. A saved product is checked only when you
press Refresh prices, which opens its product page in a visible tab before research begins. Chrome may
keep an explicitly started check running after the side panel closes; if the service worker is
interrupted, the extension stops that check instead of restarting navigation on its own.
Local purchase confirmation
Purchase confirmation is on by default so Muchita can count what you actually saved. It begins only
after you open an offer through Muchita. The extension then follows that retailer tab and any checkout
tab it opens, and checks only pages belonging to the same retailer. It does not inspect unrelated tabs,
a different retailer, or payment-provider pages. You can turn the feature off at any time in Privacy
settings; doing so immediately clears pending monitoring and prevents new purchase records and purchase
analytics.
A confirmation check reads only an order identifier when available, total, currency, and the type of
confirmation signal. Raw page content is not retained. The raw order identifier is never stored: it is
transformed immediately into a local idempotency key so a reload cannot count the same purchase twice.
The pending local record may contain the offer URL, product title, expected and source prices, currencies,
and list references. A confirmed local record may contain the idempotency key, offer URL, paid total and
currency, source price, calculated saving, list references, and time.
Pending records expire after 48 hours and are capped at 20; confirmed purchase history is capped at 50.
Confirmed purchase details attached to saved products and savings totals by currency remain in local
extension storage until that storage is cleared or the extension is removed. A one-time purchase result
shown by the panel is deleted after the panel consumes it. Turning the feature off does not silently
delete already confirmed history.
Muchita AI never receives order identifiers, idempotency keys, purchase totals, savings amounts, product
titles, URLs, merchants, or raw confirmation content. If optional analytics is enabled, purchase events
contain only coarse attribution, the confirmation-signal category, currency, a savings-percentage range,
or a fixed rejection reason. Feedback has a separate allowlist and never includes order identifiers or
purchase totals.
Information sent over the network
The extension and optional uninstall feedback page make a small number of network requests:
- Currency rates. To compare prices in your preferred currency, the extension fetches public exchange-rate data from jsDelivr or
latest.currency-api.pages.dev. The request path contains only the base currency code; the provider also receives ordinary connection data such as IP address and user agent.
- Search and comparison. Generated product/catalog queries and market/language parameters go to Google, Bing, DuckDuckGo fallback, and supported comparison, marketplace, and retailer pages. Search and discovery use the visible product tab; candidate offers are checked in temporary grouped tabs visible in Chrome. Bounded helper GETs can request candidate pages during the active check.
- Product images and icons. To confirm two listings are the same item, the extension fetches images and computes a visual fingerprint locally. Visual search can upload product-image bytes to Google Lens or Bing Images. UI image loads reach their image host; retailer icons can fall back to Google's favicon service with the retailer domain. Images are not uploaded to or stored by Muchita.
- Feedback (optional). If you submit a better-price report, the extension sends the checked and reported page URLs plus the allowlisted source and offer context described below. If you submit general feedback, it sends the category you chose, an optional note of up to 500 characters, the panel area, and any allowlisted current-product context. After removal, Chrome can open Muchita's public uninstall feedback page with the extension version in its URL. Opening the page submits no response; pressing Send feedback sends one selected reason, the optional note, that version when present, a random report ID, timestamp, and app/surface tags. The uninstall page does not load optional website analytics.
- Usage analytics (optional). Only after you explicitly allow analytics, the extension sends the pseudonymous events described below directly to Google Analytics. This is separate from data sent to Muchita AI.
Product context in extension reports is restricted to store host and canonical URL; name, brand, catalog identifiers,
image URL, category, color, and selected-variant evidence; item price or range, displayed price,
currency, shipping, pickup, availability, and condition; bounded price provenance, tax basis, and
commercial-model fields; and page language. Each report also contains a random report
ID, client timestamp, the shopping app tag, and extension version when available.
Reports, including uninstall feedback, never include the analytics identifier, order identifiers, purchase totals, search queries,
raw page text or HTML, list notes, browsing history, or arbitrary future product fields. Our feedback
service runs on Cloudflare (a Worker plus a database) at feedback.muchita.ai. The database
stores the reviewed JSON and request user-agent; the Worker does not read or persist the request IP,
although Cloudflare necessarily processes connection data to deliver the request. Please do not put
sensitive information in the optional note.
A report you submit may be read only to investigate it, respond, improve or secure the extension, or prevent abuse.
Optional usage analytics
To understand whether features work and improve the extension, you can turn on
pseudonymous usage analytics in Settings. It is off by default - no
analytics identifier is created and no analytics request is made unless you allow it.
After your first completed price check, the extension asks once whether to allow it,
with equal-weight Allow and No thanks choices and no pre-selected option.
If you decline (or simply never enable it), no analytics request is made and no analytics identifier is
stored on your device, and we don't ask again - you can still turn it on later in Settings.
When enabled, the extension sends events about price-check progress and outcomes; result
and report use; list, saved-item refresh, and share actions; coarse purchase outcomes;
feedback and rating actions; and bounded runtime health. The payload may contain a random
identifier stored on your device, random check and session identifiers, extension version
and environment, currency, and coarse counts, timing, savings, confidence, freshness, and
outcome ranges. If you arrived through a Muchita campaign and installed within seven days,
it may also contain the campaign, campaign ID, source, medium, ad-content label, and landing
locale transferred from muchita.ai after installation. This never includes a Google click ID,
search term, or advertising identifier. It never contains product titles, URLs, searches, merchant names, order
identifiers, purchase totals, notes, free text, or raw page content. The analytics
identifier is not included in feedback reports and is not mapped to a Muchita account.
Events are sent directly over HTTPS to the Google Analytics Measurement Protocol using
Google's EU collection endpoint. Each request explicitly denies advertising-user-data and
ad-personalization consent. Muchita does not use analytics for advertising, profiling, or
sale. Google necessarily receives ordinary connection data such as the request IP address
and user agent and handles it under Google's privacy terms.
Muchita configures user-level and event-level Analytics retention to two months and turns
off retention reset on new activity. Google states that this control does not remove its
standard aggregated reports. Turning analytics off deletes the local random identifier and
campaign attribution and stops future events immediately; previously processed events expire under the configured
retention. Because there is no account mapping, Muchita cannot reconnect those prior events
to you after the local identifier has been deleted.
What we do not do
- No user accounts and no sign-in.
- No advertising and no advertising identifiers. Analytics are optional, off by default, pseudonymous, and limited to the allowlisted product-use events described above.
- No selling or renting of personal information, and no building of advertising or behavioral profiles.
- No affiliate links, no affiliate cookies, and no changes to checkout or payment.
- No bypassing of CAPTCHAs, paywalls, or login restrictions.
Muchita Shopping's use of information received from Chrome and Google APIs adheres to the
Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used or
transferred only to provide or improve the extension's single-purpose comparison feature,
for security or legal compliance, or as otherwise permitted by that policy; never for
personalized advertising, lending, or sale.
Permissions and why they're needed
- Access to websites (host access). Products can appear on any online store, and a check must read prices on whichever retailers carry the item, so the extension needs access to web pages generally. It uses this for local product detection and user-started price comparison, including bounded page/image requests during an active check, and it is excluded from listed sensitive sites.
- Tabs, scripting, and web navigation. Used to navigate the product tab for search and discovery; create, read, focus, and close a bounded number of inactive temporary tabs that check candidate offers in parallel; detect when pages load; retry pages needing attention visibly; and restore the product page afterward.
- Tab groups. Used to keep the product tab, temporary offer-check tabs, and deal pages together. Temporary tabs close and the group is removed when the check ends.
- Storage. Used for the local records described below: settings and consent, lists, notes, offers, history, purchase records, live/recent comparisons, report preferences, provider/search memory, exchange rates, and unsent feedback retries.
- Side panel. The price-comparison results are shown in Chrome's side panel.
Data storage and retention
Settings and consent choices; lists, products, URLs, images, notes, offers, statuses, price history, and
savings ledgers; purchase records; recent comparison snapshots; report preferences and filters;
provider/comparer/search-recipe memory; and exchange-rate data are stored locally. Session storage also
keeps live/finished comparison state, tab-group mappings, bounded performance records, and kept-panel
state for the browser session. The extension does not create IndexedDB, CacheStorage, sessionStorage, or
extension cookies. Chrome's ordinary HTTP cache may retain page, image, or currency responses under
browser/site cache rules.
Price history is capped at 60 points per item; recent completed comparisons at 10 distinct products;
pending purchase records at 20 with a 48-hour expiry; confirmed purchase history at 50; provider,
comparer, and search-recipe memories at their documented bounded limits; and terminal performance
records at 16 per browser session. Report filter preferences are not currently pruned when an old
comparison is evicted. Other user-managed local records remain until removed individually, reset, or
uninstall. Turning analytics off deletes its local random identifier, first-open timestamp, and campaign attribution.
Before sending, the extension stores the newest 50 reviewed feedback payloads locally. A failed send
remains queued without a time-based expiry and is retried when the panel next opens or feedback is
submitted again. It is removed after the service acknowledges it, an older report is displaced by the
cap, extension storage is cleared, or the extension is removed. Submitted feedback is retained by
Muchita AI only as long as reasonably needed to analyze and improve the product and prevent abuse.
The uninstall feedback page has no extension storage and does not keep or retry a failed submission.
Google Analytics user-level and event-level data is configured for two-month retention
without resetting the period on new activity; Google's standard aggregated reports are not
governed by that event-level retention control.
Third-party services
- Google Search, Shopping, Lens, and favicon service.
- Bing Search, Shopping, and Images; DuckDuckGo Lite as an optional search fallback.
- Supported comparison sites, marketplaces, online retailers, and product/image hosts requested during an active check.
- A public exchange-rate content-delivery network (jsDelivr / a currency-rates API) for converting prices.
- Cloudflare, which hosts muchita.ai and our optional feedback service.
- Google Analytics - only if you opt in, and only the pseudonymous events and ordinary connection data described above.
These third parties process information according to their own privacy practices.
Children
Muchita Shopping is not directed to children under 13, and we do not knowingly collect personal
information from children under 13.
Changes to this policy
We may update this Privacy Policy when the extension or our practices change. The effective date at the
top shows when it was last updated.
Contact and deletion
Use Settings → Privacy → Reset all local data to stop active work and clear
extension-managed local/session data, or uninstall the extension. The data controller is Zahi Cohen,
operating under the Muchita AI name. For privacy questions or requests about identifiable feedback stored
by Muchita, contact privacy@muchita.ai, or see
Muchita AI data deletion.
