Legal
Privacy Policy
Last updated: August 2026
VHF Radio Assistant Ltd ("the Company", "we," "us," or "our") operates the mobile application ("the App") and the website vhfradioassistant.com ("the Site"). We are committed to protecting your privacy. This Privacy Policy explains how data is handled within our services and across our platforms under applicable data protection laws, including the UK GDPR and the Irish Data Protection Act 2018.
1. The Core Principle: Local On-Device Processing
We believe your boat's data belongs on your boat. VHF Radio Assistant Ltd does not own, run, or rent any central databases, cloud storage networks, or remote servers to harvest or store your navigational, hardware layout, or personal safety data.
- 100% local execution: all core calculations — including GPS positioning, live AIS tracking, "Rule of Three" proximity scanning, Voice Warmup layout changes, and text-to-speech scripting — are performed entirely on your local, physical device.
- Zero transmission: no location history, vessel identities, MMSI numbers, personal safety beacon IDs, customised radio layout configurations, or transmission logs are ever transmitted to us or any third-party cloud systems.
2. Information We Access (App Permissions)
To function as a live helm assistant and provide real-time situational awareness, the App requires you to grant specific system permissions. Here is exactly how that data is used locally:
Location Services (GPS Data)
- How it's used: calculates your current coordinates, speed over ground (SOG), and course over ground (COG) to automatically fill in the position details on your emergency radio scripts.
- Background access: if explicitly enabled, location data is processed in the background to maintain live collision alerts (CPA/TCPA) while the display is sleeping or while you are viewing other screens.
- Storage: this data is volatile, remains strictly on your device, and is never stored permanently or shared.
Local Network & Wi-Fi Access
- How it's used: functions as a standalone network socket client to connect directly to your onboard shipborne electronics (such as an AIS receiver, chartplotter, or NMEA multiplexer) via TCP/UDP protocols over your local boat Wi-Fi network.
- Data read & safety command processing: the app reads standard NMEA data streams locally to populate targets on your chart. Additionally, the network decoding engine scans the local stream to process targeted digital safety instructions sent directly to your vessel's MMSI by maritime authorities (such as the strings
STOP,ML,VL, andVD). - RAM cache volatility: these incoming safety commands are processed strictly within the device's volatile RAM memory cache to dynamically refresh the active script display text and text-to-speech audio output. This stream is entirely isolated from the internet and never leaves your vessel's local network.
Nearby Devices & Bluetooth (BLE) Access
- How it's used: utilised to power the custom-built, air-gapped device-to-device Bluetooth Low Energy (BLE) pipeline for peer-to-peer data syncing.
- Privacy guardrails: this permission allows the direct, over-the-air transfer of custom shortcuts, button pacing layouts, saved marina directories, and captured local alert records between nearby hardware devices. This pipeline supports full, cross-platform bi-directional mirroring, including Android-to-Android, Android-to-iOS, iOS-to-iOS, and iOS-to-Android. All data transfers remain localised, encrypted over the air, and completely bypass the internet. No unique device identifiers, tracking profiles, or syncing metrics are ever logged or uploaded to the Company.
- OS requirements: on Android and iOS devices, local wireless and nearby device permissions are operating system requirements to discover and communicate with local network or BLE hardware.
Personal Safety Beacon Data Storage
- How it's used: users opting to leverage the Single-Handed MOB Automated Distress Relay must manually register their officially licensed personal safety beacon ID or MMSI within the application.
- Privacy guardrails: this hardware ID is stored entirely inside the device's secure, isolated local storage sandbox. The application uses this string strictly to power the background dual-device verification loop (ensuring a live transmission via the connected Digirig Mobile interface is only permitted if the physical beacon is actively triggered in the water). This identifier is kept entirely confidential and is never transmitted off the host device.
Audio & Audio Session Permissions
- How it's used: required strictly to generate the text-to-speech audio route through your physical device speaker, headphone jack, or a third-party USB audio interface (e.g. Digirig Mobile) to drive your VHF radio transmitter.
- Immediate manual control: the operator retains full control over the audio stream. Tapping the manual "Abort" button on the interface immediately halts the text-to-speech engine.
- No recording: the App does not record, stream, process, or store ambient microphone or cockpit audio.
3. Contact & Website Infrastructure (Site Only)
Direct Email Form
If you voluntarily submit your name and email address through our launch notification form on the Site, that information is sent directly to our secure inbox. We do not upload, sync, or store your email address on third-party marketing or tracking platforms. Your details are used strictly to send you a notification update regarding the app's availability. You can request permanent deletion at any time.
Website Cookies & Security
Our Site utilizes Cloudflare to optimize performance and protect against automated cyber attacks, scrapers, and bots. Cloudflare may place essential, non-identifying operational cookies (such as __cf_bm) on your browser strictly for security purposes. These cookies do not track your browsing habits, contain no personal identity information, and cannot be used for marketing or advertising purposes.
4. App Store & Google Play Store Compliance
In accordance with Apple App Store Privacy Details (Data Nutrition Labels) and Google Play Data Safety requirements, the App falls under the following strict data classifications:
- Data not collected / not linked to you: neither platform collects user data, contact info, identifiers, financial details, or browsing history through the software.
- On-device data diagnostics: any diagnostic data or performance logs generated during an application crash remain entirely on your physical device unless you explicitly opt in to share them via Apple's native crash reporting or Google's Android Vitals.
5. Changes to This Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date at the top.