Privacy

Daniel Ehrensperger
P.O. Box
3013 Bern
Switzerland
dev@nauticcalc.com

Website

Hosting: The website is hosted by Vercel Inc. (USA). When you access it, technically necessary connection data are processed so the page can be delivered. For reach measurement on the website we use Vercel Web Analytics (anonymised, privacy-friendly statistics without classic cookie-based tracking).

Server logs: When you visit, limited technical information may be processed temporarily, such as IP address (possibly truncated), timestamp, requested URL, user agent and referrer. This supports stability, operational security and server-side error analysis.

Cookies and local storage: For your selected website language, next-intl sets a cookie (locale storage). For light/dark appearance the site uses next-themes and typically stores the setting in your browser’s local storage. You can also choose “System”; then the UI follows your device or browser light/dark setting.

Contact: If you contact us by email, we process the data you send (e.g. sender address and message content) to handle your request.

App (iOS / iPadOS)

The following applies to the iOS/iPadOS app. The anchor #app makes it easier to link from the App Store or support.

Data stored locally in the app

NauticCalc is built on an “offline-first” approach. Log entries, trips, crew, calculator settings and deviation tables are kept only in local app storage. This content is not transmitted to our servers and is not analysed by us.

Crew data: may include sensitive contact and ID details. In the app you can optionally mask such data in the UI and choose on PDF export whether crew entries are included or masked.

iCloud backup: If you have enabled iCloud Backup for the device, local app data (logbook, trips, crew, settings) may be included in Apple’s backups — subject to Apple’s privacy terms. You can manage backup per app in iOS Settings (Apple ID → iCloud → Manage Storage).

Deleting data: You can remove all locally stored app data by uninstalling the app from your device.

Location data (GPS)

The device location service is used for:

• Automatic logbook: recording position, course and speed during a trip
• Anchor watch: monitoring anchor position and local alerts on deviation

This may require location access in the background. Location data are stored locally on the device and are not transmitted to us.

If you enable optional weather or tide services with your own API key, coordinates may be sent to the respective third-party provider for queries (see table below).

Optional third-party APIs

Weather, marine and tide services are optional and require your own API key. The app then talks directly to each provider:

The respective providers’ privacy notices apply. API keys are stored in the iOS Keychain and are not readable by us.

Push notifications

There are only local notifications for anchor watch. No marketing push; no delivery via our servers.

Security

• Sensitive keys are stored in the iOS Keychain
• Your navigation content stays on the device
• Crash reports do not contain personal logbook content

Children

NauticCalc is aimed at adult users. We do not knowingly collect data from children under 13.

Disclosure and processors (overview)

Personal data from the app are not transmitted to us as a central user record. Technical transmissions mainly concern Google Firebase (Analytics, Crashlytics, Remote Config; see below) and — only when you optionally use them — the weather/tide API providers you choose.

For website hosting and reach measurement, the information under “Website” above applies.

Retention (overview)

Website: Server logs at the host are deleted or anonymised within usual, limited periods.

App: Your content remains until you delete it in the app or remove the app. Firebase data are subject to Google’s retention and deletion rules for Analytics and Crashlytics (aggregated or technically limited).

Firebase Analytics

Firebase Analytics (Google LLC, USA) collects aggregated usage events, e.g.:

• Calculators and tools used
• Logbook and trip actions (without readable content)
• In-app navigation
• Settings such as language and appearance
• Technical error indicators

We do not collect names, email addresses or directly identifying personal data for advertising purposes. Processing may take place in the USA; Google is certified under the EU-US Data Privacy Framework.

Restriction: On iOS you can limit tracking in Settings under Privacy & Security → Tracking.

Legal basis (EU): legitimate interests in improving the app (Art. 6(1)(f) GDPR).

Firebase Crashlytics

When the app crashes, technical reports are sent (device type, iOS and app version, stack trace, app state). Logbook text and GPS tracks are not included.

Legal basis (EU): legitimate interests in fixing errors (Art. 6(1)(f) GDPR).

Firebase Remote Config

With Remote Config we can adjust technical parameters and feature switches remotely (e.g. safety-related limits or gradual feature rollouts). No content from your logbook or personal entries is transmitted.

App: Providing app features on the device (navigation, logbook, alarms), optional live data via providers you choose.

Firebase: Stability, error analysis, product improvement and technical configuration — without ad profiles and without selling personal data.

• Access to personal data we process
• Rectification of inaccurate data
• Erasure or restriction of processing
• Objection to processing based on legitimate interests
• Complaint to a data protection authority

You control logbook and navigation content directly on the device. For questions about Firebase-related processing you can reach us at the email address below.

dev@nauticcalc.com