Privacy Policy

Effective October 2026

The short version: we don't know who you are, and we'd like to keep it that way. Your files stay on your device, and so does your precise location. Only an approximate location leaves the phone: for weather (including the temperature the app keeps current on its home screen) and when you search for a place online. We keep anonymous tallies (how many visits, how many exports) with no accounts, no tracking cookies, and no identifiers. When the app or website loads maps, weather, or search results, the servers providing them see what any web server sees; this page lists them.

This policy covers getmapgo.com, the CacheMap tool, GetMapGo Studio (its Plan and Print pages), the location-sharing page, and the GetMapGo mobile app, all operated by Spanyo LLC, a Kansas limited liability company.

Your files never leave your device

CacheMap parses your GPX file, assigns counties, animates, and renders exports entirely in your browser. GetMapGo Studio opens, edits, and saves Atlases, GPX, KMZ, and KML files in your browser too. Neither uploads your files to us; you can verify this in your browser's network tools. In the app, your Atlases, tracks, routes, waypoints, and notes are stored on your device.

Preferences, corrections, and unsaved Studio drafts are kept in your browser's local storage, on your device, and can be cleared by you at any time.

Your location stays on your device (with two exceptions)

The app uses your GPS position to show where you are, record tracks, and center maps and searches. It is processed and stored on your device, and no server of ours receives your precise location. Two app features do send a location to another service, as described under "What other services see": weather sends the forecast point, rounded to about half a mile, to the National Weather Service, and online place search sends your approximate location (within about 5 miles) with your search so nearby results come first. The temperature on the app's home screen uses your last known position and refreshes on its own when its saved forecast is more than an hour old.

The location-sharing page puts the shared position in the part of the link after the #, which browsers never send to a server. The page only requests the map tiles around it.

No accounts, no cookies, no tracking identifiers

The Service has no user accounts, sets no tracking cookies, and does not fingerprint or identify visitors. We do not track you across other sites or services, so a browser's Do Not Track or Global Privacy Control signal changes nothing about what we collect.

What other services see

When the website or app fetches data over the internet, the server providing it sees what any web server sees: your IP address and what was requested. Specifically:

Each of these has its own privacy policy. In an Atlas map, the app's "Use downloaded maps only" setting keeps map tiles, elevation, and trail routing on the device. It does not cover weather, tide tables or place search: those still go online when you open them, and weather and tide tables are refreshed when you run a Field Ready check with a connection.

GetMapGo mobile app error reporting

When "Share anonymous crash reports" is enabled in the GetMapGo mobile app's Profile (on by default; you can turn it off there), the app uses Sentry to send scrubbed diagnostics about crashes, errors, and freezes (when the app stops responding). A report may contain the error and its stack trace and severity; the app version; the operating system and its version; device details such as model, memory, free storage, screen, and graphics chip; the device's language and time zone; and a short list of recent in-app events such as screen changes, with names, paths, and coordinates removed. They do not contain screenshots, session replay, Atlas or map files, tracks, routes, waypoints, notes, searches, API keys, or precise GPS coordinates. Before a report leaves your device, the app removes file and folder paths, Atlas, route, waypoint and track names, coordinates, and keys from its text. One exception: a crash the phone's system records is sent the next time you open the app, and if it is sent before that cleanup starts it may include a file path or a random per-install identifier created by Sentry. Reporting can be turned off at any time in the app. Reports created without connectivity may be queued on the device and delivered after it reconnects.

We use crash reports only to find and fix problems in GetMapGo. They are not used for advertising or profiling, and we do not sell or share them.

Sentry necessarily processes the connection's IP address while receiving a report. The app configures the Sentry SDK not to attach an IP address to the report payload. Sentry's processing is also governed by its own privacy policy.

Anonymous usage statistics

So we can tell whether anyone uses the website, we count aggregate, anonymous events: page visits (without cookies), which Studio mode was opened, taps on the links to the beta app, the number of CacheMap animations built and exports made (by format), and coarse, bucketed size ranges (for example, "an animation of roughly 5,000 to 5,500 finds was exported"). In Plan and Print we count actions, not content: an Atlas started, opened, or saved (with a size class such as "up to 5 areas"), a file imported (by type), a route added, and a GPX or PDF made (with the page count). These counts contain no names, no coordinates, no identifiers, and cannot be traced back to a person or a geocaching account. Visits from search engines and other automated crawlers are left out. When CacheMap's embed helper is used, we also count which hosting service it was used for (for example "a Google Drive link was converted"); the link itself is never transmitted or stored.

GetMapGo mobile app usage statistics

When "Share anonymous usage statistics" is enabled in the GetMapGo mobile app (on by default), the app sends coarse product events to our own Cloudflare-hosted endpoint. Examples include an Atlas being created or opened, an offline download completing, a Field Ready result, a track being saved, or weather and route-profile features being opened. Events may include the app version, operating system, broad result categories, waypoint type, and coarse duration buckets.

These statistics do not contain a device or advertising identifier, GPS location, Atlas/route/track/waypoint names, search text, notes, filenames, imported file contents, or exact distances and times. Events created while offline may be held in a small, capped queue and delivered after the app reconnects. Turning statistics off in Profile deletes queued events and stops new ones.

GetMapGo mobile app permissions

GetMapGo mobile app age check

So the app can follow app-store age laws (such as Texas's), after you agree to the Terms of Service it asks your app store for your age range. On Android it asks Google Play wherever you are, and Play decides what to share: it answers where such laws apply and otherwise only if your Play settings allow it. Google Play can also report whether a parent has approved certain app changes. On iPhone the app asks only where Apple says age rules apply to your account. We never ask for your birthdate, and the store decides whether to show its own prompt, based on your store settings.

The app uses the answer only to apply our minimum age (13) and to comply with these laws. It keeps, on your device, only the outcome (whether the app may open, or a reminder to verify your age in the Play Store), when it was checked, and an internal number that tells it when a new check is due. The age range itself is not stored and is never sent to us or anyone else.

Hosting and logs

The website and our map servers are hosted on Cloudflare. Like any web host, Cloudflare processes standard request metadata (such as IP addresses) to deliver the site and defend against abuse; that processing is governed by Cloudflare's own privacy policy. Our servers keep short-lived request logs (about three days) for troubleshooting. We do not store your IP address in our statistics. Our map server also counts about one request in a hundred by product and type of data (for example "website, terrain"), without the IP address or the map location requested. Anonymous app, website, and map server counts are stored in Cloudflare Workers Analytics Engine.

Sharing is your choice

An Atlas, GPX, or PDF leaves your device only when you share or save it somewhere. A shared Atlas contains its areas, routes, waypoints, notes, imported files, and any name and change notes you typed into its history, so review it before you share. Geocache descriptions and hints are left out of shared Atlases by default; the cache's code, type, difficulty, terrain, size, and owner stay with its waypoint.

An Atlas you share with GetMapGo or post in a GetMapGo community space, such as our Discord server, may be shown, shared, and promoted publicly, including commercially, as our Terms of Service describe. We may remove personal details or sensitive locations first. Atlases you send privately to other people never reach us.

Feedback

Feedback and ideas you send us (by email, in Discord, or otherwise) may be used and shared as our Terms of Service describe. If you email us, we keep your address only to reply, and you can ask us to delete the conversation.

Email sign-up

If you give us your email on the sign-up form, we use it for GetMapGo updates only, such as beta testing invites, launch news, and new tools. We don't sell, share, or enrich it. Every email includes an unsubscribe link, and you can ask us to delete it at any time (see Contact). If you ask for an Android beta invite, we add your email to our tester list on Google Play so Google can give you access.

Things you choose to do elsewhere

Links and actions that take you to other services are governed by those services' terms and privacy policies, not this one. That includes our Discord server, TestFlight, Google Play, the App Store, Ko-fi, the email app or share sheet you send an Atlas with, and wherever you host an export (Google Drive, Dropbox, your geocaching profile).

Children

The Service is not directed at children under 13, and we do not knowingly collect personal information from children under 13. The personal information we handle at all is limited to what this page describes, such as an email address you give us and the IP addresses our hosts and providers necessarily process. Where the app store reports that an account belongs to someone under 13, the GetMapGo mobile app shows a notice instead of opening.

Your choices

Changes

If our practices change, this page changes first, with a new effective date. We will not quietly weaken the promises above.

Contact

Questions or requests about your privacy: feedback at getmapgo dot com.