Privacy Policy for Blue Map (Fake GPS Mock Location Changer)

Developer: LRLR · Effective date: September 28, 2026

This Privacy Policy explains how LRLR (“we”, “us”) handles information in the Android app Blue Map, which is published on Google Play under the name Fake GPS Mock Location Changer. It applies to every version of the app we distribute.

1. Summary

• The app has no user accounts and shows no ads. We do not sell your data.
• Your saved locations, routes, tracks and settings are stored on your device. We do not run a server that receives them.
• Some features send data to third-party services (maps, search, routing, crash reporting, analytics and purchases). Each is listed below.

2. Data stored on your device

The app stores the following on your device only:

• Locations, routes, tracks and areas you save, your mock-location history, and your app settings.
• GPX and KML files you import, and files you choose to export.
• Google API keys you enter yourself (optional). These are stored encrypted with the Android Keystore.
• A diagnostic log of mock-location activity, kept only if you turn on diagnostics.

This data stays on your device unless you export or share it, or Android backs it up as described in section 7. Uninstalling the app deletes it.

3. Location

With your permission (ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION), the app reads your device's real location to show it on the map and to let you return to it. The real location is obtained through Google Play services location APIs. The app does not send your real location to us.

The app's main purpose is to set a mock (simulated) location on your device through Android's developer option “Select mock location app”. The mock location you choose is provided to the Android system on your device; it is not sent to us.

4. Maps, place search and routing

To draw maps, find places and plan routes, the app sends requests to the services below. A request contains what is needed for the task — the map area being viewed, your search text, or the coordinates to look up or route between — together with standard technical information such as your IP address. These services handle that data under their own privacy policies.

5. Crash reports, analytics and app services (Google Firebase)

We use Google Firebase to keep the app working and to understand which features are used:

• Firebase Crashlytics — crash and error reports, including device model, manufacturer, Android version, app version, and the state of the app at the time of the crash.
• Firebase Analytics — app usage events, such as which features and modes are used. Events do not contain the coordinates you mock or save.
• Firebase Performance Monitoring — app start-up time and network request performance.
• Firebase Remote Config — downloads settings such as update notices.
• Firebase App Check with Play Integrity — verifies requests come from a genuine copy of the app, to protect shared API quotas.

These services use identifiers such as the Firebase installation ID and app instance ID, and may derive an approximate region from your IP address. Google processes this data as described in the Firebase privacy information and the Google Privacy Policy, and retains it according to Firebase's retention settings.

6. Purchases, reviews and updates (Google Play)

• Google Play Billing — optional supporter and donation items. Payment is handled by Google Play; we never receive your card or payment details. The app receives only the purchase status needed to unlock the item.
• Google Play In-App Review and In-App Updates — to ask for a rating and to offer app updates, handled by Google Play.

7. Backup

If Android backup is turned on for your Google account, Android may back up the app's saved data and settings to your Google account and restore them on a new device. The encrypted API keys, the diagnostic log and the offline map cache are excluded from backup. Backups are managed by Google, not by us. You can turn backup off in your device settings.

8. Feedback and diagnostic logs you send us

If you send feedback from the app, your email app composes a message to us that includes the app version, device model and Android version. We receive that message and your email address, and use them only to respond and to fix problems. If you choose to share a diagnostic log, it is sent through the app you pick in the share sheet. We delete feedback on request.

9. Permissions

• Location — show your real position on the map (section 3).
• Mock location — provide the simulated location you choose.
• Foreground service and notifications — keep the mock location running and show its status.
• Display over other apps — show the floating joystick and controls while you use other apps.
• Internet and network state — load maps, search places and calculate routes.
• Run at start-up — resume mocking after a reboot, only if you turn this on.

10. Sharing

We do not sell or rent personal data. Data is shared only with the service providers listed in sections 4 to 7, for the purposes described there, or when required by law.

11. Your choices

• You can deny or revoke the location permission; the map then cannot show your real position.
• You can keep using the default services instead of turning on Google Maps, Google Places or Google Routes.
• You can turn off Android backup, and you can delete all on-device data by clearing the app's storage or uninstalling it.
• To ask about or delete feedback you sent us, email robin1050302@gmail.com.

12. Security

Network requests use HTTPS. API keys you enter are encrypted on the device. No method of storage or transmission is completely secure, but we limit what leaves your device to what each feature needs.

13. Children

The app is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has sent us personal information, contact us and we will delete it.

14. Changes to this policy

We may update this policy when the app changes. The effective date above shows the latest version.

15. Contact

LRLR — robin1050302@gmail.com