PB PrimeBite Fishing Premium Fishing Intelligence
Privacy

Privacy Policy

Last updated: May 19, 2026

The PrimeBite Fishing app is designed to keep your Logbook data local-first on your device. We do not track you for advertising, and we do not sell your data. PrimeBite now also offers optional account sign-in. If you choose to sign in, limited account and session data may be processed off-device by our account providers. Signing in by itself does not upload your old Logbook trips, catches, or photos. If you later use Delete Account inside the app, PrimeBite is designed to remove the optional account and any copied account-side Logbook data tied to it, while leaving the local Logbook already stored on your phone in place unless you delete that local data too.

What We Collect (On Your Device)

  • Trip Logs: Trip start time, hours fished, target species, trip outcome, optional fish count, optional trip notes, and optional linked catches.
  • Catch Photos (optional): References (URIs) to photos you attach to entries.
  • Fishing Notes: Text you add to your catch log or trip log.
  • Location Data (optional): GPS coordinates used for local forecasts, sunrise/sunset, weather views, optional current-location selection, and optional catch or trip tagging.
  • Preferences: Settings like pounds vs. kilograms, saved weather/location choices, and other app preferences.
  • Notification Preferences (optional): Settings for forecast notifications, including species selection, rating thresholds, and notification times.

What We Collect (Optional Account Data)

  • Account Identifiers: Your email address or provider-linked account identifier if you choose Sign in with Apple, Sign in with Google, or email magic-link sign-in.
  • Session And Auth Data: The limited auth/session data needed to keep you signed in and restore your optional account session.
  • Basic Account Profile: A small account profile row used to connect your optional account to PrimeBite.
Your Logbook entries stay on your device by default. Optional account sign-in uses limited off-device auth/profile handling, but signing in alone does not move old Logbook trips, catches, or photos off your phone.

Why We Use This Data

  • Logbook: Save and review your catches and full trips.
  • Trip Tracking: Let you record whole outings, including no-catch trips, trip length, and linked catches.
  • Forecast Accuracy: Improve bite forecasts, sunrise/sunset times, and weather views for your chosen or current area.
  • Optional GPS Tagging: Remember where a catch or trip happened.
  • Bite Windows and Forecasts: Show suggested times using sunrise/sunset, moon phase, weather, and related forecast inputs.
  • Preferences: Keep your chosen units, saved locations, and settings.

Permissions

  • Location (Foreground Only, Optional): Used for local forecasts, sunrise/sunset, current-location selection, weather views, and optional catch or trip location tagging.
  • Camera (Optional): Used when you choose to take a catch photo inside the app.
  • Photos/Library (Optional): Used when you choose to attach an existing photo or save a catch photo to your camera roll.
  • Notifications (Optional): Used when you choose to enable forecast reminders or alerts.

The app works without granting these permissions.

Notifications

The app may send you push notifications for forecast reminders if you enable this feature. Notification preferences (including which species to monitor, rating thresholds, and notification times) are stored locally on your device. You can disable notifications at any time in your device settings or within the app.

App Updates & Community Polls (Optional Broadcast Notifications)

PrimeBite also offers an optional broadcast notification channel — controlled by the "App updates & community polls" toggle in Settings — that the developer can use to notify all opted-in installs about new species, voting windows, and app updates. This is separate from the forecast reminders described above.

When you grant notification permission and leave this toggle enabled, the app registers this install with PrimeBite's Supabase backend so the developer can deliver these broadcasts. The following information is uploaded and kept up to date for as long as the install is active:

  • An Expo push token — an anonymous device token issued by the Expo Push service (a third-party push relay) so the broadcast can be delivered to your device.
  • An anonymous install identifier — a random identifier generated on first registration and stored on your device. Used to keep one row per install across token refreshes.
  • Your signed-in user id, only if you are signed in to a PrimeBite account at the time of registration. If you use the app without signing in, no user id is sent.
  • Your "App updates & community polls" opt-in flag, the app version, and your platform (for example, "iOS 26.4") — so a broadcast can target only the installs that asked for it.

How broadcasts are sent: when the developer triggers a broadcast, PrimeBite's Supabase backend forwards the message to the Expo Push service (), which in turn delivers it to Apple's APNS for your device. Expo's privacy policy: .

You can opt out at any time by turning off the "App updates & community polls" toggle in Settings, or by disabling notifications for PrimeBite in your iOS Settings. Opting out keeps the row on file with the opt-out flag set, so future broadcasts skip your install.

Optional Accounts

Account sign-in is optional. You can still use PrimeBite in guest mode. If you choose to sign in, PrimeBite may use Sign in with Apple, Sign in with Google, or email magic links through our auth provider. The current sign-in flow is for account access and session handling. It does not automatically copy your old Logbook data into the cloud. If you later use Delete Account in Settings, PrimeBite is designed to remove that optional account and any copied account-side Logbook data tied to it, while leaving the local Logbook already on your phone unless you delete it there too.

Online Services We Call

Open-Meteo (Forecast, Marine, Air Quality, and Related Weather Data): We query Open-Meteo for sunrise/sunset times, weather forecasts, marine data, air-quality data, and related forecast/location information using your coordinates, date, and in some cases place-search text. These requests help power forecast accuracy and weather-related app features. If the network is unavailable, some features fall back to local calculations or become unavailable until you reconnect.

NOAA CoastWatch ERDDAP (Ocean Data): For offshore species forecasts, we query NOAA's CoastWatch ERDDAP service for sea surface temperature (SST) data using your coordinates and date. This is a free, public U.S. government service. Requests are anonymous. NOAA's privacy policy:

Copernicus Marine Service (Chlorophyll Data): For offshore species forecasts, we query the Copernicus Marine Service (via a proxy server) for chlorophyll-a concentration data using your coordinates and date. Requests are anonymous. The proxy server does not store or log any user data. Copernicus privacy policy:

OpenStreetMap / Nominatim (Place Search and Reverse Geocoding): When you search for a place, drop a pin, or refine a saved location name, the app may send your place-search text or coordinates to OpenStreetMap's Nominatim service so the app can resolve or label that location.

National Weather Service (Official Alerts): For supported weather-alert views, the app may query National Weather Service alert endpoints using your coordinates to display official alerts for your area.

Supabase (Optional Account Auth, Profile Handling, And In-App Feedback Storage): If you choose to sign in, we use Supabase for account authentication, session handling, and a basic account profile record. Supabase may process your sign-in email or provider-linked account identifier, session data, and related auth/profile data needed to keep your optional account working. Supabase also stores messages submitted through the in-app feedback form (see "In-App Feedback" below). Supabase privacy policy:

Resend (In-App Feedback Email Forwarding): When you submit a message through the in-app feedback form, we use Resend to forward that message from our Supabase backend to the app developer's email so the developer can read and act on it. Resend receives only the message text, your optional reply-email field (if filled), the feedback category, the source surface (which screen the feedback came from), your app version, and your platform. Resend privacy policy:

Apple / Google Sign-In Providers (Optional): If you choose Sign in with Apple or Sign in with Google, Apple or Google also handle parts of that sign-in flow according to their own privacy terms.

Subscription Services

RevenueCat: We use RevenueCat to manage subscriptions, purchases, entitlement status, and limited promotional or complimentary premium access for PrimeBite Pro. RevenueCat may collect:

  • App user identifiers and device identifiers
  • Your Apple ID or Google account information (for purchase verification, when applicable)
  • Purchase and subscription history
  • Subscription status

This data is used to manage subscriptions, restore purchases, verify premium access, and administer limited promotional or complimentary access when applicable. RevenueCat's privacy policy:

Premium Features: The app offers a premium subscription (PrimeBite Pro) that provides access to extended forecast features. Subscriptions are managed through Apple's App Store or Google Play Store and are subject to their terms and conditions. Subscriptions automatically renew unless cancelled at least 24 hours before the end of the current period.

Data Sharing and Tracking

  • We do not sell your personal data.
  • We do not share your personal data for cross-app or cross-site advertising.
  • We use limited service providers only when needed to operate subscriptions, account sign-in, or app functionality, such as RevenueCat for subscriptions, Supabase for optional account auth/profile handling, and the external data providers listed above for forecasts.
  • We do not track you across apps or websites.
  • No analytics or advertising SDKs are included.

If You Choose To Share Logbook Data With PrimeBite

PrimeBite can offer manual email-share helpers for Logbook validation data. These helpers only run after a clear user action inside the app. They are not automatic cloud sync.

  • Share My Logs: Sends a shared-safe validation export that removes fishing place names and softens coordinates before the draft email is created.
  • Share Exact Spots: Sends an exact validation export that includes your exact coordinates and fishing place names, but only if you clearly choose that option and confirm it.

If you use one of these manual share helpers, PrimeBite may receive the exported Logbook data you choose to email, and may use it to validate and improve bite-rating accuracy.

In-App Feedback

PrimeBite Fishing includes an in-app feedback form. You can use it to send a feature idea, a bug report, or a general note about the app. It appears in a few places: the Settings tab ("Tell me what to build" and "Report a Bug"), a small "Anything missing?" link at the bottom of the Today tab, and once at the end of the new-user setup (asking what species you fish for so we know what to add next).

The form only runs after a clear user action — typing into it and tapping Send. We do not send anything in the background.

When you submit feedback, the following information is sent from the app to PrimeBite's Supabase backend, stored there, and then forwarded by email to the app developer through Resend:

  • The message text you typed.
  • The feedback category you picked (feature idea, bug, or other).
  • The source surface (which screen of the app you submitted from — used by us to see which entry points get the most use).
  • Your app version and platform (for example, "1.4.8" and "iOS 26.2") — so we know which build the message came from when we read it.
  • Your optional reply-email, only if you choose to fill in that field. Leave it blank and the message is sent anonymously.
  • Your signed-in user id, only if you are signed in to a PrimeBite account at the time you submit. If you use the form without signing in, no user id is sent.
  • An anonymous install identifier: a random identifier generated by the app on first feedback submission and stored on your device. It is not linked to your name, email, or any advertising identifier, and it is used only so PrimeBite can tell whether multiple feedback messages came from the same install or from different installs (for example, to spot abuse or duplicate submissions).
  • Your IP address: captured by our backend from the network request when you submit feedback. It is used for the same anti-abuse and duplicate-detection purpose as the install identifier, and is not used for advertising, tracking across apps or websites, or building a profile of you.

You can submit feedback without an account. We do not require sign-in for this form.

Optional photo attachment: The in-app feedback form lets you attach a photo from your camera roll (for example, a screenshot of a bug). When you tap the attach button, PrimeBite asks for permission to read your Photo Library; you can decline and still submit feedback without a photo. If you do attach a photo, the image is uploaded to a private Supabase Storage bucket, a temporary 90-day link to the image is generated, and that link is included in the email forwarded to the app developer through Resend. Only the developer (using a private service key) can access the bucket directly. The link expires after 90 days.

Your Control

  • Stay Guest Or Sign In: You can keep using PrimeBite without creating an account.
  • Sign Out: If you use the optional account, you can sign out inside the app. Signing out does not delete the Logbook entries already stored on your phone.
  • Delete Account: If you use the optional account, you can delete it inside the app. PrimeBite is designed to remove the optional account and any copied account-side Logbook data tied to it, while leaving the local Logbook already on your phone unless you delete that local data too.
  • Export: Create a JSON backup of your catch and trip logbook data in Settings.
  • Choose Safe Or Exact Sharing: If you manually share Logbook data with PrimeBite, you can choose a shared-safe version or an exact-spots version first.
  • Import: Restore a JSON backup of your catch and trip logbook data in Settings.
  • Delete Individual Entries: Remove catches or trips from your logbook.
  • Delete Local App Data: Uninstalling the app removes local app data from your device. It does not automatically delete any optional account data or copied account-side Logbook data stored off-device unless you also use Delete Account.

The current backup flow may involve copying your backup JSON into a cloud document or storage service you choose, such as Google Drive. If you do that, the copied backup is also subject to that provider's privacy and security practices.

Children

This app is intended for general audiences and is not directed to children under 13. We do not knowingly collect personal information from children.

Security

Your Logbook data remains on your device by default unless you choose to export or share it. If you use optional account sign-in, limited auth/profile data is also handled off-device by the account providers used for sign-in. Avoid sharing exported backups publicly, and only use exact-spot sharing if you truly want PrimeBite to see your exact locations.

Contact

Questions or requests? Email .