Privacy Policy for Mock Location

Last updated 14 October 2026 · Developer: Eugen Ungurean · Contact: eugen.ungurean@gmail.com

Mock Location is an Android app that sets a mock location on your own device for development and testing. This policy describes what the app does with data, in plain terms. It covers the app published on Google Play under the package name com.nan.elsewhere.

The short version. The places and routes you save and the location you mock stay on your device. Mock Location has no user accounts and no server of its own, and your real location never leaves your device because of us. Crash and error diagnostics go to Google's Firebase, and never contain a location. Showing a map, searching for an address, opening a shared Google Maps link, and building a route that follows roads involve Google, as described below. For road-following routes, that means the route points you place are sent to Google; you can turn this off.

What stays on your device

The following is stored only in the app's private storage on your phone. We cannot see it, and it is never transmitted to us:

If you have saved places or routes, the app also gives the names of up to four of them to Android as app shortcuts, which your launcher shows when you long-press the app icon. These shortcuts are held by Android on your device. The list is updated when you delete a place or route, though a shortcut you have dragged onto your home screen stays there until you remove it or uninstall the app.

A route you are building is held in memory only, and is gone when you leave the app, unless you save or export it. GPX, KML and GeoJSON files you import are read from, and routes you export are written to, the place you choose in Android's file picker; the app keeps no copy of the file.

Deleting a saved place or route in the app removes it (the app offers a few seconds to undo). Stopping a mock deletes the copy of it in progress; the last-mocked copy stays until another mock replaces it. Uninstalling Mock Location, or clearing its storage in Android's settings, deletes all of it.

No backup, no transfer

Mock Location opts out of Android's app backup. Your saved places and routes, your settings, and the mocks above are not included in your device's backup to Google, and they are not copied when you transfer to a new phone. They exist only on the device you created them on, which also means they do not survive a reset or a move to a new device.

Your location

Mock Location asks for location permission so it can show where you actually are on the map and give you a starting point. From Android 14, Android also requires it before an app can run a location service such as the mock. The app reads your position through Google Play services on your device.

We do not collect, store, or transmit your real location. It is used on the device, in the moment, and nothing more. Places you choose to mock are a different matter only in one case: the points of a road-following route, which are sent to Google to work out the roads between them, as described below.

You can revoke location permission at any time in Android's app settings. Mock Location continues to work; the map simply opens on a world view instead of on you.

What leaves your device

Crash and error diagnostics (Firebase Crashlytics)

Mock Location uses Google's Firebase Crashlytics to report crashes and a small number of specific non-crash failures — mainly the case where a phone model refuses to register a mock location provider, which is otherwise invisible to us and leaves the app appearing to work when it is not.

When that happens, the following is sent to Firebase:

CategoryWhat it is
Crash logs and diagnosticsThe stack trace of the failure, the exception type and message, and whether the app was in the foreground
Device and OS informationDevice model, manufacturer, Android version, CPU architecture, available memory and storage, and the app version
IdentifiersA Firebase installation ID and a Crashlytics installation UUID — random identifiers for this installation of the app. They are not tied to you, your Google account, or your device's advertising ID.
Session dataA random session identifier used to group events from a single run of the app

Alongside each report we attach three technical values of our own: which mock provider failed, what kind of failure it was, and your Android API level. No latitude, longitude, address, place name, or search term is ever included in a report.

Firebase Analytics is deliberately not included in Mock Location. We do not track how you use the app, which screens you open, or which places you mock.

Google retains Crashlytics crash traces and their associated identifiers for 90 days before beginning removal from live and backup systems. Firebase acts as our data processor for this, under Firebase's privacy and security terms and Google's Privacy Policy.

Maps and address search (Google)

The map in Mock Location is drawn by the Google Maps SDK for Android, and address search uses Android's built-in geocoding service, which on most devices is provided by Google.

Using these means data is sent to Google directly — including the text you type into search, your IP address, and the map coordinates being displayed. This happens as part of Google's service, not through any server of ours, and we do not receive a copy of it.

Google's use of that data is governed by the Google Privacy Policy, which applies to your use of the mapping and search features in this app. If you would rather not send search terms to Google, you can place a pin directly on the map instead of searching.

Road-following routes (Google Routes API)

When you build a route with Follow roads switched on, the app asks Google's Routes API for the way along roads between each pair of points you place. Each request sends Google:

The request goes from your device straight to Google; we do not receive or keep a copy. Your real location is not part of it, and nor is anything that identifies you or your device. Google's use of it is governed by the Google Privacy Policy. Turn Follow roads off in the route menu and routes run in straight lines between your points, with nothing sent at all. Routes imported from a file are used as they are, and are not sent. A saved route keeps the path it was given when you saved it, so running it again sends nothing.

Shared Google Maps links

When you share a short Google Maps link (maps.app.goo.gl) into the app, or paste one into search, the app asks Google where the link leads, so it can find the place. That request goes to Google only, and contains the link and your IP address. Links to other sites are never opened.

Commands from a connected computer (adb)

A developer can also start and stop mocks with adb commands from a computer connected to the phone. Android lets only that connection send these commands without a key. The commands are handled on the device and nothing is sent anywhere because of them. Routes started this way run in straight lines and are not sent to Google.

Automation apps you allow

If you turn on Allow automation apps in the settings, other apps on your phone, such as Tasker or MacroDroid, can start and stop mocks too, but only by presenting the key shown there. It is off until you turn it on. Making a new key stops every app that had the old one.

When you make a shortcut for one of these apps, or for your home screen, the app that asked for it receives the shortcut, and with it the key and what the shortcut does: for a saved place, its name and coordinates; for a saved route, its name. That app then holds them under its own privacy policy, not this one. Nothing is sent to us, and Mock Location sends nothing over the internet because of it.

What we never do

How the data is protected

Data on your device sits in the app's private storage, which Android isolates from other apps. Diagnostic reports are sent to Firebase over encrypted connections (HTTPS/TLS) and are held under Google's security controls. Because we operate no servers and hold no accounts, there is no database of ours for anyone to breach.

Your choices and how to delete your data

Depending on where you live, you may have rights to access, correct, or delete personal data held about you. Because Mock Location holds no accounts and no personal records, in practice there is very little to act on — but write to us and we will respond.

Children

Mock Location is a developer and testing utility. It is not directed at children, and we do not knowingly collect personal information from children.

Changes to this policy

If this policy changes, the updated version will be posted at this address with a new date at the top. Material changes affecting how data is handled will also be noted in the app's release notes on Google Play.

Contact

Questions about this policy or about privacy in Mock Location: eugen.ungurean@gmail.com.