Underway Privacy Policy

About this policy

Antoine Meunier provides the Underway app for Android and iOS. This policy explains how the app handles your information. Contact support@underwayboating.com for questions or privacy requests. Website privacy is described separately at underwayboating.com/privacy/website/.

Your logbook and location

Journeys, tracks, times, totals, notes, summaries, boat details, saved places and settings are stored in the app’s private storage. Recording, review, editing and GPX export work offline. Maps and marine information depend on available downloads or cached data.

Public journeys start when you tap Start journey and can continue with the screen locked. You can end them manually or disable automatic ending. Public builds request foreground location permission. Experimental departure watching may request separate background permission. Granting location permission does not by itself upload your track.

Accounts, cloud backup and optional automatic-journey sharing are not available in current public builds. We will explain new collection and any required choices before enabling those features.

Maps, geography and marine information

The app downloads nearby geography and place-name data for offline use. Cloudflare and Supabase receive the requested broad area and ordinary network information, including your IP address. These requests do not include your raw track, notes or installation identifier. Where geography download reporting is enabled, we count downloaded areas or requests to understand coverage and demand; those reports do not identify individual installations.

Mapbox receives requests for map areas viewed or downloaded for offline use, including automatic nearby downloads. We draw your track on the device rather than sending it to Mapbox. Downloads may use Wi-Fi or mobile data.

Marine forecasts may send an area or forecast point to Environment and Climate Change Canada. Current-wind requests send the requested latitude and longitude to Open-Meteo. Shared tide and current data comes from Supabase. These services may also receive your IP address and other network information. We do not send your saved journey or track with these requests.

Updates and notifications

Expo receives an installation identifier, app and update information, network information and update errors when checking for or downloading software updates. The app also requests shared release announcements from Supabase and release notes from our website. Those shared requests contain no app-supplied installation identifier or journey data.

If you enable marine-warning notifications, our service stores a push token and your selected forecast area in Supabase in Canada. Expo and the platform notification providers, Google FCM or Apple APNs, process the information needed to deliver warnings. The registration does not include your GPS position or journey track. Turning warnings off deletes the registration.

AI summary drafts

AI summary drafts are optional and off until you enable them in Settings › Privacy. When enabled, the app sends a short journey digest through our Supabase service to Anthropic. The digest includes dates, start and end times, place names, distance, duration and other journey totals. It excludes raw coordinates, track points, notes and boat names.

Recorded journeys with no summary may be processed after recording ends or when the app opens. Where imported journeys are supported, their summary request starts when you open the journey. Our summary function does not retain the digest or response; Anthropic handles requests under its applicable service and retention terms. The returned draft is stored on your device, and your edits take priority.

You can turn summary drafting off in Settings › Privacy to stop new requests. Requests already sent cannot be recalled; existing summaries remain in your local logbook.

Purchases and subscription information

The app uses RevenueCat to check paid access, offer plans and restore eligible purchases. It may connect when the app opens, before you buy anything. RevenueCat processes a generated purchase identifier, app and device information, network information, store receipts or purchase tokens, and purchase, trial, renewal and access status. RevenueCat processes this information in the United States for purchase validation, access, fraud prevention and subscription reporting.

Apple or Google handles your payment details. We do not receive your payment-card details or supply RevenueCat with your name, email or journey data. Restoring a purchase restores eligible paid access, not your local logbook. Deleting the app does not cancel a subscription.

RevenueCat may also send purchase and subscription events to PostHog in the United States for subscription analysis. These can include product and transaction identifiers, dates, amounts, currency and subscription status, including renewals, cancellations and refunds. This separate server-side reporting can occur while the app is closed and uses the purchase identifier, not the app’s analytics identifier.

App analytics and crash diagnostics

App analytics and crash reports are on by default. You can turn them off in Settings › Privacy. We use PostHog to understand feature use and investigate recording problems. Data can include app and device information, app activity, permission and recording settings, onboarding choices, journey counts, rounded journey distance and duration, recording outcomes, and crash diagnostics. Boat and berth information is limited to categories; it excludes entered names and saved locations. Existing recorded journeys may be included once after an update. Imported and discarded journeys do not send per-journey observations, although imports are included in current logbook counts.

The app creates random installation and boat labels that are not based on your name or the boat name you enter. Before sending app analytics and crash events, it filters out coordinates, tracks, place names, notes, summaries, journey identifiers, and journey dates and start/end times. Screen and touch tracking, session replay and console capture are disabled.

Events retain their capture time and a persistent installation identifier, so the records are pseudonymous rather than anonymous. PostHog derives approximate geography from the upload connection’s IP address, then discards the raw IP from stored app events. This can differ from where a journey took place. App analytics are processed in the United States.

You can turn app analytics and crash reports off in Settings › Privacy to stop app analytics and crash uploads. This does not delete information already transmitted. Purchase-service reporting is a separate path described above. Contact us for privacy requests.

Problem reports

If you send a problem report, it includes your five most recent journeys and tracks, boat details, and diagnostic information about the app and device. This can include precise locations, notes and summaries. The report sheet lists what will be sent before you tap Send. Older versions may include the full logbook, as described on their report sheet.

Reports also include installation and generated analytics identifiers to help us investigate the issue. They are sent to Supabase in Canada only when you tap Send. A new report replaces the previous report for that installation. Reports are diagnostic copies, not a backup or restoration service.

Service providers and international processing

Our service providers include Cloudflare, Mapbox, Environment and Climate Change Canada and Open-Meteo for geographic or marine information; Supabase in Canada for backend services; Anthropic for AI summaries; RevenueCat and PostHog in the United States for purchases, analytics and diagnostics; Apple and Google for store purchases; and Expo, Google FCM and Apple APNs for updates or notifications. Our website host also receives ordinary request information when delivering release notes.

Providers may process network information such as IP addresses to operate and secure their services. Information may be processed outside your country and be subject to the laws of that country. We do not use these requests to create an advertising profile.

Retention and deletion

Local information remains until you edit or delete it, reset the app, or uninstall it, subject to your device’s backup and storage behavior. Copies you export are controlled by the destination you choose.

Warning registrations are removed when disabled, invalid, or inactive for 90 days; delivery receipts are removed after 24 hours. Problem reports are retained while the issue is investigated, then deleted. Our summary function does not store summary requests or responses; providers may retain their own service records under their applicable terms.

We do not currently schedule automatic deletion of PostHog analytics events, purchase records or aggregate geography-download statistics. We review what remains necessary at major releases. A provider’s limit on query history does not establish deletion. Legal requirements may also affect how long purchase records are retained.

Deleting a journey, deleting all local data or uninstalling does not automatically remove previously transmitted analytics, purchases, exports or provider records. Delete all data resets the app’s installation identity, but does not reset Expo’s separate update identifier. Contact us to request deletion of information we can identify; provider and legal requirements may affect what can be removed.

Your choices and privacy requests

In Settings › Privacy, you can enable or disable app analytics and crash reports and AI summary drafts independently. App analytics is on by default unless you turn it off. AI summary drafts stay off until you enable them. Recording and your local logbook remain available with both off. You can also manage device permissions, disable warnings or automatic ending, edit or delete your logbook, export journeys, and delete local app data. Manage or cancel subscriptions through the store used for purchase. The Privacy choices described here require an updated app; earlier versions may not offer them.

Depending on where you live, you may have rights to access, correct or delete personal information, restrict or object to its use, withdraw consent, or complain to a privacy regulator. Contact support@underwayboating.com. We may need information to verify your request and locate the relevant records. A name or email alone may not identify pseudonymous analytics; a problem-report request may need the installation ID shown on its report sheet.

Security and children

We use private app storage, encrypted network connections and restricted backend access. No storage or transmission method is completely secure. Protect your device and exported files.

Underway is not directed to children under 13. We do not knowingly collect personal information from children under 13. Contact us if you believe a child has provided information so we can investigate and delete it where appropriate.

Changes and contact

We may update this policy as the app, providers or legal requirements change. The updated date identifies the current revision. We will explain material new collection and obtain any required permission before it begins. Questions and privacy requests: support@underwayboating.com. This policy does not limit rights provided by applicable law.