Support — URL Editor Pro

01 Frequently asked questions

Does the extension send my URLs to a server?

No. There is no server, no telemetry, and no analytics inside the extension. Every feature — parameter editing, regex matching, JWT decoding, QR generation — runs locally inside your browser. The extension never makes outbound HTTP requests of its own.

Why does it need permission to "read and change all your data on all websites"?

That's Chrome's standard wording for the <all_urls> host permission, which the rule engine needs so your regex rewrites can match arbitrary domains. The extension does not request the scripting permission, ships no content scripts, and never reads page content. With no rules configured, the extension does nothing on any site.

Will my rules sync across devices?

Only if you opt in. Open Settings → Cross-device sync and turn it on. Sync uses Chrome's own account storage (chrome.storage.sync) — never our infrastructure. Annotations and URL history stay local to the originating device.

How many regex rules can I have?

Up to 5,000 dynamic rules per profile — the maximum Chrome's declarativeNetRequest API permits. You can split them across rule profiles and toggle profiles on or off.

Are JWT signing secrets persisted?

No. The HMAC secret you type into the JWT signer lives in the popup component's React state and is discarded the moment the popup closes. It is not written to chrome.storage, never transmitted, and never visible outside the signer panel.

Does it work in Firefox / Edge / Brave?

Edge and Brave: yes — both run Manifest V3 extensions. Firefox: not yet, because their declarativeNetRequest implementation has different rule semantics. A Firefox port is on the roadmap.

What's the minimum Chrome version?

Chrome 109 or newer. Earlier versions lack reliable Web Crypto support inside service workers, which the JWT signer relies on.

How do I reset everything?

Open Settings → Reset all data, or visit chrome://extensions, click Remove, and reinstall. Both wipe rules, environments, annotations, and history.

02 Troubleshooting common issues

A regex rule isn't firing

Open the rule and use the Test box at the bottom — paste an example URL and click Run.
Confirm the rule profile is Enabled in the Rules tab header.
If the URL is served from the back/forward cache, ensure the webNavigation permission is granted (Chrome may have prompted you to re-approve after an update).
Check for rule conflicts — earlier-priority rules can match first and short-circuit later ones.

The popup is blank or shows "Failed to load"

Right-click the extension icon → Inspect popup and check the console for errors.
Reload the extension from chrome://extensions.
If errors mention storage or quota, you may have hit the chrome.storage.sync 100KB limit — disable sync or trim rules.

JWT signer says "Invalid algorithm"

Web Crypto must be available in the service worker context. Update Chrome to 109+ and ensure no enterprise policy has disabled subtle crypto.

QR batch ZIP is empty

Confirm at least one valid URL is in the input list (one per line, no blank lines mixed in). The renderer skips lines that fail URL parsing.

Sync isn't replicating across devices

Both devices must be signed into the same Google account with Chrome sync enabled and Extensions selected as a sync category. Sync may take up to a few minutes to propagate. Check chrome://sync-internals for state.

03 Permissions, in plain English

Each permission has a single, narrow purpose. Cross-reference with the source on the Chrome Web Store listing.

declarativeNetRequest Runs your URL rewrite rules inside Chrome's native rule engine.

declarativeNetRequestFeedback Logs rule matches in the dev console — debugging only, unpacked builds.

storage Saves rules, environments, annotations, and history to chrome.storage.

tabs Reads the URL of the active tab so the popup can show what you're editing.

webNavigation Re-applies rules to URLs served from Chrome's back/forward cache.

host_permissions: <all_urls> Required by Chrome so user-defined rules can match arbitrary domains. We never read page content.

04 Where your data lives

Everything is local. To export, import, or wipe — use the controls in Settings inside the popup.

→Rules & environments: chrome.storage.local (and chrome.storage.sync if you opt in).
→Annotations & URL history: chrome.storage.local only — never synced.
→JWTs & HMAC secrets: never persisted; popup memory only.
→Removing the extension deletes all chrome.storage.local data immediately.

For the full data-handling story, see our privacy policy.

05 Reporting a bug

Email us at [email protected] with the subject line URL Editor Pro - Bug report. To help us reproduce quickly, please include:

1.Extension version — visible in the popup header (e.g. v1.4.0).
2.Chrome version — chrome://version.
3.OS — Windows / macOS / Linux + version.
4.Steps to reproduce — the shorter and more specific, the faster the fix.
5.Expected vs. actual — what you thought would happen vs. what did.
6.Console errors — right-click popup → Inspect → Console. Copy any red text.
7.A redacted rule export if the issue is rule-related (Settings → Export rules, then strip anything sensitive).

Please don't paste real JWTs or secrets into bug reports. Reduce them to a non-sensitive example token if you can — we don't need the original to debug.

06 Feature requests

We're a small team and prioritize ruthlessly — but every request gets read. Email [email protected] with the subject URL Editor Pro - Feature request.

Useful things to include: the workflow you're trying to support, a concrete example URL or rule, and whether an existing feature gets you most of the way there.

07 Contact

For anything not covered above:

DealsGroup

Email: [email protected]

1/3, Arihantkumar Jain, Jorawarpura, Nokha

Bikaner, Rajasthan — 334803, India

We aim to respond within 3 business days.

URL Editor Pro Support

Need help fast?