Privacy Policy

CoyoteEdge is a coyote-hunting forecast and logging app operated by CoyoteEdge LLC, a Kentucky limited liability company (“CoyoteEdge”, “we”, “us”). “We” throughout this policy means that company. It covers the CoyoteEdge app for iOS and Android and the website at coyoteedge.com. It is written to match what the app actually does. If we change what the app does, we change this page.

What changed on September 29, 2026. This update adds that, in current versions of the app, a stand you delete on its own stays on our servers, set aside, until you delete your account.

What changed on September 27, 2026. This update adds that profile pictures are checked by the AI service that checks kill photos; that a kill photo, or something you write, may be turned away if it has something that is not allowed here; that current versions of the app send property lines, owner searches and weather through our server; that a night you delete stays on our servers, marked as deleted, until you delete your account; that your sign-in history stays after you delete your account; and it names the copy of your sign-up name kept with your login, our request logs, the app’s update check, Mapbox’s own statistics, and where older versions of the app differ.

1. What we collect

Your account

• Email address and password. Used to sign you in and to reach you about your account — a password reset, or a deletion request you send us. Your phone also remembers the last email you signed in with, so the sign-in screen can fill it in; that one stays on the phone after you sign out. There is no Apple, Google, or social sign-in.
• Hunter name. The name you type at sign-up. It is visible to other hunters on leaderboards, tournaments, and in messages. A copy of that name is also kept with your login, where no other hunter can see it, and changing your hunter name later does not change the copy. If the name has a word that is not allowed here, the app may ask you to pick another, or give you the name Hunter and your code instead. Accounts created before September 2026 may have been given a name taken from the front of the email address. You can change it in Settings.
• Hunt code. A code the app generates (HUNT-XXXXXXXX) so other hunters can add you. Other signed-in hunters can see it.
• Profile picture, if you add one. Other signed-in hunters can see it.

Location

With your permission, the app reads your phone’s location only while you are using it. There is no background or always-on tracking.

We use it to:

• pull tonight’s conditions for where you are standing — your coordinates go to the weather and elevation services listed in section 2, some of them straight from your phone;
• place the stands, kills, tracks, pins, bearing lines, and grounds you create on your map;
• run turn-by-turn directions to a saved ground, if you ask for them — which sends Mapbox your exact position and the ground’s exact position, and follows your position while that screen is open.

Coordinates you attach to a stand, kill, camera, pin, bearing line, or ground are stored on your account. A saved track stores the whole walked path, not one point. A tournament entry also stores how accurate the GPS fix was, and a state worked out from the coordinate.

If you type a hunt in later from a photo, the app can read that photo’s date and — where the photo carries one — the GPS position stored inside it, and use them as the hunt’s time and place.

Photos and video

• Kill photos. Analyzed by an AI service to confirm species and count before the kill is verified, then stored on your account and shown to your friends on the feed. We resize and re-encode the photo first, and we strip the camera’s embedded metadata — including any GPS position — out of both the full photo and the thumbnail before either one leaves your phone. The AI’s written verdict is stored on the kill and travels with it on the feed. The same check may also turn a photo away, season or tournament, because it shows something that is not allowed here. A photo turned away is not kept on our servers and the kill is not posted; our server’s log keeps your hunt code and the check’s few words about why, for a limited time.
• Tournament kill photos. Same AI service, and their camera metadata is stripped the same way. Unlike a season kill, the photo is sent at full size rather than resized. The prompt also carries the verification rules the tournament’s director wrote.
• Tournament proof videos. Recorded with sound, and uploaded so the director can review the entry. A video is not sent to the AI service. Before it uploads, the location and camera metadata the phone wrote into the file are blanked out; the picture and the sound are untouched.
• Trail-camera frames. When you import a trail-cam photo, we store the time it was taken — read from the photo, or typed by you from the time printed on it — along with the spot and the name you give the camera, the hour, your coyote count, the conditions, and any notes. The photo itself stays on your phone and is never uploaded.
• Profile picture. Stored on your account, with the location and camera metadata removed before it uploads.
• The record of your photo checks. Each time a kill photo is checked, our server records your hunt code, the time and whether it was a season or a tournament kill, so no account can send more than a set number of photos an hour or a day. Each record is cleared once it is more than about a day old, the next time one of your photos is checked, and deleting your account removes them all. Profile pictures are checked too: for each one our server keeps your hunt code, the picture’s link, when it was checked, what was decided and the check’s few words of reason, until you delete your account.

Things you write and log

Stands, hunts, kills, notes, howling events, the sound or call you name on a kill, comments, likes, direct messages, group hunts, tournament entries, friend connections, and any reports or blocks you file are all stored on your account. Direct messages are stored as plain text. Your saved call library stays on your phone. Our own database may refuse a comment, a message, a name, a tournament’s name or rules, a team name, a group-hunt guest’s name or a director’s review note because it has a word that is not allowed here. The check is made by our database and nothing is sent anywhere else for it; a refused text is not stored in our database, and no record of the refusal is kept there.

Questions you ask the Edge AI scout

Each question you type is stored (up to 500 characters), along with your account, the month, your subscription level, which model answered, and how it was answered. We keep the questions to see what hunters ask and to improve the guide. The answers are not stored — we keep how long an answer was and what kind it was, never its text.

Forecast records

Once a night, when the app builds tonight’s forecast, it writes down the conditions it read, how long it had been since you last hunted within about 12 miles of where your phone was, and the numbers it produced — by the forecast you see and by a second, older method that runs in the background and is never shown to you. Those two records carry your hunt code and your phone’s exact location as the app last read it, which may be your home rather than where you hunt. It also keeps a short summary of the night under your hunt code: the date, the night’s rating and the forecast numbers behind it, when it was taken, and, if you confirm at END HUNT that every stand was logged, how many stands you logged. The summary carries no location. These are written automatically as part of building a forecast; there is no separate prompt for them. We use them to check how well the forecast worked and to improve it (see section 3).

Device and notification data

A push-notification token and whether the phone is an iPhone or an Android, so we can send alerts you turn on. We also keep records of the notifications we queued and sent you, and your notification settings. We store your subscription level. We do not collect an advertising ID, and we do not ask to track you across other apps.

Landowner searches

With a Pro subscription the map can show property lines and owner names, and you can search for land by the owner’s name. Current versions of the app send both through our server, which passes them on to our parcel-data provider: the provider sees the name you typed and the area being searched, coming from our server rather than your phone, and our server passes the answer back without keeping the name you typed. Older versions of the app send them straight from your phone to the provider, so it also sees your device’s IP address. What comes back — each owner’s name and where the land is — is shown on your screen and is not saved on our servers. The property lines on the map also carry owner names in the tiles your phone downloads. We do not store landowner names or addresses on our servers.

Our server holds each hunter to a daily number of owner searches. For each search it keeps your hunt code, the time, whether land was found, how many results came back and how large an area was searched — never the name you typed or where you were looking. We keep that record while your account is open, and deleting your account removes it. In current versions of the app, our server also keeps a daily count of the property-line tiles your account drew — your hunt code, the day and the number, never where — and our app server’s host keeps, in its request log for a limited time, the address of each property-line tile asked for: which part of the map it covers, under a code for your account that does not show your hunt code. Deleting your account removes the daily tile count too.

On your phone, the app keeps your last ten owner searches (each name and how many results it found) so you can repeat them, and any hunt-area outlines you build from property lines. Each one expires 30 days after it was first fetched, and both are cleared when you sign out.

What your phone keeps

Your hunt log, your grounds, tracks and pins, your last GPS fix, your call library, and cached feed content from other hunters are all stored on the phone so the app works without a signal. Signing out clears most of it. A few things stay on purpose: the last email you signed in with, and the map tiles already downloaded, including any property lines and owner names on them.

2. Where it goes

We do not sell your personal information. We share it only with the services that make the app work. Many of them are contacted directly by your phone — every map, basemap tile, place-lookup and elevation request goes straight from your phone to the provider rather than through our servers, and so, in older versions of the app, do property lines, owner searches and recent-days weather — which means those providers also see your IP address. Some go through our own servers instead: our app server, hosted by Railway, fetches weather, passes property lines and owner searches on to our parcel-data provider, relays the Edge AI scout and sends some notifications, and Supabase’s server functions verify kills and send the rest. For those requests the provider hears from us, not your phone. RevenueCat, the app stores, Sentry, the phone’s own geocoder, Expo’s update service, and Expo’s push service when the app signs up for notifications are reached straight from your phone.

We ask none of these AI or weather providers to hold or not hold what we send; what they keep is governed by their own terms, and we cannot recall it.

Our database host keeps a log of the requests the app makes to it — your IP address, the country it resolves to, which account made each request, what it asked for, and the software details your phone sends with it — for about a week. Our app server’s host keeps its own request log for a limited time, with your IP address and the web address of each request, which for a weather request includes the coordinates asked about. Our sign-in service also keeps a history of sign-ins, with the email address used and no IP address; it is not removed when you delete your account. For each phone that is signed in, it also keeps that phone’s IP address and the software details it sends, until the phone signs out or the account is deleted. Separately, the sign-in service’s own log records each sign-in with the email address and IP address used; we cannot delete anything from that log, and it clears itself after a limited time.

Crash reports

CoyoteEdge uses Sentry for crash reporting. When the app crashes or hits an unexpected error, it sends a diagnostic report so the fault can be found and fixed.

That report is diagnostic data only — what failed, where in the code it failed, your device model, your OS version, and the app build. It is not linked to your identity or your account, and it is not used to track you across other apps or websites. It can also include a short trail of what the app was doing just before the fault.

Location data and console logs are removed from the report before it is sent. Crash reports do not carry hunt entries, kill records, photos, or coordinates.

Crash reports are used for one thing: fixing the app.

The subscription and map components we build on are supplied by RevenueCat and Mapbox and may report their own usage diagnostics back to those companies. Mapbox’s map component also sends Mapbox its own usage and location statistics, which are not tied to your account.

3. How we use it

• To build your forecast and Hunt Index from local conditions.
• To store and show your logs, kills, map, and stats.
• To run the kill feed, friends, messages, group hunts, and tournaments.
• To send notifications you turn on.
• To operate your subscription.
• To handle reports and blocks and keep the feed civil.
• To improve the forecast. The records described in section 1 are collected automatically, once a night, for every hunter. Later, by hand and offline, we pull hunt logs, kill records and those forecast records together and study them to check and improve the forecast. In that study we replace hunter names with internal code labels — but those labels can still be traced back to an account by us, and the hunt coordinates are kept exactly as logged, so treat it as your record under a different name rather than as anonymous. We keep that mapping private and never publish it. Only the study is done by hand; the collection is automatic. The forecast on your phone does not learn while you use it: your own history does not change the number you see, and it is the same forecast for everyone at your spot.

We do not use your photos, location, or logs for advertising, and we do not share them with data brokers.

4. What other people can see

• Other signed-in hunters can see your hunter name, hunt code, profile picture, badges, your career kill total, the tournament boards you are on, and comments you leave.
• Your kills are for your friends. A verified kill — the photo, the count, the night rating, the conditions and the AI’s verification note — is visible to you, to hunters you have added as friends, and to an app administrator. A hunter who is not your friend cannot see your kills — only the total on your hunter card.
• No location shows with a season kill. The coordinates are stored on your account, and no other hunter’s app displays them — not blurred, not reduced to a state. A kill on the feed does carry the weather saved with it, and that includes the moon’s position in the sky, calculated from where your phone was when you logged the kill. A tournament entry shows the state it was worked out to be in, and never a coordinate.
• Private: no other hunter can read your direct messages — only you and the person you are writing to. Reports and blocks you file are visible only to you and to us.
• Photo links. Kill photos, tournament stills, tournament videos and profile pictures are served from links that are not listed anywhere, but anyone who has a link can open it without signing in, and the link itself contains your hunt code. Treat a kill photo or a proof clip as something you would be comfortable having shared.
• We can see it. Being the people who run the app, we can read any hunter’s hunts, howling log, trail-camera entries and kill locations, including coordinates. Direct messages are stored as plain text, so we can read those too. We use that for anti-cheat, for handling reports, and for support. It is not something another hunter can do, and it is not something we do for fun.
• The public leaderboard at coyoteedge.com is off by default. Nothing about you appears on the website until you turn on PUBLIC PROFILE, under THE FEED in the app’s Settings. When it is on, the website shows your hunter name, your kill total and place on the season board, and each of your verified kills — its date, how many coyotes, the night’s rating and the photo; past seasons list their leading hunter by name and total. Nothing else: coordinates, counties and your email are never shown on the website, and your hunt code is never printed — though, as noted under Photo links above, the link behind a kill photo carries it. Turn it off and you drop off the website within a few minutes.
• Tournament directors can see the kill photos, proof videos, GPS accuracy and resolved state of entries in tournaments they run, so they can verify them. They cannot see your exact coordinates or the conditions stored with the entry, and neither can other entrants.
• Group hunts. A shared kill is split among everyone on it. If one hunter deletes their account, their share of that kill goes with them; the others keep theirs.

5. Subscriptions

Subscriptions are billed by Apple or Google through your store account and managed by RevenueCat. We never see your card number. We give RevenueCat your account’s internal ID, and it tells us which subscription you hold; your phone then writes that level onto your account. Cancel any time in your App Store or Google Play subscription settings.

6. How long we keep it

We keep your account data while your account is open. When you delete your account, we remove it as described in section 7.

Backups. We keep seven days of daily database backups, which are then overwritten. So for up to seven days after a deletion, a backup taken beforehand may still hold database rows about you. Backups cover the database only — they do not include stored files. Photos and videos live in file storage rather than in the database, so a deleted photo is gone from storage immediately and is not sitting in a backup.

Edge AI questions are deleted automatically once they are 180 days old, by a nightly job. Forecast records have no expiry: we keep them while your account is open, and they go when you delete it.

A night you delete in the app leaves your Log, but we keep it on our servers, with its stands, marked as deleted, while your account is open. It can still be part of the forecast study described in section 3, and deleting your account removes it.

A stand you delete on its own leaves your Log too, and in current versions of the app we keep it on our servers, set aside, while your account is open. It can still be part of the forecast study described in section 3, and deleting your account removes it.

7. Deleting your account

You can delete your account from Settings → Delete account in the app, or by emailing support@coyoteedge.com from the address on the account. Full steps are at coyoteedge.com/delete-account.

Deletion removes: your login, profile, hunts and stands (nights and stands you deleted earlier included), howling events, group hunts you created, kills and kill photos, map pins, tracks, grounds, bearing lines, trail-camera entries, direct messages (both sides of every conversation), comments and likes, friend connections, blocks, push tokens and notification records, tournament entries, invites and proof media, forecast records, Edge AI questions, the record of your owner searches, the daily count of property-line tiles your account drew, and the record of your photo checks, for kill photos and profile pictures.

What stays:

• Tournaments you created remain, so the event is not taken away from the other hunters in it. Your name and code come off them — the director reads as “Deleted hunter”.
• Reports you filed, or that were filed about you, and our record of anything we took down or any suspension, are kept for moderation and safety. That includes our record of a profile picture the automatic check took down. They reference your hunt code, not your name or email.
• Results of tournaments that already finished. When a tournament closes, its final standings are saved as a permanent record so the other hunters in it keep their result. Your line in that record — your hunter name, hunt code, team name, kill count and place, the time of your first kill and the time you reached your final count, and a winner or first-blood mark if you earned one — is not removed, and any signed-in hunter who opens that tournament can still see it. The final-result notification the other entrants received, which may name the winner, stays in their notifications.
• Past season results. At the end of each month we save every scoring hunter’s hunt code, verified kill total and place among their friends. Those rows stay after you delete your account. They do not hold your name or email.
• Photos and prompts already sent to our AI providers are governed by those providers’ own retention terms, which we do not control and cannot override; we have no way to recall them. See xAI’s privacy policy and Anthropic’s privacy policy.
• Your subscription record at RevenueCat. It is keyed to an account ID that no longer exists anywhere else. Nothing in the app deletes it, so if you want it gone, email support@coyoteedge.com and we will ask them to remove it.
• The study files we have already built. The offline work described in section 3 produces files that sit outside the app’s database, and a deletion does not reach into a study that has already been run. Nothing in them carries your name; they do carry a label we could trace back to you, which is why section 3 does not call them anonymous.
• Request logs. Entries already in our hosts’ request logs and in our sign-in service’s own log (section 2) are not removed by a deletion; they expire on their own schedule.
• Your sign-in history. Our sign-in service’s history of sign-ins (section 2) stays after you delete your account. It holds the email address you used, and no IP address.

Deletion is not instant, and it is not atomic. If any part of it fails, your login is kept so you can sign in and try again or contact us, rather than leaving pieces behind that you cannot reach. In the rare case where we cannot match your hunt code, stored photos may survive a deletion that otherwise reported success — tell us and we will go get them.

8. Children

You must be at least 17 to use CoyoteEdge. It is not directed to children, and we do not knowingly collect information from anyone under 17. The app asks the year you were born when you sign up — and once, after an update, if you already had an account — and does not let anyone go on whose answer means they could be under 17. It does not verify the answer and never keeps the year itself: on your account it keeps only that you passed, when, and which version of the Terms you agreed to, and a phone that turned someone away keeps only when that happened. If we learn that someone under 17 has an account, we will delete it.

9. Security

Your data is stored with Supabase and protected by row-level access rules so hunters can only read what they are allowed to — your own records, and your friends’ kills. Passwords are handled by Supabase’s sign-in service, hashed and never visible to us. Connections are encrypted in transit. No system is perfectly secure, and we cannot promise absolute security.

10. Your rights

You can see and correct your data inside the app, delete it from Settings → Delete account, and ask us for a copy of it by emailing support@coyoteedge.com. There is no one-tap export in the app yet; we will put your copy together by hand.

California residents have the right to know what personal information we collect, to delete it, and to not be discriminated against for exercising those rights. We do not sell or share personal information for cross-context advertising.

CoyoteEdge is offered in the United States only, and is not listed in the EEA or UK app stores.

11. Changes

When this policy changes, we update the date at the top. Material changes will be called out on this page and, where practical, in the app.

12. Contact

support@coyoteedge.com
Email is the only way to reach us about this policy. We reply within two business days.