Privacy at a glance
Your voyage records start on your device. Online maps and forecasts contact their data providers. Web route sync and community contributions have their own account and sharing flows. You control permissions, exports and the optional connections you use.
1. Who this policy covers
This policy explains how OceanSea Nav handles information in its iPhone/iPad app and its web account and route planning service at akincijet.com/oceanseanav. The developer and privacy contact is Yiğit Can Akıncı, reachable at yigitcan.akinci@gmail.com.
Different features use different data. Local voyage tools, the OceanSea Nav web account and Apple iCloud/CloudKit services are separate. Enabling one does not automatically enable the others.
2. Location and information on your device
- Location and navigation: with your permission, the app uses precise location and available navigation readings to show your position, follow routes, record tracks, mark a man-overboard position and operate anchor watch. An activity you start can continue using location in the background when the device permits it.
- Voyage records: routes and waypoint coordinates, tracks and timestamps, saved places, notes, man-overboard records, boat settings and related photos or videos are stored on the device. Data from connected instruments may be included in a track you record. Fuel capacity, remaining fuel and reserve settings are stored locally.
- Media: the app receives the photos or videos you choose with Apple’s system picker. If you choose to record a video for a saved place, it uses the camera and microphone and stores the video on the device, associated with that place. It does not infer a new position from the video. Place videos are not included in plain JSON voyage backups or iCloud archive sync.
- AIS recordings: if you start recording received AIS data, the local recording may contain vessel positions, MMSI identifiers, safety message text, source and receive times. These recordings are not automatically uploaded and are not included in iCloud archive sync. You can delete them or explicitly export them; the JSON export can include messages as well as positions.
Local records are not automatically published. They can leave the device through a service you enable, an export or share action you choose, or your own device backup settings.
3. Online maps, search and environmental data
Online requests go to the provider for the feature you use. Depending on that request, a provider receives the selected map area or tile coordinates, search text, a chosen coordinate or station, date/time range and technical network information such as your IP address. These requests obtain map imagery, marine marks, places, depth products, weather, tides, currents and astronomical information; they are not an automatic upload of your whole voyage archive.
Sources used by the app include Apple Maps, OpenStreetMap/Overpass, OpenSeaMap, GEBCO, Open-Meteo, NOAA, USACE and the US Naval Observatory. Availability depends on the layer, region and feature. The app shows source and attribution details where the data is used. If you configure a custom provider or boat server, requests also go to that endpoint.
World package downloads contact our hosting service with the selected package request and ordinary connection information. Updating a USACE lock report downloads the publication; that action does not send your location, route or search text. A provider or hosting service can still receive the request’s IP address.
External providers operate their own infrastructure and privacy practices. Their services may process requests in countries other than your own. You can avoid an optional online request by not using that feature, and use installed offline data where available.
4. Web account, sign-in and route sync
If you create or use an OceanSea Nav web account, the service processes an account identifier, username, display name, email address if provided, and account and sign-in timestamps. Password-based accounts store a password hash, not a readable password. With Sign in with Apple, we receive the Apple account identifier for our service and any name or email Apple supplies, which may be an Apple relay address. We do not receive your Apple password or biometric information.
Sign-in and account protection also use temporary session and challenge records, protected cookies and IP-derived rate-limit records. Apple authorization tokens required for the sign-in relationship and its revocation are stored encrypted on the server.
After you explicitly link the account for web route sync, saved routes and their associated waypoint, planning and route-note fields are transferred between the app and the web service. The service stores route identifiers, versions and changes needed to reconcile edits and deletions. Automatic sync runs while the app is in the foreground. Tracks, photos, live location and separate iCloud settings are not part of this web route sync.
Disconnecting web sync stops that connection; it does not delete the web account or previously saved route copies. Signing out, disconnecting and deleting an account are different actions.
6. Your permissions and choices
- Location: used for position and navigation features. Background location is associated with activities such as route following, track recording, anchor watch or an active man-overboard record. Stop the activity in the app or change location access in device Settings.
- Local network: connects to the boat devices or servers you select. Disabling it prevents those connections.
- Photos and videos: selected through the system picker; the app does not request access to your entire photo library for this selection.
- Camera and microphone: used when you choose to record a place video, including its sound.
- Notifications: permission is requested for local alerts. You can change it in device Settings. Alert delivery also depends on device and operating system conditions.
- Files and sharing: importing and exporting uses your file selections and sharing choices.
You can change permissions in iOS/iPadOS Settings. A denied permission can limit the feature that needs it. It does not by itself remove information already saved or shared.
7. Retention, security and tracking
Local records remain until you remove them or the app’s local data, subject to your own device backups. Web account and route records remain for the account and sync service until you delete the relevant data or account. Community submissions, published contributions and reports remain for their publication, review and moderation purposes until withdrawn or removed through the applicable flow. Independently exported or shared copies are controlled by their recipients.
The web service uses short-lived technical records to protect sign-in and finish deletion safely. Sign-in challenges, deletion tickets and temporary anti-recreation markers have a 10-minute validity window; completed deletion receipts are eligible for cleanup after 24 hours. Expired records are removed by service cleanup rather than a guaranteed deletion at the exact expiry second.
Hosting infrastructure may keep technical access and security logs, including an IP address, request time and response status. Support emails contain your address and whatever information you choose to send; they are used to handle the request and related follow-up. Their retention depends on the support or security purpose and any applicable requirement. You can ask the privacy contact about retained information or request deletion.
The app does not include advertising or cross-app tracking software. These static support and privacy pages do not add analytics or tracking cookies. The separate web account service uses session and security cookies for its sign-in functions. App Store purchase or subscription management is handled by Apple; we do not receive your card or bank details. Current access to available app features is free.
We use access controls and the protections available in the app and hosting service, including HTTPS for the public web service, password hashing and encrypted Apple token storage. No system can promise absolute security. Do not include passwords, verification codes or private keys in a support request.
8. Delete an account or request removal
Delete your OceanSea Nav web account
- In the app, open Tools → Web route sync and its web account deletion section.
- Select Check web account to delete and confirm the account shown is the one you intend to remove.
- Select Permanently delete this web account, then confirm Delete web account and server data. Follow any displayed completion step if the operation is pending.
You can also use the direct web account deletion page. Its final action is currently labelled “Hesabımı kalıcı olarak sil”. You do not need to email support to start this normal deletion flow.
Deletion removes the web account, its server-side route data and the stored Apple sign-in association. The service attempts to revoke the Apple authorization. If Apple authorization revocation cannot be completed automatically, the result provides a manual follow-up. Your Apple Account itself is not deleted.
Deletion does not erase independent routes or media on your devices, installed map packages, separately stored iCloud/community data or copies previously shared with someone else. Manage local records in their own app screens. For a community or other service record you cannot remove yourself, contact us and identify the record. Do not send your account password.
Existing App Store subscriptions must be managed separately in Apple’s subscription settings. Account deletion does not cancel billing. Small, time-limited technical deletion records are described above.
Your privacy requests
Contact yigitcan.akinci@gmail.com to ask about information associated with you or request access, correction, a copy or deletion. State the service or record concerned; we may need proportionate information to verify the request. Available rights and any lawful retention requirements depend on your location and circumstances. Do not send identity documents unless a necessary, secure verification method has been agreed.
9. Policy updates and contact
We will update this page when the app’s data use or available services change. The date at the top identifies this version. Material changes that require your permission will be presented through the relevant service before that new use.
OceanSea Nav — Yiğit Can Akıncı
Support and privacy: yigitcan.akinci@gmail.com
Visit the support page