Is Location Guard safe?
Location Guard ships a hardcoded third-party geocoding API key in its extension bundle.
The extension includes a plain-text OpenRouteService API key directly in its JavaScript source (js/gui/options.js). This key is passed to the geocoder component and is sent as a request parameter to api.openrouteservice.org whenever the geocoding feature is used. Anyone who inspects the extension source can read and reuse this key.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itKostas Chatzikokolakis - no other listings under this identity, 6 shared hostnames
Kostas Chatzikokolakis - no other listings under this identity, 6 shared hostnames
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 6 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 2.5.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on every site you visit
http://*/*
Read and change your data on every secure site you visit
https://*/*
Store data in your browser
storage
Where it sends data
Destinations our analysis observed Location Guard contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- api.openrouteservice.org
Location Guard sends data to api.openrouteservice.org. No other extension we have analyzed sends data here.