Privacy Policy

Last updated October 28, 2026

Huck is an offline trail map. It is built so that your data stays on your phone.

What Huck collects

Huck keeps your data on your phone. It has no accounts, no in-app analytics and no advertising, and it never asks for your name, your email or anything else about you. When your phone asks our server for something, the server sees your internet address, as every web server does, and shortens it before writing anything down. Everything that goes over the network is listed under Network use, below.

• Location — used to show your position on the map, snap you to the trail you are on, and record tracks you explicitly start. Since version 1.5.5, Huck also keeps the last 24 hours of where it has seen you, on your phone only, so Get me out can lead you back the way you came; Settings → Remember my path turns it off and clears it. Location data is stored only on your device, and in your phone's own backup if you use one (see Data deletion). A track you are recording carries on while the screen is off, still only to your device: on iPhone, iOS shows a location indicator while it does, whether or not you let Huck use your location all the time; on Android, Huck never asks for "Allow all the time" location, and shows a "Huck is recording your track" notification if you let Huck show notifications. On Android the position itself comes from Google Play services on the phone, as it does for most Android apps, and if the phone's location or Google Location Accuracy setting is off, Huck may bring up Google's own prompt to turn it on; what Google's location service then collects is set by your phone's Google settings, not by Huck. Since version 1.5.2, Huck itself never sends your position off the phone unless you ask it to. What you choose to send can carry it: a Huck+ hunt forecast you ask for from the hunt-unit chip sends where you stand, to about 35 feet (see Network use); a trip plan says where you sent it from, to within a few feet; a shared waypoint carries its exact coordinates; and on iPhone a share picture is a snapshot of the map, so it shows your position dot if the dot is on screen. On Android, Huck currently shares the text and the link only, with no picture. Before version 1.5.2, Huck sent your position by itself in one case: opening hunt details from the hunt-unit chip fetched the forecast for where you stood, to about 35 feet.
• Tracks, waypoints, favorites, routes, trip plans — stored only on your device, and in your phone's own backup if you use one. Otherwise they leave it only when you share them, for example as a trail link, a trip plan or a GPX or KML file, through your phone's share sheet. Links point to our server; see Shared links, below.

Network use

Huck's maps work entirely offline. The app connects to the internet only for the following. None of it carries a Huck account or an identifier from Huck; the subscription check runs under your own store account — your Apple Account on iPhone, the Google account signed in to Google Play on Android — as every store purchase does.

• Downloading a map region. A file fetch from our own server, packs.gohuck.app. No identifiers or personal data are sent. The server keeps a log of requests for about thirty days, and shortens every address before writing it down — the last part of an IPv4 address, and everything past the first 48 bits of an IPv6 one, is dropped — so the log shows roughly which network a request came from and, from an iPhone, which version of Huck and iOS made it, never who you are. Huck on Android adds neither version to its requests, so they name only the networking software that sent them. We use the log only to count things: how often Huck is opened and on which version, how many regions are downloaded, roughly where, roughly how many phones come back, and how many shared links are previewed or opened. After about thirty days, only the totals are kept.
• Checking for updated map data. When Huck opens, each time you come back to it, and when you open Downloads, it asks the same server whether the regions you have were rebuilt, for updated closures, area restrictions, points of interest and statewide map layers — and, for Huck+ subscribers, the campground and lookout listings and, from version 1.5.4, snow depth readings — and whether this version of the app is still supported. These requests name the files; from an iPhone they carry the version of Huck and of iOS, as every iPhone app's requests do, and from Android they carry neither.
• Shared links. A trail, route or waypoint you share, and the link in a trip plan, points to share.gohuck.app, which is our server too. A trail link names the trail; a route link carries the route's name and its trails; a waypoint link carries the name you gave it and its exact coordinates. When a link is loaded — by a messaging app drawing its preview (in Apple's Messages, that is your own phone as you send it), or by someone who opens it in a browser, which includes anyone without Huck on an iPhone and everyone on Android, where Huck does not open these links itself — our server writes down the time, which kind of link it was (a trail, a route or a waypoint), the shortened address and the app or browser that asked, and keeps that for about thirty days. It writes down nothing the link carries: not which trail, not the route's name or its trails, not the waypoint's name or its coordinates, and not the site the link was followed from. Entries written on or before October 4, 2026, can still hold the whole link, and that site when a browser sent it, until they are deleted, about thirty days after they were written.
• Wildfire and weather alerts. Huck fetches current wildfire perimeters and new fire starts from the National Interagency Fire Center's public map service (hosted on Esri's ArcGIS), the current fire restriction stages from the Idaho Department of Lands' map service, and active weather alerts for Idaho from the US National Weather Service, when Huck opens, each time you come back to it, and when you tap refresh on the fire or alerts sheet. These ask for the whole state's data; they contain no location and nothing about you.
• Avalanche danger. From version 1.5.4, while the Avalanche danger layer is on, Huck fetches the national avalanche danger map from avalanche.org (api.avalanche.org): when you turn the layer on, and when Huck opens or you come back to it, at most once every half hour. It asks for the whole country's map and keeps the zones that touch Idaho; the request contains no location and nothing about you.
• Checking your subscription. On each launch Huck asks your phone's app store — Apple's App Store on iPhone, Google Play on Android — whether a Huck+ subscription is active and what Huck+ costs. On Android it asks again each time you come back to the app, and confirms a new purchase to Google Play. This goes to Apple or Google, not to us — see Purchases below. On Android, Google's billing library, which runs these checks, can also send Google its own diagnostic logs about them.
• Weather forecasts (Huck+ features). When you ask for the forecast at a trail, Huck requests it from the US National Weather Service at weather.gov for that trail's coordinates. In the hunt details for a spot, a forecast is requested only when you tap "Get forecast", and one already saved nearby shows without a request. When you open them from the hunt-unit chip, the spot is where you are standing, so that request carries your position. These requests carry the coordinates, to about 35 feet, and, like every request on the internet, your IP address, and nothing else about you. Before version 1.5.2, opening the hunt details for a spot fetched its forecast by itself, unless a recent one nearby was already saved.
• Links that leave the app. Links on Huck's own screens open in your browser: "Check dates on Recreation.gov", an agency's page for a spot or an advisory, the links in Idaho Parks & Recreation's notes on a trail, a permit shop, the data sources, the App Store or Google Play. Huck sends those sites nothing beyond the page you tapped. On iPhone, driving directions open Apple Maps with the destination's coordinates. On Android, from version 1.5.2, they open Google Maps (or its website, where the Maps app is not installed) with the destination's coordinates.
• Documents you add (a Huck+ feature). Huck shows the photos and other files you add in its own viewer, on the phone, and on iPhone the PDFs too. The viewer loads nothing from the internet, and a link you tap inside a document opens in your browser. Before version 1.5.2, if a document linked to or embedded something online — a link you tapped inside a PDF, or a picture in a saved web page — the viewer loaded it from that site inside Huck, as a browser would, and that site saw your IP address.

Purchases

Huck+ is an auto-renewing subscription, sold by Apple on iPhone and through Google Play on Android. Payment, renewal and cancellation are handled by the store — entirely by Apple on iPhone, and by Google Play on Android — and we never see your payment details. On Android, Google Play also keeps a record of each Huck+ order and shows it to us: an order number, when it was charged, the model of phone it was bought on, and the buyer's country and state (and city and postal code too, in countries where we rather than Google are the seller of record). Google Play lets us look an order up by the buyer's email address, so that we can answer a question about a purchase or a refund, and lets us refund or cancel it. Huck asks the store on each launch (on Android, also each time you come back to it) whether your subscription is active, and stores only a yes-or-no answer on the device. The two stores do not share subscriptions: Huck+ bought on an iPhone does not unlock it on Android, or the other way around.

Children

Huck is rated 4+ on the App Store and Everyone on Google Play. It has no accounts and asks no one, child or adult, for a name, an email or any other personal information. The only records are the shortened server logs described above, the counts we make from them and, for a Huck+ purchase on Google Play, the order record Google Play keeps for us (see Purchases). They are the same for everyone.

Data deletion

Delete a track, waypoint, route or favorite in the app and it is gone from Huck, along with any GPX or KML copy of it you exported, except a picture Huck made when you shared it: that stays in Huck's cache on the phone until the phone's system (iOS or Android) clears it or you delete the app, and a waypoint's picture shows its name and coordinates. We never had a copy, with one exception: if you shared it as a link and the link was loaded on or before October 4, 2026, our server's log can still hold that link (for a waypoint, the name you gave it and its coordinates) until that entry is deleted, about thirty days after it was written. A link loaded after October 4, 2026, leaves nothing of what it carries in that log. A GPX or KML file you export is deleted at your next export or Huck's next launch, if not before: on iPhone, usually as soon as the share sheet closes. Before version 1.5.2, it stayed in Huck's cache on the phone, even after you deleted the track or waypoints in it, until the phone's system (iOS or Android) cleared it or you deleted the app; version 1.5.2 deletes any such copy at launch. Deleting the app deletes everything it stored on the phone. If your iPhone backs up to iCloud or to a computer, Huck's data is part of that backup, held by Apple or your computer for you, never by us, until the backup is replaced or deleted. On Android, Huck lets Android back it up: with backup turned on, Android may copy Huck's data to your Google account, and moving to a new phone can copy it across — held by Google or your phones for you, never by us. Anything you already shared stays wherever you sent it.

Who receives anything

Huck sells nothing to anyone and has no advertising or analytics partners. Apart from websites you open (and, before version 1.5.2, anything a document you added points to), six services receive anything from the app: the first four below, on every phone; avalanche.org, only while its layer is on; and your phone's app store, which is Apple on an iPhone and Google on Android. None of them gets a name or an identifier from Huck, and only the Weather Service can get your position, only as described above:

• Our own server — requests for map files, updates and the pages behind shared links, logged as described above, with the address shortened and, for links loaded after October 4, 2026, nothing a shared link carries, and kept for about thirty days.
• The US National Weather Service — a request for Idaho's active alerts; the coordinates of a trail or hunt spot whose forecast you asked for, to about 35 feet, which are your own position when you asked from the hunt-unit chip; and your IP address, which every web server sees for every request. Before version 1.5.2, opening a spot's hunt details was enough to send them.
• The National Interagency Fire Center's map service, on Esri's ArcGIS — a request for Idaho's current fire data, and your IP address, as above.
• The Idaho Department of Lands' map service — a request for Idaho's current fire restriction stages, and your IP address, as above.
• avalanche.org, the National Avalanche Center's public data service, from version 1.5.4 and only while the Avalanche danger layer is on — a request for the national danger map, and your IP address, as above.
• Apple, on an iPhone — your subscription status, as part of running the App Store purchase you made with them; the destination of any driving directions you open in Apple Maps; and your rating, if you answer the App Store's rating prompt.
• Google, on Android — your subscription status and any Huck+ purchase, through Google Play under the Google account you are signed in with, as part of running the purchase you made with them; any diagnostic logs Google's billing library sends Google about those checks; the destination of any driving directions you open in Google Maps; and your rating and review, if you answer Google Play's rating prompt, which Google publishes as a public review on the Play Store.

Map data displayed in the app comes from public sources — the US Forest Service, Idaho Parks & Recreation, the Bureau of Land Management, the National Park Service, Idaho Fish and Game, the Idaho Department of Lands, Recreation.gov, USDA and USGS imagery, the FCC's broadband map and OpenStreetMap contributors — and is in the app's map files. Apart from the fire restriction request above, and any of their pages you choose to open in your browser, nothing is sent to them.

This website

gohuck.app is served through a content delivery network, whose standard logs record each request with the last part of the address already removed. From them we count which pages were viewed, how many times, which other sites linked to them, which addresses were not found, from which countries (and, in the US, which states), and roughly how many different browsers; after thirty days, only the daily totals are kept. The site loads nothing from anyone else: no cookies, no JavaScript trackers, no third-party fonts and no third-party analytics service. The app itself contains no analytics code. On Android it does carry Google's billing library, which sells Huck+ through Google Play and can report its own diagnostics to Google, as described above.

Changes

If this policy changes, the date at the top changes with it. Material changes will be noted in the app's release notes.

Contact

Questions: support@gohuck.app