VPN and Geolocation: Why Maps, Taxi and Delivery Apps See a Different City in 2026

A VPN can change your visible IP address, but it doesn't have to change GPS, Wi‑Fi geolocation or app permissions. Because of that, maps, taxi services, delivery apps, marketplaces and websites sometimes show different cities: one source sees the phone's real position, another sees the region of the VPN server. Below is a safe checklist that helps you figure out exactly where the confusion comes from and configure your VPN without breaking everyday services.

Why a VPN changes geolocation differently than you expect

When a user says "my geolocation is broken because of VPN", three different signals usually get mixed up:

1. IP address — seen by websites, some apps and anti-fraud systems. A VPN can indeed expose an IP from another region.
2. GPS, Wi‑Fi and cellular networks — used by mobile apps that have location permission. Apple explicitly notes that iPhone and iPad may use GPS, Bluetooth, Wi‑Fi and cellular signals to determine location. Google also explains that Android uses the device location settings for local results, routes and nearby scenarios.
3. Browser and app permissions — Chrome and other browsers ask permission for a site to access your location. MDN describes the Geolocation API as a mechanism available to sites only in a secure context and usually requiring the user's consent.

That's why the same phone can behave strangely: a store website thinks you're in one city based on IP, the delivery app shows another city based on GPS, and a browser map asks for a separate permission.

Where the problem shows up most often

Typical 2026 scenarios look like this:

• a taxi app drops the pickup pin in the neighboring district or can't refine the address;
• a delivery service offers restaurants from a different city;
• a marketplace changes the regional listings, pickup point or currency;
• a website asks you to confirm sign-in because your IP suddenly looks "unusual";
• a browser map shows a wide blue area instead of a precise point;
• an app sees the real GPS, but the web version of the same service relies on the VPN IP.

This is not always a VPN bug. It's often a normal reaction by the service to contradictory signals: real GPS points to one city, IP points to another, and the old app cache remembers a third.

Quick diagnosis: which signal is wrong

Start with a simple test instead of changing all settings at once.

Main rule: don't try to "spoof GPS" to bypass a service's rules. That can violate platform terms and lead to bans. The safe goal is to remove the technical conflict between the VPN IP and your real location where the service genuinely needs to know your address.

Checklist: what to do on your phone

1. Check whether this particular app needs a VPN

For maps, taxi, delivery and banking it's usually better to use your real location and a stable network. If your VPN client supports split tunneling, exclude from VPN the apps that need local context: maps, taxi, delivery, banking apps, smart home apps. This approach is covered in detail in our article on VPN split tunneling.

If split tunneling isn't available, use a simple mode: enable VPN for the browser, messengers and public Wi‑Fi, but temporarily turn it off before ordering a taxi or placing a delivery where precise geolocation is critical.

2. Verify location permissions

On iPhone, open privacy settings and confirm that the app has location access set to "While Using". For navigation and delivery services precise location also matters, when this option is available. Apple specifically notes that apps can request Location Services and the user chooses the access level.

On Android, open location settings and the permissions of the specific app. Google states that when location is enabled, Android can use it for local search, routes and nearby scenarios. If the app is denied access, it may fall back to IP, an old address or a manual city choice.

3. Test the browser separately from the app

The browser and the app of the same service can use different sources. For example, a site in Chrome will ask for location permission, while the app already has — or doesn't have — access at the OS level. In Chrome, location settings are managed separately: a site can be allowed, blocked or reset in site settings.

If the site shows the VPN region but the app shows the real address, that's not a contradiction. The web version probably looks at the IP or the browser permission; the app receives a GPS/Wi‑Fi signal from the phone.

4. Switch the VPN server closer to your actual region

If the service doesn't need precise GPS but cares about the region — for example, a marketplace, a news site or local listings — pick a VPN server closer to your actual city or country. The smaller the gap between the IP and how the account is actually used, the fewer reasons for additional checks.

Don't constantly hop between distant regions on the same account. Some services treat sudden IP changes as risk. We can't know each service's specific anti-fraud rules, so this is a practical hypothesis, not a universal guarantee.

5. Remove DNS conflicts

Sometimes the issue looks like "geolocation", but actually the app can't load data properly due to DNS. On Android check Private DNS, on iPhone check third-party DNS/VPN profiles, on the router check the DNS pushed to the whole network. If after connecting the VPN sites only partially open or apps see the network unstable, it helps to go through the checklist in the article VPN DNS settings.

6. Clear app cache and the saved city

Many services store the region in the account, cookies or local cache. After switching the VPN server they aren't required to instantly recompute the city. Fully close the app, reopen it, check the selected city in the profile, update the delivery address or pickup point. In the browser you can test the site in a private window to separate a cookie problem from a VPN problem.

Settings for popular scenarios

Taxi and delivery

The best option is not to route these apps through VPN if they need a precise point on the map. Keep location on, allow precise access and make sure the app isn't restricted by battery saver mode. If you use VPN on public Wi‑Fi, first go through the network's captive portal, then enable VPN; more details are in the article on VPN on public Wi‑Fi.

Marketplaces and local websites

Check three places: the region in the account, the delivery city and the IP region. If the marketplace shows the wrong city only in the browser, reset cookies or the site's location permission. If currency or language changes, pick a VPN server closer to the needed region or temporarily open the site without VPN.

Maps in the browser

Google Maps explains that the blue dot can be inaccurate: the wider the light blue circle, the lower the confidence in your location. If the map "drifts" in the browser, check the site permission, whether Wi‑Fi is on, whether you're indoors with poor GPS reception and whether the browser blocks access to geolocation.

Home router with VPN

If the VPN is enabled on the router for the whole network, it covers TVs, laptops, phones and smart devices. For location-based services this is often too coarse. It's more practical to set up a separate Wi‑Fi network or routing rules: TV and browser go through VPN, while the phone with taxi and delivery apps connects directly. For similar logic see our guide on VPN on a home router.

Safe setup scheme with FoliVPN

1. Connect FoliVPN to the nearest stable server.
2. Check which apps actually need to go through the VPN.
3. Exclude maps, taxi and delivery from the tunnel if the client supports per-app rules.
4. For the browser separately check the site's location permission.
5. If an app shows the wrong city, restart it and check the saved address.
6. If the issue only repeats on one network, compare Wi‑Fi and mobile internet.
7. Don't use suspicious "GPS spo