Introduction
BiteRadar is operated by Jeremiasz Grodzicki, Polish tax identification number (NIP) 8421782665 ("we," "our," or "us"). This Privacy Policy explains what data is accessed, collected, and processed while using the BiteRadar mobile application and related backend services.
Important: BiteRadar does not sell personal data and does not use location, catch, session, or account data for advertising or cross-app tracking. Location access is optional and used only when you choose a place, tap the "use my location" button, or use a feature that needs your fishing location.
Data We Access or Process
Location for forecasts. BiteRadar lets you select a fishing location by searching, tapping the map, or using your device location with your permission. When you use device location, the app requests foreground location access only. BiteRadar does not request background location access and does not continuously track your location.
The selected coordinates or place name are sent to BiteRadar's backend to provide fishing forecasts and reverse geocoding results. This location data is used for app functionality and is not used for advertising or tracking.
Account and authentication data. BiteRadar uses Firebase Authentication and may create an anonymous guest account when you start using online features. You can sign in with Google or Apple. We process account and provider identifiers and basic information provided by the sign-in provider, such as an email address when available. A guest account is still an account even if you have not supplied an email address.
Saved locations. Saved fishing locations and changes to them are synchronized with the active account. This includes the coordinates and associated location information needed to show your saved places and their forecasts. Account switching changes the saved-location data available to the app.
Local catch log and preferences. Catch entries, measurements, tags, personal records, attached photos, and saved forecast context are currently stored on your device. Favorite species and device preferences are also stored locally. Signing in does not provide cloud backup or cross-device restoration of catches, photos, or favorite species.
Photos and sharing. Catch photos are optional and are not uploaded to BiteRadar as a photo backup. The app processes them locally to display your log and create catch-sharing cards. If you choose to share a card, it is passed to the destination you select through your device's sharing tools, subject to that destination's own privacy practices.
Catch analytics and contributions. The app sends catch events to our backend to improve forecasts and feature reliability. These can include an installation identifier, catch and fishing-session identifiers where present, species, catch time, length, weight, tags, the number of attached photos, related forecast or fishing-water identifiers, app version, and operating system. Related forecast information can provide location context. Catch events do not contain the photos themselves or free-text notes and are not a restorable catch-log backup. We also process forecast ratings, votes, feedback, review answers, and species suggestions that you submit.
Notifications. Fishing reminders can be scheduled on your device with your permission. Where messaging registration is enabled, we process a device messaging token and installation and account identifiers to maintain the correct notification registration. Registration is separate from your locally scheduled reminders.
App usage and diagnostics. BiteRadar may use analytics, crash reporting, remote configuration, and messaging services to understand product usage, diagnose crashes, improve reliability, and configure app behavior. These services may process technical information such as device type, app version, operating system, crash logs, performance data, and product interaction events.
Purchases. If you buy or restore a subscription, the purchase is handled by Apple App Store or Google Play. BiteRadar may process subscription status information needed to unlock paid features, but we do not receive your full payment card details.
Data Usage
We use data to provide and improve BiteRadar, including generating fishing forecasts, showing place names for coordinates, saving preferences, synchronizing saved locations, handling account and subscription access, processing your feedback, maintaining notification registrations, detecting crashes, and improving forecast models and app reliability. We do not sell your personal data.
Server requests may generate operational logs such as IP address, request time, endpoint, and error information. These logs are used for security, debugging, and service reliability.
Third-Party Services
Our app uses the following third-party services:
- Weather and geocoding services: To provide weather, fishing condition forecasts, place search, and reverse geocoding based on the selected location.
- Firebase services: For authentication, analytics, crash reporting, remote configuration, and cloud messaging where enabled.
- Apple App Store and Google Play: To process subscriptions, purchases, and restores.
- Backend hosting and database providers: To operate the API and store account data, saved locations, contributions, and analytics described above.
Security
We use encrypted network connections where available and design API requests to avoid collecting unnecessary information. Access to operational systems is limited to what is needed to run and maintain the service.
Data Retention and Deletion
Forecast and location requests are processed to provide the requested app functionality. Operational logs may be retained for a limited period for security, debugging, and service reliability.
You can delete guest and signed-in accounts from the app's account controls or request help using our Account & Data Deletion page. Accepted deletion blocks normal account access and removes private saved locations, owned feedback and species suggestions, remote notification registrations, and active account subscription assignments. Identity-provider cleanup is completed in the background. This does not cancel an Apple or Google subscription.
Deletion does not automatically erase all contributions: votes, forecast ratings, and non-text review answers retain their internal contribution identifier. Installation-based catch analytics are separate from account identity and remain after account deletion; we do not describe these records as fully anonymous. Historical contributions that were not associated with an account may also remain. Review free text and associated metadata are cleared for the deleted account. Limited security and transaction records may be retained as necessary. Contact us about personal-data access or erasure beyond the automatic account-deletion process; we will assess the request under applicable law.
Device-local catches, photos, and favorites remain after account deletion or switching. Remove local entries, clear app storage, or delete the app to remove local-only data; any copies you previously shared or stored outside the app must be managed separately.
Your Choices
You can deny or revoke location and notification permissions in your device settings. You can still select a place by search or on the map without device-location access. You choose whether to attach or share photos, save locations, or sign in with Apple or Google. Analytics controls, where offered by the app or platform, apply to the collection identified by that control and do not necessarily disable separate catch-event processing. Contact us with requests concerning your personal data.
Changes to This Policy
We may update this Privacy Policy periodically. We will notify users of significant changes by updating this page and the "Last updated" date.
Contact Us
If you have questions about this Privacy Policy, contact us at:
Email: onionsoftcontact@gmail.com
This page was updated on September 23, 2026 to describe current account, local-storage, synchronization, and deletion behavior.