Effective date: September 29, 2026
bayLURE is a fishing-conditions app. It has no accounts and no analytics. We (the developer) don't collect your personal data. The only things the app contacts on our behalf are a small relay for one map lookup, a check for app updates, and — only if you subscribe to bayLURE Pro — the app store's billing and our subscription processor, described under Our relay, App updates, and Purchases below. The app is supported by a single banner ad — see Advertising. We share data only with services and SDKs that commit to protecting it at least as strongly as this policy describes.
Your catch log (species, gear, notes, sizes, dates), attached photos, saved favorite spots, presets, settings, and the bite-score tuning learned from your catches are stored only on your device. They are never uploaded anywhere. Backup files you export go wherever you choose to save or share them. Deleting the app deletes everything it stored.
When you use your location (or type an address / drop a pin), the app sends those coordinates to the services that answer for that spot. Coordinates are used transiently to answer each request; we do not store them, and they are not linked to your identity. Each service processes requests under its own privacy policy.
Weather, water and charts (US government, public domain):
Other services:
Location access is optional — the app works with a typed address or a dropped pin, and you can deny the location permission at any time in system settings.
Links you tap (your state's fishing regulations, a web search for them, directions in Apple Maps or Google Maps) open in your browser or maps app and send nothing until you tap them.
For the OpenStreetMap lookup above, phones first ask a small relay we run
on Vercel (baylure-android.vercel.app) rather than the
volunteer-run Overpass servers directly, which throttle the shared addresses
phones sit behind. The relay receives your spot's coordinates rounded to
about 10 meters, a search radius, and — like any web request — your IP
address. It forwards the query and caches the answer for that area for six
hours so the same lookup isn't repeated. We don't record these requests and
never see who made them; Vercel, which hosts the relay, may keep short-lived
operational logs under its
privacy policy. Apart from the subscription processing described under
Purchases, nothing else in the app talks to us.
To deliver bug fixes without a store release, the app checks Expo's update service (EAS Update, expo.dev) when it launches. That request carries a random installation token (not derived from your device or any account), your platform and app version, and — like any web request — your IP address; after a crash it may include the error message so a broken update can be rolled back. No other data is sent. Governed by Expo's privacy policy.
bayLURE Pro is an optional auto-renewable subscription bought through the App Store on iOS or Google Play on Android. Payment is taken by Apple or Google under your store account; we never see your card, billing address, or store credentials. To confirm the purchase and keep Pro unlocked across reinstalls and devices, the app uses the RevenueCat SDK, which receives the purchase receipt or token issued by the store, a random app user ID the SDK generates on this device (not tied to your name, email, or store account), and basic device and app details (platform, app version, locale, and — like any web request — your IP address). RevenueCat keeps a record of the subscription's status, and the paywall and the manage-subscription screen it provides may show you the current price, trial, and renewal terms from the store. RevenueCat processes this under its privacy policy. We can see that a subscription exists in RevenueCat's dashboard, but not who holds it. On Android, a redeem code entered in the app is checked on the device and sent nowhere.
The photo library permission is used only when you choose to attach a photo to a catch. The photo is copied, resized, and kept on your device, and its embedded date and GPS position (if any) are read on the device to pre-fill when and where you caught the fish. Photos are never uploaded.
bayLURE shows one banner ad served by Google AdMob on Android and iOS. The app requests non-personalized ads: they are matched to general context, not to a profile of you. To serve and measure ads, Google's advertising SDK may collect device information such as your IP address, general (city-level) location, and device identifiers — on Android, your advertising ID — handled under Google's advertising privacy policy. On iOS, bayLURE never asks for tracking permission, so the SDK receives a blank (all-zeros) advertising identifier. We do not receive this data.
If an ad looks inappropriate, report it — Guide tab → Privacy & Support → Report an ad, or email the address under Contact — and we will take it up with Google.
You can limit or reset advertising identifiers any time:
Everything bayLURE saves stays on your device, and we hold nothing on a server, so you control all of it:
bayLURE is not directed at children under 13 and collects no personal information from anyone.
If this policy changes, the updated version will be posted at this URL with a new effective date.
Questions: eyang.support@gmail.com