Dorado Division Sport
This policy describes exactly what the app does with information. It is short because the app does very little.
Effective 11 September 2026 · Version 1.1
Dorado Division Sport is a single-player sport-fishing game for iPhone and iPad. For the purposes of this policy “we”, “us” and “the app” refer to the developer of Dorado Division Sport. Because the app never sends data off your device, we never become a controller or processor of your personal data in the ordinary sense — the data simply stays with you.
All of the following is written inside the app's own private container on your device and is never uploaded, shared or backed up to us:
| Data | What it is | Where it lives |
|---|---|---|
| Ledger | Catches with species, weight, length, fight duration, basin and conditions; contract progress; crests; tackle owned; division standing; wallet balance; weigh-in streak. | JSON file in the app's Application Support directory |
| Photographs | Pictures you take with the camera or choose from your library for trophy plates and your angler portrait, compressed to JPEG. | Private files in the app's Application Support directory |
| Preferences | Music, sound effects and haptics toggles, fight-assist level and the reduced-flourish setting. | UserDefaults for this app only |
None of this is tied to your name, email address, Apple ID or any other identifier. The app never asks who you are.
Every permission is optional, asked in context at the moment you first use the feature, and the app works without any of them.
Used only to photograph a catch or an angler portrait so the app can compose it onto a trophy plate. The image is written straight to the app's private container. It is never sent anywhere and no image analysis of any kind is performed.
Used only to let you pick an existing picture for a trophy plate or your portrait. The app reads the single image you select and nothing else. It does not enumerate, scan or index your library.
Requested only at the moment you tap “Save a copy to Photos” on a finished trophy plate, so the rendered image can be written back to your library.
Apple requires apps to declare why they use certain APIs. The app ships a privacy manifest (PrivacyInfo.xcprivacy) declaring the two categories below, with NSPrivacyTracking set to false, an empty tracking-domain list and an empty collected-data-types list. Nothing else is declared because nothing else is touched:
| API category | Reason code | Why |
|---|---|---|
| User defaults | CA92.1 | Reading and writing this app's own settings. |
| System boot time | 35F9.1 | The display-link clock that times a fight. |
The app links no third-party SDKs. Its only external ingredients are bundled creative assets: compressed audio from royalty-free libraries and the Barlow typeface family under the SIL Open Font License. None of these run code, make requests or receive data.
The app carries no advertising, no in-app purchases, no chat and no user-generated content visible to anyone else. Because nothing is collected or transmitted, there is no personal information gathered from any user, of any age. The app is not directed at children under 13 specifically, but it is equally safe for them.
Under the GDPR, the UK GDPR, the CCPA/CPRA and similar laws you have rights of access, correction, deletion, portability and objection. Since the app holds no personal data about you outside your own device, every one of these rights is exercised directly by you, on your device, using the controls above. If you still wish to make a request or ask a question, you can do so through the support page and we will respond.
The app itself never contacts us. If you choose to write to us through the support page, we receive the email address you type, the reason you select and the text of your message. We use them only to reply to you and to fix whatever you reported, keep them no longer than needed to close the matter, and never add them to a mailing list or pass them to anyone else.
If a future version ever collects anything, this policy will be updated before that version ships and the change will be described in the release notes. The effective date at the top of this page always reflects the current version. Questions about this policy can be sent through the support page.