Privacy Policy — MagsTags Chrome Extensions
This policy covers the two Chrome extensions published by MagsTags: the Schema.org Structured Data Extractor and the Google Goto URL Resolver. Neither extension collects, transmits, or stores any user data on remote servers. There are no analytics, no telemetry, no accounts, no remote code, and no developer-operated server behind either of them.
Schema.org Structured Data Extractor
The Schema.org Structured Data Extractor extension does not collect, transmit, or store any user data on remote servers.
Data the extension reads
The extension reads structured data markup (JSON-LD scripts, microdata attributes, and RDFa attributes) from the current page's DOM when:
- A content script counts items on each page you visit, to display the count as a badge on the toolbar icon
- You click the toolbar icon, in which case the full extracted data is displayed in a viewer tab on your device
Data stored locally
The extension uses chrome.storage.local to temporarily pass extracted data from the background service worker to the viewer tab. This data is stored only on your device, is not transmitted anywhere, and is overwritten each time you click the icon.
Network requests
The extension makes no network requests on its own. The only external navigation occurs when you click the "Visualize" button, which opens magstags.com/schema-markup-visualizer/ in a new tab. The schema data is placed on your clipboard at that point; you paste it manually into the visualizer. No data is sent to magstags.com or any other server by the extension itself.
Google Goto URL Resolver
The Google Goto URL Resolver extension shows the real destination of Google search result links that Google has wrapped in a redirect (for example google.com/goto?url=…). It does not collect, transmit, or store any user data on remote servers.
Data the extension reads
The extension runs only on Google Search results pages. On those pages it reads the links in the results in order to display their destination in a tooltip, optionally rewrite the link so the browser shows the destination, and list the page's results in the popup. It does not read your search queries as data, your browsing history, or any content on the destination websites.
Network requests
The only network requests the extension makes go to Google, to resolve the redirect links that Google itself placed on the results page. Each request is the same one your browser would make if you clicked the link, is sent without cookies, and is made only when you hover a result, click "Resolve all links on this page" in the popup, or have chosen the automatic mode in the popup (which resolves the results on pages you open, one link at a time with a delay). The extension never contacts the destination websites, magstags.com, or any other server.
Permissions
- webRequest (read-only): used to read the
Locationheader of the redirect responses the extension itself requests. Chrome'sfetch()API hides this header, so observing it is the only way to learn where a redirect goes. The extension never blocks or modifies any request. - storage: resolved destinations are cached with
chrome.storage.sessionfor the current browser session only and are discarded when the browser closes. Your settings (resolve mode, tooltip on/off, rewrite links on/off, include images in copy) are stored withchrome.storage.sync. - Host permissions for Google search domains: required to run on results pages and to make the resolve requests described above.
Data stored locally
Only the session cache of resolved URLs and your settings, as described above. Nothing is written to disk beyond what Chrome's storage APIs keep for the extension, and nothing leaves your device except the requests to Google.
Third-party services
None, for either extension. No analytics, no telemetry, no error reporting services, no remote APIs.
Contact
mags.sikora [at] googlemail.com