Home

Lithica Explorer · GisGeo Dev

Privacy Policy

How local field data, Firebase account data, and projects optionally synchronized to Google Drive are handled in Lithica Explorer.

Request account deletion

Lithica Explorer Privacy Policy

Application
Lithica Explorer
Developer
GisGeo Dev
Policy version
privacy_v4_2026_08
Effective date
August 27, 2026

Lithica Explorer does not treat every type of information in the same way. Field content is stored initially on the device; Google and Firebase process account and technical information needed for online services; and only projects and attachments selected for optional synchronization are transferred to the user's own Google Drive account.

1. Controller and scope

Lithica Explorer is administered by GisGeo Dev. The person responsible is Jordan Angel Luciano Zavaleta Reyes, in Peru. This policy applies to the Android application and its related online services. Privacy questions and account or data deletion requests may be sent to jordanzav@gisgeo.dev or started through the deletion option available in Lithica Explorer.

2. Data stored locally

Projects, observations, coordinates, GPS tracks, photographs, audio recordings, documents, scientific records, and offline packages are stored initially on the user's device. They remain local unless the user imports, exports, shares, or voluntarily synchronizes the relevant content.

3. Location and GPS tracks

Precise location is used to center the map, georeference observations, and record tracks expressly started by the user. While a track recording is active, location may continue to be used when Lithica Explorer is minimized or the screen is off. Android displays a persistent notification during recording, and active tracking may increase battery consumption.

The user can stop recording from Lithica Explorer and can revoke location permission in Android settings. Recording is not started silently and is not permanent surveillance. Tracks are not sent automatically to GisGeo Dev. They are transferred only to the user's own Google Drive account when the user voluntarily enables synchronization.

4. Permissions

  • Precise location: centers the map, georeferences observations, and records user-initiated tracks.
  • Camera: captures photographs for field records when the user uses that function.
  • Microphone: attaches audio recordings when the user chooses to record them.
  • Files and documents: imports, exports, and manages projects and their associated files.

Denying a permission may disable only the related function. Permissions can be changed in Android settings.

5. Account and Firebase

Google sign-in uses Firebase Authentication. Firebase processes the user's email address, internal user identifier, IP address, technical data required for security and operation, and technical information about the application. Firebase may also store application preferences, including language, theme, enabled add-ons, visual settings, coordinate mode, and selected EPSG codes; newsletter preferences and consent records; Google Drive synchronization and authorization status and the scopes granted by the user; operational metrics; and technical synchronization metadata, including project, device or installation, operation, and Drive file identifiers, revisions, dates, and status.

Firebase does not receive project geometries, coordinates, GPS tracks, photographs, audio recordings, documents, or the complete scientific content of projects. That content remains on the user's device unless the user voluntarily enables Google Drive synchronization or exports or shares it.

6. Operational metrics

  • Application version, build number, and platform.
  • Sessions and days of activity.
  • Counts of projects, observations, and offline packages.
  • Synchronization results or counts.

These metrics may include a technical device or installation identifier, project and operation identifiers, and technical synchronization metadata. Operational metrics do not contain the complete scientific content of projects. Project content and attachments are transferred only when the user voluntarily enables Google Drive synchronization. These metrics are not used for advertising.

7. Google Drive synchronization

The requested drive.file scope limits access to files created by or explicitly opened with the application, rather than granting general access to every file in your Drive.

Google Drive synchronization is optional and requires additional authorization. Projects and attachments selected by the user are transferred to the user's own Google Drive account. GisGeo Dev does not sell those files or use them for advertising. Files stored in Google Drive are managed by the user under their Google account; GisGeo Dev does not control their retention period there.

8. External providers

Lithica Explorer may use services supplied by Google, Firebase, Google Drive, and providers of maps or geological layers. When a map, layer, or other external resource is requested, the provider's servers may receive normal network information such as the IP address, request date, and request type. Each provider processes information under its own applicable terms and privacy practices.

9. Purposes

  • Authentication and access management.
  • Operation of field tools requested by the user.
  • Security and abuse prevention.
  • Synchronization requested by the user.
  • Support and technical improvement.

Personal information is not processed for advertising personalization.

10. Sharing

GisGeo Dev does not sell personal data. Technical processing by service providers that help operate Lithica Explorer is different from selling or sharing data for those providers' own advertising purposes. Providers process only the information involved in the services being used, subject to their applicable terms.

11. Retention and deletion

Local data remains on the device until the user deletes it or uninstalls the application. Files synchronized with Google Drive are managed by the user from their own Google account.

The user may request deletion of their Lithica Explorer account from the application, through the public deletion page, or by emailing jordanzav@gisgeo.dev. After identity verification, GisGeo Dev will administratively process the deletion of the application account in Firebase Authentication and the associated data it controls in Firestore, such as access records, preferences, consent records, synchronization metadata, and operational metrics linked to the user.

Deleting the Lithica Explorer account does not delete the user's Google account or automatically delete files the user keeps in Google Drive or on their device. If limited information must be retained for security, fraud prevention, or a legal obligation, the reason and scope of that retention will be communicated to the user. Requests will be handled within a reasonably prompt period, and the user will be notified when processing is complete.

Account and data deletion

The public deletion page explains how to submit and verify a request and which data is controlled by the user.

Open account deletion instructions

12. Security

Online communications use encryption in transit through HTTPS/TLS. GisGeo Dev and its service providers apply access controls and reasonable security measures appropriate to the service. No method of storage or transmission can guarantee absolute security.

13. Children

Lithica Explorer is a professional and educational geology and fieldwork tool. It is not specifically designed for or directed at children, and GisGeo Dev does not knowingly seek to collect children's personal data through the application.

14. Rights and contact

Subject to applicable law, users may ask about personal data processed by GisGeo Dev, request access or correction, or request deletion. Requests can be made through the in-app option or by contacting jordanzav@gisgeo.dev.

15. Changes to this policy

Material changes will be communicated through an appropriate public or in-app notice and will be reflected by an updated policy version and effective date. This version, privacy_v4_2026_08, is effective August 27, 2026.