Ultralight Geospatial LLC ("ULGS," "we," "us") builds offline-first field tools. This page describes what our mobile apps and this website do with information, and the choices you have. It applies to every version of every app we publish — free, limited, and paid alike.
This section applies to every mobile application published by Ultralight Geospatial LLC. Where apps differ, the difference is stated here by name. If an app is ever governed by a separate policy instead, it will be named here, and that app's store listing will link to its own policy — the policy linked from an app's store listing is always the one that governs that app. As of the effective date above, no such app exists: this page is the complete privacy policy for every ULGS app. Apps are currently distributed in the United States (testing phase).
Recording your device's GPS position — points, tracks, photo positions, elevation profiles — is what these tools are for. Location is used only while you are actively using an app to record or navigate, or while a recording you started is running. In our navigation app, a recording you start continues while your screen is off or locked, shown by a visible ongoing notification; stopping the recording ends it. Our elevation-profile app has no background recording at all: it works only while it is open on screen. Position data is stored locally in the app's private storage.
Position fixes and Google's network location. On standard Android, if an app is allowed to use network-based location, the operating system may resolve your position through Google's network location service — meaning nearby cell and Wi-Fi information leaves your device to Google, by the platform, not by our code. Where our apps offer a GPS-only mode, choosing it means the app requests satellite positioning only; where network location is used at all, it is as a fallback when GPS has no fix. On de-Googled Android systems this platform service behaves according to that system's own configuration.
Waypoints, tracks, logs, routes, notes, and photos you create stay on your device. We cannot see, access, retrieve, or delete them. What happens to them if you uninstall an app depends on where that app keeps them:
Device backup and phone-to-phone transfer are governed by your device's own backup and migration settings.
Our apps currently run on Android phones and tablets, and this policy describes that architecture. We are interested in other form factors — watches, vehicle systems, and sharing between nearby devices. If we ship for them, some involve pathways this policy doesn't yet describe: syncing between a phone and a watch, for example, can pass through the platform's own services, the way network location does today. Our commitment is the same one this whole page rests on: any new data pathway will be described here, by name, before the version that uses it is released — and the promises that don't depend on architecture (no ULGS servers, no collection or storage by us, no selling, no ads, no accounts) hold on every platform we ever ship for.
Some of our apps can fetch public map and terrain data over the network. When they do, the request goes directly from your device to the public service, under that service's own privacy policy. We are not in the middle and receive nothing. One of our apps opts out entirely: our camera app declares no INTERNET permission and cannot contact any service — a structural property of the app, not a setting. The services our apps contact, by name:
Be aware of what these requests contain: fetching a map sheet or terrain layer sends the area you are asking about; sampling elevation along a route you have drawn sends that route's coordinates. Nothing about you — no name, account, or identifier we control — accompanies these requests, and we store nothing; but the request itself necessarily tells that service where you are looking or the line you are tracing, and their servers keep ordinary logs. Fetched data is cached in the app's private storage (bounded, clearable in the app, removed on uninstall) so areas you have loaded keep working offline. If you prefer that no request leave your device in the field, load your maps and terrain at home and work from the cache — the apps are built for exactly that.
In our camera app, location embedding is under your control, and photos can carry no location at all. Beyond that, the two copies the app can produce are deliberately separate in what they carry: the located copy contains position data and no camera metadata; the No Mark copy contains the camera's ordinary technical metadata — for example make, model, firmware version, and exposure settings — and no location data. No file the app produces contains both a position and a device description. Neither copy contains serial numbers or any per-device identifier.
If an app offers to send a crash report, the report is a file written on your device. It contains technical state — not your records or location history — and it is shown to you in full before anything is sent. Sending is always your action, by email, and never automatic. Anything you type into the optional note is included as you wrote it, so describe the problem in whatever detail you're comfortable sharing.
When we diagnose a report, the technical contents describe our own code, and we analyze them with our development tools. Your email address and anything you wrote in the note are yours: we separate them from the technical contents before analysis, and we never feed them into any tool or service that is permitted to train on them.
Each app requests only what its own features require. From the apps' merged manifests: our camera app requests Camera and Location; our navigation app requests Location and Notifications (the ongoing recording status described above); our elevation-profile app requests Location only. No app requests a storage or media permission: file import and export go through the system file picker, which grants access to exactly the files you choose, and the camera app writes photos to your gallery through the platform's media store — it can reach the photos it created, not the rest of your gallery. Network access is described in the services section above, and our camera app has none. Decline or revoke any permission in your device settings; the corresponding feature stops and the rest of the app carries on.
Paid licenses and upgrades are processed by Google Play. We receive transaction records (what was purchased, when, in what country) but never your payment card details.
Where we offer a free or limited version of an app, this same policy applies without exception: no advertising, no trackers, no accounts, and no additional data practices of any kind. A free version is a smaller tool, not a data funnel. Our apps do not phone home to check licenses, and we do not restrict your ability to export your own data in any version.
ulgeospatial.com is informational. No accounts, no advertising, no analytics scripts, no cookies set by us.
Our apps and site are professional field tools intended for adults. They are not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact support@ulgeospatial.com and we will delete it.
Because your records live on your device and not on our servers, you exercise most rights directly: view, export, and delete your data in the app at any time.
For what little we do hold — support email and store transaction records — you may request access, correction, or deletion at support@ulgeospatial.com. Residents of California, the EU/EEA, the UK, and other jurisdictions with privacy statutes may have additional rights under those laws; we honor valid requests regardless of where you live, and we do not discriminate against anyone for exercising a privacy right.
Your records sit in app-private storage (or, for photos and exports, your device's own gallery and Downloads), protected by your device's security. Because we do not hold your data, the measures that matter are on your device: use device encryption and a strong screen lock, and follow your organization's device policies where they apply.
Organizations that license our apps may have their own data-handling, retention, and public-records obligations covering data their teams collect. Those obligations are the organization's, and this policy does not alter them. Note for review teams: the network behavior described in Section 01 — named public services, request contents, and the offline cache workflow — is the complete inventory of the services our apps contact. If your agency needs data-handling documentation for procurement review, write to support@ulgeospatial.com.
Updates will be posted to this page with a revised effective date. Material changes will be noted in the affected apps' release notes.