MUGA receives URLs when you click links or right-click to copy a clean link. These URLs are cleaned inside your browser. MUGA never silently sends your data anywhere. Any feature that contacts an external service requires your explicit action and is disclosed here.
Your extension preferences (toggles, blacklist, whitelist, language) are stored in chrome.storage.sync. This means they sync across your own devices via your browser account. They are never visible to MUGA.
Anonymous usage counters (URLs cleaned, parameters removed, referrals spotted) are stored locally on your device via chrome.storage.local. These counters are never transmitted anywhere. Session data (debug logs, per-tab badge counts, recently cleaned URLs) is stored in chrome.storage.session and is automatically cleared when the browser restarts.
MUGA strips tracking parameters (UTMs, fbclid, gclid, and others) from URLs automatically. This happens locally. The removed parameters are not logged, transmitted, or stored anywhere.
The following features are enabled by default and can be individually toggled in Settings:
<a ping> attributes from links so the browser does not send tracking beacons when you click.All of these operate entirely within your browser. No external requests are made.
MUGA can add affiliate tags to URLs that carry none when you visit a supported store. This is how an independent developer earns income from the tool he maintains. If you opted in during onboarding, this feature is active. You can disable it at any time in Settings.
When you visit a supported store, MUGA checks the URL locally to see if an affiliate tag is already present. If not, and if you have the option enabled, MUGA modifies the URL before navigation to include our affiliate tag. This URL modification happens locally. No external request is made to determine whether to inject.
If you enable "Remove all affiliate tags from other sources", only third-party tags are removed. Our own tag is always preserved. MUGA never replaces another affiliate's tag with ours in the same operation.
MUGA evaluated affiliate programs for AliExpress, SHEIN, Zalando, Fnac, MediaMarkt, PcComponentes, and El Corte Ingles. All of them require redirect-based tracking: your click is routed through an external server (Awin, Admitad, ShareASale, or Skimlinks) before reaching the store. That server logs your visit, your referrer, and your destination.
We do not believe forcing users through external tracking servers is necessary or fair. Redirect-based affiliate tracking is a choice these networks make, not a technical requirement. We rejected every one of these programs and chose to give up that revenue rather than compromise your privacy.
Because these stores rely on redirect-based affiliate networks, MUGA actively strips their affiliate tracking parameters (awc, wt_mc, lgw_code, and others) from URLs you visit. These parameters were placed by the same redirect servers we refuse to use. When possible, MUGA also unwraps affiliate redirect URLs (e.g. from Awin or Admitad) and sends you directly to the store, so the intermediary server is bypassed entirely.
Only stores that support direct URL parameter injection -- where the affiliate tag is a simple query parameter added locally, with no server involved -- are compatible with MUGA. Currently: Amazon and eBay. We believe users deserve the freedom to reach any store directly, and we will apply this same standard to any affiliate program we evaluate in the future.
When you navigate to a store via a MUGA-modified URL, the store's own analytics may record the visit as originating from an affiliate link. This is standard affiliate behaviour and is governed by the store's own privacy policy, not MUGA's.
MUGA is a registered participant in affiliate programs including Amazon Associates and others. These programs have their own terms of service and privacy policies.
MUGA requests the following browser permissions:
MUGA is licensed under the GNU General Public License v3 (GPL v3). The complete source code is public. If you want to verify that this privacy policy accurately describes the extension's behaviour, read the code. It's all there.
Questions or concerns: open an issue at github.com/yocreoquesi/muga/issues.