Skana App Privacy Policy

1. Core privacy principles

• Skana has no user account or advertising profile.
• Skana does not sell your personal information and does not use your journey data for advertising.
• Your detailed log is stored on your device first. Production cloud backup and routine journey-learning contributions are not enabled for ordinary user installs.
• Network features have specific purposes. We aim to send only the limited information each feature needs.

2. Information kept on your device

Depending on the features you use, Skana stores the following in the app's private storage:

• GPS fixes, track points, journey start and end times, route totals, estimated gaps, departure and arrival positions, and the local journey date;
• notes and summary text that you enter or that Skana drafts for you;
• boat name and type, home-port and saved-origin positions, automatic-journey settings, and other preferences;
• cached forecasts, tide data, and local data used to calculate tides, currents, weather readouts, nights aboard, and journey intelligence; and
• optional diagnostic evidence, including bounded coordinate-free recording reliability scorecards, kept on the device until you explicitly export it or send a problem report.

Skana's automatic-journey and background-recording features use location in the background when you enable them. That processing is used to detect or record a journey and is performed on the device. Granting a location permission does not, by itself, upload your track.

3. Location and background access

When you enable automatic journeys or background recording, Skana can use location while the screen is off or while the app is not in the foreground. This allows the app to detect or record a journey. Automatic-journey processing is performed on the device.

Skana does not upload your full journey or raw track to Open-Meteo or to the map service. Individual weather and map requests can still reveal the approximate area needed to provide those features, as described below.

4. Information sent off the device

Marine weather, wind, and tides

When you request weather, Skana sends a marine-area query or an approximate point used to retrieve the relevant forecast. Environment and Climate Change Canada may therefore receive that marine area or approximate point, plus ordinary network metadata such as an IP address.

For current wind, Skana requests a forecast for the current point from Open-Meteo's GEM/HRDPS endpoint. The requested latitude and longitude are sent to Open-Meteo for that request. Skana does not send your saved journey or track to Open-Meteo.

Tide and current predictions are downloaded as a shared regional bundle from Skana's Supabase storage. The bundle is the same for every install; it does not contain your token, account, or position. The storage or delivery service may still receive ordinary request metadata.

Mapbox chart tiles

When chart tiles are enabled, Skana requests map tiles from Mapbox for the area currently visible on screen. This can reveal the approximate map area to Mapbox and ordinary network metadata to the tile service. Skana draws your track locally over the map; it does not send your track to Mapbox as part of the map display.

Warning notifications

If you enable marine-warning notifications, Skana sends a push token and the name of the marine forecast area you chose to Skana's warning service. The service uses them to deliver warnings and detect a change of watched area. It does not receive your GPS position, journey track, install ID, name, or account because Skana has no account.

The warning service uses Supabase in Canada for registration tables and Expo's push service to deliver notifications through the platform push provider (FCM on Android and APNs on iOS). Turning notifications off deletes the registration and its pending delivery receipts. Inactive registrations are automatically deleted after 90 days, delivery receipts are purged after 24 hours, and invalid tokens are removed when detected.

Journey summary drafts

When a closed journey has an empty summary, a build with summary drafting enabled may create a derived digest on the device and send it to a Skana Supabase function. The digest can contain the journey date and local start/end clock times; named places encountered on the route; distance, underway time, average speed, estimated distance, gap count, and propulsion.

The digest contains no raw latitude/longitude, raw track points, notes, boat name, or database IDs. The function sends it to Anthropic to draft two to four sentences, then returns the draft to the device. Skana does not store the digest or draft on its backend. The draft is written to the local journey only when its summary is still empty; later edits always win. Anthropic may process the request under its applicable service terms and technical logging rules.

Product analytics and crash diagnostics

Production builds may use PostHog for product-quality analytics and crash diagnosis. They can send application lifecycle and release information; explicit bounded outcomes for onboarding permissions, journey recording and saving, GPX export, automatic-start decisions, and recording recovery; and crash or error diagnostics. They do not send screen views, touches, element trees, rendered text, settings changes, or a general clickstream. PostHog assigns a pseudonymous identifier; there is no Skana account or PostHog person profile attached to it.

Skana's telemetry gate rejects journey IDs, route names, exact timestamps, coordinates, place names, notes, summaries, and unapproved free text. It also disables session replay, screen and touch autocapture, console capture, surveys, and feature flags. Network-derived geolocation is disabled in the client and the app requests IP discard from PostHog. PostHog processes this telemetry in the United States. Telemetry is enabled only in production builds with both the project key and Skana's production marker; development and preview builds cannot send events. The log never waits for telemetry.

Problem reports

When you open Settings › Diagnostics › Report a problem, read the payload list, and tap Send, Skana sends one report to Supabase in Canada. It contains the complete local log, including journeys, raw tracks, precise positions, notes, summaries, and the boat profile; the bounded in-memory diagnostic log; up to 64 coordinate-free native geofence EXIT outcomes from the previous 30 days; up to 20 coordinate-free recording reliability scorecards; the device model and OS; the app version; and the install ID.

Nothing is sent when you open Diagnostics or the report sheet. Reports are never automatic, scheduled, retried, or sent in the background. The copy is used to trace the problem you reported and is deleted when the problem is resolved. There is no restore path: this is a report sent to the maintainer, not a cloud backup.

5. Service providers

Skana uses service providers only for the product functions described above. Providers may process limited network metadata such as an IP address as part of operating and securing their services. Skana does not use that metadata to create a journey history or advertising profile.

6. Retention and deletion

• On-device data: remains in the app's private storage until you edit or delete it, reset the app, or uninstall it. An exported GPX or other shared file is controlled by the destination you choose, not by Skana.
• Warning registrations: are deleted when notifications are turned off, when a token is invalid, or after 90 days without an app refresh. Delivery receipts are purged after 24 hours.
• Summary drafts: the Skana summary function is stateless and does not retain the digest or draft after returning the response. The local copy is deleted when you delete the journey; Anthropic's handling is governed by its applicable provider terms.
• Analytics and crash data: are retained in the PostHog project for up to 12 months under the current project setting, then deleted or aggregated under that service's retention controls. We do not retain journey tracks in this path.
• Native geofence diagnostic history: is limited to 64 coordinate-free outcomes. Outcomes stop being returned after 30 days and stale entries are removed from private app storage on the next native EXIT or diagnostic read.
• Problem reports: are retained only while the reported problem is being investigated, then deleted. A deletion request may need the install ID shown in Settings › Diagnostics so the maintainer can locate the report. A report is not a user backup service.

7. Your choices and privacy requests

• decline or revoke location, background-location, and notification permissions in Skana or your operating-system settings;
• turn off warning notifications, which deletes the server registration;
• turn off automatic journeys, which stops that feature while leaving your local log available;
• edit or delete journeys and notes in the app;
• choose whether to send a disclosed problem report; and
• export a journey as GPX and decide where the exported copy is shared.

Depending on where you live, you may also have rights to request access to, correction of, deletion of, or restrictions on the use of your personal information, and to withdraw consent where processing is based on consent. Send requests toa@meunier.co. We may ask for enough information to verify and locate a request. Because Skana has no account, some pseudonymous provider data may not be identifiable from a name or email alone.

If you delete the app, its local log is normally removed by the operating system. Deleting the app does not automatically delete copies you exported or server-side registrations that have already expired or are held by a provider; use the controls above or contact us for an applicable request.

8. Security

Skana uses platform-private app storage, TLS for network requests, restricted backend access, and least-privilege service paths appropriate to each feature. No method of storage or transmission is completely secure. Keep your device, operating system, and exported log files protected.

9. Children

Skana is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided information to us, contact us so we can review and delete it where appropriate.

10. Changes and contact

We may update this policy when the app, service providers, or applicable requirements change. The effective date above records the current version.

This policy is for privacy transparency and does not replace any rights or obligations that apply under the law where you live.