GeoAppField
Android App Active Production
Legal & Transparency

Privacy Policy for GeoAppField

GeoAppField is an Android application designed for professional field geologists, prospectors, and exploration teams. We are committed to full transparency regarding data handling, offline storage, hardware location telemetry, and secure cloud synchronization.

Effective Date October 26, 2026
Developer Kevin Ortega
Domain kevinortega.dev
Application Version v1.0 (Production)

Hardware GPS Only

Location coordinates and traverse breadcrumbs are captured exclusively for geological mapping and sample tagging.

Offline-First Architecture

All rock samples, lithology codes, and structures remain in device-encrypted SQLite storage until you explicitly trigger sync.

Zero Ads & Trackers

We do not use advertising SDKs, marketing trackers, behavioral analytics, or third-party data broker services.

Enterprise Multi-Tenancy

Remote storage connects securely to designated company Firestore databases with strict role-based access rules.

1. Overview & Scope

This Privacy Policy applies to the GeoAppField mobile application for Android devices, developed and published by Kevin Ortega (kevinortega.dev).

GeoAppField is built to support geological field mapping, surface exploration, rock sampling, structure logging (strike, dip, dip direction), and mineralization documentation in remote, offline environments. Your proprietary exploration data is of high commercial value; our policy reflects the highest standards of data isolation, local sovereignty, and operational privacy.

2. Information We Collect

The application processes only the technical data required to execute geological workflows:

  • Authentication Credentials: User email and password handled securely via Firebase Authentication to authenticate the geologist against authorized enterprise workspaces.
  • Geological Sample Data: Station IDs, project names, zones, targets, mining concessions, lithology codes, colors, sample types, sample dimensions, alterations, mineral percentages, and structural geology measurements.
  • Field Observations & Comments: Field notes and descriptions inputted by the sampler during outcrop inspection.
  • Spatial Coordinates: Latitude, longitude, elevation, and UTM (Universal Transverse Mercator) projections captured directly from hardware sensors.

3. GPS Hardware & Location Data

GeoAppField requires access to high-accuracy device location services (ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION):

Location Usage Clarification

Location telemetry is utilized only for the following explicit purposes:

  1. Recording the exact spatial coordinate of collected physical rock samples.
  2. Calculating mathematical UTM Easting, Northing, and Zone projections for stratigraphic and mining grids.
  3. Rendering the geologist's live position on the offline topo map interface.
  4. Recording traverse breadcrumbs via an active foreground service (FOREGROUND_SERVICE_LOCATION) to visualize walked exploration tracks.

Background Tracking: Location tracking only operates while the foreground service notification is actively visible to the user in the Android status bar. Location telemetry is never recorded covertly or transmitted to advertising networks.

4. Offline Storage & Room Database

GeoAppField operates with an Offline-First design paradigm. When a geologist creates or edits a sample in remote terrain without cellular or satellite coverage:

  • All records are saved immediately into an internal SQLite database managed by Android Jetpack Room.
  • Data is stored in private internal application storage sandboxed by the Android operating system, preventing unauthorized access by other installed applications.
  • Samples are flagged with a synchronization state (PENDING_SYNC) until deliberate user synchronization occurs.

5. Cloud Synchronization (Firestore)

Synchronization with remote cloud storage is strictly on-demand:

  • Pending-Only Upload: Tapping the Sync button scans the local database for samples marked as PENDING_SYNC and securely batches them to the company's designated Firestore database (e.g. db-carrizal).
  • No Unsolicited Background Traffic: Automatic periodic background polling is disabled to conserve battery and satellite bandwidth in field scenarios.
  • Multi-Tenancy Isolation: All remote transmissions connect to scoped Firestore database instances partitioned per exploration project.

6. Sample Deletion & Soft-Delete Architecture

In compliance with mining exploration auditing and data integrity regulations:

Deletion Flow

When a sample is deleted using the in-app delete button on the sample detail screen:

  • Local Removal: The record is immediately and completely purged from the device's internal SQLite Room database. It will no longer appear on your local dashboard or map.
  • Cloud Audit Preservation: In Cloud Firestore, the record is not destroyed. Rather, its status is permanently transitioned to deleted with an official timestamp (deleted_at), ensuring historical compliance without polluting field sampler views.

7. Android Permissions Requested

GeoAppField requests only standard, essential permissions strictly needed for its advertised core functionality:

Permission Type Purpose
ACCESS_FINE_LOCATION Dangerous (Runtime) High-accuracy GPS hardware coordinates for geological sample pins.
ACCESS_COARSE_LOCATION Dangerous (Runtime) Cell tower / Wi-Fi fallback coordinate estimation.
FOREGROUND_SERVICE Normal Maintains live exploration tracking while the app is in the field.
INTERNET Normal Transmits samples to Cloud Firestore during user-triggered sync.
ACCESS_NETWORK_STATE Normal Detects network availability before attempting cloud synchronization.
POST_NOTIFICATIONS Dangerous (Runtime) Displays foreground tracking status and export completion alerts.

8. Data Retention & Security

We implement industry-standard technical measures to safeguard your field exploration data:

  • Transit Encryption: All cloud communications with Google Cloud / Firebase Firestore utilize Transport Layer Security (TLS 1.3 / HTTPS).
  • Storage Sandboxing: Local database records exist within the isolated user storage boundary enforced by Android Linux kernel permissions.
  • Export Control: When exporting Excel (.xlsx) or CSV files, generated files are stored in the app's secure cache and shared exclusively through Android's system share sheet (FileProvider).

9. Children's Privacy

GeoAppField is a specialized enterprise and professional industrial application not directed toward individuals under the age of 18. We do not knowingly collect or solicit personal information from children.

10. Changes to This Privacy Policy

We may update our Privacy Policy periodically to reflect app updates, new geological features, or regulatory compliance standards. Updated revisions will be published immediately at this URL with an updated effective date.

11. Developer Contact

If you have questions, feedback, or data privacy inquiries regarding GeoAppField, please contact the developer directly:

KO

Kevin Ortega

Independent Software Engineer & GeoAppField Maintainer

Website: https://kevinortega.dev

Email: contact@kevinortega.dev