Effective date: 11 May 2026
Contact: seapilotapp@gmail.com
This Privacy Policy explains how SeaPilotApp (“SeaPilotApp”, “the app”, “we”, “us”) handles information when you use the app.
SeaPilotApp is a marine navigation companion app for Android. It can receive AIS/NMEA 0183 data over Wi‑Fi TCP/UDP, Bluetooth and local network connections, display AIS targets and vessel data, show the device GNSS/GPS position, load routes and offline map files, display online map and data layers, provide weather-related map data where available, and support route monitoring and navigation alarm functions.
SeaPilotApp is not a certified navigation system, not ECDIS, and not a replacement for official nautical charts, approved bridge equipment, radar, AIS display, watchkeeping procedures, COLREGs, voyage planning requirements, or professional navigation judgement. The master and operator remain responsible for safe navigation.
SeaPilotApp is designed so that most operational navigation data is processed locally on your device. Depending on the features you use, the app may process the following information.
The app may use device location to show own ship position, speed, course and related navigation information. Location data may also be used for map display, route monitoring, cross-track error calculations, arrival-to-waypoint indications, anchor watch, GPS loss alarms and other navigation-related functions.
The app may receive and process AIS/NMEA 0183 data from external equipment, including AIS receivers, AIS Pilot Plug devices, NMEA gateways or local test files. AIS/NMEA data may be received over Wi‑Fi TCP/UDP, Bluetooth or local network connections.
This data is used to display AIS targets, own ship information, navigation aids, base stations, vessel names, MMSI numbers, call signs, positions, courses, speeds, headings, closest point of approach indicators, navigation values and AIS/NMEA logs.
Routes loaded or created by the user, including GPX/RTZ route files, waypoints, route legs, XTE corridors, arrival radius settings and route monitoring state, are processed locally on the device.
The app may process local alarm and monitoring information such as route deviation, arrival to waypoint, waypoint passed, GPS loss, anchor watch and collision risk indications. This information is used to display on-screen alerts, sound/vibration indications and notifications where enabled.
The app may use map files, chart-related files, MBTiles, Mapsforge maps, user-selected route files, saved logs and other files selected or imported by the user. These files are processed locally unless the user explicitly exports, shares or uploads them outside the app.
Where weather features are available and enabled, the app may download, store and display weather or environmental data such as wind, pressure, temperature, wave or related forecast layers. Weather packs may be stored locally for offline or offline-first use.
The app stores local settings and preferences, such as connection settings, display preferences, map settings, route monitoring settings, alarm settings, weather settings and other UI/application preferences.
If you use a save/export log feature, AIS/NMEA logs or related diagnostic/navigation logs may be stored locally on your device.
SeaPilotApp does not require a user account.
SeaPilotApp does not sell personal data.
SeaPilotApp does not upload your AIS stream, routes, offline map files, saved logs, or navigation data to a SeaPilotApp-owned server.
However, some information may be transmitted to third parties when you use online features or when diagnostic/analytics services are enabled, as described below.
SeaPilotApp may use Firebase services provided by Google, including Firebase Crashlytics and Firebase Analytics / Google measurement services, to improve app stability, understand general app usage and diagnose technical problems.
Firebase Crashlytics may collect and transmit technical diagnostic information to Firebase/Google, such as crash reports, stack traces, app version, operating system version, device model, device state, log messages, custom diagnostic keys and related runtime information.
SeaPilotApp does not intentionally send AIS/NMEA message content, route files, saved logs or precise navigation position to Crashlytics. However, crash diagnostics are processed by Firebase/Google as a third-party service provider.
Firebase Analytics / Google measurement services may collect app usage and technical measurement data, such as app launches, session information, app interactions, device and operating system information, app version, installation identifiers, app instance identifiers and related analytics metadata.
Where available and permitted by the operating system and user settings, Google measurement services may access or process identifiers such as the Android Advertising ID and related Android advertising or attribution identifiers. SeaPilotApp includes Advertising ID / Ad Services permissions in the release build because Google measurement / Firebase Analytics components are integrated.
SeaPilotApp does not use Firebase Analytics to intentionally upload your AIS stream, route files, saved logs, offline map files or precise navigation position to a SeaPilotApp-owned server. Analytics and measurement data are processed by Google/Firebase according to Google’s applicable terms and privacy practices.
If you enable or use online map layers, online weather/data sources or other online services, your device connects to the selected provider to download the requested data.
Depending on the enabled features and build configuration, such providers may include OpenStreetMap/OpenSeaMap, EMODnet/GEBCO bathymetry services, NASA GIBS, NOAA/NOMADS GFS, DWD ICON, MET Norway or other map, weather, satellite, bathymetry or environmental data providers.
When these services are accessed, the provider may receive standard technical network information required to deliver the service, such as your IP address, tile/data requests, request metadata, timestamps, user agent, device/network information and the approximate map area or data area requested.
Please review the privacy policy and terms of the selected third-party provider. SeaPilotApp does not control the privacy practices of third-party providers.
Offline maps and downloaded packs are stored and used locally on your device unless you delete, export or share them.
If you connect SeaPilotApp to AIS/NMEA equipment over Wi‑Fi TCP/UDP, the app communicates with the local network address and port selected by the user.
If you connect to AIS/NMEA equipment over Bluetooth, the app uses Bluetooth permissions to discover, pair with or connect to the selected compatible device.
On Android versions that require local network or nearby-device permissions, the app may request those permissions to access local AIS/NMEA equipment.
The app does not use these local network or Bluetooth connections to upload your navigation data to a SeaPilotApp-owned server.
SeaPilotApp may request the following permissions depending on your Android version and the features you use.
Used to show GNSS/GPS position and related navigation data, and to support map display, route monitoring, anchor watch and GPS loss alarms.
Used to discover and connect to Bluetooth AIS/NMEA gateways, Pilot Plug devices or other compatible external equipment.
Used to connect to AIS/NMEA sources over TCP/UDP, access local network equipment, load online map tiles, download online data layers and retrieve weather/environmental data where enabled.
Used to show navigation, route monitoring and alarm notifications, including critical alarm notifications.
Used to support visible active monitoring and critical alarm functions while the app is performing navigation-related monitoring.
Used for navigation alarm indications when enabled.
Used to select, import, store or export user files such as offline maps, route files, chart-related files, weather packs and saved logs.
Used by integrated Google/Firebase analytics and measurement components where available and permitted. This is used for analytics, measurement, attribution or diagnostics according to the applicable Google/Firebase SDK behavior and platform rules.
SeaPilotApp may use a visible foreground service notification to support active route/alarm monitoring and critical alarm sound while the user is actively using monitoring or alarm functions.
This may be used for navigation-related alerts such as route deviation, waypoint arrival, waypoint passed, GPS loss, anchor watch and collision risk indications.
The foreground service is shown to the user through a notification and is stopped when monitoring or the critical alarm function is stopped.
SeaPilotApp may share or transmit data in the following limited cases:
SeaPilotApp does not sell personal data and does not operate a SeaPilotApp server for uploading your AIS stream, routes, saved logs or offline map files.
Local app data remains on your device until you delete it, clear app storage or uninstall the app.
Saved logs, imported routes, offline maps, chart-related files and weather packs remain on your device until you delete them from the app, from device storage, or uninstall the app. Files stored outside the app’s private storage may need to be deleted manually.
Crash reports, diagnostics, analytics and measurement data processed by Firebase/Google are retained according to Google/Firebase’s applicable data retention practices and your applicable settings.
Third-party map/weather/data providers retain request information according to their own privacy policies and retention practices.
You can delete saved logs, route files, downloaded packs and offline files from the app where available, or from your device storage.
You can clear local app data through Android system settings.
You can uninstall the app to remove app-managed local data from the device. Files stored outside the app’s private storage may need to be deleted manually.
You can control app permissions, including location, notifications, Bluetooth/nearby devices and other permissions, through Android system settings.
SeaPilotApp does not create user accounts, so there is no SeaPilotApp account deletion process.
SeaPilotApp is not intended for children under 13. The app is intended for marine navigation-related use by competent users.
SeaPilotApp processes most navigation data locally on the device. You should only connect the app to AIS/NMEA sources, Bluetooth devices and network equipment that you trust.
No mobile application or network transmission can be guaranteed to be completely secure. You should use appropriate operational judgement when using any navigation aid.
We may update this Privacy Policy from time to time. When changes are made, the effective date will be updated.
If you have questions about this Privacy Policy, contact:
seapilotapp@gmail.com