Privacy

Privacy Policy

Last updated: October 5, 2026

This Privacy Policy explains how PrimeBite LLC, an Illinois limited liability company ("PrimeBite," "we," "us," or "our"), handles information through the PrimeBite Fishing app and website.

The 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)

Catch Logs: Catch and save times, species, weight and length measurements, release status, notes, linked trip, entry source, gear, bait, structured tackle, technique, depth, water clarity, lure color, structure, water flow, and tide stage when you add or save them.
Fish Finder Readings (optional): The water temperature you choose to type in from your own fish finder, and the unit (°F or °C) you typed it in.
Trip Logs: Created, start and end times, trip status, hours fished (or "under 1 hour", or that you don't remember) and whether hours came from the trip clock, from you, or from a default, target species, water type, trip outcome including your answer to whether you caught your target fish, optional fish counts, including fish you add during a trip with + Fish, +5 or a number you type (each with the fish name, the time you added it, and the bait when known), the bait you used and, on a timed trip, when you switched, linked catches, custom title, notes, whether the trip was a practice trip or on the ice, and your optional note on how the bite was (Poor to Hot). To avoid asking you the same question too often, PrimeBite also keeps a few small reminder notes on your phone: the date it last offered "Add your hours", and, for a trip left running, when you last chose "I'm still fishing" and, for some of those trips, when it first reminded you. PrimeBite does not upload these notes. They have no set expiry, may stay after you delete a trip, and are removed from the phone when the app's local data is cleared, for example when you delete the app. In version 1.8.0 and later, trip records can also include anglers aboard, rod or spear, clarity or visibility, a water temperature and unit you typed, hours with lines in or time in the water, later answers, and when or how a fish target was added. The trip water-temperature field is separate from the catch fish-finder reading described below. Trip extras and later answers can be included in your private JSON and trips CSV exports; the catch fish-finder export limits remain as described below.
Catch Photos And Local Asset IDs (optional): App-owned copies of photos you take in the app, attach, or import. Before version 1.8.0, these copies are full size. In version 1.8.0 and later, a new photo larger than 2560 pixels on its long side is normally saved as a smaller JPEG copy, 2560 pixels on that side. A photo that already fits, or that cannot be made smaller, is copied unchanged and keeps any details its file already had. The smaller copy does not keep the photo's location, capture date, or camera details; when PrimeBite uses a photo's date or place, it reads them from the original, not from its own copy. When you take a photo in the app, PrimeBite first tries to save the full-size shot to your photo library. If that save fails, for example because photo access is not allowed, PrimeBite does not make its own copy smaller. Photos already in your Logbook are not made smaller or changed; an older photo that PrimeBite moves into its private storage is copied unchanged. These private local copies keep the Logbook working without changing or deleting the originals in your photo library. Log From Photos can also store photo-library asset identifiers on the catch and in a separate local duplicate-prevention list. When an Android picker does not give an identifier, PrimeBite tries to create and store a code worked out on the phone from the photo's contents instead. If no identifier or code is available, the photo may not be remembered in the separate duplicate-prevention list. The list can remain after you delete the catch so that photo is not offered again. PrimeBite's recovery and upgrade copies refer to these photo copies but do not contain the photos themselves. If you include a photo in a trip picture card, or save a Logbook photo to your photo library, PrimeBite uses its own copy, not the original.
Location Data (optional): Exact GPS coordinates, spot and place names, waterbody, time zone, location source, and your Exact, Water, or Secret sharing choice for a catch or trip. Location is also used for local forecasts, sunrise/sunset, weather views, and current-location selection.
Environment And Conditions: Moon phase, sunrise and sunset, weather and ocean snapshots and history, recent weather, saved-condition state, and related source and capture times when available.
Saved Rating Records: Saved rating results and labels, the source time or window, best-window or trip timeline details, and the app version and build, model version and benchmark cohort version used when the record was made. These are stored history fields only. This list does not change what a PrimeBite rating means or how one is calculated.
Private Recovery And Upgrade Copies: To protect the Logbook from an interrupted save, app stop, or old-data upgrade, PrimeBite can keep app-private transaction journals, recovery files, one-time upgrade snapshots, and quarantined copies. These can contain exact catches, trips, locations, hidden Logbook state, and references to locally stored photos. A quarantined old-format copy can contain the exact raw Logbook data that could not yet be safely read or replaced.
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, plus your fishing-pattern alert and trial-reminder choices.

In version 1.8.0 and later, your phone also stores water profiles: water names, types, sizes, sharing choices, spot identifiers and coordinates, private pin names, water notes, and the history needed to join or split waters. A new water starts private. Private pin names and confirmed pin-name choices stay out of the private JSON and relevant CSV exports. Water names, notes and exact coordinates can still be in those exports. Local water-upgrade progress and display choices help the app remember what you have already checked.

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: Your account ID, the sign-in method you first used, the name your sign-in provider shares (when it shares one), a random local profile ID that links the account to the app on your phone, and when the profile was created or updated.
Research Preference (optional): If you change "Help improve ratings" while signed in, the preference, consent-version number, and change time may be saved to your account profile. This does not upload your Logbook.

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.

Local Logbook Recovery And Cleanup

PrimeBite keeps these recovery copies only on the device and removes them cautiously. A finished transaction copy is removed after its marker is safely closed. An unreferenced temporary or active recovery file is removed only after it is at least 24 hours old and the app proves a fully clean start. A legacy-upgrade snapshot is removed only after recovery is resolved, at least seven days have passed, and three different clean app starts have been recorded. An escaped newer-format quarantine or older raw quarantine is removed only after at least 30 days and three different clean app starts.

Cleanup fails closed: if PrimeBite cannot safely read, remove, or verify one of these private copies, it keeps the copy and tries again later instead of risking data loss. When you delete a catch or trip, PrimeBite purges retained upgrade snapshots and quarantines that could still contain that entry. An active transaction needed to finish the deletion remains only until its recovery marker safely closes.

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. If location is already allowed, the Logbook may also check your position on the phone to suggest a spot near you, or to ask about your hours when you end a trip far from where you fished. That position is not saved or sent.
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, save a catch photo to your camera roll, or run the optional "Log From Photos" import described below.
Notifications (Optional): Used when you choose to enable forecast reminders or alerts.

The app works without granting these permissions.

Log From Photos (Optional, On-Device)

PrimeBite offers an optional "Log From Photos" feature (formerly "Fill from Camera Roll"). On iPhone, if you choose to run it and grant photo library access, the app scans your photo library entirely on your device using Apple's built-in image analysis to find photos that appear to contain fish. On Android, the app instead opens your system photo picker so you choose the fish photos yourself — there is no automatic scanning. Either way, for each photo, the app reads the photo's capture date and location (if present) to create a catch entry in your local Logbook with the real weather and conditions from that day and spot.

The photo image itself stays on your device. To rebuild weather conditions, PrimeBite may send its fishing-spot coordinates and a date range based on the photo's capture date to Open-Meteo. PrimeBite may also send the coordinates to Open-Meteo to resolve the time zone, and to your phone operating system's native geocoder to get a place name.

On Android, photo location details may be hidden. In version 1.7.1 and later, if PrimeBite asks you to choose a replacement spot, typing a place sends the search text to Open-Meteo's geocoding service and may send it to OpenStreetMap/Nominatim if Open-Meteo returns no match, or if the search includes a water word (such as lake or river) and Open-Meteo finds no water place. Selecting any replacement spot, including a Saved or Recent place, a search result, current location, or a dropped map pin, may send the selected coordinates to Open-Meteo for time zone resolution. Current location and dropped pins may also send coordinates to the phone operating system's native geocoder for a place name. Opening the Android map picker uses the Google Maps SDK, so Google may receive map requests, the viewed area, and normal network metadata. The photo image is not sent through these spot-picker routes.

The scan runs only when you start it. There is no background or automatic scanning.
No photo leaves your device during import. On iPhone the image analysis happens on your phone using on-device processing; on Android you simply pick the photos. The image itself and the scan result are not uploaded to PrimeBite or an outside provider by this feature. The date and spot may be sent as explained above.
Saved catches use private local copies. PrimeBite copies each accepted photo into its private app storage. A cancelled or failed import removes unfinished copies. Deleting a catch removes its private copy after the short Undo period, and startup cleanup removes copies left by an interrupted import. Your original photo-library file is not changed.
The app does not identify fish species. You add the species and details yourself.
Imported catches behave like any other Logbook entry. They stay on your device unless you separately review and confirm an account-copy action. You can edit or delete them at any time.

Saved Logbook Weather Checks And Refresh

When you log a catch or trip, or change its time, place or fish, PrimeBite sends the fishing spot's coordinates to Open-Meteo, with a date range when the day has already passed, to look up the weather and, when needed, the spot's time zone. For a finished trip, it may also look up the weather over the hours you fished. For saltwater species it also looks up sea temperature and chlorophyll from NOAA and Copernicus, through our Railway proxy for Copernicus. If a lookup can't finish right away (for example, with no signal), the log is saved first. The app then tries again on its own when you open or return to the app, or close that log's screen, with signal. It does not run in the background. The log's own lookups keep trying for 7 days after the app first records an Open-Meteo answer that doesn't finish them. After that, they wait for one more try that gets an answer, and then stop. The weather over a finished trip's fishing hours has its own 7-day window and stops when that window ends, without a last try. Tapping Try again on the log restarts only the log's own lookups, not the whole-trip weather. Nothing else from the log is sent: no species, notes, photos, catch details, rating or account information. When you confirm a saved-weather check or refresh, PrimeBite may send the same coordinates and a date range to Open-Meteo to retrieve historical weather. A bulk refresh can process eligible saved catches and trips, including entries hidden by the current list filter. The app asks for confirmation before starting. Original saved weather remains in the entry's local history, and the refresh provides an Undo option.

Notifications

With notification permission, PrimeBite schedules reminders on your phone for the features you turn on: forecast alerts, fishing-day reminders you set from the forecast calendar, fishing-pattern alerts and, during a free trial, a reminder before it ends. The app sets these itself; PrimeBite's servers do not send them. 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.

The optional "Still fishing?" reminder starts off. If you turn it on and allow notifications, your phone can remind you about a timed trip after four hours. Its notification contains a general message, not your fishing location, fish or photo. The app keeps the trip identifier, trip start, notification identifier, due time and scheduling state locally to manage the reminder and avoid repeats. This feature does not upload those records. Turning it off cancels the scheduled reminder, while a used-reminder marker may remain until a later trip-state check clears it or local data is cleared.

App Updates & Community Polls (Paused)

PrimeBite is not currently sending server-sent app-update or community-poll notifications. Current app versions hide the unfinished broadcast switch and do not register for broadcasts automatically. Some older installed versions may still show the switch or attempt registration until they are updated.

If an older version registers for this paused feature, it may upload an Expo push token, a random install identifier, the broadcast preference, app version, platform, timestamps, and the signed-in user id when present to PrimeBite's Supabase backend. PrimeBite will not use those records to send broadcasts while the feature is paused. The retention and deletion rules in this policy still apply.

If PrimeBite offers broadcast notifications later, we will update this policy and the applicable store disclosures before turning the feature back on.

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.

Account deletion and interruptions: The app keeps limited recovery records in secure storage and outcome-warning records in app-private storage on your device. These may contain a random deletion-attempt ID, your account ID, a recovery secret, creation time, and status or cleanup information. They help the app handle interrupted requests and tell you when it cannot confirm whether deletion finished. A lost connection or expired session is not treated as proof that your account was deleted. These records do not contain your email, Logbook entries, or photos. To request deletion or check on it, the app sends your account ID, the deletion-attempt ID and the recovery secret to PrimeBite's deletion service.

The local warning record remains until you acknowledge the warning and cleanup is complete or safely guarded, or a verified result safely replaces it. Other recovery records can remain while the outcome is unresolved. An older-server attempt marker can be retired without claiming successful deletion only after at least 31 days and when it blocks a different signed-in account. Secure device storage can survive uninstall, depending on the operating system; uninstalling is not a guaranteed way to erase these records. Contact us if an account deletion remains unresolved.

Public Website

PrimeBite's public website is delivered through Netlify. When you request a page, Netlify and normal internet or content-delivery systems may process the IP address, browser and device details, requested page, date and time, and security or error information needed to deliver and protect the site. Netlify's account settings, logs, and retention still require separate live-provider review.

The current website source does not load outside scripts, fonts, or images when a page opens. It does not intentionally set cookies, local storage, session storage, IndexedDB, or a service worker, and it has no client advertising, replay, or analytics code. Store, research, provider-policy, and other outside links contact their destination only after you choose the link. Ordinary browser and destination-site practices can apply after that choice. The one exception is primebitefishing.com/get: when a link to it carries one of PrimeBite's social-media tags (facebook, instagram, tiktok, or youtube) and you open it on an iPhone, iPod touch or Android phone or tablet, it sends you straight to the App Store or Google Play without waiting for you to tap a store link. That store link carries only fixed PrimeBite campaign labels: the platform's name with "_bio" added (for example, "tiktok_bio"), plus PrimeBite's own App Store provider number on Apple or the word "social" on Google Play. This helps us compare store visits and downloads from each social platform in Apple's and Google's reports. Nothing about you or your device, no cookies, and nothing else from the address you opened is added. The store's own practices apply once it opens.

Online Services We Call

Requests to forecast and location providers can include coordinates, a date or search text, and normal network information such as an IP address. PrimeBite's proxy host, Railway, and the outside provider may keep security, error, or request logs under their own practices.

Open-Meteo (Forecast, Marine, Air Quality, Time Zones, and Related Weather Data): We query Open-Meteo for sunrise/sunset times, weather forecasts, marine data, air-quality data, time-zone resolution, and related forecast/location information using your coordinates, date, and in some cases place-search text. Log From Photos, and a library photo you choose for a new catch, may send a photo's coordinates and a date range based on its capture date for historical weather, and may send the coordinates for time-zone resolution. 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. When a Logbook entry's weather lookup can't finish right away (for example, with no signal), the app tries again automatically later, as described under Saved Logbook Weather Checks And Refresh.

NOAA CoastWatch ERDDAP (Ocean Data): For offshore species forecasts and saltwater Logbook entries, 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. NOAA and normal network systems may receive network metadata with the request. NOAA's privacy policy: https://www.noaa.gov/protecting-your-privacy

NOAA CO-OPS (Tide Predictions): For supported coastal and offshore locations, we use your coordinates to find a nearby NOAA tide station, then request that station's tide predictions for the needed dates. PrimeBite stores these public station predictions briefly on your device to reduce repeat requests. NOAA's privacy policy: https://www.noaa.gov/protecting-your-privacy

WorldTides (Worldwide Tide Predictions): When NOAA has no clear station match and you choose to request worldwide tides, PrimeBite sends the selected ocean coordinates and fishing date through our Railway proxy to WorldTides. A free request returns the next high and low tides; PrimeBite Pro can request the seven-day tide chart. The Railway request also uses a random install identifier, and Pro requests include the RevenueCat app-user identifier needed to verify premium access. PrimeBite does not send your name, email, species, catch, notes, photos, or rating to WorldTides. Tide results are prediction data, not observed water levels, and are kept only briefly on the device and server. WorldTides provider logging and retention may also apply. WorldTides terms: https://www.worldtides.info/terms

Copernicus Marine Service (Chlorophyll Data): For offshore species forecasts and saltwater Logbook entries, we query the Copernicus Marine Service through our Railway proxy for chlorophyll-a concentration data using your coordinates and date. Copernicus, Railway, and normal network systems may receive network metadata and may keep operational logs under their own practices. Copernicus privacy policy: https://marine.copernicus.eu/privacy-policy

Phone Operating System Native Geocoder (Place Names): During a Log From Photos import and other location flows, the app may send selected coordinates to the native geocoder supplied through your Apple or Google operating system to get a place name. The photo image is not sent.

OpenStreetMap / Nominatim (Place Search): In version 1.7.1 and later, when a supported typed place search returns no Open-Meteo match, or the search includes a water word (such as lake, reservoir, river, or bay) and Open-Meteo finds no water place, including in Android's Log From Photos replacement-spot chooser, the app may send the search text to OpenStreetMap's Nominatim service to find a location. Other supported place-search or location-labeling flows may also use Nominatim.

OpenFreeMap / MapLibre (Offshore Map Background): Opening the offshore map uses MapLibre to request OpenFreeMap's dark map style and the map resources needed for the area you view. OpenFreeMap and normal network systems can receive the viewed map area, style and tile requests, and normal network metadata such as an IP address. The purpose is to render the offshore map background. Signed iOS/Android traffic is not verified for this source-only update and remains open. OpenFreeMap provider logging and retention are not verified.

Google Maps SDK (Android Map Pickers And Views): Opening a map picker or supported map view on Android may send the viewed area, map requests, and normal network metadata to Google. Android's Log From Photos replacement-spot chooser can open this map picker when you choose to drop a pin.

Apple Maps (iPhone Map Pickers And Views): On iPhone, map pickers and map views other than the offshore map use Apple Maps, so Apple may receive the viewed area, map requests, and normal network metadata.

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.

Weather can keep a successful alert feed in memory for the current app session. Separately, to avoid repeating requests for places the National Weather Service does not cover, your phone can store up to 100 rounded coordinate pairs with expiry times. They expire after seven days; the app removes expired entries when it next checks and can update the stored cache. These local coverage records contain no spot names or alert contents and are not copied to an account or uploaded by this cache. Weather requests can still send coordinates as described above.

Supabase (Optional Account Auth, Profile Handling, Preferences, Feedback, And Cancellation 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. If you change the "Help improve ratings" setting while signed in, the preference, consent-version number, and change time may also be saved to your Supabase profile. Supabase also stores the feedback and setup answers you send as described under "In-App Feedback" below, and answers you explicitly send through the optional cancellation survey. Supabase privacy policy: https://supabase.com/privacy

Resend (Feedback And Cancellation Email Forwarding): When you send in-app feedback or setup answers, or send the optional cancellation survey, we may use Resend to forward that submission from our Supabase backend to the app developer's email so the developer can read and act on it. This can include the fields described in "In-App Feedback" below and an optional attachment link when provided. Resend privacy policy: https://resend.com/legal/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
Store purchase receipts, transaction identifiers, and subscription details
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. If you explicitly send the optional cancellation survey after choosing a reason, PrimeBite also writes the reason category, when you sent it, and up to the first 256 characters of the optional message to RevenueCat customer attributes. Skip and closing the survey do not write cancellation-survey attributes. When PrimeBite tests two versions of first-time setup, it also writes which version your install was given to a RevenueCat customer attribute. This label contains no name, email, location, fish or free text. It is used only to compare the two versions. When the test ends, an app update asks RevenueCat to clear it the next time you open PrimeBite. The label can stay if that update is never opened on your phone, if PrimeBite was deleted from the phone first, or if the request does not reach RevenueCat. RevenueCat's privacy policy: https://www.revenuecat.com/privacy

Premium Features: The app offers a premium subscription (PrimeBite Pro) that provides access to extended forecast features. Subscriptions are managed through the Apple App Store or Google Play account that billed you and are subject to that store's terms. PrimeBite Pro renews automatically until cancelled. Apple advises cancelling a free or discounted trial at least 24 hours before the trial ends if you do not want it to renew. Google Play subscriptions can be cancelled before the end of the current billing period, and cancellation applies to the next period. The purchase screen shows the plan, price, and how it renews. Your store account shows the renewal date and your cancellation choices.

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 advertising SDKs are included. PrimeBite's own in-app usage events and the RevenueCat setup-test label are described in this policy.

Logbook Export, Text Sharing, and Pattern Images

These are eight separate user-started routes. PrimeBite does not automatically send any of them to its own servers. A clipboard, Photos library, operating-system share sheet, or destination app can keep its own copy under that system's rules.

Exact JSON clipboard export: Settings copies the supported validation JSON fields for catches and trips. This is not a full backup or restore file. In versions 1.7.0 and 1.7.1, it can include exact spot and place names (including your own spot names), waterbodies, unrounded numeric coordinates, Logbook identifiers, environment snapshots, and saved rating/model/build record fields. There is no separate confirmation or cancel step after you tap the button: the copy happens immediately, and your operating system controls the clipboard.
Catches CSV clipboard export: Settings copies one catch per row with the available catch, equipment, condition, environment, and location columns. In versions 1.7.0 and 1.7.1, location columns can include the stored waterbody, place name, and your own spot name, plus unrounded numeric coordinates. The copy happens immediately after the tap, with no separate in-app cancel step.
Trips CSV clipboard export: Settings copies one trip per row with the available times, effort, outcome, linked-catch count, environment, and location columns. In versions 1.7.0 and 1.7.1, location columns can include the stored waterbody, place name, and your own spot name, plus unrounded numeric coordinates. The copy happens immediately after the tap, with no separate in-app cancel step.
Quarantine recovery copy: If PrimeBite cannot safely read part of your local Logbook, you can tap Save a copy of my logbook file. PrimeBite places the exact raw catches and trips in a temporary JSON file in the operating system's cache, then opens the native share sheet. PrimeBite verifies that its temporary cache copy is removed after the native share call returns, including cancellation, or ends with an error. If the app stops first, it tries again on the next start and also removes residue from the older Documents-file location. PrimeBite does not upload this file. A destination you choose may keep its own copy.
Native Trip/Catch text sharing: Share Trip and Share Catch build a short text summary and open the phone's native share sheet. The text route does not add numeric coordinates: coordinate-only place values and PrimeBite-generated Dropped Pin or Ocean Spot labels containing coordinates are removed. Numbers you wrote in a Trip title or notes are not removed. For a non-Secret entry, the text may include an ordinary saved spot or waterbody name and notes. The private spot-name field is not added. Words you put in a title or notes can still be shared. Secret sharing removes structured spot names, location-derived trip titles, linked Secret-trip labels, and notes. PrimeBite does not choose or receive the destination. Trip and catch text sharing also respects the current water's sharing choice and the strictest trip or linked-catch privacy choice. Private sharing leaves out the structured place, location-derived title and notes.
Trip image share: In version 1.8.0 and later, Share Trip can create a temporary PNG with selected fish results, hours, a general water type and saved weather facts. A catch photo is included only if you choose it; this choice starts off. The app removes EXIF and text metadata from that PNG and opens the phone's share sheet only after you tap Share. The app tries to release its temporary capture after the share attempt finishes or fails. The image leaves out saved location fields and trip notes, but a photo or fish name can still reveal private details. A destination you choose may keep its own copy.
Pattern image save: From a pattern detail, Save to Photos asks for photo-library permission before creating a 9:16 PNG of the local pattern card. If permission is denied, no PNG is created, saved, or sent. After approval, PrimeBite captures the PNG, saves it to Photos, and releases the temporary capture when the save returns or ends with an error. The current pattern image can show locally calculated pattern words and numbers, but it does not add numeric coordinates. Closing the Pattern sheet before choosing Save or Share creates no PNG and saves or sends nothing.
Pattern image share: Only after you tap Share, PrimeBite captures the same pattern PNG as a temporary local file and opens the phone's native image share sheet. PrimeBite does not upload the PNG. The temporary capture is released when the share call returns, including cancel, or ends as unavailable or with an error. A destination receives it only through the choice you make in that sheet. The final output and cancel behavior of each native share sheet still need exact signed-build proof; that signed-build proof remains open.

In version 1.8.0 and later, private JSON and the relevant CSV files also include water profiles, water notes and join/split history, available trip extras and later answers, and saved results for trips with more than one target fish. They omit private pin names, confirmed pin-name choices and local water-upgrade progress, but can still contain water and place names, exact coordinates, identifiers and text you typed. A private water sharing choice does not hide those details in an exact export. Copy only to a destination you trust.

Clipboard contents, saved Photos, native share destinations, and provider apps are outside PrimeBite's direct control after you choose them. Treat exact exports and any location-bearing text as private. Signed traffic, destination behavior, and third-party retention were not proved by this source-only policy update.

Improving Our Ratings With Catch Data (Optional, Off By Default)

The "Help improve ratings" switch is optional and off by default. In the current release, it saves only your preference. It does not upload your Logbook, catches, trips, photos, notes, or locations. The Logbook cloud-upload gate is closed.

The preference is stored on your phone. If you are signed in, the choice, its consent-version number, and the time it changed may also be saved to your Supabase profile. You can change the choice any time in Settings. PrimeBite will update this policy and clearly explain any Logbook copy or research flow before enabling one.

Fish Finder Water Temperature (Optional)

While logging a catch, you can optionally type in the water temperature your fish finder shows, along with whether you typed it in °F or °C. PrimeBite checks that the entry is a number within a possible water-temperature range before saving it.

This reading is stored on your device. PrimeBite does not automatically upload or share it, include it in the JSON or CSV exports or shared text, or copy it to your optional account. If you save the recovery copy of your Logbook described above, that file can contain it. Your phone's own backups follow your phone's settings. It is not combined with other anglers' readings, and PrimeBite does not yet keep a saved, shared correction for any lake or river from it. Deleting the catch it belongs to removes the reading. Uninstalling the app removes it along with your other local Logbook data.

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. In version 1.7.1 and later, it appears in several places, including Settings, Today, onboarding, the bait guide, and the Logbook and My Patterns.

In version 1.7.1 and later, feedback is sent only after a clear action: tapping Send (or Send and continue), tapping a thumbs up or thumbs down answer to a "How was this?" question, or tapping an answer to a setup question such as "How did you find PrimeBite?" Fish you pick on that setup card are sent with your answer; closing the card sends nothing. 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, except where an item below says otherwise:

The message text you typed, or the setup answers you tapped, together with the question shown on screen.
The feedback category (feature idea, bug, or other). Setup answers and paywall-exit feedback use other.
The source surface (which screen of the app you submitted from — used by us to see which entry points get the most use). Paywall-exit feedback also includes which app feature opened the paywall.
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 if you do not want a reply.
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.
A pseudonymous install identifier: a random identifier the app creates the first time it needs one and keeps in secure storage on your device. On iPhone it can survive reinstalling the app. It is not an advertising identifier. The app also sends it with the cancellation survey and worldwide tide requests. It may appear in the same feedback record as an optional reply email or signed-in user id, and it is used so PrimeBite can tell whether multiple messages came from the same install (for example, to spot abuse or duplicate submissions).
Your IP address: our backend reads it from the network request, but since August 2026 it stores only a salted one-way code made from it, and it does not put the address or the code in the email. Feedback sent before then may still hold the raw address in the stored record and the developer email. 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.

If you send a note about a feature in "Try new features", the feedback also includes that idea's identifier, revision and title, its current and requested switch states, and the app build. It uses the same feedback service and recipients described here and does not attach your Logbook or photos. Opening the note or changing the switch sends no note. A retry after an unconfirmed send may send it twice.

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

Optional cancellation survey: If you start cancelling a trial or subscription, the app may show a short optional survey asking why. Only tapping Send & Continue to Cancel sends the survey. Skip sends nothing and continues to the store's cancellation screen. Using the X, backdrop, Android Back button, or "Never mind, stay subscribed" closes the survey and sends nothing.

When you tap Send, the submission is stored in PrimeBite's Supabase backend and may be forwarded through Resend to the developer's email. The sent fields are the reason category, optional message, optional reply email, whether you continued to cancellation, app version, platform and platform version, signed-in user id when available, stable RevenueCat app-user identifier, and the random install identifier. Our backend also reads your IP address from the request and stores only a salted one-way code made from it, to limit abuse. Normal network metadata may also be handled as part of the request. If you chose a reason, RevenueCat separately receives the reason category, when you sent it, and up to the first 256 characters of the optional message as customer attributes. These records are used to improve the app, not for advertising or cross-app tracking.

PrimeBite does not use these addresses for a general marketing list. We may reply to feedback or a cancellation note when you leave an address and ask us to answer. Older installed versions may also send a legacy later-follow-up flag; it is not an automated email schedule.

Photo attachments: In PrimeBite 1.7.0 and later, the feedback form has no photo option, so no photo is picked or sent. Some earlier versions let you pick a photo (for example, a screenshot of a bug) after asking for Photo Library permission, but cannot send it: when you tap Send, the app says it couldn't upload the photo and offers to send your message without it. When it tries, it sends only the photo's file type and size and the install identifier, not the image. Some older versions may still upload an attached photo to a private Supabase Storage bucket. For an uploaded photo, a temporary link to the image is generated and included in the email forwarded to the app developer through Resend. The link is set to expire after 90 days; this does not mean the stored photo or emailed copy is automatically deleted after 90 days. Anyone with a working link may be able to view the image, so treat that link as private. You can ask us to review or remove feedback and its attachment through the contact below.

In-App Usage Data

To understand how people move through the app and where the setup, alerts, review flow, Logbook, bait guide, or upgrade screens can be improved, earlier versions of the app send a small number of in-app events — for example, that an onboarding step was viewed, that an alert was created or opened, that a review prompt was attempted, that a new app session began, that the upgrade screen was opened or closed, or that a trial or subscription started. PrimeBite 1.7.0 and later do not send these events. In earlier versions, each event goes to PrimeBite's Supabase backend with the event name, a small bounded piece of context, the app version, your device's operating system and its version, and a stable RevenueCat app-user identifier. The most recent earlier versions also send the random install identifier described under In-App Feedback and, if you are signed in, your sign-in session; PrimeBite's backend does not accept their event requests, so PrimeBite does not save them, though Supabase may keep its normal request logs. Older versions save their events directly, without the install identifier. If you answer the Natural bait guide's helpfulness question in an earlier version, the event carries only a yes-or-no value. These identifiers can connect events from the same app user or install, and the RevenueCat identifier can connect them with subscription status, but they are not used for advertising or tracking across other apps or websites. Your bait and ice safety acknowledgments stay on your device and are not sent.

Event data from earlier versions does not include names, email addresses, or free-form text. It is used only to improve the app. It is not sold or shared with advertisers.

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. The service removes the Supabase account/profile and copied cloud Logbook data tied to it. If the app cannot confirm completion, it tells you the result is uncertain. Local Logbook entries stay on your phone unless you delete them there too. Limited local recovery and warning records may remain as explained under Optional Accounts. Other support, feedback, billing, or provider records may require a separate deletion request.
Copy Logbook Data: Copy exact Logbook JSON or CSV data to your device clipboard. Nothing is sent until you paste or share it.
Delete Individual Entries: Remove catches or trips from your logbook.
Delete Local App Data: Uninstalling the app removes ordinary local app data from your device. Some sign-in tokens or app identifiers kept in secure device storage may remain after uninstall, depending on the operating system. Sign out before uninstalling if you want to clear the current session. Uninstalling does not automatically delete optional account data or copied account-side Logbook data stored off-device; use Delete Account for that.

Deleting your PrimeBite account does not cancel an Apple App Store or Google Play subscription. Cancel billing separately in your store account. If you used Sign in with Apple, also go to iPhone Settings > your name > Sign in with Apple > PrimeBite > Delete > Stop Using to fully revoke Apple's sign-in access.

Some records outside the main Supabase account — such as feedback, cancellation, subscription, vendor security, or email records — may remain for support, fraud prevention, legal, billing, or service-operation needs, or may be de-linked from your account. To ask us to review or delete account or remaining PrimeBite-controlled records, email primebitefishing@gmail.com with the subject "Delete my PrimeBite data." Include the account email or sign-in method if available, and say whether you want the account, remaining records, or both reviewed. We may ask for a reasonable identity check before deleting account-linked records.

How Long We Keep Data

Different records have different lifetimes. This is what we do today.

Local Logbook Data: Stays on your phone with no expiry date. It is removed from the phone when you delete the entries yourself or uninstall the app. On iPhone, an iCloud or computer backup you keep may still contain earlier copies until that backup is replaced or deleted. We cannot delete your phone data or those backups for you because we do not hold them.
Local Logbook Recovery Copies: Unreferenced temporary or active recovery files wait at least 24 hours and a fully clean app start. Legacy-upgrade snapshots wait until recovery is resolved, three different clean starts have passed, and they are at least seven days old. Escaped newer-format and old raw quarantines wait for three different clean starts and at least 30 days. An uncertain cleanup keeps the copy and retries later. Deleting a catch or trip purges retained recovery copies that could contain it.
Optional Account And Account-Side Logbook Copies: Kept while the account exists. Using Delete Account in the app is designed to remove them.
Local Account-Deletion Recovery And Warning Records: Kept on your device while needed to handle an interrupted request, protect cleanup, or show an outcome warning, as explained under Optional Accounts. There is no blanket 30-day deletion promise for these local records. Some may remain until the unresolved recovery is closed, and secure storage may survive uninstall.
Feedback, Cancellation Survey, In-App Event, And Push Token Records: Feedback and cancellation records become eligible for deletion after 730 days, feedback photos after 90 days, and in-app events after 395 days. Invalid or opted-out inactive push-token records become eligible after 30 days, and all inactive push-token records after 180 days. Unreferenced feedback uploads have a one-day retry window before cleanup. Scheduled cleanup removes eligible records; actual removal can occur later if a job is delayed or fails. App-generated feedback, digest, and cancellation email copies are reviewed quarterly for removal after 730 days. Provider-held copies and logs follow the providers’ own rules.
Website Request Logs: Held by Netlify and normal internet systems on their own schedules, not ours.

Companies we rely on — Apple, Google, RevenueCat, Supabase, Netlify, and Resend — keep their own records under their own policies and retention periods. We do not control those.

To ask us to review or delete records we still hold, email primebitefishing@gmail.com with the subject "Delete my PrimeBite data." We will update this section if these schedules change.

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. If you use optional account sign-in, limited auth/profile and synced preference data is handled off-device by the account providers used for sign-in. Treat clipboard exports carefully because an exact export may include private fishing locations.

Data Breach Notification

If we learn that personal information we hold has been exposed, taken, or misused, we will investigate it, take steps to limit the harm, and notify people and regulators as applicable law requires.

Where we have your account or reply email, we will contact you there. Where we do not, we will post notice on this page and, when we can, inside the app.

Our notice will tell you what we actually know: which kinds of data were involved, what happened as best we understand it, what we have done about it, and what you can do next. Most of your Logbook stays on your device by default, so a problem on our side would usually reach account, feedback, or subscription records rather than your local catches and photos.

If you think you have found a security problem or a leak of PrimeBite data, tell us at primebitefishing@gmail.com with the subject "PrimeBite security report."

International Processing

PrimeBite is based in the United States. Our service providers may process information in the United States or other countries where they operate. Local privacy rights may still apply based on where you live. Contact us to ask about or use those rights.

Contact

Questions or requests for PrimeBite LLC? Email primebitefishing@gmail.com.