Support
Purix strips known tracking parameters — utm_*, fbclid, and
site-specific tokens on sites like Amazon, YouTube, X/Twitter, eBay, AliExpress, Walmart,
LinkedIn, and Instagram — from links as you browse, click, and copy them. Common questions
are below; anything else, email
contact@abhijitbansal.com.
A site broke — how do I disable Purix there?
Open the Purix popup while you're on the affected site and turn on Disable on this site. That switch is per-hostname: it turns off navigation cleaning, link rewriting, copy interception, and stats collection for that one site only — everywhere else keeps working normally.
The disabled state is read from local storage as soon as the page starts loading, so it survives a reload. Turning it back off (re-enabling Purix on that site) takes effect immediately, without needing to reload the tab.
If the whole browser needs Purix out of the way for a moment instead of just one site, use the main on/off switch in the popup — that disables cleaning everywhere until you turn it back on.
How do I add my own rule?
Open the dashboard (popup → Open dashboard, or the Settings link in the popup footer) and go to Custom rules. Two kinds of rule are available, layered on top of the built-in rule set:
-
Strip — remove an extra parameter Purix doesn't already know about.
Leave Host blank to strip it everywhere, or set a host to scope it to one
site. Turning on Prefix matches any parameter starting with the text you
enter (for example, an
aff_prefix rule matchesaff_id,aff_src, and anything else starting withaff_). - Never strip — protect a parameter a site actually needs, scoped to a host. This is useful when a site-specific built-in rule is slightly too aggressive for your use of that site; a "never strip" rule for that host always wins over a strip rule for the same parameter.
q, v, t, id,
p, page, list, index, th,
psc) protects parameters most pages need to function. A global strip rule (no
host set) can't override the keep-list — the dashboard warns you if a rule you're adding
would try to. A rule scoped to a specific host can override the keep-list for that
host only, since you're making a deliberate, narrow exception rather than a blanket one.
Custom rules, like everything else Purix stores, live in local storage on your device and are included in the data export.
Why do the counts on Chrome look different from what was actually cleaned?
On Chrome, navigation cleaning runs through a static Declarative Net Request ruleset that redirects a tracked URL before the request ever leaves the browser — which is great for speed, but it means Chrome doesn't let a Web-Store-installed extension see that a redirect happened in real time. Purix's counter for navigations is therefore best-effort: it re-runs the same cleaning logic in the background to estimate what was stripped, and that estimate can occasionally drift slightly from what the ruleset actually stripped, if the two interpretations disagree at the edges.
Link clicks and copies don't have this gap — rewriting an <a href> or
intercepting a copy always runs Purix's own code directly, so those counts are exact on
every browser, Chrome included. Firefox's navigation count comes from the same code path
that performs the redirect, so it matches what happened. Safari's does too, with one
narrow exception: a very tight internal timing race can occasionally drop a single count
(see Known limitations).
If you want a number you can fully trust on Chrome, count link clicks rather than address-bar navigations — right-click a tracked link and choose "Copy Link Address" or Purix's own "Copy clean link," and it will register every time.
How do I export or reset my data?
On the dashboard, under Your data:
- Export data JSON — downloads everything Purix has stored (settings, usage counters, activity log, custom rules) as a single JSON file, so you can inspect exactly what's kept.
- Reset stats — clears your usage counters. Settings and custom rules are unaffected.
- Clear log — clears the recent activity log. Entries also expire automatically after 30 days on their own.
Uninstalling the extension removes all of this data too — none of it is stored anywhere outside your browser's local storage on that device.
Known limitations
Copying a URL straight from the address bar isn't cleaned
Browsers don't give extensions a way to intercept a copy that happens entirely inside the address bar. Use the popup's Copy clean URL of this page button instead — it computes the clean URL and writes it to the clipboard for you.
A page that writes to the clipboard with JavaScript can bypass Purix
Purix intercepts the browser's native copy event (keyboard shortcut,
right-click Copy, etc.). A site that calls navigator.clipboard.writeText()
directly from its own JavaScript, without going through that event, isn't seen by Purix.
Safari's very first request to a tab may briefly load the tracked URL
Safari navigation cleaning uses a content script that replaces the page at the earliest possible moment, rather than a pre-request redirect (see fig 02 on the home page). The original URL can be requested once before the content script fires, and on a very tight internal timing race the count for that navigation can be missed — expected behavior, not a bug.
No "Copy clean link" context-menu item on Safari for iOS
The context-menu API isn't available to extensions on Safari for iOS. Use the popup's copy button or link rewriting on that platform instead.
How do I report a bug?
Email contact@abhijitbansal.com with:
- Browser and version (Chrome, Firefox, or Safari — macOS or iOS)
- The Purix version, shown in the popup footer
- The exact URL you tried (or a close, non-sensitive substitute if the real one is private)
- What you expected to happen, and what actually happened
If a specific link isn't being cleaned the way you'd expect, that's useful signal about the rule set — include it, since Purix is blocklist-only and deliberately leaves anything it doesn't recognize untouched.