StrikeSage Privacy Policy
Last updated: September 10, 2026
This Privacy Policy explains what information StrikeSage: Fishing Diary ("StrikeSage," "we," "our," "the app") collects, how it is used, and the choices available to you.
Information We Collect
Account information
When you sign in with Apple or Google, we store basic account information — including your email address — in our database, associated with your account.
Fishing log data
StrikeSage stores the information you choose to record: catches, missed bites, and no-catch sessions, including species, technique, lure/bait details, weather conditions at the time, location, and notes, and (for catches) weight and length. This data is stored in our database (Google Firebase / Firestore).
Photos
If you add a photo of a fish or a lure to an entry, that photo is uploaded to and stored in our cloud storage (Google Firebase Storage), associated with your account.
Location data
With your permission, StrikeSage accesses your device's GPS location to record where a fishing session took place. If a photo you add already contains location data, that location may also be read from the photo. The coordinates of a fishing session are also sent, on their own, to our weather data provider (Open-Meteo) to retrieve weather conditions for that location — this request does not include your account information.
Subscription information
If you purchase a Pro or Elite subscription, the purchase is processed by Apple's or Google's in-app purchase system. We receive and store only the resulting product identifier and subscription status — we never receive your payment card details.
Third-Party Services We Use
- Google Firebase (Authentication, Firestore, Cloud Storage) — account sign-in and storage of your fishing log data and photos.
- Open-Meteo — the coordinates of a fishing session are sent to retrieve weather data for that location. This request contains only coordinates, not any account information.
- Apple / Google — for sign-in and for processing subscription purchases.
What We Don't Do
- We do not use analytics SDKs.
- We do not use crash-reporting SDKs.
- We do not use advertising networks.
- We do not sell your personal information.
How We Use Your Information
We use this information solely to operate the app's features: storing your fishing history, generating statistics and patterns from your own data, providing weather context, and automatically detecting tactical details (such as lure type, depth, or retrieve style) from your notes directly on your device.
Your Choices
Local backup: you can export a local backup of your data — including your catches, misses, no-catch sessions, their notes and locations, and fish/lure photos — at any time from within the app, and re-import it later. This is a manual, local action and does not involve our servers. Once you have exported and saved or shared a backup file outside the app, that file is outside our control and this policy does not apply to it.
Account deletion: you can delete your account directly from within the app (Profile → Delete Account). Before anything is deleted, you'll be asked to re-authenticate for security — if that's cancelled or fails, nothing is deleted. Once it succeeds, this removes your account and your fishing log data — including your catches, misses, no-catch sessions, subscription and reward records, and photos — from our servers. This action is irreversible. It does not cancel an Apple App Store or Google Play subscription, which must be cancelled separately in your Apple ID or Google Play account settings. Backup files you have already exported and saved or shared outside the app are not affected. See our account deletion page for full details, including how to request deletion if you can't sign in to the app.
Data Security
Your data is stored using Google Firebase infrastructure. No method of electronic storage or transmission is 100% secure, and we cannot guarantee absolute security.
Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above.