Delete your account & data

HelioMaps, by HelioLogix LLC

This page explains how to delete your HelioMaps account (made by HelioLogix LLC) and the data associated with it. Much of HelioMaps works with no account at all, if you never signed in, we hold no cloud data for you, and uninstalling the app removes everything from your device.

If you subscribe to Pro or Scout: deleting your account does not cancel the subscription. Cancel it in your App Store or Google Play subscription settings, or it keeps renewing and you keep being charged.

Delete your account in the app (fastest)

You can delete your account yourself, right from HelioMaps:

1. Open HelioMaps and make sure you're signed in.
2. Go to Account ▸ Delete account.
3. Confirm when prompted. Your account is deleted, or, if that cannot be done in one go (for a very large account, for example), closed at once and then deleted, usually within a few hours. The device you delete it on is signed out at once, and your sign‑in on your other devices ends within an hour. See “What gets deleted” and “What may be kept” below.

Or request deletion by email

If you can't get into the app or you've already uninstalled it:

1. Email [email protected] with the subject line "Delete my HelioMaps account." If you are writing from a different address, tell us the email address you sign in to HelioMaps with.
2. To make sure the request comes from you, we send a one‑time code to your account's sign‑in address. Reply to that email with the code. We delete nothing until the code comes back.
3. We confirm by email when it's complete.

If you use Sign in with Apple and chose Hide My Email, your sign‑in address is the forwarding address Apple made for HelioMaps, which you can find under Sign in with Apple in your Apple Account settings. Tell us that address and we send the code there. If you can't receive email at your sign‑in address but can still sign in to the app (with Apple, Google or your password, or on a phone that is still signed in), use Account ▸ Delete account there instead.

What gets deleted

• Your account and sign‑in credentials (email / authentication records).
• Content you synced to our cloud for your own ranches: property boundaries, pins, trails, roads, tracks and notes, and every trail‑cam photo you backed up, including photos on a ranch someone else owns.
• Any map‑sharing links and live‑location records tied to your account.
• The 3D map's phone‑check records tied to your account: the public half and ID of each of its phone keys, including replaced keys not yet deleted, what we noted from their checks, any one‑time codes not yet deleted, and any exemption we set by hand to let your account through the check.
• For each HelioTimer you own: its stored feed, battery and diagnostic history and settings, the commands sent to it, the name you gave it, and the WiFi network name it reported, with its next feed, how often it checks in and when it last did. The timer itself is released so someone else can claim it. It still holds its recent feed log, battery history, settings including its location, and saved WiFi network until it is factory reset on the timer, and anyone who connects to it over Bluetooth can see that network's name. If it is not reset, its logs and settings are uploaded again after its next owner claims it, when someone connects to it over Bluetooth or it checks in over WiFi, and that owner is shown them. Any other command you sent to a timer is deleted too.

What may be kept

• Pins, notes, trails, roads, tracks, named areas, routes, hunt assignments and journal entries you added to a ranch someone else owns stay with that ranch, as part of its owner's map; our server keeps no record that you added them, except the photo entries described next. Your photos are removed from it, but an entry for each, marked deleted, can stay with that ranch until its owner deletes their account; it holds the pin the photo was on, when it was added and deleted, and a file name that begins with your account’s random ID.
• Readings you uploaded, or that a timer uploaded while it was yours, stay with that timer if you don't own it when you delete your account (it is someone else's or no one's, or you released it earlier), unless whoever owns that timer deletes their account while they own it. They are unlinked from you, and a timer's owner is shown only the readings stored since they claimed it, plus any they uploaded themselves.
• Data stored only on your device is not on our servers. Deleting an item in the app (a ranch, pin, note, trail, track, route or photo) hides it but does not erase it from your device: its record, and for a photo possibly a copy of the image, stays there until you choose Account ▸ Sign out ▸ Sign out & remove (offered while you are signed in) or Delete account in the app on that device, or uninstall HelioMaps. Deleting your account by email or from another device does not clear it.
• If you held an Apple or Google purchase or used AI reports: for up to 1 year and 7 weeks, 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 the count carries over if a purchase is restored on another account. With no account ID, name or email, we also keep the store’s reference numbers for each of its purchases and for their latest transactions (each naming the store and whether it was a test purchase), to recognize a purchase if it reaches another account; each is deleted within 1 year and 7 weeks of the last notice RevenueCat sends us about the purchase. A notice that names your account after it is deleted records none and does not extend that time.
• If you held an Apple or Google purchase: for up to 40 days, with no name or email, how many 3D map minutes were counted to your account on each of its last 39 days on which any were, with the deleted account’s random ID and when it was deleted, so those minutes count if a purchase is restored on another account.
• If RevenueCat ever moved a purchase to or from an ID it keeps for an app install, such as the ID it uses while the app is signed out, and the purchase or the install was yours: for up to 1 year and 7 weeks after each note, with no name or email, a code made from that ID, with the store’s reference number of each purchase noted under it (naming the store and whether it was a test purchase) or a placeholder standing for a move, and dates recording when it held each one. This lets the AI reports and 3D map minutes used on a purchase count on the next account it reaches. We can also note a purchase, or a placeholder standing for a move, under such a code when RevenueCat moves it to or from your account, if RevenueCat’s notice lists such an ID beside yours. These notes are not deleted with your account; they are set out under “When a purchase moves between accounts” in our Privacy Policy.
• If your account was refused 3D map access for reaching its daily or monthly limit: possibly, for about 13 months, our record of it (we keep one such record each UTC day, normally of the day’s first such account; a later one can replace it if our server could not confirm that the email about it was sent), with your account’s 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 just above) were counted with it; and, with no set end date, our email about it, with your account’s random ID, the day, which limit it reached, that limit and those minutes, which we receive through our email service, Resend.
• If we exempted your account by hand from the 3D map’s phone check: possibly, with no set end date, our email saying it was let through the check without passing it, with your account’s random ID and the day. We receive it through our email service, Resend, and send at most one such email each UTC day, about the first exempted account let through that day.
• From our request counts, with no name or email, your account’s random ID can stay as follows. If it sent requests to our database other than plain reads or called our Sign in with Apple or road‑import functions: with its counts of the last two UTC days, for up to about 2 days. If it was among the busiest accounts of a UTC day: in our lists of them, for about 400 days. If it was among the busiest callers of a minute: in our lists of them, for about 7 days. If it was the busiest account of a 5‑minute window, or a path to one of your backed‑up photo files (whose name begins with your account’s random ID) was among that window’s busiest paths: in what we keep from the service logs of Supabase, our sign‑in and database provider, for about 7 days. If it was blocked from sending requests: until about 7 days after the block ends. If we raised its limits by hand: until we remove that. If it reached or passed one of our request limits, was blocked, or was the busiest account in an alert about requests across the service, or if a path to one of your photo files was among the busiest paths in such an alert: possibly, for about 400 days, our record of the email we sent ourselves about it, with your account’s random ID and its counts or, for a block, its reason and when it ends, and, with no set end date, the email itself, which we receive through our email service, Resend. An IP address you used can stay too, if it was among the busiest: for about 7 days in our lists of each minute’s busiest callers (for requests sent without signing in) and in what we keep from Supabase’s logs; and, if it was in one of our emails about requests, for about 400 days in our record of the email and, with no set end date, in the email itself. These are set out under “Request counts” in our Privacy Policy.
• If you backed up photos: for about 6 months after each upload, our record of the file name it was given (which begins with your account’s random ID) and when; and, with no set end date, our record of each photo file we erased, or tried to erase, from our cloud storage, with your account’s random ID, the file name, the times and any error.
• If you backed up photos: until our server clears them, usually within a few minutes, our count of each of your photos in our cloud, with its file name (which begins with your account’s random ID); and, usually for a few minutes, the file names of any of your photos waiting on a retry list on their way to erasure.
• For about a day after the deletion, or until our counts of your photos are cleared if that is later, with no name or email: your account’s random ID and when it was deleted, so that our server knows whose photo counts to clear.
• If, after a drop in your plan, a phone’s copy or restore of one of your photos was saved hidden: our note of your account’s random ID and when, usually for a few hours. If our job that hides or deletes photos after a drop in your plan had failed for your account: for about a minute, its record of the tries, with your account’s random ID, how many times it tried, when, and what last stopped it.
• If you backed up photos while holding an Apple or Google purchase: with no name or email, until about two days after each photo’s file is erased from our cloud storage and no photo still in the app names it, our record of each such photo’s file name (which begins with your account’s random ID), with your account’s random ID, the store’s reference number of each purchase you held when you backed it up (or a placeholder standing for a move), and when.
• If a photo backup of yours was refused because the photos of other accounts holding your Apple or Google purchase filled its limit: for up to about a day after that day ends, a count of that day’s such refusals for each Apple or Google purchase you held, with the store’s reference number (or a placeholder standing for a move) and no name, email or account ID.
• If your photos were backed up under an Apple or Google purchase: for up to about a day after that day ends, a count of that day’s new photo backups for each such purchase, with the store’s reference number (or a placeholder standing for a move) and no name, email or account ID.
• If you signed in with Apple: for up to about 2 months, a record with your account’s random ID of our request to Apple to end your Sign in with Apple link to HelioMaps, which holds Apple’s sign‑in token until Apple confirms or for up to 29 days.
• Until your account’s deletion is finished, and for about a day after, a record with your account’s random ID of when its deletion was asked for, how far it has got and any error, so that our server can finish the deletion and remove anything added to the account at the last moment.
• If you ever signed in: RevenueCat, the service that manages our subscriptions, keeps its own record under your account’s random ID, with any purchases and the device identifier it collected. We do not delete it when you delete your account.
• For up to a week, our sign‑in and database provider's own service logs of requests, which include IP addresses, and our server's own logs, which can show your account's random ID, the other IDs RevenueCat keeps for you, the codes made from them and the store's reference numbers for your purchases and their latest transactions.
• For up to about a day, with no name or email, the deleted account’s random ID with counts of what it saved or sent to our server on each of its last few days (how many items of each kind and, for most kinds, how much new and changed data, and at times how much it sent us to save or delete, undone requests included) and the total new data it ever added, which we kept to enforce our limits on how much one account, or the accounts holding one Apple or Google purchase, can save.
• If your account had added about 800 MB of new data: for up to about 5 minutes after the deletion, your account’s random ID and when we first recorded it passing that mark; and, with no account ID, name or email, the combined new data of a large set of Apple or Google purchases it held, described under “Data retention & security” in our Privacy Policy, until about 20 minutes after the deletion, or about 20 minutes after no other account that has added about 800 MB holds that set if that is later.
• Limited records we're required to keep for legal, tax, or fraud‑prevention purposes (for example, a record that a purchase occurred) may be retained in de‑identified form as the law requires.

How long it takes

We delete your account and the data listed under “What gets deleted” within 30 days of confirming the request is yours (for a request by email, from when your code comes back), and usually much sooner. For a very large account, deleting its records can take hours, and erasing its photo files from our cloud storage can take days, within the 30 days.

Delete only some data (without closing your account)

You don't have to delete your whole account to remove data.

In the app. You can delete your own ranches, and pins, cameras, trails, tracks and photos, at any time; on a ranch someone else owns, only while you have Pro or Scout. A deleted item is hidden, not erased from the device: it stays there until you choose Sign out & remove or Delete account in the app on that device, or uninstall HelioMaps (see “What may be kept” above). On any plan, a photo you delete in the app while you are signed in, on a phone that still has it, is deleted in our cloud too. So is each photo you backed up that is on a pin or ranch you delete there. The photo's file is erased from our cloud storage within about 30 days, unless something else in our cloud, such as a copy of its ranch or the ranch it was copied from, still uses that file. A ranch you own and delete there while you are signed in is deleted in our cloud too, on any plan, with everything on it. Anything else you delete reaches our cloud only while you have Pro or Scout, and is then hidden on your other devices too. Once a delete reaches our cloud, the item's record stays there, marked deleted and hidden, until you delete your account; on a ranch someone else owns, it stays with that ranch.

By email, a whole ranch you own. On any plan, you can ask us to delete a whole ranch you own: email us at the address above with the ranch's name. We confirm the request comes from you with a one‑time code the same way first, then delete the ranch and everything on it the way the app does. Its photo files are erased from our cloud storage within about 30 days, except files that something else in our cloud still uses, such as a copy of the ranch (in your account or someone else's) or the ranch it was copied from. Its other records stay in our cloud, marked deleted and hidden, until you delete your account. We don't delete single items by email.

Anything else. Without Pro or Scout, to delete anything else on a ranch you own in our cloud (a photo no phone of yours still has, or any other single item), ask us to delete the whole ranch, as above, or delete your account. On a ranch someone else owns, deleting your account removes your photos from it; your other items stay with that ranch (see “What may be kept” above).

Questions

Email [email protected]. See also our Privacy Policy.