Privacy Policy — Desta

Last updated: 26 September 2026

Who is responsible

Desta is operated by Dinzel IT d.o.o., full registered name Dinzel IT društvo s ograničenom odgovornošću za računalne djelatnosti i usluge, Ulica Lea Müllera 43, 10090 Zagreb, Croatia, OIB 94890617087. We are the controller for personal data we use to operate Desta. Contact dinz@dinzzz.com, or write to that address, for support and privacy requests.

Information we process

Passage records, active anchor/return positions and some preferences are stored locally. Legacy position-marker data from earlier versions is also local; updated builds remove the retired marker. Local files and device backups are separate from server-side account data.

Purposes and legal bases

We process data to deliver requested features, authenticate accounts, sync preferences, verify purchases, provide support and protect the service. Where GDPR applies, we rely on contract for processing objectively necessary to provide the requested service, legitimate interests for proportionate security/abuse prevention and legal claims, and applicable legal obligations for statutory records and requests. Optional crash-report sharing relies on consent in versions offering that choice. Device access and other optional processing require consent where applicable law requires it.

Location permission is not permission for unrelated advertising. We do not sell your personal data to data brokers, use it for targeted advertising or track you across other apps for advertising. No advertising network is included in Desta.

Your controls

You can select a place without allowing device location. Denying or limiting location disables features that need an accurate position. Stop an active passage or anchor watch when it is no longer needed. Manage location and notification permissions in iOS Settings.

In versions with Settings → Privacy → Share crash reports, reporting is off by default. Enabling it allows reports from use after that choice to be sent on a later launch while it remains enabled. Turning it off prevents future app-initiated uploads and discards pending reports; it does not recall reports already sent. The SDK may keep local crash information until a later cleanup. Earlier versions without this control initialize automatic crash reporting; their behaviour differs from the updated opt-in implementation.

Providers and recipients

We use Railway for backend hosting, Google Firebase for crash diagnostics, Resend for account emails, Apple/Google for your chosen sign-in provider, and Apple for App Store purchases, push delivery, maps/geocoding and WeatherKit. Open-Meteo provides weather and marine forecasts, WorldTides provides tide predictions, and MeteoAlarm supplies Croatian warnings. Squall watch requests RainViewer radar information directly from the device. Build 9 used an Open-Meteo precipitation outlook; subsequent builds restore RainViewer.

Some requests pass through our backend; others go directly from the device. A direct recipient can receive your network address and request information. Providers act as processors where they operate on our instructions, and may independently control parts of their own services under their privacy policies. We may also disclose information where necessary to comply with law, establish or defend legal claims, or protect rights. A corporate transfer remains subject to applicable privacy and notice requirements.

International processing

Some providers process information outside Croatia and the EEA, including in the United States. The applicable transfer arrangement depends on the provider, service and receiving entity; an EEA hosting region alone does not determine all processing locations. Contact us for the recipients, relevant adequacy arrangements or contractual safeguards and how to obtain information about safeguards applicable to your data. Your rights under applicable transfer rules remain unaffected.

Retention

Account and synced preference data normally remain while your account is active, until replaced or deleted. Valid account-deletion requests remove associated active application records, subject to specific legal retention duties. We do not retain a whole account indefinitely simply because a particular record is needed for a claim.

Our updated backend runs daily cleanup for verification/reset challenges more than one day past expiry, refresh-session records more than 30 days past expiry, alert-event records older than 30 days, and Apple notification-processing records older than 90 days. Cleanup resumes after an interrupted maintenance run. These periods do not extend a token's validity and do not describe Apple's independent transaction records.

Written consumer-complaint records are retained for the statutory one-year period. Purchase, accounting and claim records are retained to meet the specific applicable obligation or resolve the relevant dispute, with access limited accordingly. General support records are retained as needed to resolve the issue and any related claim. Technical logs and backup copies have separate provider/backup lifecycles; deletion from the live application is not a promise that every backup copy disappears immediately. Retained backup copies are for recovery and must not be used to restore deleted accounts into ordinary service.

Firebase describes retaining relevant crash information and associated identifiers for 90 days before starting removal from live and backup systems. This is not a guarantee of complete erasure on day 90. Firebase retention information.

Local records remain subject to the app's controls and your device/backup settings. Uninstalling does not delete your server account or Apple's purchase records.

Account deletion and your rights

Use the account-deletion control in Desta Settings, or email us if you cannot access it or it fails. Account deletion does not cancel an App Store subscription; manage billing separately in your Apple subscription settings. You may request deletion while a subscription remains active. Contact us if account deletion affects restoring paid access.

Depending on applicable law, you may request access, correction, deletion, restriction, objection, and a portable copy of relevant data. You may withdraw consent without affecting earlier lawful processing. We verify identity proportionately and respond within the applicable deadline—normally one month for GDPR requests, with lawful extensions explained where needed. Email dinz@dinzzz.com. You may complain directly to AZOP or another competent supervisory authority.

We do not use solely automated decisions intended to produce legal or similarly significant effects about you. Forecast scores and automated entitlement checks support the service; contact us to question an account or purchase decision.

Children, security and changes

Desta is a general boating service, not designed for children. A store content rating is not proof of a child's ability to consent or enter a contract. Where parental authorization is legally required, it must be obtained. Contact us if you believe a child's information has been provided without the required authorization.

We use safeguards appropriate to the information and risk, including encrypted network connections and restricted access. No system is completely secure. We will provide appropriate notice of material policy changes; publishing a new policy does not obtain consent for a new optional purpose.