Privacy Policy – Location History Explorer
Last updated: 1 July 2026
Location History Explorer is developed and provided by Fabian Mueller.
This Privacy Policy explains how information is handled when users install and use Location History Explorer.
1. Developer and contact
Developer:
Fabian Mueller
Email: lochistvis@gmail.com
Questions concerning this Privacy Policy or the application can be sent to the email address above.
2. Imported location-history data
Location History Explorer allows users to select and import exported location-history files.
The user explicitly chooses which file to open. Imported location-history files are processed locally on the user's device.
The developer does not receive, upload, store, or have access to the contents of imported location-history files.
Location History Explorer does not request or access the device's current GPS or network location. The application does not require precise-location or approximate-location permissions.
Locations displayed in the application originate from files selected by the user.
3. Local processing and storage
Imported location-history data, application preferences, visualization settings, story scenes, and related project information may be stored locally in the application's private storage on the user's device.
The application uses local storage and a local database to provide its functionality.
The developer does not operate a server for storing imported location histories, application projects, visualization settings, or generated media.
Users can remove locally stored information by using available deletion functions in the application, clearing the application's data through Android system settings, or uninstalling the application.
4. Backups and device transfers
Location History Explorer is configured not to include its private application data in Android cloud backups or device-to-device application-data transfers.
Operating-system functions and device-manufacturer services operate independently from the developer. The developer does not receive or have access to Android system backups or device-transfer data.
Files intentionally exported by the user to shared device storage may be handled by the user's device, storage provider, or backup configuration.
5. Background maps and network requests
Location History Explorer uses external map services to display background maps.
The application may request map tiles and related map resources from providers such as CARTO and OpenStreetMap-related services.
When map resources are requested, the relevant provider may receive technical information required to deliver those resources, including:
- the IP address used for the connection;
- requested map-tile coordinates;
- the requested zoom level;
- the date and time of the request; and
- standard technical network-request information.
The requested map area may represent a historical location, a manually selected area, or another area viewed by the user. It does not necessarily represent the user's current physical location.
The application does not send the imported location-history file to a map provider.
The developer does not receive map requests through a developer-operated server.
External map providers process technical request information according to their own privacy policies, terms, security practices, and retention rules.
6. Network security
Network requests initiated by Location History Explorer use encrypted HTTPS/TLS connections.
No method of electronic storage, software operation, or network transmission can be guaranteed to be completely secure.
7. Accounts and authentication
Location History Explorer does not provide or require:
- user accounts;
- registration;
- login credentials;
- social sign-in;
- OAuth authentication; or
- cloud profiles.
The developer does not maintain user-account information.
8. Advertising, analytics, and tracking
Location History Explorer does not contain advertising.
The current version does not use advertising identifiers, advertising SDKs, cross-app tracking, or user-profile tracking.
The current version does not use Firebase Analytics or another remote analytics service to monitor user behaviour.
The current version does not use Firebase Crashlytics, Sentry, or another developer-operated remote crash-reporting service.
9. Exports and user-initiated sharing
Users may create and export images, videos, or other generated content.
Exported content is created locally and saved to a location selected or made available by the user's device.
If a user chooses to share exported content through another application or service, the selected recipient or service may receive that content. Such sharing is initiated and controlled by the user and is governed by the recipient's or service provider's own privacy policy and terms.
Users should review exported media before sharing it because it may reveal sensitive locations, routes, or travel patterns.
10. Data sharing and sale
The developer does not sell personal information.
The developer does not share imported location-history files with advertisers, data brokers, analytics providers, or other third parties.
Technical network information may be processed directly by external map providers when background-map resources are requested, as described in Section 5.
Information voluntarily included in a support communication is handled as described in Section 11.
11. Support communications
If a user contacts the developer by email, the developer receives the information voluntarily included in that communication. This may include:
- the user's email address;
- the user's name, if provided;
- the contents of the message;
- attachments voluntarily provided by the user; and
- technical information voluntarily included in the request.
This information is used only to respond to the request, investigate a reported issue, maintain necessary support records, protect the security and reliability of the application, or comply with applicable legal obligations.
Users should not send complete location-history exports or other highly sensitive information unless this is necessary for resolving a specific support issue.
Support communications are retained only for as long as reasonably necessary to handle the request, maintain appropriate records, resolve disputes, or comply with legal obligations.
12. Data retention and deletion
The developer does not retain server-side copies of:
- imported location-history files;
- saved visualization projects;
- story scenes;
- generated images or videos; or
- locally stored application preferences.
Locally stored application data remains on the user's device until it is deleted through the application, cleared through Android settings, or removed when the application is uninstalled.
The developer cannot remotely access or delete information stored only on the user's device.
External map providers may retain technical request information according to their own privacy policies and retention rules.
13. Security considerations for location-history data
Location-history files may contain highly sensitive information, including home addresses, workplaces, travel patterns, frequently visited locations, and information about other people.
Users should protect access to their devices and should not share exported location-history files or generated media with untrusted parties.
14. User rights
Depending on the user's location and applicable law, users may have rights concerning personal information held by the developer, including rights of access, correction, deletion, restriction, objection, and data portability.
Because imported location-history data is processed locally and is not accessible to the developer, requests concerning locally stored app data must be handled directly on the user's device.
Users may contact the developer using the email address listed in Section 1 regarding information contained in support communications.
Users may also have the right to lodge a complaint with the competent data-protection authority in their country of residence.
15. Children's privacy
Location History Explorer is intended for users aged 18 and over.
The application is not designed for or directed at children. The developer does not knowingly collect personal information from children through the application.
16. Third-party services and international processing
External map providers and email service providers may process technical or support-related information in countries outside the user's country of residence.
These providers process information according to their own privacy policies, contractual obligations, and applicable legal requirements.
17. Changes to this Privacy Policy
This Privacy Policy may be updated if the application's functionality, technical implementation, third-party services, or applicable legal requirements change.
The current version will be published on this page. The “Last updated” date indicates when the policy was most recently revised.
18. Contact
For questions, privacy enquiries, or requests concerning information held by the developer, contact:
Fabian Mueller
Email: lochistvis@gmail.com
Location History Explorer is an independent application and is not affiliated with Google or Google Maps.