The browser extension: the tour
The extension is URnetwork inside the browser, and the ur.io web app is its control plane: one product, two halves. This page is the deep dive: the proxy machinery in each browser, the controls with their shipped defaults, what the kill switch does and does not promise, and what to check when something breaks. For the network behind it, who the providers are and what each party can see, read the overview. For store links, sign-in, and first connect, start with getting started in the browser.
The framing to keep, always: this is a browser proxy, not a VPN. A proxy is a middleman that fetches sites for the browser, so sites see its address instead of yours. The extension configures the browser's own proxy settings, so it governs exactly what that browser sends, no more. Covered: every tab and window of that browser, incognito too, on Chromium always and on Firefox once you allow it in Private Windows. Not covered: other browsers, your mail app, system updates, everything else, unprotected and unbroken alike. Install it per browser; whole-device coverage is the URnetwork apps' job (Android, iOS, macOS, Windows, Linux): same account, same kill switch, one layer down.

Settings at a glance
The extension keeps its surface small on purpose. Two controls, both in the popup:
| Setting | Default | Effect | Main cost |
|---|---|---|---|
| Kill switch | Off | blocks browser traffic when the proxy drops, instead of falling back to your direct connection | tabs error during an outage |
| Geolocation override | Off | the browser's geolocation API reports your exit city instead of your real position | sites you want your real location for need it off; staying current needs an open ur.io tab |
Caveats that go with the table:
- Two app switches have no browser equivalent, by design. There is no Post Quantum Encryption here, because the extension has no client-to-provider session to seal; the full carve-out is under Data collection below. And there is no Strong Anonymization switch, because direct mode is forced off on the hosted proxy device the extension runs on: no provider can ever be handed your real address.
- Once you turn it on, the kill switch persists across browser restarts, so an outage keeps you blocked, not exposed, until you disconnect or the path recovers.
- Running out of data is not an outage, and the switch does not decide it: whichever way it is set, the proxy stays set and the popup says so (see Out of data).
How it works
The extension is Manifest V3 on every browser. Each install holds one hosted URnetwork proxy at a time, created on its first connect and applied again on later ones, and hands the browser that single proxy. The plumbing differs, because the browsers' APIs do:
- Chrome and Edge (and Chromium-family browsers generally) use the proxy settings API: the extension sets the proxy as the browser's one fixed proxy, with a bypass list for local addresses and the URnetwork API. Setting it claims the browser's proxy configuration, which is also why two proxy extensions cannot coexist (see troubleshooting): the extension sets it only while the browser lets it, and when another extension holds the setting with priority, or policy fixes it, it does not connect and the popup says which. A fixed proxy has no fallback of its own, so while it does not answer, requests fail until the health checks below act. The extension never touches OS settings and undoes cleanly: disconnect releases the claim, so the browser's own proxy settings apply again (a system or corporate proxy, or none), and uninstall removes it.
- Firefox has no equivalent settings handoff, so it uses
proxy.: the extension is consulted per request and answers with that one proxy. While the kill switch is off, as it ships,onRequest directfollows the proxy in that answer, so a request the proxy cannot carry goes direct; armed, the answer is the proxy alone, and while it is down, requests fail.
There is no Safari version, because Safari lacks these APIs. On Apple devices the app covers everything, Safari included.
Browsing exits through a small window of providers at once: member devices whose owners opted in and participate in the UR protocol. "Your exit IP" is plural, and per-site affinity keeps each site on one exit, so your bank sees one consistent address.
The URnetwork SDK ships as WebAssembly inside the extension package. Provisioning, location listing, and API calls all run locally. Nothing executable is fetched at runtime; what the store reviewed is what runs.
The web app is the extension's control plane; they are one product. Sign in once at ur.io and the page and the extension talk over a documented bridge: a short verb protocol (SETUP, CONNECT, DISCONNECT, SET_LOCATION, kill switch, geo sync) carried by window., the only channel that works on Chrome, Edge, Brave and Firefox alike. SETUP hands the signed-in session straight over, which is why setting up from the app never asks you for an auth code. The split of labour is real: the extension mints the proxy session and installs the browser proxy, while the app holds the live device. Changing location in the app re-routes it with no browser reconnect, and each surface shows what you did in the other.
The bridge is deliberately narrow. It runs only on ur.io and manager. pages; no other site can talk to the extension. One other script does load on every page, the geolocation override, and it stays inert, natives untouched, unless you turn it on (below).
Signing in requires an account, since usage is metered per account: an email or phone number with its password, one of ur.io's SSO options, a wallet signature, or an auth code generated on a device you are already signed in on. The email-free routes here are the wallet and the auth code; the one-tap email-free Instant Account is created in the phone and desktop apps, and the extension picks that account up like any other. Free is a daily data allowance; Pro adds a large monthly one ($5/month or $40/year; current numbers at ur.io/products).
Kill switch semantics
What it does: if the proxy connection drops while the kill switch is on, the extension blocks the browser's traffic instead of letting the browser quietly fall back to your direct connection and expose your real address mid-session.
- It is off by default: turn it on in the popup, where its subtitle changes from Traffic may leak on failure to Blocks traffic on failure.
- Enforcement is the browser's own proxy rule: armed, it has no "otherwise go direct" escape hatch, so requests fail rather than fall back. It persists across browser restarts. You come back blocked, not exposed.
- If it triggers, only this browser stops (tabs error; the popup shows why). The rest of your computer never went through it.
- Leaving it off means failing open: a dropped connection reverts you to the browser's own connection, direct for most, visibly in the popup but silently in your tabs. Acceptable only where a leak is an inconvenience, not a harm.
- Out of data is the exception that holds either way: the proxy stays set and nothing falls back (see Out of data).
- Scope limit: it blocks browser traffic, which is all an extension can govern; it is not a system firewall. Local addresses (localhost, printers) bypass on purpose, and WebRTC (in-browser voice/video) can open connections that ignore proxy settings, a gap in every proxy extension; browsers can restrict it.
Geolocation override
Two signals: your IP address now says Amsterdam, but the browser's geolocation API, answered from OS signals like nearby Wi-Fi, still reports where your body is. Sites that compare the two see the contradiction. The override fixes the second signal so both stories agree:
- Off by default. Nothing changes until you enable it in the popup.
- Enabled, it answers at
document_in all frames, so the geolocation API gives your exit location before any page script can ask, including in iframes trying to race it. The coordinates are the city of your oldest connected provider, and they reach the extension over the app bridge: the extension holds no device of its own, so an open ur.io tab is what keeps the position current.start - Disabled, it says nothing at all: the page keeps its native geolocation and no site is handed a fresh signal that you run an extension. Flip it off when you want sites to see your real location (maps, delivery).
Health pings and the degraded state
While connected, the extension fetches a lightweight endpoint (my-ip-info on the URnetwork API) through the proxy every minute, negligible even against the free allowance, and again right away when the browser reports a proxy error. That proves the path works end to end, not just that the settings applied. A fetch that fails or takes longer than eight seconds counts as a failure, and a success resets the count. One check runs at a time: proxy errors that arrive while one runs share it. In an outage every page's requests fail, and so does the check's own fetch, so a failure counts at most once every 45 seconds, and a proxy error in that time starts no check: a burst of errors counts once, and three failures in a row take the schedule's two minutes. After three, the kill switch decides:
- Off, as it ships: the extension takes the proxy off, releasing the browser's proxy setting, and the browser connects without URnetwork. Nothing reconnects on its own: the popup shows Disconnected with the reason under the button, and Connect applies the install's proxy again, or creates a new one if the server no longer has it.
- On: the proxy stays set and the browser's traffic stops until the proxy answers. That is the degraded state: the popup's status line reads Proxy not answering, with the reason under the button. Nothing reconnects in the meantime; the next check that succeeds returns it to Connected.
Until the third failure, a Chromium browser's requests fail at the silent proxy whichever way the switch is set, since a fixed proxy has no fallback of its own. On Firefox with the kill switch off, each request falls back to direct by itself, so the checks pass over the direct path and the proxy stays set; the popup's Proxy active but network unreachable. note is the sign (see troubleshooting).
Degraded is not a leak. You are still pointed at the proxy, and a dead path blocks rather than exposes. To browse before it recovers, disconnect: that goes back to the browser's own connection.
A failed check first asks whether the account has data left, and an account without any is not a dead path: see the next section.
Out of data
When your data runs out, the proxy carries nothing until data is back, and the extension does what the URnetwork apps do: it keeps the proxy set, alerts you, and leaves disconnecting to you. It never falls back to your direct connection for it, whichever way the kill switch is set, since a disconnect you did not make could leak your traffic. On Firefox the per-request fallback to direct is off for as long as it lasts too.
The extension tells it apart from a proxy that does not answer by reading your account balance when a check fails: less than 1 MiB left is out of data, the point below which the server refuses new connections, as ur.io's Connect screen judges it. The popup then shows:
- Insufficient balance in the status line and above the alert, or on Pro, Data limit reached;
- when the data comes back: Free data refreshes in 5h 12m., counting down to 00:00 UTC, or on Pro, that a data pack adds more now;
- Pages won't load in this browser until data is available or you disconnect.;
- Get Pro (never on Pro) and Buy data, which open ur.io. Through the held proxy ur.io cannot load either, so the alert says To upgrade, press Disconnect first. Payment can't get through until you do. (on Pro, To buy data, …). After you disconnect, the alert stays in the open popup, so its links load.
It also posts one browser notification per episode, and only where the browser already allows the extension to post them: the extension never asks for that permission. The alert ends at the next check that passes (your data is back: the free refresh, an upgrade or a data pack), with a balance that has data again, or with a connect or a disconnect. A balance that does not come back keeps it. If data is back and the proxy still does not answer, the failures count from there as above.
Data collection: none
- The Firefox listing declares it in the manifest, machine-readably:
data_is none. That is a store-enforced statement, not a privacy-page promise.collection_ permissions - The extension talks only to the URnetwork API to provision your proxy, the same calls any client makes. No analytics, no telemetry, no browsing history collection anywhere.
- Host permissions differ by browser, for a reason. On Chrome the extension requests access only to the URnetwork API hosts (
api.,bringyour.com api-v4.bringyour.com); the proxy settings API does not need to see your requests. On Firefox the extension needs<all_urls>:proxy.consults the extension for every request it might route, and Firefox requires host access for that to work. Broader permission there is the cost of Firefox's proxy API, not a data grab.onRequest - No third party has assessed the extension. URnetwork's Android app passed a Leviathan Security Group MASA AL2 assessment in May 2025, Google's fixed security checklist for mobile apps, and an independent firm penetration-tested the web application and API in April–May 2025; neither covers the extension, and no independent audit covers the protocol or the operator's server code. What this page offers instead is falsifiable: those permissions are readable in your own installed copy, nothing is fetched at runtime, and the source is public. Claims you can check, not a certificate.
What the service keeps: your account and a per-device byte-count ledger (that is allowances and provider metering), never destinations or URLs; a client address held as a keyed one-way hash of your IP block rather than the address itself; and an approximate city from a geographic lookup. Providers egress without learning your real address, seeing only ISP-grade metadata (site names, never pages or passwords, which stay HTTPS-sealed); websites see only the exit.
Be exact about the middle, though. The network has three modes, and the browser only ever occupies one of them:
| Mode | Operator sees | Provider sees | Available here |
|---|---|---|---|
| Relayed standard | your account and source connection, which providers you are on, and the destinations and packet bytes inside | destinations it egresses and a device/contract id, not your real IP | yes: the only browser mode |
| Relayed sealed | the same, but ciphertext with its timing and volume in place of destinations | as above | no: the apps' encrypt-to-the-provider session, a switch there that ships off, has no browser equivalent |
| Direct | less relay involvement | your real IP and the destinations it egresses | no: forced off on the hosted proxy device the extension runs on |
That first row is the browser position, and the contrast with the apps is sharp rather than soft: they can seal the client↔provider session, with a switch that ships off, and the browser has no session there to seal. It cannot have one. A browser speaks its own proxy protocol and cannot run the network's engine, so your client device runs remotely inside the operator, which translates between the two protocols — a seal started from that device would begin at the operator, the party a seal exists to blind. The implementation traded the seal for reaching the browser at all. The guarantee here is a storage one rather than an encryption one. Any browser proxy hands each destination to the endpoint it dials, so the operator handles yours in transit; what stands behind that is a proxy data path that writes no log at all, pinned by a regression test in the open source, and a ledger with nowhere to put a destination. The apps' Strong Anonymization switch is likewise absent and likewise unneeded: with direct mode forced off, no provider can ever be handed your real address.
For what the network itself can and cannot see once your traffic is flowing, read the overview. The threat model goes further and names the browser path's missing seal as one of its own failures.
Troubleshooting
"Failed to connect. Check your account.", or the server's reason
A connect that fails shows why under the button, with Retry. When the server refused the proxy, the reason is the server's own and says what to do: your plan's limit of active proxies is reached, so remove one you no longer use on ur.io's Proxies page, or upgrade; or its limit on new proxies a minute is reached, so try again in a minute (see the limits). Failed to connect. Check your account. shows when no reason came back:
- Confirm you can sign in at ur.io and check your plan.
- Sign out of the extension and back in to refresh credentials.
A connect at another location that fails, other than at your plan's limit, leaves the browser on the proxy it had: the popup stays Connected, shows the reason with The browser is still connected at the previous location., and keeps Disconnect.
"The proxy stopped answering, so the extension turned it off. This browser connects without URnetwork until you connect again."
The health checks failed three times in a row with the kill switch off, so the extension took the proxy off, and this browser connects on its own settings, without URnetwork. The popup shows this under Disconnected, also if it was closed at the time, until you connect again. Your underlying network likely changed (moved networks, laptop slept, hostile Wi-Fi). Running out of data does not do this: it shows its own alert (see Out of data). Connect again from the popup; if it recurs on one network, that network may be blocking the proxy ports.
"Insufficient balance" or "Data limit reached"
Your account is out of data, and the proxy holds this browser's traffic until data is back or you disconnect (see Out of data). To get Pro or a data pack, press Disconnect first, then Get Pro or Buy data: ur.io can't load through the held proxy. Or wait for the free refresh at 00:00 UTC; the next check that passes returns the popup to Connected with nothing to do.
Another extension controls the proxy
Only one extension can control the browser's proxy settings at a time (on Chrome, the most recently installed one wins). On Chromium the extension checks who holds the setting: when another extension holds it with priority, the status line reads Another extension controls the proxy, with Another extension controls this browser's proxy settings, so URnetwork can't connect. Turn that extension off to use URnetwork., a connect is refused before anything is set up, and nothing reconnects over it at a browser start. If URnetwork was connected when the other extension took over, Disconnect ends URnetwork's setting under it, so it does not come back when the other extension goes. chrome:// names the current holder; disable the other one. When an administrator's policy fixes the proxy settings, the status line reads Proxy managed by policy, and the extension cannot connect in that browser.
On Firefox each extension answers per request, and Firefox does not say which other add-ons do: check for installed add-ons with proxy permission. The tells are the popup's IP line, whose dot turns gray when your requests do not leave through URnetwork, and the Proxy active but network unreachable. note that follows (see Reading the status).
Captive portals
Hotel and airport Wi-Fi needs you to sign in through a portal page before the internet works, and with the proxy up (especially armed), the portal cannot load. You cannot get wedged: disconnecting is local and needs no network. Disconnect the extension, complete the portal sign-in, then reconnect. Inherent to every proxy and VPN, not an extension bug.
Reading the status
The status line at the foot of the popup is the fastest diagnosis. The popup's labels and messages follow the browser's language; they are quoted here as they read in English. Until the background answers, a popup that opens shows no status and no Connect or Disconnect, only a neutral button.
- Disconnected: the proxy is off, and the browser connects on its own settings. If a connect failed, or the health checks took the proxy off, the reason shows under the button, with Retry. A popup opened after the checks took the proxy off shows that reason too, until you connect again.
- Connecting…: applying the install's proxy, or creating one.
- Connected: the browser is set to the proxy.
- Proxy not answering: the degraded state. The kill switch is on and the proxy failed three checks in a row, so this browser is blocked until the proxy answers or you disconnect. The reason under the button reads The proxy is not answering. The kill switch keeps the browser offline until it does. Nothing reconnects in the meantime. A popup opened during the outage shows this at once, from the last check.
- Insufficient balance, or on Pro Data limit reached: the account is out of data and the proxy holds this browser's traffic (see Out of data).
- Another extension controls the proxy, or Proxy managed by policy: the extension cannot set the browser's proxy (see Another extension controls the proxy).
If a change to the kill switch or location sync toggle cannot be saved, the toggle goes back and the popup says The setting couldn't be saved, so it didn't change. Try again.
A note can also appear under the button: Proxy active but network unreachable. The popup's own IP check, every 15 seconds while it is open, found three times running that your requests do not leave through URnetwork. On Firefox with the kill switch off, this is how a dead proxy shows: requests have gone direct.
Where to go next
- Getting started in the browser: store links, sign-in, and first connect, including the private-window note.
- How URnetwork works: the network behind the popup and where the providers come from.
- FAQ: plans, allowances, and account questions.