Privacy

This is short because there is very little to describe. The regulations, the management unit boundaries, and the sunrise and moon figures all live on your device, and the app works with no signal. What follows is the whole picture: what your location is used for, what is kept on your phone, and the few things the app downloads.

Your location

Location is optional. The app never asks for it on its own, and you can use every part of it without ever granting it — open the Map tab, tap the unit you want, and tap Show seasons here. That is a complete substitute for GPS.

If you do use the locate button, your coordinate is used on your device for three things: to work out which management unit contains the point, to calculate sunrise, sunset and moon phase for where you are, and to warn you when you are close to a unit boundary. All three are computed on-device against the regulation database already stored on your phone. Nothing about your location is sent over the network — not to us, not to anyone.

Your coordinate itself is never written to storage. It is held in memory while the app is running and is gone when the app closes. The one thing that is kept is the management unit code it resolved to — a value like 4-09, covering an area typically thousands of square kilometres — so the app can show you something useful before your next fix. That code stays on your device. The one exception is a track you deliberately start recording — see Waypoints and recorded tracks below.

On iOS the permission prompt reads: "BC Hunt uses your location to identify which management unit you are in, so it can show the seasons and bag limits that apply where you are." That is what it is used for unless you deliberately start recording a track — see the next section.

Waypoints and recorded tracks

If you drop a waypoint or start recording a track, that is a deliberate action — the app never records your location on its own. A waypoint stores the coordinate you marked, plus any name and note you gave it. A track stores the sequence of coordinates recorded from the moment you tap Start to the moment you tap Stop, so you can retrace it later without cell service.

Both are written to a database file on your device, the same way your starred LEH hunt codes are. Neither is transmitted anywhere, backed up to us, or synced to an account — there is no account. Recording continues if the screen locks, because the app keeps requesting fixes in a foreground service so the track does not gap every time you put the phone in your pocket, but recording never starts on its own and stops the moment you tap Stop.

Deleting a waypoint or a track removes it immediately; there is no undo because there is nothing kept anywhere else to restore it from. As with everything else on this page: no analytics measure how often you record, no ad network sees a waypoint, and none of it requires or creates an account.

You can also edit, move, delete and export any of it. Export writes a GPX or KMZ file — the formats GPS units, hunting apps and Google Earth read — and then hands that file to you: on a phone through the system share sheet, in a browser as a download. Nothing is uploaded in the process; the app has nowhere to upload to. What happens to the file afterwards is entirely your decision, and worth stating plainly: if you mail it, put it in a cloud drive or hand it to another app, your waypoints and tracks go wherever you sent them. That is the only way anything here leaves your device, and it only happens when you ask for it.

What is stored on your device

All of this stays on your device. None of it is transmitted, backed up to us, or synced anywhere — there is no server holding your copy of it, because there are no accounts.

• The regulation dataset — the seasons, conditions, LEH hunts and unit boundaries, as a database file. It ships inside the app.
• The official synopsis PDFs, if you open one — kept so they reopen offline. Roughly 13 MB each.
• Your last management unit, and whether it came from GPS or from a pin you placed.
• Your starred LEH hunt codes — the My Hunt Codes list.
• On the website, the same dataset in your browser's own storage, plus a note of which version is active, so the site works offline too.

Deleting the app removes all of it. On the website, clearing site data for bchunt.ca does the same. If you back up your phone, that backup is yours and goes wherever your backups go — we never see it.

The app does not read your contacts, photos, calendar, microphone, camera, health data, or files. It has no permission to, and no code that asks.

What the app connects to

Every request below is an ordinary download — a plain GET for a file. Your coordinate, your management unit, the species you looked at, the date you picked, and your starred hunts are never placed in a web address, a header, or a request body. There is no identifier for you or your device in any request, because none exists.

• On a phone or tablet, a cold start makes no network requests at all. The dataset is already inside the app.
• data.bchunt.ca — the map background, downloaded in pieces as you pan the Map tab. Also the regulation dataset itself, but only when you tap Check for updates now in More. The app never checks for regulation updates on its own.
• www2.gov.bc.ca — the official synopsis PDF, when you open it. On a phone the app fetches it straight from the Province's website, so their web server sees your request the same way it would if you had opened the PDF in a browser. On the website it goes through bchunt.ca instead, and the Province's server sees our server rather than you.
• bchunt.ca — the website, if you use the app in a browser. While a tab is open it checks roughly every 15 minutes whether a newer version of the site has been published, by re-reading a small version file from bchunt.ca. That check exists so the browser tab can offer you a reload; it sends nothing about you. The app on a phone does not do this.

Server logs

These downloads are served by Cloudflare on our behalf, and like every web server on the internet, it records the request: the IP address it came from, the time, the file requested, and the browser or app version string. That is a normal, unavoidable consequence of asking a server for a file, and it is worth being straight about rather than claiming nothing is ever observed.

Two honest details. The map background is fetched in byte ranges, so those log entries indicate which part of the province was on screen. And because the app on a phone downloads the synopsis PDF directly, the Province of British Columbia's own web server sees that request, under their policies, not ours.

We do not use these logs to build a profile, do not combine them with anything else, do not attach an identifier to them, and have no analytics of any kind layered on top. They are operational records — enough to know a file was served and whether it failed.

This page

There is no script on this page, no web font, no image loaded from another site, no cookie, and no analytics. It is one file of text. The same is true of the support page.

Children

BC Hunt is a reference tool for licensed hunters and is not directed at children. It collects no personal information from anyone, of any age, so there is nothing about a child for it to collect, use, or disclose.

Changes to this policy

If this ever changes, the new version replaces this page and the effective date at the top changes with it. Anything that materially affects what the app collects or transmits will be called out here in plain terms, not slipped into a longer document. If the app ever begins collecting something — it has no plans to — that would be described here, and on iOS it would also require an updated privacy disclosure on the App Store listing before release.

Contact

Questions about privacy, or anything else, go to the same place as everything else: [email protected]. That is the address behind Report an issue in the app, under More.

Email [email protected]

BC Hunt is an independent project by Gustavo Nobrega. It is not affiliated with, endorsed by, or produced by the Province of British Columbia.