Privacy Policy
The short version
- No account, no sign-up, no password. You can use every feature anonymously.
- Your catches, photos, notes and scores are stored on your device only.
- Fish photo identification runs on the device. Photos are never uploaded.
- No advertising, no analytics SDK, no tracking across apps or websites.
- Two things do leave the app: a push token and an install identifier for notifications (section 3), and whatever you type into the support form.
01Who this policy covers
This policy explains how the Dorado Sport Fishing mobile app for iPhone and iPad ("the app") handles your information. It applies to the app and to this website. It does not apply to any other app, website or service you may reach from here.
By using the app you agree to this policy. If you disagree with any part of it, please stop using the app and remove it from your device.
02Information stored on your device
The app is built to work offline. Everything you create is written to your device's private app storage and stays there. We have no server holding your fishing data, and we cannot read it.
| What | Why it is stored |
|---|---|
| Catch log entries โ species, weight, length, date, notes | So your catch history and statistics persist between sessions |
| Photos you attach to a catch or add to the gallery | To show them in your catch log and photo gallery |
| Display name and short bio | To personalise your in-app profile screen |
| Favourite species and favourite spots | To keep your bookmarks |
| Quiz high scores | To track your best result per category |
| Settings โ notification toggle, reminder hour, onboarding state | To remember your preferences |
None of the above is transmitted anywhere. If your device has iCloud or an encrypted device backup enabled, this data may be included in that backup under Apple's terms โ we have no access to it.
03Information sent to our servers
Push notification registration. When the app first opens it registers for push notifications. That registration sends two values to our server:
- A push token โ issued by Apple and Google's messaging service, this is the address a notification is delivered to. It is specific to this app on this device, it is not your Apple ID, and it changes by itself from time to time.
- An install identifier โ a random code the app generates for itself the first time it runs, stored in the device keychain. Its only job is to recognise this installation so we do not send you the same notification twice. It is not derived from your device's serial number, advertising identifier or any other hardware id, it is not shared with other apps, and it is not joined to any profile about you.
Be aware: this registration runs when the app opens, whether or not you allow notifications. Allowing notifications controls whether messages are actually delivered to you โ it does not control whether the pair above is sent. If you would rather it were not held at all, ask us to delete it (section 11) or remove the app.
The pair is used only to deliver notifications about the app, and to avoid duplicate sends. It is not used to build a profile, not sold, not rented, and not shared with third parties for their own purposes. It is not combined with data from other companies, so it is not used to track you in the sense the App Store uses that word.
The support form. When you choose to submit it, we receive exactly what you filled in:
- Name โ so we can address you in the reply.
- Device โ so we can reproduce the problem on the right hardware and OS version.
- Email address โ so we can send you an answer.
- Your question โ the message itself, plus anything you choose to include in it.
Alongside these we record the app version, the platform, and the time of submission, so that a report can be matched to the right build.
This information is used only to answer your request and to fix the issue you reported. It is not used for marketing, it is not added to a mailing list, and it is not sold, rented or shared with third parties for their own purposes. Please do not include sensitive personal information in the message field โ a support request does not need it.
04Camera and photo library
The app asks for camera access when you photograph a catch, and for photo library access when you pick an existing photo or save one. iOS shows these prompts the first time, and you can change your answer at any time in Settings โ Privacy & Security on your device.
Photos you select are saved into the app's own storage so they can appear in your catch log and gallery. They are not uploaded, not backed up to us, and not shared with anyone. The app does not read your photo library in the background โ only the images you actively choose.
Declining camera or photo access does not lock you out: you can still log catches without a photo, and every other feature keeps working.
05Fish identification
When you ask the app to identify a fish from a photo, the analysis runs entirely on your device using Apple's built-in image classification framework. The image is processed locally, matched against the species reference list bundled inside the app, and the result is shown to you. Nothing is sent to a server, and no copy of the image is retained outside the app's own storage.
Identification is a convenience feature and can be wrong. Do not rely on it for decisions about catch legality, protected species, or whether a fish is safe to eat.
06Notifications and Firebase
The app uses two different kinds of notification:
- Local reminders โ the daily "time to fish" reminder at the hour you pick. These are created and delivered by iOS on your device. Nothing is sent anywhere for them.
- Push messages โ sent by us, about the app. These need the push token described in section 3.
To deliver push messages the app includes Firebase Cloud Messaging, a Google software component. It is the only Firebase product in the app โ there is no Firebase Analytics, no Crashlytics, and no advertising component. To issue and refresh a push token, Firebase Cloud Messaging communicates with Google's servers, and in doing so Google receives technical information about the device and the app instance. That processing is governed by Google's Firebase privacy documentation.
You can turn the daily reminder off inside the app's settings screen, and revoke notification permission entirely in iOS Settings. Revoking permission stops messages from being displayed; to also have the stored token and install identifier deleted, see section 11.
07Location
The current version of the app does not collect, request or store your location. The fishing spots in the encyclopedia are a fixed reference list bundled with the app, not results based on where you are.
If a future version introduces location-based features, it will ask for your permission first through the standard iOS prompt, and this policy will be updated before that version ships.
08What we do not do
- We do not sell or rent your personal information. Ever.
- We do not show advertising and we do not embed advertising SDKs.
- We do not track you across other apps or websites, and we do not ask for the App Tracking Transparency permission.
- We do not join the install identifier to data from any other company, and we do not use it to build an advertising profile.
- We do not collect your device's advertising identifier (IDFA), serial number or phone number.
- We do not embed an analytics or crash-reporting SDK.
- We do not use cookies for tracking on this website.
- We do not require an account, and we do not collect contact lists, calendars, health data, or microphone input.
09Legal bases for processing
For users in the European Economic Area and the United Kingdom, the limited processing described in section 3 rests on these legal bases under the GDPR:
- Consent โ you decide whether to submit the support form; nothing is sent unless you press send.
- Legitimate interests โ responding to your request and diagnosing app defects so the app works correctly for everyone; and registering the device so the app's notification feature can function without duplicate sends.
You can object to the notification registration at any time by asking us to delete the token and install identifier (section 11), or by removing the app.
Data kept on your device is not processed by us at all, because we never receive it.
10How long information is kept
- On your device โ for as long as you keep the app installed. Deleting the app removes it.
- Push token and install identifier โ kept while the installation is active, so notifications can reach it. A token that Apple or Google reports as no longer valid is discarded, and a record with no activity is removed. Ask us and we will delete it sooner.
- Support messages โ kept only as long as needed to resolve your request and to recognise repeat reports of the same defect, then deleted.
11Your choices and rights
You are always in control:
- Delete individual entries โ swipe to remove any catch or photo inside the app.
- Delete everything โ uninstalling the app erases all locally stored data. This cannot be undone, so export or back up anything you want to keep first.
- Change permissions โ camera, photos and notification access can be granted or revoked at any time in iOS Settings.
- Delete your push registration โ removing the app deletes the install identifier from your device and stops any further notifications. To have the stored token and install identifier erased from our side as well, ask through the support page.
- Access, correction, erasure, restriction, objection and portability โ for the push registration and for anything you sent through the support form, you can ask us to show it to you, correct it or delete it. Send that request through the support page and we will act on it.
Depending on where you live, you may also have the right to lodge a complaint with your local data protection authority.
12Children
The app is a general-audience fishing companion and is not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has sent us personal information through the support form, contact us and we will delete it.
13Security
Data the app stores lives in its private container, protected by the sandboxing and file encryption iOS provides โ keeping a passcode or biometric lock on your device is the single most effective protection for it. The install identifier is held in the device keychain, marked so that it is never carried into an iCloud backup. Support submissions and the push registration are sent over an encrypted connection.
No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security, but we keep the amount of information we handle to the minimum the app needs.
14Changes to this policy
This policy may be updated when the app changes or when the law requires it. The effective date at the top of the page always shows the current version. Material changes โ for example a new category of information being collected โ will be announced in the app before they take effect. Continuing to use the app after an update means you accept the revised policy.
15Contact
Questions about this policy, or a request about your information? Use the support page โ it reaches the people who maintain the app directly, and it is the fastest way to get an answer.
Still have a question?
Send it to us and we'll reply to the email address you provide.
Contact Support