HelioMaps Get the app

Privacy Policy

Last updated: November 4, 2026

HelioMaps is a hunting‑property mapping app made by HelioLogix LLC ("HelioLogix," "we," "us"). This policy explains what we collect, why, and the choices you have. We built HelioMaps to be useful offline and to keep your data yours. We don't sell your personal information.

What we collect

How we use it

Location, in detail

Location is used to center the map on you (which then decides the map area the lookups below send), to record tracks, to fetch weather and your county's rut dates when your ranch has no location of its own, to start an approach path from where you are when you choose My location, and, only when you explicitly start it, to show your live position to others on the ranch you have open who are also sharing. Live sharing is off by default, is opt‑in each time, and stops on its own after 5 hours. You can revoke location access anytime in your device settings.

While the app is not in use. Two features keep using your location after you put the phone away: recording a road or a track, and live sharing. While either is running, the app collects your location with the screen locked or the app in the background, so the line you are recording is not broken and others on the ranch you have open who are also sharing can still see you. Your phone shows an ongoing notification or a location indicator the whole time, and collection stops the moment you stop recording or stop sharing. While a recording runs, and while the map follows you during a live share, the map keeps centering on you. The lookups the map makes each time it comes to rest (under "Moving the map", "All public land" and "Public access easements" below) wait while the app is out of sight, and run once for the view you come back to. The basemap, the Water detail layer, the roads overlay and the other layers drawn as map images (Soils, Crops, BLM land, and All public land whenever it shows as images), and property lines and terrain from our own tile service, may still load for the area around you with the screen locked, and while your ranch has no boundary, parcels or saved center point, so may the weather and rut‑county lookups, each sending your phone's location rounded to about a kilometer. Nothing else in the app uses your location in the background, except that once you have opened the 3D map, Mapbox's software may keep collecting de‑identified location data while HelioMaps has location access, until you close the app (turn it off with ⓘ on the 3D map).

Where your coordinates go. Your ranch's center is the middle of its boundary or, without one, of its parcels; for a ranch with neither, it is the ranch's saved center point, which can be an earlier location of your phone. Weather is requested for your ranch's center rounded to about 10 meters, and the county behind rut dates for the same place rounded to about a kilometer; when the ranch has no center, both use your phone's location rounded to about a kilometer (Best blinds, the Route report, Weather here, Plan approach and Show approach path add weather points of their own, set out below). Place searches send what you type or paste and, when the map is zoomed in closer than a view of several states, the middle of the map rounded to about 10 km, so nearby places come first; routing sends your start and destination. Loading the map sends the area you are viewing to the map services listed below, and property lines only to our own tile service. That area is usually the property you are looking at, but whenever the map is centered on you (you center it, it follows you or records a road or a track, or it opens on your location because nothing else is saved to show) it is the area around you. Which services receive that area, a point or the square around your ranch's boundary and parcels, and when, is set out in "What each action sends" below: some when the app opens or as you move the map, others only after you turn on a layer, tap the map, download an area, import roads, open a pin's card, open Best blinds, the Route report, Weather here or Plan approach, ask for an approach path, look for likely deer spots, or ask for a Ranch overview. A Ranch overview sends Anthropic the ranch outline, its pins' coordinates, the paths of its trails, roads and fences, and the center of each named area; a Best blinds report or a Route report sends Anthropic none, though opening Best blinds can send the coordinates of a stand or other pin to USGS where our own terrain copy has no height for it.

What each action sends

Beyond the basemap, the Water detail layer (on by default), the roads overlay when you turn it on, and the property‑line and terrain tiles from our own tile service, which load for the area you view while they are showing, and the search, routing, road‑import, 3D‑map, connection‑check and firmware requests (see "Services we rely on"), here is what the app sends, and on what action. Most recipients are public‑records services run by government agencies. Each feature is labeled with the tier it comes with. A layer you turn on stays on, even after you close the app, until you turn it off. While you are signed in and the app has not yet confirmed your tier with our server, paid layers left on from an earlier Pro or Scout plan keep loading, and Best blinds, Plan approach and Show approach path can open and make their lookups, and Find likely deer spots and Line of sight can run.

Property lines come from our own copies. Parcel boundaries and owner names come from public government records, but the app reads them from copies we prepare and host, so drawing them sends the map area and your IP address, with no account information, only to our tile service, which runs on Cloudflare. No county or state server is asked for property lines. Other layers and map taps do reach government services, as set out above.

AI reports: Ranch overview, Best blinds and Route report

On a paid tier (Pro or Scout), three features are written by Claude, an AI model run by Anthropic: the Ranch overview, a standing write‑up of one ranch; the Best blinds report, which explains your phone's own ranking of your stands for the next 24 hours; and the Route report, which explains your phone's own ranking of the walking routes to the stand, blind or elk pin you are navigating to. Nothing is sent to Anthropic until you tap Write overview (or Write again), Get report (or Get a new report) on Best blinds, or Get route report (or Get a new report) on the Route report; the app never asks for any of them on its own. Before your first AI report on a phone, the app asks whether you allow details of your ranch to be sent to Anthropic; until you tap Allow, that tap sends nothing, to Anthropic or anyone else. It asks again on that phone when a different account uses AI reports. You can withdraw it on the Account screen, under AI reports consent (Anthropic); the app then asks again before your next report. It also asks again after Sign out & remove or Delete account, or if the question's wording changes in an update. The request goes from your phone to our server, which passes it to Anthropic. The other lookups each feature makes, including the ones that go out when you open Best blinds or the Route report, are set out under "What each action sends" above.

What Anthropic receives for a Ranch overview, for the ranch you chose: its name, outline, acreage, center point and bounding box, the state and county it is in, and the coordinates of its pins, with the pin names and types; your pin notes, unless you switch "Include my pin notes" off; trails, roads and fences, with their paths, and named areas, with their center points (a walk you saved as a trail or road is sent as one); how many tracks you have recorded and their total length, never their paths; the dates and times of stand assignments, without the names of the people assigned; feeder schedules, feed logs, battery readings, firmware versions and last sync times; trail‑camera photo counts by hour, never the photos; the county rut phase and deer season; your ranch's time zone, which your phone works out from where the ranch is, or your phone's time zone where the app cannot tell the ranch's; and the public land, soil and elevation lookups for the property, plus the crop lookup. It sends no weather forecast. Right after an overview is written, "Export the data sent" on the overview screen shows you the exact file; the button is gone once the app restarts.

What Anthropic receives for a Best blinds report. Your phone ranks the stands itself. For the top five stands in each sit window, it sends the window's times, each stand's name and place in the ranking, and up to six short lines the phone wrote about it: the forecast wind and where your scent drifts, the names of nearby pins with their distance in yards and compass direction from the stand, feed times and how each feeder has been running, the walk in from its parking pin, fog, low sun, how far a pin lies above or below the stand, and how often it was hunted in the days before. With these goes the time zone the times it sends are on: your ranch's, which your phone works out from where the ranch is, or your phone's where the app cannot tell the ranch's. It sends Anthropic no coordinates, no ranch name or outline, and no notes.

What Anthropic receives for a Route report. Your phone ranks the routes itself, by how much each would disturb the ground you hunt. It sends the name of the pin you are walking to and the animal you chose (whitetail or elk). For each route it sends its name (such as Route 2), how its length compares with the most direct route, and up to six short lines the phone wrote about it: the hour the forecast wind carries your scent onto the hunting area or, when your scent stays off the hunting area, which way it drifts; the hour that, in light wind, rising or sinking air carries your scent to a spot of the hunting area, and how many feet above or below the path that spot is; how close the route passes to pins where animals are likely then, and to funnel, water and sign pins; how many yards of it run close to the hunting area; and, on Scout, how many yards of it are in view of the pin, or of a pin near it, on bare ground. With these go a few lines about the whole report: the time the walks are timed from (when you tap), with the time zone of the pin you are walking to, which your phone works out from where that pin is, or your phone's time zone where the app cannot tell the pin's; the pins around the one you are walking to; and what the report could not check. Wherever these lines name another pin, they give its name with its distance in yards and compass direction from the pin you are walking to. It sends Anthropic no coordinates, no route paths, no ranch name or outline, and no notes.

What is never sent, by any of the three: your name, email address or account identifier; feeder or timer serial numbers; camera labels; the names on hunt assignments; your photos; and the names or addresses of any landowner, yours or your neighbours'. Anthropic receives only a one‑way hash of your account as an abuse‑prevention identifier.

How Anthropic handles it. Anthropic acts as our service provider under its commercial terms: it processes the request to write the overview or report, does not use your data to train its models, and deletes inputs and outputs within 30 days, except where longer retention is required by law or to enforce its usage policy. Our server does not keep what was sent: it keeps a usage record of each request (which feature, when, how many tokens it used and Anthropic's reference number for it), to count the AI reports on your account in each allowance period (your plan's billing month or year, the monthly period set by a redeem code entered on Android, or otherwise the calendar month, in UTC) and for billing, and deletes that record with your account, apart from the daily counts described next. The finished overview or Best blinds report is saved on your phone; a Route report is not saved: it is kept only while the app is running, and is cleared when you sign out.

When a purchase moves between accounts. AI reports, 3D map access, cloud photo backup and the amount of new data an account can add are counted for each Apple or Google purchase as well as for each account: our server notes which purchases each account has held, by the store’s reference number for the purchase or, when the IDs a purchase moves from hold no purchase to move, by a placeholder standing for a move. To recognize a purchase when it reaches another account, our server also keeps the store’s reference numbers for the purchase and for its latest transactions (renewals, for example), each naming the store and whether it was a test purchase, with the time each was last recorded and with no account ID, name or email. Each is deleted within 1 year and 7 weeks of the last notice RevenueCat sends us about the purchase; a notice that names an account already deleted records none and does not extend that time. If an account that held a purchase or used AI reports is deleted, we keep, for up to 1 year and 7 weeks and with no name or email, the deleted account’s random ID, the store’s reference numbers for its purchases (each naming the store and whether it was a test purchase) or placeholders standing for moves, with dates recording when it held each one and when the account was deleted, and, if it used AI reports, how many it used on each day, so that restoring a purchase on another account carries its count over. If an account that held an Apple or Google purchase is deleted, we also keep, for up to 40 days and with no name or email, how many 3D map minutes were counted to it on each of its last 39 days on which any were, with its random ID and when it was deleted, so that restoring the purchase on another account carries those minutes over too. For each photo an account that holds an Apple or Google purchase starts backing up to our cloud, our server also records the photo’s file name (which begins with the account’s random ID), the account’s random ID, the store’s reference number of each purchase the account held at that moment (or a placeholder standing for a move), and when, so that the photo can count toward that purchase’s photo limit on every account that holds it. We erase that record within about two days once the photo’s file has been erased from our cloud storage and no photo still in the app names it; a photo never saved to a ranch, or never finished uploading, is erased about 6 months after it was started. The total of new data an account has added (see “Data retention & security”) can also count toward the data limit of every account that holds a purchase it holds or held.

Sometimes RevenueCat moves a purchase to an ID that is not a HelioMaps account. Usually that is the ID of an app install that was not signed in, or the install ID RevenueCat keeps beside a signed‑in account. Our server then notes the purchase under a code made from that ID, as it would for an account: the store’s reference number (naming the store and whether it was a test purchase), with dates recording when the code held it. When RevenueCat moves a purchase to or from such an ID while the IDs it moves from hold no purchase to move, our server notes, instead of the reference number, a placeholder standing for a move, with the date of this move, under the code of each ID it moves to or from that is not a HelioMaps account. From then on, it can also note under any of those codes a purchase named in a later RevenueCat notice for that code’s ID, or for another ID RevenueCat joins to it. This is so that the AI reports and 3D map minutes already used on a purchase still count on the next account it reaches. No name or email is kept with any of it, and each note is deleted within 1 year and 7 weeks of when it was made.

Our server’s logs are kept for up to a week. For each move, they show the RevenueCat IDs named in RevenueCat’s notice, including any HelioMaps account’s own ID, and the code made from each ID that is not an account. For RevenueCat’s other purchase notices, they can show IDs the notice names, some beside their code or beside the HelioMaps account’s own ID. When noting a purchase fails, they show the store’s reference number, at times beside the code or the account’s own ID. When the app asks our server to re‑check your plan (such as at sign‑in, when the app starts, or on a Restore), or when RevenueCat’s notice moves a purchase to another account, they can show the account’s own ID, at times beside the store’s reference numbers for its purchases and their latest transactions.

An overview or report is generated text based on the data above. It is not a prediction, it is not legal or regulatory advice, and it can be wrong. Verify locally.

Services we rely on

These providers process what's needed for their function.

We do not sell your personal information. We never give advertisers your GPS location, your coordinates, your map content or your photos; AdMob does receive your IP address, which indicates your approximate area (see "Advertising" above).

Property records and landowner names

This section is for landowners, whether or not you use HelioMaps.

HelioMaps displays property boundaries drawn from public county and state records, and — where that government publishes it as part of the same public record — the name on the parcel, along with the parcel number, acreage, situs address and land use. We do not create this information, we do not buy it from data brokers, and we do not combine it with anything else. It is shown as reference for someone working out where a boundary runs.

We prepare our copies from official government publications whose terms allow redistribution — statewide programs such as the Texas Geographic Information Office's StratMap land‑parcels dataset and North Carolina's NC OneMap — and the app reads those copies from our own service so the map works quickly and offline. It is the county's record, published through that government's own program, and it is public whether or not HelioMaps exists.

Where a county withholds an owner name — several states exempt law‑enforcement officers, judges and domestic‑violence survivors from disclosure — HelioMaps shows the name blank, and we never fill a blank name in from another source.

If you want your name removed, the county is where that happens. We are not the source of the record and cannot change it: your county assessor or appraisal district holds it, publishes it, and is the only place it can be corrected or restricted. Many counties have a process for this, and several states have a statutory exemption you may qualify for. Once your county updates its record, HelioMaps picks up the change when we next refresh that county's data.

Something wrong? If the information we show does not match your county's record — a stale name, the wrong parcel, a boundary in the wrong place — email privacy@heliomaps.com with the county and the parcel number or address and we will look into it.

Your choices & rights

Data retention & security

We keep your synced content while your account is active, except backed‑up photos that a drop in your plan puts over its limit, wherever they are (see "Trail‑cam photos" above), and delete it when you delete your account, in the app or by email. On any plan you can also ask us by email to delete a whole ranch you own, which we do the way the app does; single items are deleted in the app, not by email (see “Delete only some data” on Delete your account). For what a delete leaves in our cloud, and what stays after you delete your account, see "Delete your data" above. We use reputable providers and reasonable safeguards to protect your data, though no method of transmission or storage is 100% secure. Ranch overview, Best blinds report and Route report requests are deleted by Anthropic within 30 days, with the exceptions described above; we keep only a usage record of each request, which is deleted with your account, apart from the daily counts described under “When a purchase moves between accounts” (in “AI reports” above) and the request counts set out under “Request counts” below. We also keep daily counts of your 3D map sessions and road imports, and a history of your plan, to enforce limits and for billing; these are deleted with your account, apart from the 3D map counts described under “When a purchase moves between accounts” (in “AI reports” above) and the counts of road imports described under “Request counts” below. Each day (UTC), our server may keep a record of one account refused 3D map access for reaching its daily or monthly limit, normally the first that day (a later one can replace it if our server could not confirm that the email about it was sent): its random ID, when it was refused and when the email about it was sent, which limit it reached, that limit, how many 3D map minutes counted toward it and, if any, how many other holders of the same Apple or Google purchase (other accounts, or the codes described under “When a purchase moves between accounts”) were counted with it. We keep that record for about 13 months, and, to watch for misuse of the 3D map, we send ourselves an email about it through our email service, Resend, with the random ID of the account, the day, which limit it reached, that limit and those minutes; neither is deleted with the account, and we keep the email with no set end date. The records of the 3D map's phone check are kept as set out under "Phone check for the 3D map" above. If we have exempted an account by hand from that check, we may also send ourselves an email about it through Resend, saying it was let through the check without passing it, with its random ID and the day. We send at most one such email each UTC day, about the first exempted account let through that day. It is not deleted with the account, and we keep it with no set end date. We also keep daily counts of what your account saves or sends to our server, including map items, shares and links, timer readings and commands, and live sharing (how many items of each kind and, for most kinds, how much new data and how much changed data), for up to about two days, and a total of the new data it has added, for as long as the account exists, to enforce our limits on how much one account, or the accounts holding one Apple or Google purchase, can save; after you delete your account they are kept, with no name or email, for up to about a day. Once an account has added about 800 MB of new data, our server also keeps the account's random ID and when we first recorded it passing that mark, so that, when the Apple or Google purchases such an account holds, taken together as one set (each by the store's reference number or a placeholder standing for a move), have more than 1,000 holdings between them, past or present, by accounts or by the codes described under “When a purchase moves between accounts”, it can keep the combined new data that counts toward their shared limit, under a scrambled code (a hash) of those reference numbers and placeholders, with no account ID or email; for a set with more than a million such holdings it keeps only when it last checked the set, with no total. That record is recomputed by a job that runs every 5 minutes (a set can wait for a later run) and is deleted within about 20 minutes once no such account holds that set. The account's ID and when we first recorded it passing that mark are deleted within about 5 minutes after the account is deleted. When our server refuses to back up a photo because a cloud photo limit is full, it keeps, with the account's random ID and the date (no photo, file name or email), a count of that day's such refusals and the time of the last one, so that it can limit how often it re‑checks a full account. When the photos of other accounts holding the same Apple or Google purchase decided the refusal, it also keeps such a count for each Apple or Google purchase the account holds, with the store's reference number (or a placeholder standing for a move) and the date and no account ID, so that it can limit how often it re‑checks a full purchase. For each Apple or Google purchase, it also keeps a count of each day's new photo backups by the accounts whose photos that purchase covers, with the store's reference number (or a placeholder standing for a move) and the date and no account ID, so that it can limit them per purchase; that count is deleted within about a day after its day ends. The account's record is deleted when the account is deleted, and its counts of earlier days the next time that account is refused for a full limit, so a count can be kept until then; a purchase's count of refusals is deleted within about a day after its day ends. To count your backed‑up photos toward your plan's limit, our server also keeps, with your account's random ID, the file name of each photo you backed up that is in our cloud, in any ranch, and not deleted or hidden there, with how many such copies of it there are; each is deleted soon after its last such copy is deleted or hidden. A photo file's name (which begins with its uploader's random ID) can also wait on a retry list, usually for a few minutes, before our server checks it again and, if nothing in our cloud still uses the file, queues it for erasure. After a drop in your plan, if a phone copies or restores one of your hidden photos to our cloud, our server keeps a note of your account's random ID and when, until the drop ends or those photos are deleted for good; our hourly check then clears it. If our job that hides or deletes your photos after a drop cannot finish for your account, our server keeps your account's random ID with a record of how many times the job tried, when, and what last stopped it, until the job finishes or is no longer needed. We also keep, for your account, a count of how much it sent us to save or delete on the latest UTC day it sent any, counting requests that were then undone, and how much of that went through, kept until a few minutes after that day ends, to limit how much can be sent and then undone in one day; both are deleted with your account, or at the latest about a day after it. We also keep one record for your account of when its latest 10‑minute period of subscription checks (when the app asks our server to re‑check your plan) began and how many checks were counted in it, to limit how often they can run; it is deleted with your account. We also keep one record for your account of the latest UTC day on which we counted a redeem code it entered on Android that gave it nothing new (a wrong or used‑up code, for example), and how many we counted that day, to limit how many can be tried; it is deleted with your account. To limit how much public map links can send, our server may count, for each hour, how much data it sent for an account's public map links; any such counts are deleted within about two hours, and with the account. Other short‑lived rate‑limit records, which can include your IP address, are deleted within about three hours, apart from the request counts set out under “Request counts” below. Supabase, which runs our sign‑in service and database, also keeps its own service logs of requests, which include IP addresses, for up to a week before deleting them.

Live location. While you share your live location, our server keeps only your phone's latest position on the ranch you have open, the time your phone took that position and the time our server last heard from your phone, with a random number the app makes each time it starts and a counter; the app shows that position, with your display name, to others on that ranch who are also sharing. If your phone stops reaching our server, our server stops sending that last spot to others 30 minutes after it last heard from your phone, and a phone that has itself lost touch with our server can keep showing the last spot it received. The position is deleted when your stop reaches our server or you delete your account, and otherwise 30 to 35 minutes after your phone last reached it. A stop leaves a note that you stopped, with no position, which is deleted 30 to 35 minutes after the stop or with your account. Our server also counts how many live sharing records your account creates each day (for example when your phone starts or stops sharing), with no position, kept like the other counts described above.

Request counts. To spot one account, script or IP address overloading our database or running up our costs, to stop such an account, and to keep the service running, our server counts the requests sent to our database other than plain reads (some of the app's reads count too): a request sent while signed in under the account's random ID, and one sent without signing in under the IP address it came from. It also counts each account's calls each UTC day to two of our server functions: the one that saves a Sign in with Apple link, and road import. Each counted request is held, with that random ID or IP address and the path it called on our server, until it is added to the counts below, normally within about two minutes. For each account we keep how many counted requests it sent in each minute, for about 10 minutes. For the current and the previous UTC day, we keep how many it sent that day, the count of its busiest minute, in how many minutes it reached our per‑minute limit, and its calls to those two functions; and, for about 2 days, the minutes in which it reached that limit. For each UTC day, we keep our lists of that day's busiest accounts, up to 50 by requests and up to 50 by busiest minute, with each one's random ID, requests, busiest minute and minutes at that limit, for about 400 days.

If an account is blocked from sending requests, by our server or by us, we keep its random ID, the reason and when the block ends, until about 7 days after it ends. If we raise one account's limits by hand, we keep its random ID and by how much, until we remove it.

For each minute, we keep how many counted requests were sent across the service, signed in and not, with no account information, for about 30 days. For about 7 days, we also keep that minute's busiest callers (by account random ID or, for requests sent without signing in, by IP address) and busiest paths, with their counts.

Our server can also read Supabase's own service logs of our project every 5 minutes. It keeps the counts of requests by service and by function, for about 30 days. When a count reaches our level, it also keeps up to 5 of the busiest IP addresses and paths of those 5 minutes (a path to a photo file holds the random ID of the account it belongs to), and the busiest account's random ID where those logs carry it, for about 7 days. None of the request counts and lists above holds the content of a request or of its answer (only the path it called), or a name or email address.

When an account reaches or passes one of our request limits or is blocked, when requests across the service jump, or when that log check stops or cannot read, we send ourselves an email through our email service, Resend, normally at most one for each kind of alert each UTC day. It holds the counts and, depending on the alert, an account's random ID, up to 5 IP addresses and the busiest paths. We keep our record of each such email, with those details, for about 400 days after its day, and the email itself with no set end date. None of the request counts, lists, records or emails above is deleted with an account: an account's random ID can stay in them after the account is deleted, until the times above.

Children

HelioMaps is intended for adult hunters (18+) and is not directed to children. We don't knowingly collect personal information from anyone under 18.

Terms

Your use of HelioMaps is also governed by our Terms of Service, which include important safety, boundary‑accuracy, and liability disclaimers.

Changes

We may update this policy as the app evolves. We'll post the new version here and update the date above.

Contact

Report a problem, in the app, opens an email to support@heliomaps.com in your own mail app, filled in with your phone's system and its version, the app's version, your account identifier and the time. You can edit or delete any of it before you send it, and nothing is sent unless you send that email.

Questions, or want your data deleted? Email support@heliomaps.com. Before we act on a deletion request sent by email, we confirm it comes from you with a one‑time code sent to your account's sign‑in address (see Delete your account).

HelioLogix LLC · Engineered for the Hunt · heliomaps.com