MapCraft is built upon a strict local-first, offline-sovereign database model. Unlike traditional cloud GIS platforms, all spatial data collected on the app — including project folders, layer maps, recorded routes, triangulation targets, location points, and attributes — is stored completely locally inside the device's secure SQLite / Room database containers.
We do not operate servers that gather, harvest, monitor, index, or store your coordinates, maps, or field logs. Your data remains fully your own, and you have exclusive access and rights to export, delete, or clean up your GIS databases at any time.
To provide high-accuracy mapping and network dead-zone logging, MapCraft requires specific system permissions. Here is a transparent breakdown of why these are requested and how they are handled:
If you choose to activate Professional Mode using a department code, the app will make HTTP connections to the official Git repositories and endpoints configuration files configured by your department. This fetch pipeline checks for GIS boundary revisions and retrieves layers. During this process, only the department identifier and version number are transmitted; no personal field data is uploaded.
This documentation and support website does not use cookies for tracking or analytics. We utilize HTML5 Local Storage strictly to remember your preference for Light or Dark theme styling to improve readability.
For legal inquiries, GDPR data requests, compliance certificates, or support regarding custom setups, contact:
Email: privacy@mapcraft.app