Marine Tools Privacy Policy
Local-first by design. This policy covers the Marine Tools website, its PWA, and the Android and Windows local-calculator applications.
Policy revision: .
1. Controller and contact
Marine Tools is operated by Walterfang Design, a Norwegian sole proprietorship (organisation number 938 606 242). Walterfang Design is the controller for its processing described here. Privacy questions and requests can be sent to contact@marinetools.app.
Public policy address: https://www.marinetools.app/privacy. No Marine Tools account is required for the bundled local calculators. Protected development and Education previews may require separate website authentication.
2. Information stored on your device
The website stores vessel profiles, preferences, favourites, recent tools, calculation history, consumption and bunkering records, fuel/energy logs, saved voyage estimates and optional experimental route/analysis information in browser local storage. The website may also save weather results and the requested position for later reference. PWA caches hold application files for offline use. Cached external information must be treated according to its timestamp, not as live information.
The local-calculator apps also save supported unfinished calculator inputs, navigation and settings locally. Results must be recalculated after reopening. Education tools may save their own scenarios and unfinished inputs in their website origin. Storage is specific to the browser, application and device; it is not automatically synchronised to a Marine Tools account.
Local storage does not mean that every feature stays offline: requesting weather or route forecasts transmits coordinates as described below. Files you export, messages you send and content you deliberately share leave the local workspace. Avoid entering personal or confidential information that is unnecessary for the calculation.
3. Website usage analytics and controls
The website's own analytics can transmit page/tool identifiers and labels, calculation success or invalid-input outcomes, device class, application version, visible-time measurements, coarse traffic-source categories, a random browser identifier and a visit identifier to the Marine Tools API. The usage collectors do not include calculation values/results, vessel-profile fields, route coordinates, weather positions, raw search text or full referring URLs in their event payloads.
The stored browser identifier has a 180-day renewal threshold checked when the collector initialises its browser record; an already open page can keep its in-memory identifier longer. The visit identifier is renewed after 30 minutes of inactivity when the collector next checks it and is held in session storage. A returning-visit marker is also stored locally. These identifiers can link events from the same browser. We therefore describe this processing as pseudonymous usage analytics, not guaranteed anonymous statistics; browser counts are not a count of individual people.
In the current website version analytics is enabled by default unless disabled in Settings, excluded for this browser, or blocked by Do Not Track or the collector's environment checks. Go to Settings → Usage analytics to turn off “Help improve Marine Tools” or choose “Exclude this browser from analytics”. These controls affect future events in that browser. They do not automatically delete already transmitted server records. Clearing all site data removes the saved preference too; set it again before resuming website use.
Analytics events are written to Cloudflare Analytics Engine. The event writer does not add IP addresses to the stored event fields, but hosting, network and security providers receive IP addresses and request metadata in delivering requests and may process logs. No claim of zero IP processing or of anonymity is made.
4. Online requests, maps and external infrastructure
Website requests reach GitHub Pages/Cloudflare hosting and the Cloudflare-hosted Marine Tools API, which process technical request information such as IP address, requested resource and connection metadata. Actual enabled edge analytics, security logging and retention require confirmation in those provider accounts.
- Weather: latitude and longitude entered or selected by you are sent to the Marine Tools API. The Worker requests MET Norway Locationforecast/Oceanforecast and can request BarentsWatch forecast services. The configured global wave fallback also requests the selected geographic area from NOAA/NCEP GFS-Wave. These coordinates may describe a vessel, intended route or other selected position; they are not necessarily your device location.
- Experimental routes and AIS: route coordinates and waypoint information are sent to the Marine Tools API for forecast sampling. AIS requests send geographic bounds to that API. The BarentsWatch path retrieves AIS data and filters bounds on the server; the configured Pelyr fallback sends the requested bounding box to Pelyr. Forecast providers receive sampled coordinates; we do not claim that route information always remains local.
- Maps and library delivery: map views request OpenStreetMap and OpenSeaMap tiles, revealing requested map areas and technical request metadata to those providers. Leaflet resources are downloaded from unpkg in the current website version.
- Voyage Estimate: routing code/public datasets are downloaded from esm.sh, jsDelivr and the Norwegian Offshore Directorate's public map services. The selected distance/route calculation runs locally in the current module. Dataset providers still receive the download request and technical metadata.
Operational API requests may carry coordinates in their query URLs. Those URLs can be visible to infrastructure and logging systems. This is separate from the restricted usage-analytics event payload.
5. Forms, support and other external services
Website survey links use Tally. Suggestion links open your email application. Information you submit is processed by that service and received by the form owner according to the form configuration. Website support integrations use Buy Me a Coffee; its widget is loaded automatically by the reviewed website code and may contact its infrastructure before you choose to donate. Mail links open your email application; information you choose to send is handled by your email service and the recipient's mail service. Other external links include LinkedIn.
The local app candidate blocks the Tally and Buy Me a Coffee destinations in its link adapter and does not bundle their collector/widget scripts. Other permitted HTTPS links and protected Education open through the operating system browser facility. On Android this uses a browser Custom Tab, which may share the browser's cookies and authentication state. A website controlled by Marine Tools does not become unrelated to this policy just because it is opened from the app.
Provider information: Cloudflare, GitHub, MET Norway, OpenStreetMap Foundation and Tally. Provider policies do not replace Walterfang Design's responsibility to confirm its own arrangements.
6. Android and Windows local-calculator applications
The Marine Tools Preview 0.2.0 local-calculator configuration does not enable app analytics, advertising SDKs or automatic crash-report uploads. It does not provide live AIS/weather, and protected Education is not included in the offline package. This is different from the website analytics and online services described above. A future online app or telemetry-enabled release requires this policy and its store declarations to be reviewed again.
The Android candidate declares internet access and an app-internal signature-protected receiver permission. It does not request camera, microphone, contacts, precise-location, advertising-ID or broad-storage permissions. Local file selection uses a system chooser. Internet permission is not proof of any particular data collection, and a future signed build must be checked again.
Android file export writes a copy into a private temporary app cache, then opens the system share sheet. Old temporary exports are cleaned on a later app start if more than 24 hours old; the OS may remove them earlier. Desktop export uses a user-selected Save As destination. Copying writes the chosen result to the system clipboard. Share recipients, clipboard consumers and exported files are controlled outside Marine Tools; these are not erased when app data is cleared.
Android application backup is disabled in the current manifest. Windows/browser data and external copies may be subject to operating-system backup settings. Local storage is not a credential vault, and we do not claim application-level encryption of locally stored calculator data. Signing and distribution do not imply independent security certification. Google Play, Microsoft Store, Android, WebView/Custom Tabs and Windows may process their own installation, browser or diagnostic information under their platform settings and policies.
7. Purposes of processing
Processing purposes include providing requested online features, retaining your chosen local workspace, responding to support, operating and securing the service, and understanding website usage.
For questions about the purpose or legal basis of a particular processing activity, contact contact@marinetools.app. You can use the analytics controls and local-data controls described in this policy.
8. Recipients and international processing
Data recipients can include the hosting/CDN/API providers, weather and maritime-data services, map and library providers, form/support services, email providers and recipients you select when exporting or sharing. Provider roles may differ between processing on Walterfang Design's behalf and independent processing.
Some infrastructure and providers operate internationally and may process information outside Norway or the EEA, depending on the service and its configuration. Contact Walterfang Design if you have questions about a particular provider, processing location or international transfer.
9. Retention and deletion
Local profiles, history and other saved workspace information generally remain until you clear them, clear site/app data, uninstall where the OS removes that data, or the browser/OS evicts storage. Browser identifiers expire as described in section 3; those expiry periods are not a promise that matching server events are deleted at the same time.
The base forecast Worker caches some coordinate-keyed forecast responses in process memory with a five-minute validity check. This is a freshness interval, not a guaranteed memory-deletion deadline or a retention statement for provider/edge logs. The global-wave wrapper also has coordinate-keyed caches with validity checks (including 20 minutes for wave fields). Expired entries can remain in process memory until replaced or the runtime is discarded. These are not promised deletion deadlines.
Cloudflare documents a standard retention period of three months for its Analytics Engine service. This service period does not describe retention of exported copies, separate infrastructure logs, form responses, support mail or backups. Retention for those records depends on the relevant service and its configuration. Contact Walterfang Design for information about a particular record or to request deletion.
Settings provides local backup/restore and controls to clear history or local Marine Tools data. App Settings also provides a control to clear saved calculator drafts. Clearing local data does not remove server-side events, mail, form submissions, already shared files, recipient copies or independent backups. Contact the controller for a server-side request; identification and technical feasibility must be assessed without collecting unnecessary additional information.
10. Security
Public website/API links use HTTPS. The local app configuration disables cleartext Android traffic and limits app network access through its content security policy. Access to private development/administrative services is intended to be restricted separately. The existence of these controls is not a guarantee of absolute security or evidence that every deployed administrative configuration has been audited. Provider permissions, secure signing, logging and access controls require continued review.
11. Your choices and rights
Where the GDPR applies, you may request access, rectification, erasure, restriction or portability as applicable, and object to processing based on legitimate interests. Where consent is the basis, you may withdraw it without affecting prior lawful processing. Some rights are subject to conditions and legal exceptions. Contact contact@marinetools.app; do not send sensitive operational information unnecessarily.
You may complain to the Norwegian supervisory authority, Datatilsynet, or another competent authority. Local-only information cannot be retrieved remotely by Walterfang Design merely from an email address. Describe the relevant feature so the controller can explain available controls and assess any server-side records.
12. Changes and scope
The public website and the local-calculator apps share this policy source, with their different behavior stated explicitly. An installed app can carry an offline copy from its release; the public URL provides the current version of this policy. Changes to collection, permissions or providers require renewed review of policy text, user disclosures and store Data Safety answers. Material changes requiring consent must not be treated as accepted merely because this text changes.