Privacy Policy
Last updated: July 5, 2026
Short version: GField Mapper is designed for geological field mapping. The Android app stores project data locally by default. The app may use Firebase Analytics and Crashlytics for diagnostics, stability, and product improvement, but we do not send project names, coordinates, geometry, file paths, attachments, or geological content to Firebase. We do not sell your data.
1. Who we are
GField Mapper ("we", "our", "the app", or "the service") is a geological field mapping product available as an Android application and as a web viewer at gfield.aicodesys.com and webgfield.aicodesys.com. This Privacy Policy explains what data the app and web service handle and how.
2. Android app data stored on your device
The following data is created and stored locally on your Android device. It is not transmitted to our servers unless you explicitly use an online feature or share/export it:
- Project data: boundaries, observation points, geological contacts, faults, structural measurements
- Attachments: photos, videos, audio recordings, and documents you attach to observations
- Topographic data: Copernicus DEM tiles downloaded for offline use
- Imported files: KML files, georeferenced images (JPG+TAB), and other map layers
- App settings and preferences
3. GField Mapper Web
When you use the web viewer, you may upload a .gfield.zip project package. The package is processed on our backend to normalize the project model, prepare map tiles, render heavy layers, and allow the project to be viewed in the browser.
Depending on the package contents, the uploaded project may include geological objects, coordinates, project boundaries, styles, imported map layers, topographic files, and attachments. You should upload only project packages that you are allowed to process through the web service.
4. Google Sign-In
The web service may offer Sign in with Google. When you sign in, Google provides us with basic account information:
- Your email address
- Your name
- Your profile picture, if available
- A stable Google account identifier
We use this information to create a local user profile, attach web viewer sessions to your account, and prepare future project workspace, export, debug, and subscription features. We do not receive your Google password.
5. Data stored on our server
When you use server-side features, we may store the following data:
- User profile data from Google Sign-In: email, name, profile picture URL, and a non-public internal user id
- Authentication session metadata; session tokens are stored as hashes, not in plain text
- Viewer session metadata, including the user that owns the session
- Temporary copies of uploaded project packages and extracted assets needed to display the project in the web viewer
- Generated map tiles and cache files used to speed up rendering
- Debug packages or logs if you explicitly send them for support
- Subscription or promo-code entitlement status when required to unlock paid features
6. Data we do not sell or intentionally collect
We do not sell your data. We also do not intentionally collect:
- Your Google password
- Your payment card details
- Your background GPS location or device location history
- Photos, videos, or media unless you add them to a project package or send them for support
- Your project names, geological coordinates, object geometry, file paths, attachment names, or attachment contents through analytics events
- Advertising identifiers for advertising tracking
7. Diagnostics and analytics
The Android app may use Firebase Analytics and Firebase Crashlytics to understand how the app is used, diagnose crashes, improve stability, and prioritize product work.
Analytics events are limited to privacy-safe technical and product signals, such as app start, project creation, project import/export, raster export, promo-code activation, and subscription status changes. Crash reports may include technical information such as device model, operating system version, app version, stack traces, and crash state.
We intentionally filter analytics parameters so that the following are not sent to Firebase Analytics: project names, object names, coordinates, geometry, file paths, attachment names, photos, videos, audio recordings, documents, and project package contents.
8. Network requests
GField Mapper may make network requests for the following purposes:
- Copernicus DEM download — elevation data is fetched from the Copernicus Data Space (dataspace.copernicus.eu) when you choose to download topography for a project. Only the geographic bounding box you request is sent as a query parameter.
- Subscription verification — if you subscribe via Google Play, the app uses the Google Play Billing API to verify your entitlement. This is handled entirely by Google and subject to Google's Privacy Policy.
- Firebase diagnostics and analytics — the app may send privacy-safe analytics events and crash diagnostics to Firebase, as described in section 7.
- Demo build expiry check — pre-release demo builds verify the build expiry date against a server timestamp. No personal data is sent.
- Web viewer processing — the web viewer sends uploaded project packages to our backend for normalization, tile rendering, and viewing in the browser.
- Google Sign-In — the web viewer uses Google Identity Services to authenticate users.
9. Google Play, Google Maps, Firebase, and third-party services
Downloading the app through Google Play is subject to Google's own Privacy Policy and Terms of Service. In-app purchases are processed by Google Play Billing. We receive only the subscription status (active / inactive), not your payment details.
The Android app and web viewer may use Google Maps to render the base map. Map tile requests are made directly to Google's servers according to Google Maps Platform Terms. We do not send your project package to Google Maps.
The Android app may use Firebase Analytics and Firebase Crashlytics, which are provided by Google. Firebase data processing is subject to Google's privacy and data processing terms.
The web viewer uses Google Identity Services for Sign in with Google. Google handles the authentication flow according to Google's Privacy Policy.
10. Android permissions
The app may request the following Android permissions:
- Location (optional) — used only when you tap "Use GPS coordinates" for a point. Location is not collected in the background.
- Camera / Storage — used to attach photos and files to observation points. Files are saved to the local project package only.
- Internet — required for DEM downloads, map tiles, subscription verification, Firebase diagnostics and analytics, and web service features as described above.
11. Retention and deletion
Android project data remains on your device until you delete it in the app or uninstall the app.
Firebase Analytics and Crashlytics diagnostic data is retained according to Firebase retention settings and Google's applicable terms.
Web viewer sessions, uploaded package assets, and generated tiles may be kept temporarily to provide the service, improve performance, and support debugging. They may be deleted automatically or during maintenance. User profiles and subscription entitlement records may be kept while your account is active or as required to provide paid access and support.
You may request deletion of your web user profile, uploaded packages, debug files, and related server-side data by contacting us at the email address below.
12. Security
Google ID tokens are verified on the backend. Authentication session tokens are stored as hashes. Access to user-owned web viewer sessions is restricted to the owning user or to session-specific access tokens used for map tile loading.
No system can be guaranteed to be perfectly secure. If you believe your data has been exposed or accessed incorrectly, please contact us immediately.
13. Children's privacy
GField Mapper is a professional tool intended for adult users. The app does not knowingly collect data from children under 13.
14. Changes to this policy
We may update this Privacy Policy when the app adds features that affect data handling. The "Last updated" date at the top of this page will reflect any changes. We will not reduce your privacy protections without clear notice.
15. Contact
If you have questions about this Privacy Policy or about data handling in GField Mapper, contact us at: [email protected]