unmapped
Unmapped Navigation LLC / Legal

Privacy Policy

The complete privacy policy for Unmapped's iOS app, website and related services.

Effective Date: Last Updated:
Read Terms of Service
Jump to a section

This Privacy Policy describes how Unmapped Navigation LLC, doing business as Unmapped ("Unmapped," "we," "us," or "our"), collects, uses, stores, discloses, and otherwise processes information in connection with the Unmapped iOS application, website, beta application process, backend services, and related services (collectively, the "Services").

Unmapped is designed around data minimization and local storage. Our goal is to provide useful navigation, offline mapping, trip planning, hiking, road, trail, weather, hazard, and outdoor features without maintaining a centralized database of our users’ complete travel histories.

Some features necessarily communicate with Unmapped or third-party services and may transmit location or other information. This Privacy Policy explains those circumstances.

1. OUR PRIVACY PRINCIPLES

Unmapped is designed around the following principles:

Local first. Personal adventure information that does not need to be centrally stored should generally remain on the user’s device.

Collect less. We seek to collect only information reasonably necessary to provide, secure, maintain, or improve the Services.

No location advertising business. We do not use users’ personal travel histories to create advertising profiles.

No sale of user data. We do not sell user personal information, including location information, and intend this commitment to continue even if Unmapped is acquired or sold.

Unmapped does not maintain an account-based database of users' complete saved trips, journals, favorites, or location histories. Voluntary geographic contributions described below are separate from those private local records.

These principles are subject to the more specific disclosures below.

2. INFORMATION STORED LOCALLY ON YOUR DEVICE

Many core Unmapped features store information locally on your device.

Depending on the features you use, locally stored information may include:

  • saved trips and trip legs;
  • routes;
  • journal entries and historical notes;
  • hiking tracks;
  • recorded hiking coordinates;
  • timestamps associated with recorded tracks;
  • elevation information;
  • photos associated with hikes, journals, or other local content;
  • favorites and saved places;
  • downloaded maps and offline regions;
  • cached points of interest;
  • locally collected cellular coverage observations awaiting transmission;
  • application preferences and settings;
  • authentication preferences;
  • other information you intentionally save within Unmapped;
  • user-created campground listings and queued submissions;
  • queued place corrections, roadside reports, and route-experience feedback;
  • vehicle profiles, fuel-planning settings, and selected trip statistics;
  • local elevation history and recording preferences;
  • local consent choices for coverage sharing and performance analytics; and
  • a short log of recent app events and, after the app ends unexpectedly, crash and hang diagnostics, kept only on your device unless you choose to send them with a bug report (described in Section 8).

The app does not currently synchronize complete saved trips, journals, favorites, private hike tracks, vehicle profiles, or local photos to a centralized Unmapped account. An optional, separately confirmed trail-data contribution can transmit a trimmed portion of a recorded hike. User-added campground entries and some other expressly submitted community content can also be sent to Unmapped's backend.

Device Backups and Exports

Information stored locally should not be understood to mean that the information can never leave your physical device. Depending on your device settings and services provided by Apple or other parties, locally stored information may be included in device or system backups.

Information may also leave your device when you intentionally export, share, copy, or send it to another application, person, or service.

The privacy practices of a destination selected by you are governed by that destination’s applicable terms and policies.

Deleting Local Information

You may delete certain locally stored information using controls provided by Unmapped.

Removing the app may remove its local data, subject to iOS behavior, backups, previously exported information, and other copies outside Unmapped's control. Some separately submitted community contributions may remain on Unmapped's servers after local deletion.

Signing out of an authentication feature does not automatically delete your locally stored trips, journals, hiking tracks, favorites, or other local application data.

3. LOCATION INFORMATION

Location information is necessary for many navigation and outdoor features.

With your permission, Unmapped may use your device’s location to:

  • show your current position;
  • provide navigation and routing;
  • record hikes and tracks;
  • calculate speed, distance, heading, elevation, and related navigation information;
  • determine progress along a route or trail;
  • find nearby campsites, trails, fuel stations, and other places;
  • provide geographically relevant weather information;
  • provide wildfire or hazard information;
  • display public-land or road information;
  • provide cellular-coverage functionality;
  • support offline navigation; and
  • provide other geographic features requested by you. Unmapped requests iOS While Using the App location permission. Live location is ordinarily used in the foreground, but lower-rate updates may continue in the background during an active trip recording or navigation session that you started, when iOS permits. The app currently samples elevation history approximately once per minute during eligible background activity and displays the iOS background-location indicator. It does not request Always-location authorization.

You can control location permission in iOS Settings and stop trip recording or navigation in the app. Features that depend on location may be limited or unavailable when permission is denied. Foreground, background, and precise-location availability also depend on iOS controls and device behavior.

4. PERSONAL LOCATION AND TRIP HISTORY

Unmapped does not currently maintain a centralized database containing your complete personal location history.

Saved trips, private hiking tracks, journal entries, favorites, vehicle profiles, and similar personal records are generally device-owned rather than synchronized with an Unmapped account. When you expressly choose to contribute a recorded trail track, a trimmed and reduced version is transmitted as described under Section 7.

This does not mean that no geographic information ever leaves your device.

Certain features transmit precise or approximate geographic information when necessary to provide those features. Those features are described below.

Requests for maps, search results, directions, weather, radar, public-land information, topographic information, and similar geographic services may also reveal the area being viewed, searched, downloaded, or traveled.

We do not sell your personal location history.

We do not use your personal travel history to create third-party advertising profiles.

5. CELLULAR COVERAGE CONTRIBUTIONS

Unmapped offers optional on-device cellular coverage recording. Recording and automatic sharing are separate user controls, and you can also choose to send queued points manually. Recording occurs only when an eligible cellular connection is the phone's active network route; Wi-Fi, hotspots, and similar connections are excluded by the current implementation.

When coverage sharing occurs, the device transmits observations that may include:

  • precise latitude and longitude;
  • timestamp;
  • cellular network or cell information;
  • radio technology;
  • signal quality;
  • location accuracy;
  • carrier, when available; and
  • a locally generated sample UUID, the app's cell identifier, and whether the user reports using a cellular booster or external antenna.

Automatic coverage sharing is off unless you enable it. When both recording and automatic sharing are enabled, the app may send batches after at least 50 points are queued and a connection is available. The Share Points button permits manual submission. Disabling future uploads does not retract previously accepted points.

Server Processing

When you submit cellular coverage observations, Unmapped's backend processes the points, stores raw batch archives in Cloudflare R2, and maintains geographic coverage aggregates in Cloudflare D1.

The current R2 coverage archive stores normalized records containing:

  • precise latitude and longitude;
  • radio technology and qualitative link status;
  • carrier, when provided;
  • whether a cellular booster or external antenna was reported;
  • observation time and a cellular-route context value; and
  • batch ingestion time and the number of accepted points.

The Worker also receives sample UUIDs, original timestamps, client cell identifiers, and location-accuracy values. It converts the observation timestamp for the raw archive but does not place the sample UUID, client cell identifier, or accuracy value in that archive. D1 holds geographic cell, carrier, technology, quality, booster, date, and sample-count aggregates. These storage paths have different retention characteristics.

Those archives and geographic aggregates do not intentionally attach an Unmapped account identifier or your saved trip records. This is not a promise that submitted coordinates or dates cannot be linked back to someone.

Important Limitation Regarding Anonymity

We do not represent that precise location information is guaranteed to be anonymous.

Precise coordinates, timing information, IP addresses processed during Internet communications, carrier information, free-text information, or combinations of information can potentially identify or be linked to an individual.

Accordingly, coverage contributions should be understood as contributions made without an intentionally attached Unmapped user identity, rather than as information guaranteed to be incapable of identification.

6. ROADSIDE, ROAD CONDITION, AND HAZARD REPORTS

Unmapped may allow users to contribute road, roadside, closure, hazard, or similar reports.

A roadside report submitted through the app may transmit:

  • report type;
  • precise latitude;
  • precise longitude;
  • the time the report was captured;
  • an optional note;
  • a source MVUM route identifier, when the report concerns one; and
  • a random submission UUID for retry and duplicate prevention.

Our backend may store:

  • a server-generated report identifier;
  • report type;
  • latitude and longitude;
  • report time;
  • server creation time;
  • expiration time;
  • report status; and
  • a note, if supported by the applicable feature and provided.

Reports may be assigned expiration times to prevent stale information from continuing to be presented as current.

Expiration does not necessarily mean that the underlying database record is immediately physically deleted.

These reports are not intended to be associated with your complete personal trip history or an advertising profile.

Precise-location reports should not be considered guaranteed anonymous.

Users may also confirm or dismiss an existing roadside report. A corroboration request includes the report identifier, an independent submission UUID, and whether the report is still present. The backend stores those verdicts and updates confirmation, dismissal, and status counts. Active, location-bounded reports may be returned to other users.

7. REVIEWS AND OTHER COMMUNITY CONTRIBUTIONS

Unmapped includes explicit community submissions, including trail and campground ratings, place corrections, user-added campground listings, route-experience feedback, and voluntary trail-track contributions. These data flows are distinct from private local trips and journals.

For example, a trail review may contain:

  • a trail identifier;
  • scenery or view rating;
  • trail-quality rating;
  • effort rating; and
  • a written comment.

Our backend may add a server-generated identifier and creation timestamp.

Submitted reviews, comments, ratings, and aggregated review information may be returned to other users. The app currently supports both trail ratings and campground ratings. Morning camp-condition check-ins are saved locally to the private journal, rather than uploaded as public reviews. Current native trail and campground review submissions do not intentionally include an Unmapped account identifier. They do identify the reviewed trail or campground and include the selected ratings and optional comment; the backend adds a submission identifier and creation time.

Anything you voluntarily include in a public comment may become visible to other users. You should not include personal, confidential, or sensitive information in public community content.

The backend also contains schemas for other community data. A server schema by itself does not mean that the current iOS interface submits every such field or that every route has been deployed.

User Added Campgrounds

If you add a campground, the app saves its name, precise selected map coordinates, type, reservation information, fire restrictions, amenities, fee information, stay limit, notes, and local creation or update times. Saving a campground also queues a server review submission containing available listing fields, a random submission identifier, and app version. The app attempts to send pending listings after saving and during later active sessions. There is no corresponding Unmapped account identity in the submission. Server acceptance does not mean the listing is verified or published to everyone.

Place Corrections

When you report incorrect place information, the app can send the displayed place identifier, place type, source and source record identifiers, displayed place coordinates, issue category, field name, displayed or proposed value, notes, data version, app version, and a random submission identifier. Those are coordinates of the place being corrected, not necessarily your current location. Pending submissions may be saved locally and retried. The server keeps a review-status record and does not immediately overwrite the source listing.

Route Experience Feedback

An optional off-road route questionnaire may send an MVUM route identifier, observed date, selected difficulty, conditions, obstacles, whether a vehicle scraped, and broad vehicle-capability categories such as clearance band, drivetrain, low range, tire type, and vehicle class. It does not send a personal vehicle nickname, make, or model in that payload. Successful submissions reach Unmapped's backend for community-data review and analysis. Failed attempts may remain in an on-device retry queue for up to approximately 13 days.

Voluntary Trail Track Contributions

A hiking track starts as local data. You must select recording and then separately confirm contribution after the hike. When you choose to contribute, the app removes approximately the first and last 200 meters of the route, samples no more than 2,000 remaining points, rounds coordinates, and sends a trail identifier, a random submission UUID, the observed calendar day, total distance, ascent, trim distance, and track points. Points can include latitude, longitude, altitude, relative elapsed seconds, horizontal accuracy, and segment-break flags. The submission does not include a complete private journal or a name, but a route can still be identifying.

The current backend stores the submitted trail-track points as a raw R2 object intended to expire no later than 31 days after the observed hike day and keeps a D1 submission record with trail, date, point count, distance, ascent, processing status, and object reference. Scheduled deletion is implemented, but successful deletion at a precise time depends on scheduled tasks and configuration. Do not assume the metadata row is deleted when the raw track is removed.

8. FEEDBACK AND SUPPORT

If you submit a bug report, feature request, support request, or other feedback through Unmapped, we may receive:

  • the type of feedback;
  • your message;
  • contact information, if you choose to provide it;
  • application version;
  • application build number;
  • operating-system version;
  • device model;
  • application logs, including the log from before an unexpected shutdown and any crash or hang diagnostics the device recorded, and recent API activity, if you choose to include them (described below);
  • if you choose to let the developer see your API requests on a bug report, a short one-way installation fingerprint and a random code created just for that report (described below);
  • the number of days, from 3 to 30, that you choose for Unmapped to keep these diagnostics; and
  • up to three screenshots or images you expressly attach to your feedback, and the number of days, from 3 to 30, that you choose for Unmapped to keep them (described below).

The bug-report form currently starts with log inclusion selected, with the option to let the developer see your API requests turned off, with the diagnostic period set to 14 days, and, once you attach a screenshot, with the screenshot period set to 30 days. Recording your API requests happens only if you turn that option on, separately from logs. You can change any option and the period, and use "Preview what will be sent" to see the exact log and API activity text before you send anything. The underlying installation secret is never sent.

Application Logs

These are short text entries the app records while it runs (for example, that a list of places finished loading or that saving a favorite failed), plus error entries the operating system recorded for the app. The most recent entries, up to 300, are also saved to a file on your device so that they are still available if the app ends unexpectedly. That file is excluded from device backups, is never uploaded automatically, and is replaced each time the app starts. Before sending, the app automatically removes text that looks like coordinates, email addresses, phone numbers, IP addresses, and file paths, and our backend repeats that filtering. Automated filtering can miss information, so please review the preview and do not include logs if you are concerned.

Crash and Hang Diagnostics

If the app ends unexpectedly while you are using it, for example because of a crash, a memory shortage, or because it stopped responding, the app detects this the next time it opens and keeps the saved log from that earlier session on your device instead of replacing it. The app also records, on your device, the name and a short technical stack trace of any uncaught error that caused the shutdown.

The app also receives crash, hang, processor-usage, and disk-write diagnostic reports prepared on your device by Apple's MetricKit framework, which iOS generally delivers within about a day after the event. These reports describe the type of problem, the version of the app and of iOS, the device model, and the technical call stack of the program at the time. They identify code locations in the app and do not contain the content of your trips, journals, or photos. The app stores up to five such reports and does not collect MetricKit performance or battery measurements.

None of this is sent to Unmapped or to anyone else automatically. It is included in a bug report only if you send one with the application logs option turned on, and it appears in the "Preview what will be sent" text before you send anything. The same automatic removal of coordinates, email addresses, phone numbers, IP addresses, and file paths described above is applied to it, and it counts toward the same size limit as the rest of the logs. After you send a report that includes it, the app deletes the saved log and the stored MetricKit reports from your device. Anything you do not send is deleted automatically after 14 days (saved logs) or 30 days (MetricKit reports), or sooner if you remove the app.

Recent API Activity

This is a list of up to the last 100 requests the app made to Unmapped's servers during the current session. Each entry contains only the time, the request method, a route template such as /v1/poi/campsites/{id} with identifiers removed, the response status, how long it took, and a short error label if it failed. It does not contain request addresses with identifiers or search text, coordinates, headers, or request contents.

Screenshots

You can attach up to three screenshots or images to a report. They are not sent inside the report itself. After the report is saved, the app sends each image as its own request, at full resolution and without reducing its quality. The app re-encodes each image before sending, which removes metadata embedded in the file, such as the location a photo may carry, but it does not change what the picture shows. A screenshot can show your location, a place name, a name, a message, or other personal information, so please review each one and remove anything you do not want us to see.

Each image is tied to its report by a random code created on your device just for that report, together with the report's identifier. Our backend stores only a one-way hash of that code and rejects an image that does not present it. The images are stored in Unmapped's backend object storage, separately from the structured feedback record, and our team can view them in an administrator dashboard. The backend also stores each image's size, type, and upload time, and how many images you said you attached, so we can tell when one did not arrive.

You choose how long Unmapped keeps your screenshots: from 3 to 30 days after you send the report, 30 by default. When that period ends they are deleted automatically from live storage; a scheduled clean-up runs hourly, and a screenshot past its end date is not shown to our team. Stopping and deleting recorded diagnostics, described below, does not delete your screenshots. To have them deleted earlier, contact us as described in Section 28 and include the date you sent the report. As with other feedback information, infrastructure providers, including any backups, may keep copies for limited periods under their own practices. Screenshots are not included in the outgoing feedback email, although the email states how many you attached and until when they are kept.

Report Code, Installation Fingerprint, and Diagnostic Period

If you turn on the option to let the developer see your API requests, your app creates a random code just for that report. For the number of days you chose after you send the report, your app adds that code to its requests to Unmapped's servers. While that period is open, our backend records, for each such request, only the API route category, request method, response status, and duration, up to a fixed limit for that report. Our backend stores only a one-way hash of the code, which is used to match those records to your report and to no other report. We do not record your location, the full request address, request contents, or your IP address in this diagnostic record. The code does not identify you, your Apple Account, or your device, but a device that holds the code can add records to that report's period.

The fingerprint is the first eight characters of a one-way hash of an anonymous random value created on your device. It is sent with the report only to let us tell which reports came from the same installation, and it can be matched across your reports from that installation. Older versions of the app used the fingerprint, instead of the report code, to record API requests; records made that way are kept under the same rules and period. Separate infrastructure and security logs described in Section 16 may still process network information such as IP addresses.

You can stop the recording and delete what was recorded at any time from the Contact Developer screen while the period is open. Stopping takes effect on your device immediately. Deletion asks our backend to remove the recorded requests and the logs and recent API activity that came with that report; if your device cannot reach our servers, the request is saved and retried the next time you open the screen. Withdrawing diagnostics does not delete the message, category, or reply contact you sent, which are handled as described in Section 17.

Unmapped's backend stores the feedback category, message, optional contact details, app and device version metadata, the optional installation fingerprint, a one-way hash of the report code, delivery status, and, if you included them, the filtered application logs and recent API activity together with the date your chosen diagnostic period ends. If you turned on API request recording, the backend also stores the route category, method, status, and duration records described above. When our team opens a report's diagnostics, the backend records which administrator did so and when. Logs, API activity, and these request records are deleted automatically when the diagnostic period ends, or sooner if you stop and delete them; a scheduled clean-up runs hourly, and information past its end date is not shown to our team. Screenshots are stored separately and kept for the period you chose for them, as described under Screenshots above. This deletion applies to Unmapped's live database. Cloud infrastructure still handles the submitted request in transit, and infrastructure providers, including database point-in-time recovery and any backups or exports, may keep copies for limited periods under their own practices, so we do not promise that every copy disappears on the end date.

When configured, feedback email delivery sends the submission identifier, category, time, optional contact, app version, device information, optional installation fingerprint, whether diagnostics were stored and until when, and message to Unmapped's operating mailbox. Screenshots, application logs, and recent API activity are not included in the outgoing feedback email; the email states only how many screenshots you attached and the date they are kept until. The email provider may retain delivered messages according to its policies.

Please do not include sensitive personal information in feedback unless it is reasonably necessary for us to address your request.

9. SIGN IN WITH APPLE

Unmapped offers Sign in with Apple and a Continue as Guest option. The current app uses these choices as a local entry gate; it does not operate a proprietary Unmapped username-and-password account database.

If you choose Sign in with Apple, the app asks Apple for your name and receives an Apple user identifier. Apple may supply only part of a name or no name depending on prior authorization.

The app stores the Apple user identifier and available display name in the device Keychain. A guest preference is stored in local app settings. These values are used for local authentication state.

Unmapped's native sign-in flow does not send the Apple user identifier to its backend. Sign in with Apple and guest access are local entry options rather than accounts that synchronize complete private trip records.

Apple separately processes information necessary to provide Sign in with Apple according to Apple’s privacy practices.

Signing out removes applicable authentication preferences but does not automatically delete other locally stored Unmapped content.

10. PURCHASES AND SUBSCRIPTIONS

Unmapped is currently in private TestFlight beta. The app contains a StoreKit purchase and entitlement framework, but paid Pro subscriptions are not currently available through the app. If purchases are offered in a later release, Apple will process App Store transactions.

Apple processes App Store transactions. Unmapped does not receive your complete payment-card information.

If subscriptions become available, Apple and Unmapped may process verified transaction and entitlement information necessary for paid features. The current app validates StoreKit entitlements locally and does not send private trip notes or hiking tracks to the backend for purchase verification.

Apple’s processing of payment, Apple Account, and App Store information is governed by Apple’s applicable privacy policies and terms.

11. APPLE MAPKIT AND OTHER APPLE SERVICES

Unmapped uses Apple technologies and services that may support:

  • map display;
  • destination and place search;
  • geocoding;
  • directions;
  • routing;
  • fuel-station or other place searches;
  • authentication; and
  • purchases.

When you use these features, Apple may receive geographic, search, route, authentication, purchase, device, or network information necessary to provide the requested service.

Apple’s processing of that information is governed by Apple’s applicable privacy policies and terms.

12. EXTERNAL MAP, RADAR, AND DATA PROVIDERS

Some features communicate directly with external data providers or open third-party destinations. Observed examples include topographic map tiles from the U.S. Geological Survey, weather radar from the Iowa Environmental Mesonet, and route forecasts requested from Open-Meteo using the requested waypoint latitude and longitude. Apple MapKit also receives requests for maps, search, and directions.

Requests for tiles or similar geographic resources necessarily identify the map area or geographic resource being requested. Together with ordinary network metadata such as an IP address, those requests may allow the provider to determine the geographic area being viewed or downloaded.

Remote images or thumbnails may similarly cause your device to contact the server hosting that resource.

Unmapped may also allow you to open third-party websites, applications, telephone actions, or other external resources.

Those third parties process information according to their own applicable policies and terms.

Website and Beta Applications

The Unmapped website uses an active Google Forms private-beta application. Google processes the information that applicants enter in the form and makes responses available to Unmapped for beta selection and communication. The requested fields are displayed in the form when you apply. Form responses are subject to Google's processing and Unmapped's access and retention practices.

The Unmapped website uses Cloudflare analytics. Website delivery and analytics may process visiting IP addresses, browser and device details, page requests, and activity metadata as applicable to the deployed service. These website analytics are separate from the optional app performance-analytics control.

13. BACKEND GEOGRAPHIC AND PUBLIC DATA REQUESTS

Unmapped’s backend may retrieve geographic and outdoor information from government, public, or third-party sources.

Examples may include:

  • public-land information;
  • recreation facilities and campsites;
  • wildfire information;
  • weather information;
  • trails;
  • Motor Vehicle Use Map information;
  • road information; and
  • other geographic datasets.

Your device may transmit a map cell, geographic bounding box, facility identifier, or similar information to the Unmapped backend to request relevant information.

Such a request indicates the area or resource being requested and may correspond to an area you are viewing or your location.

The backend may then communicate with an external data provider to obtain the requested information.

14. ARTIFICIAL INTELLIGENCE

Unmapped's backend can produce AI-generated summaries of recent trail reviews using Cloudflare Workers AI. This is different from an AI route-planning service; Unmapped does not currently offer an AI trip planner.

The currently implemented backend AI functionality uses Cloudflare Workers AI to summarize recent trail reviews.

When sufficient written reviews are available, information provided to the AI system may include:

  • trail identifier;
  • recent review comments;
  • scenery or view ratings;
  • trail-quality ratings; and
  • effort ratings.

The current implementation does not intentionally insert reviewer account identifiers, IP addresses, private journals, saved trips, personal photographs, or complete trip histories into the AI summarization prompt.

Review comments themselves may contain personal information if a user chooses to include it.

Cloudflare processes AI requests as a service provider subject to its applicable terms and privacy commitments. If Unmapped introduces additional AI functionality that materially changes what personal information is processed, we will update this Privacy Policy and provide any additional disclosures or choices required by applicable law.

15. CLOUD INFRASTRUCTURE AND NETWORK INFORMATION

Unmapped currently uses Cloudflare for portions of its backend infrastructure.

Requests to Unmapped's backend use HTTPS and app-release HMAC signatures containing method, path, request timestamp, and body digest. The signing key is shared by supported app releases rather than tied to a user's account. This reduces certain unauthorized and modified requests, but does not by itself prove that a request originated on genuine Apple hardware or make transmitted data anonymous.

When your device communicates with Unmapped’s backend, Cloudflare and Unmapped’s services may process ordinary network and request information, which may include:

  • IP address;
  • request headers;
  • endpoint, path, or query information;
  • timing information;
  • submitted request content;
  • security information; and
  • anti-abuse information.

Communications with the Unmapped backend use HTTPS encryption in transit.

HTTPS does not mean that submitted information is end-to-end encrypted from the backend. Cloudflare and Unmapped’s backend may process readable request content where necessary to provide the applicable service.

Unmapped does not intentionally use ordinary network metadata to construct a complete personal travel history.

16. OPERATIONAL LOGGING AND ANALYTICS

Unmapped uses limited server logging and operational analytics to operate, secure, troubleshoot, and improve its infrastructure.

Current custom operational analytics may include information such as:

  • API route category;
  • request method;
  • response status category;
  • HTTP status;
  • API request duration in milliseconds for custom request metrics; operation-specific numeric measurements, including counts; and
  • operation counts.

These custom aggregate datasets are designed not to deliberately include precise coordinates, account identifiers, or IP addresses. They are separate from any request-level Cloudflare logs, security protections, optional app performance analytics, and the short-lived diagnostic records described in Section 8, which are kept in a separate database table, only for reports where the tester turned on API request recording, and only for the period they chose or until they stop and delete them.

Separate infrastructure or security logs may process additional network information. For example, IP addresses may appear in certain security or rate-limiting logs.

Unmapped does not currently embed third-party advertising SDKs, behavioral advertising SDKs, or third-party crash-reporting SDKs in its iOS app. The app uses Apple's MetricKit framework, part of iOS, to receive crash and hang diagnostics on your device as described in Section 8. That framework does not send them to Unmapped.

Optional App Performance Analytics

The Privacy Dashboard offers Share performance analytics, off by default. If enabled, the app may send a bounded set of event names (map ready, route calculation, offline download, topographic tile, or tile fetch), outcome category, rounded duration and byte-size buckets, app version, and iOS version. The payload excludes precise coordinates, searches, saved-trip contents, photos, comments, and a stable user or device identifier. The current app queue is memory-only and uploads at most 20 events at a time without retrying failed batches. Turning the option off clears queued events and cancels pending uploads; already received analytics remain subject to server retention.

Cloudflare Analytics Engine accepts the validated event fields. Cloudflare still processes ordinary network metadata such as an IP address for the transmission. The backend also records aggregate API and data-operation metrics independently of this optional app setting.

17. DATA RETENTION

We seek to retain information only for as long as reasonably necessary for the purposes for which it is processed, subject to operational, security, legal, and technical requirements.

Local Information

Trips, journals, tracks, favorites, downloaded maps, local photos, and similar locally stored information generally remain on your device until you delete them, remove the application, or they are otherwise affected by your device or backup configuration. The saved app log, crash log, and MetricKit reports described in Section 8 are an exception: they are deleted after you send them, after 14 or 30 days as stated there, or when you remove the application.

Coverage Contributions

Accepted coverage measurements are stored in raw Cloudflare R2 batch archives containing precise coordinates, observation times, carrier and cellular-quality context, and may also be represented in geographic D1 aggregates. No automatic expiration or deletion is currently configured for the raw coverage archives or aggregates.

Disabling collection, clearing a local queue, or deleting the app does not delete earlier contributions already received by Unmapped. These server-side coverage archives and aggregates may be retained until Unmapped removes them or changes its retention practices, subject to applicable legal obligations.

Community Reviews

Reviews and similar community contributions may remain available while useful to the Services. We do not currently represent that all community reviews are automatically deleted after a fixed period.

Roadside Reports

Roadside reports may receive an expiration time that prevents them from being treated as current. Expiration does not necessarily result in immediate physical deletion of the database record.

Feedback

Feedback may be retained in backend systems and applicable email systems for as long as reasonably necessary to respond to the submission, investigate issues, maintain appropriate business records, or improve the Services. The optional diagnostics described in Section 8 are an exception: application logs, recent API activity, and request records are kept only until the end of the diagnostic period you chose (3 to 30 days, 14 by default), or until you stop and delete them, and are then deleted automatically from live storage as described in Section 8. Screenshots are likewise kept only for the period you chose for them (3 to 30 days, 30 by default) and are then deleted automatically.

Logs

Operational, security, and infrastructure logs may be retained according to our service configurations and the retention practices of applicable infrastructure providers.

Trail Track Contributions

The backend's raw contributed trail tracks have an intended expiry of 31 days after the recorded hike day and a scheduled cleanup process. Submission metadata in D1 can remain after the raw object is deleted. A missed cleanup or a provider backup may delay physical removal.

Other Community Submissions and Analytics

User-added campground submissions, place corrections, route-experience feedback, review content, and corroborations do not currently have a universally fixed automatic deletion period. Optional app analytics and operational metrics are retained according to the applicable service configurations and provider retention practices.

18. NO SALE OF USER DATA

Unmapped does not sell user personal information.

This is intended to be a continuing privacy commitment and is not limited to Unmapped’s current owners, management, corporate structure, or business model.

Unmapped will not sell, rent, license, exchange, auction, or otherwise transfer user personal information in exchange for money or other valuable consideration for another party’s independent advertising, profiling, data-broker, or unrelated commercial purposes.

This commitment includes, where applicable:

  • precise or approximate location information;
  • cellular coverage observations;
  • personal location history;
  • saved trips and routes;
  • hiking tracks;
  • favorites and saved places;
  • journals and notes;
  • user-submitted location reports;
  • reviews and community contributions;
  • authentication information;
  • personal device or network information;
  • feedback and associated contact information; and
  • information derived from these categories that can reasonably be linked to a person or device.

Unmapped will not operate a business whose product is the sale of users’ location, trip, or behavioral information to advertisers or data brokers.

Service Providers

This prohibition does not prevent Unmapped from allowing a service provider to process information when reasonably necessary to operate Unmapped or provide a feature requested by a user.

For example, information may be processed by cloud infrastructure, mapping, routing, authentication, payment, geographic-data, weather, email, security, or artificial-intelligence providers.

Providing information to a service provider for those purposes does not authorize the provider to purchase the information as an independent commercial user dataset.

No Standalone Sale of the User Database

Personal information collected through Unmapped may not be sold, licensed, auctioned, or otherwise transferred as a standalone commercial dataset, location dataset, customer database, advertising dataset, or data-broker product.

This commitment applies whether the proposed transaction occurs during ordinary operations, restructuring, financing, insolvency, bankruptcy, dissolution, acquisition, merger, or an asset sale.

Previously Collected Information

Our intent is that personal information collected while this commitment is in effect will remain protected by this commitment.

Unmapped will not rely solely on a later change to this Privacy Policy to retroactively authorize the sale of previously collected personal information for advertising, profiling, data-broker, or unrelated commercial purposes.

Where a materially incompatible new use would require consent under applicable law or the privacy commitments applicable when the information was collected, Unmapped will seek affirmative consent before applying that new use to previously collected personal information.

19. DISCLOSURES REQUIRED BY LAW AND FOR SAFETY

Unmapped may preserve, use, or disclose information where we reasonably believe doing so is necessary to:

  • comply with applicable law;
  • comply with a valid legal process or governmental request;
  • investigate fraud or abuse;
  • investigate or respond to security incidents;
  • enforce applicable agreements;
  • protect the integrity of the Services; or
  • protect the rights, property, or safety of Unmapped, our users, or others.

This section does not authorize Unmapped to commercially sell user information.

Because Unmapped does not maintain a centralized database containing users’ complete locally stored trips and personal location histories, we generally cannot disclose information that we do not possess.

20. USER DATA REQUESTS AND DELETION

Much of the personal information used by Unmapped is stored locally and can be managed through the application or your device.

You may delete applicable locally stored trips, tracks, favorites, journals, notes, maps, and other information using available controls.

Some community contributions are intentionally submitted without an Unmapped account identifier. As a result, Unmapped may not be able to reliably identify a particular contribution as belonging to a particular person after submission.

Unmapped does not currently maintain a server-side deletion mechanism that can automatically identify every non-account-associated community contribution made from a particular device or by a particular person.

For information that we can reasonably identify as relating to you, you may contact us to request access, correction, or deletion where applicable.

We may need information from you to reasonably verify and fulfill a request.

21. CHILDREN’S PRIVACY

Unmapped is a general-audience service, not specifically directed to children under 13. We do not impose an additional minimum age beyond applicable law.

We do not knowingly collect personal information from children under 13 in violation of applicable law.

If we obtain actual knowledge that we have collected personal information from a child under 13 without authorization required by law, we will take appropriate legally required steps to stop further collection and address or delete information that we can identify. Because many community submissions have no linked user account, we may not be able to identify every past submission from a particular individual without sufficient details.

A parent or guardian who believes a child has provided personal information to Unmapped inappropriately may contact us using the information below.

22. SECURITY

Unmapped uses reasonable technical and organizational measures intended to protect information processed through the Services.

Our privacy architecture also emphasizes data minimization. Personal adventure information that does not need to be centrally stored is generally kept locally.

The application includes integrity checks designed to detect unauthorized modifications, such as jailbreaks or attached debuggers. If a compromised environment is detected, the application may clear certain sensitive local data, including authentication preferences and installation nonces, to protect your information.

Communications with Unmapped’s backend use HTTPS encryption in transit.

No application, network, device, server, or storage system can be guaranteed to be completely secure.

Users should maintain appropriate security for their devices and independent copies of information they cannot afford to lose.

23. NAVIGATION AND SAFETY INFORMATION

Unmapped provides navigation, mapping, weather, geographic, hazard, trail, road, recreation, and outdoor information. Maps, Motor Vehicle Use Map information, road status, property or access information, weather, hazards, wildfire information, trail conditions, cellular coverage, public-land information, community reports, and other datasets may be incomplete, inaccurate, delayed, or outdated.

Users remain responsible for observing actual conditions, posted signs, official closures, laws, access restrictions, property boundaries, weather conditions, emergency instructions, and other authoritative information.

The collection or display of a community report does not mean that Unmapped has independently verified the report.

Additional rules concerning use of the Services may be contained in Unmapped’s Terms of Use.

24. ACQUISITION, MERGER, OR SALE OF UNMAPPED

Unmapped itself may someday be acquired, merged with another entity, reorganized, financed, enter bankruptcy or insolvency proceedings, or sell substantially all of its operating assets.

A change in ownership of Unmapped does not, by itself, convert user personal information into a product that may be sold for unrestricted use.

If control of Unmapped or substantially all of the operating business is transferred to another entity, information necessary to continue operating Unmapped or a substantially similar service may be transferred as part of that transaction, subject to applicable law and the privacy commitments applicable to that information.

Successor Obligations

Our intent is that any purchaser, successor, assignee, or other entity receiving personal information collected under this Privacy Policy must agree to honor the material privacy commitments applicable to that information, including the prohibition on selling user personal information described in Section 18.

A successor should not obtain broader rights to exploit previously collected personal information merely because ownership of Unmapped has changed.

User personal information may not be separated from the operating business and sold as an independent location database, advertising dataset, customer list, behavioral dataset, data-broker product, or similar commercial data product.

Materially Different Uses Following an Acquisition

If a successor wishes to use previously collected personal information for a purpose materially incompatible with the commitments applicable when the information was collected, the successor must comply with applicable law and obtain affirmative user consent where legally required or necessary to honor those commitments.

A change in corporate ownership alone is not intended to constitute user consent to a materially incompatible use of previously collected personal information.

Dissolution or Discontinuation

If Unmapped ceases operation and personal information cannot be transferred in a manner consistent with the privacy commitments applicable to that information, our policy is that such information should be deleted or appropriately de-identified where reasonably practicable and legally permitted rather than sold as a standalone user-data asset.

Continuing Commitment

Our intended principle is:

A change in who owns Unmapped should not turn information entrusted to Unmapped into a product.

25. YOUR PRIVACY CHOICES

Depending on the features you use, you may:

  • control location access through iOS Settings;
  • decide separately whether to record coverage points, share them manually, or enable automatic sharing;
  • decide whether to submit road, trail, hazard, or other community reports;
  • choose whether to submit reviews;
  • choose what information to include in public comments;
  • choose whether to provide contact information with feedback;
  • choose whether to use Sign in with Apple;
  • decide whether to request available AI-generated summaries and refrain from including sensitive information in public review text;
  • delete applicable locally stored information;
  • choose whether and where to export information;
  • contact us regarding information held by our Services;
  • turn optional app performance analytics on or off;
  • choose whether to attach screenshots, application logs and recent API activity, and permission for API request recording to feedback, preview exactly what will be sent, choose how many days (3 to 30) those diagnostics are kept, choose separately how many days (3 to 30) your screenshots are kept, and stop and delete recorded diagnostics at any time while the period is open;
  • choose whether to submit a trimmed hiking track after recording; and
  • use the local guest option instead of Sign in with Apple.

Certain features require particular information to function. For example, live GPS navigation cannot operate without access to location information.

26. INTERNATIONAL PROCESSING

Unmapped and its service providers may process information in the United States and other jurisdictions where applicable service providers operate.

Privacy and data-protection laws in those jurisdictions may differ.

We intend to comply with applicable requirements governing international processing and transfers where those requirements apply to Unmapped.

27. CHANGES TO THIS PRIVACY POLICY

Unmapped is actively developed, and our Services and data practices may evolve.

We may update this Privacy Policy to reflect:

  • new functionality;
  • changes in service providers;
  • changes in technology;
  • legal requirements;
  • security requirements; or
  • changes in our privacy practices.

When we materially change this Privacy Policy, we will update the “Last Updated” date and provide additional notice where appropriate or required by applicable law.

Changes to this Privacy Policy do not, by themselves, eliminate privacy commitments applicable to information previously collected where doing so would violate applicable law or the commitments made when that information was collected. In particular, the provisions concerning the sale of previously collected user personal information are intended to survive ordinary updates to this Privacy Policy as described in Section 18.

28. CONTACT US

Questions, concerns, and privacy requests may be directed to:

Unmapped Navigation LLC Doing business as Unmapped

Privacy Email: privacy@unmappednav.com
Support Email: help@unmappednav.com
Website: https://unmappednav.com
Mailing Address: 701 South St, Ste 100
Mountain Home, AR 72653
United States

When contacting us regarding privacy, please provide enough information for us to understand and respond to your request, but do not provide unnecessary sensitive information.