/ Unmask URL
Privacy Policy
Last updated: 15 September 2026
Unmask URL collects nothing, stores nothing about you anywhere but your own browser, and sends nothing to its developer or to any third party.
There is one network request it makes, described in full below, because it would be dishonest to claim no network activity when there is some.
What it collects
None of the following is collected, transmitted, sold or shared: personally identifiable information; your searches, search results or browsing history; authentication details, passwords or cookies; location, health or financial information; personal communications; analytics, telemetry, crash reports or usage statistics.
There is no server. The developer receives no data of any kind and has no way to observe your use of the extension.
The one request it makes, and why
Since August 2026 Google has wrapped search result links in a redirect of the form google.com/goto?url=CAES.... That token is signed and opaque: it is not an encoding of the destination, so no software can decode it on your computer.
The only way to learn where a result points is to ask Google's own redirector and read the redirect target it returns, without following it.
So, to Google and to nobody else, Unmask URL sends a request to that same address, on the Google page you are already on, using the session you already have. It reads only the destination from the response. No new information about you is created or disclosed by this: Google already knows which results it served you.
You control when it happens:
- Show every URL straight away (default): one request per redirected result on the page you are viewing.
- Show a URL when I point at it: a request only for links you hover.
Direct links that are not redirect-wrapped need no request at all.
What is stored, and where
- Your settings
- chrome.storage.sync, on your machine. Kept until you change them or uninstall, and synced by Chrome across your own signed-in devices.
- Resolved destinations
- chrome.storage.session, which is memory-backed and erased when you close the browser. Nothing about the pages you looked at is ever written to disk.
Permissions, and why each exists
- webRequest
- To read the redirect target of Google's goto redirect. Observation only: Manifest V3 has no blocking webRequest, and Unmask URL never modifies, blocks or redirects any request.
- scripting
- To act on a Google results page that was already open when you installed or enabled the extension, instead of making you reload it.
- storage
- Your settings, and the in-memory cache above.
- Access to Google search sites
- To run on results pages and make the lookup described above. Nothing runs on any other site, and the extension exits immediately on Google pages that are not search results: Gmail, Drive, Docs and the rest are excluded in code.
Children
Unmask URL is not directed at children and collects no data from anyone.
Changes
Any change to this policy will be published at this URL with an updated date. Every claim above is backed by the extension's own code, which ships unminified and unobfuscated and can be read in full in the installed package.
Contact
Neeraj Jivnani, neeraj@hiigher.co. Or use the contact page.