This Privacy Policy explains how Field Master GPS processes local app data, technical licensing data, and data exchanged with Google and Firebase services.
The controller for contact data, licensing identifiers, and support handling is Michał Dudko. Contact: kontakt@fieldmaster.pl.
The app stores data locally on the device, including fields, groups, crop history, GPS passes, manual treatments, reports, tasks, calculator inputs, treatment plans, navigation settings, local thumbnails, weather and geoportal-tile caches, profitability-register data (weight tickets, purchase invoices, season results), watched-crop and price-alert settings, downloaded orthophoto tiles, and locally saved exports or backups created by the user.
These data remain on the user's device unless the user chooses to export, share, or otherwise transmit them to a third party.
On Android, the app uses Firebase Authentication with anonymous sign-in. Firebase creates a random technical user ID (Firebase UID) without requiring a name or email address.
Depending on the app release and enabled features, the licensing infrastructure may process the Firebase UID, license state, timestamps, license source, and technical device information such as app version, installation ID, platform, locale, or device label.
The app may use Firebase Analytics for anonymous diagnostics and usage statistics. This helps measure active users, retention, app stability, navigation starts, saved field and task counts, and trial or license state.
Analytics events do not include field names, notes, farm names, precise GPS coordinates, or text entered by the user. Anonymous diagnostics and statistics can be disabled in the app settings.
When diagnostics are enabled on Android, the app may obtain the technical App Set ID from Google Play Services solely to measure additional installations of the same app. The raw identifier is immediately hashed locally; only a pseudonymous digest is sent to Firebase Analytics as its user identifier. It is not an advertising identifier, is not used for advertising or licensing, and is not stored in Firestore. The feature may be unavailable on devices without Google Play Services, and the App Set ID may be reset by the system.
The app uses Google Maps and may send technical requests and location-related data to Google services required for maps, geocoding, weather lookups, and field thumbnails. Exact location, approximate location, and, if permitted, background location are used only for navigation and location-based features.
The app lets you configure a connection to a third-party RTK correction service (NTRIP) to improve position accuracy together with a connected external GNSS receiver. The server address, port, mountpoint, and login credentials for the correction provider you choose are entered by you and stored locally on the device — they are not sent to the developer or to Firebase. The app only relays the correction stream (RTCM3) between the NTRIP server you specify and the connected GNSS receiver.
The "shared session" feature lets several devices see each other's position and tracks live within one working session. Data exchanged between devices in a session is encrypted in transit and is not used by the developer for any purpose other than operating this connectivity feature. The feature is limited during the trial and requires a verified, compatible device — see the Terms of Service for details.
Rain alerts use the device's approximate location and external weather data solely to generate a local system notification. The plant protection product search may query publicly available national plant-protection registries (depending on the country set in the app, including the Polish Ministry of Agriculture register and the US EPA registry) solely to look up product information. Neither feature sends data identifying you to the developer.
If you enable the cadastral parcel overlay or the additional geoportal layers (visible only to users in Poland), the app fetches map tiles and reference data directly from public government services: the Head Office of Geodesy and Cartography (GUGiK; e.g. mapy.geoportal.gov.pl, integracja.gugik.gov.pl, uldk.gugik.gov.pl) and the General Directorate for Environmental Protection (GDOŚ; sdi.gdos.gov.pl). Only the coordinate extent of the map area currently on screen, as needed to return a tile or parcel record, is sent to those services; no data identifying you, no Firebase account identifier, and no field data are sent. You may optionally download a slice of the GUGiK orthophoto to the device for offline use — those files are stored locally only and can be deleted in the app. Use of GUGiK and GDOŚ data is subject to those institutions' terms of access.
"Buy-in prices" and "Pest warnings" (visible only to users in Poland) use a public data feed (JSON) served by a backend function in Firebase (region europe-west1). That function periodically collects and organises data from publicly available external sources: crop buy-in price quotes from farmer.pl (Agroskop) and pest-signalling communiqués from the Pest Signalling Platform operated by the Institute of Plant Protection – National Research Institute (sygnalizacja.agrofagi.com.pl). The app fetches this feed anonymously — no authentication, no account identifier, and no user data are sent. Your watched-crop selection and price-alert thresholds are stored locally on the device, and notifications are generated locally.
The app can optionally (off by default) broadcast the corrected position in NMEA 0183 format over TCP or UDP on the local network, to work with external agricultural equipment (e.g. a lightbar, section controller, or sprayer computer). This data stays on your local network and is not sent to the developer or to Firebase.
The "Connect a browser" feature lets you pair a web browser on a computer with the phone (via a code or QR code) to view and partially manage the phone's data - fields, tasks, treatments, and settings - from a computer. While at least one browser is linked, the app syncs this data to Firebase, from which the linked browser reads it; a specific task's GPS trail is only transmitted on the browser's explicit request. Adding or editing a treatment from the browser is only a proposed change - the phone is the one that actually saves it. Without an active paid license, a newly linked browser gets one-time, non-renewable access for 20 minutes from the moment of linking; with an active paid license, access is not time-limited. The connection can be revoked at any time from the phone (menu → "Link a browser").
On your explicit request ("Download NDVI report" in the field details), the app sends the outline of the selected field (boundary coordinates in GeoJSON) and its approximate area to a protected backend function in Firebase (region europe-west1). The call requires anonymous Firebase authentication and a valid App Check token; a technical account identifier (Firebase UID) and the license status are also passed, solely to count the daily quota and check eligibility. The backend function retrieves an image and NDVI statistics for the field area from the Copernicus Data Space Ecosystem (Sentinel-2 satellite data of the European Union's Copernicus programme); the PDF is assembled locally on the device or in the linked browser. No data identifying the user is sent to Copernicus - only the area geometry and a date range. The app does not perform any automatic monitoring of fields and does not send this data to artificial intelligence models. The number of reports is limited per day (see the Terms), and the date and identifier of the satellite scene used are recorded in the generated report.
After a data country is selected, the app may use official agricultural and geographic sources relevant to that country. Embedded sources are fetched on demand and cached only locally or delivered through Firebase; other sources are links to external portals only. The app shows the feature scope, source and data date where available.
The listed providers are not our agents or commercial partners merely because their data or services are available in the app. Their own terms, privacy policies, licences and reuse restrictions apply. The catalogue may change when the selected country, service availability or licence terms change.
If Google Play products are enabled in a given release, purchases are handled by Google Play. The developer does not receive your payment card data. Technical purchase metadata may be processed to verify entitlements and restore access.
If the user saves JSON files, PDF files, or backups or shares data outside the app, that action is performed by the user. Once the data leave the device, they may be subject to the rules of the selected sharing channel, recipient, or cloud service.
If you contact us by email, we process your email address and the content of your message in order to answer you, handle support, complaints, or assist with licensing and organizational matters.
The roles depend on the feature and the data category:
The developer does not receive card numbers or full payment method details. The developer may process technical purchase metadata needed to activate, verify or restore a license.
Local data remain on the device until the user deletes them, clears app data, or uninstalls the app. Technical data in Firebase may be stored as long as needed for licensing, support, security, and accountability.
You may request information, rectification, deletion, or restriction with respect to data actually processed by the developer. For data stored only on your device, you manage them directly yourself.
The Polish version is the main and legally governing document. Other language versions may be machine translated and are provided for convenience only. In case of any discrepancy, the Polish version prevails.
This policy may be updated when app features, licensing, payment flows, or third-party integrations change.
Google Maps is a trademark of Google LLC.