URL Editor Pro / Privacy

Legal · Privacy

URL Editor Pro Privacy Policy

URL Editor Pro is a fully-offline tool. We do not collect, transmit, sell, or share any of your data. There is no server. There is no account. Everything you do in the extension stays inside your own browser.

Effective · Last updated · Extension version 1.4.0

The short version

✓No server. The extension makes no outbound HTTP requests of its own.
✓No account. Nothing to sign up for.
✓No telemetry. No analytics, no crash reports, no fingerprinting.
✓No content scripts. We never read page contents.
✓chrome.storage only. Rules and settings live on your device.
✓Sync is opt-in. If you enable it, Chrome (not us) replicates rules across your account.

Jump to section

Data handled Permissions Cross-device sync all_urls Never collected Children Changes Your rights Contact

01 Data the extension handles

All of the following is processed locally on your device only:

Data type Where it comes from Where it lives
Active tab URL chrome.tabs when popup opens RAM only — not persisted
Regex rules Your input in the Rules tab storage.local + .sync if opted in
Environment groups Your input in the Environments tab storage.local + .sync if opted in
URL annotations Your input in the Notes tab storage.local only — never synced
URL history (last 25) Auto-recorded when you Apply & Navigate storage.local only — never synced
JWTs & Base64 strings Your input in the Tools tab RAM only — never persisted
HMAC signing secrets Your input when signing JWTs RAM only — never persisted, never transmitted

The extension never sends any of the above to a remote server, makes outbound HTTP requests of its own, injects scripts into pages, reads cookies, tracks browsing history, or uses analytics or crash reporting.

02 Permissions, in plain English

declarativeNetRequest Hands your URL rewriting rules to Chrome. Chrome runs them; we never observe matches.
declarativeNetRequestFeedback Used in development builds only to log rule matches to the developer console. Not active in the published version.
storage Reads and writes your settings to chrome.storage (Chrome's own per-extension storage area).
tabs Reads the URL of your currently active tab so the popup can show what you're editing.
webNavigation Re-applies your rules when Chrome serves a URL from the back/forward cache (otherwise rules silently fail on cached pages).
host_permissions: <all_urls> Required by Chrome so your rules can match any site you choose to rewrite. The extension itself never reads page contents.

03 Cross-device sync — what happens if you turn it on

In Settings → Cross-device sync, you can opt in to mirroring your regex rules and environment groups to your Chrome account. When enabled:

  • →Chrome (not us) replicates the data across browsers signed into the same Google account, using chrome.storage.sync.
  • →The data flows through Google's infrastructure under Google's privacy policy — not ours.
  • →Annotations and URL history are never synced — they stay on the originating device.
  • →Disabling sync stops future writes; previously-synced data is preserved on your account so re-enabling on another device is non-destructive.

Sync is off by default. We don't see your synced data — it's between you and Google.

04 The "host permission" question

Chrome marks <all_urls> as a sensitive permission. Here's what it does and doesn't mean for you:

What it does

Allows your user-defined regex rules to match any URL you visit. Without it, you'd have to pre-declare every domain you might ever want to rewrite, which would defeat the purpose.

What it doesn't do

  • ✗Read page contents
  • ✗Inject scripts into any page
  • ✗Observe network responses
  • ✗Fingerprint you or build any dataset

The rule engine is fully opt-in. With no rules configured, the extension does nothing on any website.

05 Data we never collect

The Chrome Web Store requires explicit disclosure of what's collected. To be thorough:

  • ✗Personally identifiable information
  • ✗Health or biometric information
  • ✗Financial or payment information
  • ✗Authentication credentials
  • ✗Personal communications
  • ✗Location data
  • ✗Web browsing history
  • ✗User activity (clicks, mouse movement, keystrokes outside the popup)
  • ✗Website content

A note on JWTs and secrets: the JWT inspector and signer accept tokens and HMAC secrets as input. These never leave your browser's memory. They are not persisted to storage, not transmitted anywhere, and are discarded when you close the popup.

06 Children

URL Editor Pro is a developer tool not directed at children under 13. We do not knowingly collect any data from anyone, and we do not differentiate by age because we don't collect data in the first place.

07 Changes to this policy

If a future version of the extension changes its data practices in any meaningful way, we will:

  1. Update this document with a new "Last updated" date.
  2. Note the change in the Chrome Web Store version notes.
  3. Bump the major or minor version number.

08 Your rights

Because we don't have a server, we don't have any data about you to delete on request. To remove all extension data from your device:

  1. Right-click the extension icon → Remove from Chrome — or visit chrome://extensions and click Remove.
  2. If you had cross-device sync enabled, also visit chrome://sync and review your synced extension data.

This gives you complete control. There is no backend account to delete.

09 Contact & Grievance Officer

For privacy questions, bug reports, or feature requests:

DealsGroup — Grievance Officer

Email: [email protected]

1/3, Arihantkumar Jain, Jorawarpura, Nokha

Bikaner, Rajasthan — 334803, India

We will endeavour to respond to grievances within 30 days of receipt, as required under the IT Act 2000 and applicable rules.

See also: URL Editor Pro homepage · Terms · Support