Effective date (Last updated): July 15, 2026
App: MaritimeHub
Developer: Reida Volodymyr
Contact email: reida3rdmate2016@gmail.com
This Privacy Policy explains how the MaritimeHub mobile application accesses, uses, stores, and shares information.
MaritimeHub is designed primarily as an offline maritime calculation, reference, and navigation-support application. Most processing is performed locally on the user’s device.
MaritimeHub may request access to the device’s precise or approximate location when the user opens or activates a feature that requires vessel position, speed, course, distance, or map positioning.
Location may be used by features such as:
Location access starts only after a relevant user action or when a location-dependent screen is opened.
Location data is processed locally on the device. MaritimeHub does not transmit location data to the developer, does not store location history on the developer’s servers, and does not use location for advertising or user profiling.
Location monitoring is stopped when the relevant feature is closed or when the app is moved to the background, except where the operating system temporarily pauses the app for a permission or settings screen.
MaritimeHub may use device sensors, including the accelerometer, magnetic-field sensor, and other orientation sensors, to provide features such as vessel heel or roll indication and heading-related calculations.
Sensor data is processed locally on the device and is not transmitted to the developer or stored on external servers.
The Morse Code feature may use the device flashlight to transmit Morse signals.
On some Android devices, the operating system requires Camera permission in order to control the flashlight. When requested, this permission is used only for flashlight access.
MaritimeHub:
The Morse Code feature may generate audible tones through the device speaker.
MaritimeHub does not access the microphone, does not record audio, and does not collect audio data.
MaritimeHub may store information locally on the device in order to preserve user settings and app content. This may include:
Local data may be stored using HTML local storage, application preferences, or local application files.
This locally stored information is not automatically uploaded to the developer or to a developer-operated server.
Some features may allow the user to select or import files, such as RTZ route files.
Selected files are processed locally on the device for the requested function. MaritimeHub does not automatically upload selected files to the developer or to an external server.
MaritimeHub may offer one-time purchases and recurring subscriptions through Google Play Billing.
Google Play processes purchases, subscriptions, refunds, and payment information. The developer does not receive or store full payment-card details.
The app may communicate with Google Play to:
Google may process account, device, transaction, and payment-related information according to Google’s own privacy policies and terms.
Most MaritimeHub tools work offline. Internet access may be used for functions including:
External websites are opened in the device’s system browser or another application chosen by the user.
MaritimeHub does not control the privacy practices of external websites, email providers, social networks, or Google Play. Once an external service is opened, that service may process information according to its own privacy policy and terms.
When the user selects an email-related function, MaritimeHub may open the device’s email application with a recipient, subject, or message text already filled in.
No email is sent automatically. The user must review and send the message through the selected email application.
If a user voluntarily contacts the developer, the developer may receive:
This information is used only to respond to the request, provide support, investigate a reported problem, or maintain necessary correspondence.
MaritimeHub may use offline or bundled coastline, basemap, port, maritime-area, and other reference datasets, including data derived from sources such as Natural Earth.
These datasets are used to display maps and reference information. The datasets themselves do not collect user information.
MaritimeHub does not currently include third-party advertising SDKs and does not use personal data for targeted advertising.
MaritimeHub does not currently use third-party analytics services to track users across apps or websites.
If this changes in a future version, this Privacy Policy and the Google Play Data safety declaration will be updated before or when the change is released.
The developer does not sell user personal data.
MaritimeHub does not transmit locally entered calculations, routes, reports, ship particulars, sensor readings, or location history to the developer.
Information may be processed by a third party only when necessary for a user-requested external action, such as Google Play Billing, opening a website, or sending an email through the user’s chosen provider.
Data saved inside MaritimeHub remains on the device until it is:
MaritimeHub does not provide user accounts and does not maintain a remote user profile database.
Support emails and related correspondence may be retained only for as long as reasonably necessary to respond to the request, resolve a problem, maintain records of the correspondence, or comply with applicable legal obligations.
A user may request deletion of support correspondence held by the developer by contacting:
reida3rdmate2016@gmail.com
MaritimeHub minimizes data transmission by performing most calculations and processing locally on the device.
However, no device, storage system, email service, or internet transmission method can be guaranteed to be completely secure. Users should avoid including unnecessary sensitive personal information in support messages, reports, routes, or other locally stored content.
MaritimeHub is a professional maritime utility and is not directed to children under the age of 13.
The developer does not knowingly collect personal information from children through the app.
This Privacy Policy may be updated when MaritimeHub features, permissions, data practices, third-party services, or legal requirements change.
The updated version will be published at the same privacy-policy URL, and the “Last updated” date will be revised.
For privacy-related questions or requests, contact:
Reida Volodymyr
Email: reida3rdmate2016@gmail.com
© 2026 Reida Volodymyr. All rights reserved.