The API itself is agnostic to how the browser or device determines the current location: a phone or other mobile device might use a Global Positioning System (GPS) receiver, while a laptop’s location might be triangulated from nearby Wi-Fi networks or inferred from its IP address. Common sources of location information include Global Positioning System (GPS) and location inferred from network signals such as IP address, RFID, WiFi and Bluetooth MAC addresses, and GSM/CDMA cell IDs, as well as user input. No guarantee is given that the API returns the device’s actual location.
The good news is that Kameleo can override the location retrieved to the websites. We recommend you to set up a location that fits your IP’s geolocation. Read more about in the article that tells how to get 100% anonymity on websites.
Geolocation API is not the same as the location derived from the IP
Please note that the location derived from the Geolocation API is not the same as the IP's location.
Basically, a website has 2 different ways to tell the user's location:
Get the location of the IP
Like this website, websites can tell the location based on the IP. These are stored in databases. Google Maps is using this technique. Once you open the map the default location will be the city that is derived from the IP.
Use the Geolocation API
This way websites can get a very accurate location. This is not a very popular method to use. So if you keep it 'Disabled' it will be also okay but for best anonymity, you should set up so it matches the location of your IP. If you visit browserleaks.com/geo now with your regular browser. You may be asked for permission by the website to know your location. If you block it the map won't show your location.
You can use this website to get the latitude and longitude for a required place: https://www.latlong.net/