Privacy Notice

Last updated: 16 September 2026

This notice explains what personal data Naviger processes, why it is processed, how long it is kept, and what rights users have. Naviger is a free public beta passage-planning service and is not a navigation authority.

Controller

Naviger is operated by Adam Lazinski. Adam Lazinski acts as controller for personal data processed by the service. Privacy requests should be sent by email to a.lazinski99@gmail.com. Provider identification is published at the Imprint page.

Data We Collect

Route data: start and destination coordinates, selected vessel mode, speed and fuel settings, sailing calibration speed, route preferences, selected wind/current mode, shore-clearance settings, custom no-go zones, and generated route outputs.

Location data: browser GPS position is processed only if you press the live-location control and allow location access in your browser.

Technical data: IP address, request time, requested path, response status, response time, error logs, rate-limit metadata, and basic operational logs may be processed for security and debugging.

Optional product analytics: if you explicitly enable route analytics in the planner, Naviger records a random browser deletion key, coarse 10-degree start and destination area bands, route mode and scale, broad duration/distance/compute buckets, data-source categories, departure-scan summary, and route-quality outcome. Exact positions, route geometry, vessel or profile names, free-form errors, and exact departure or event times are excluded from this analytics record.

Legal Bases

Route calculation requests are processed to provide the service you request. Security logs, rate limits, abuse prevention, debugging, and capacity monitoring are processed on the basis of legitimate interests in keeping the service secure and available. Browser GPS is optional and is used only after browser permission is granted. Optional product analytics are processed only on the basis of your consent, which can be withdrawn at any time in the planner.

How We Use Data

Data is used to calculate and display routes, fetch selected live wind and current forecasts, enforce authentication and route limits, debug errors, protect against abuse, and maintain the service.

Retention

Route jobs are held as ephemeral server-side state with a short time-to-live and can be deleted by the app after completion. Depending on deployment, this state is held in process memory or in a non-persistent Redis queue. It is not a permanent route-history database. Forecast cache files may be retained to reduce repeated provider downloads. Server and proxy logs are retained only as needed for short-term troubleshooting, security, and abuse prevention.

Anonymous operational summaries such as route outcome, vessel mode, planning scale, queue delay, and calculation duration may be retained for a short rolling period. These summaries exclude route coordinates, no-go geometry, access tokens, and profile names.

Consented product-analytics outcomes are retained for no more than the period shown in the planner, currently up to 180 days. Turning the option off stops future sharing. The "Delete my shared outcomes" control uses the random browser key to remove records previously contributed by that browser. Clearing browser storage first may remove that deletion key, in which case the records cannot be matched back to the browser.

Each route job is protected by a random access token. The browser sends this token in a request header rather than in the URL, reducing exposure through browser history and ordinary proxy request logs.

Third-Party Services

Hetzner hosts the server infrastructure in Europe. Map tiles are loaded by your browser directly from OpenStreetMap and OpenSeaMap tile servers, which receive technical request data such as your IP address. Live wind and current forecasts are requested by the Naviger server from NOAA and Open-Meteo for the area of your route; those requests come from the server, not from your browser.

International Transfers

The application server is intended to run on European infrastructure. Some browser-loaded resources or forecast providers may process technical data outside your country. Wider public launch should review each provider and add appropriate transfer safeguards where required.

Cookies, Local Storage And Optional Analytics

Naviger does not use advertising cookies, tracking cookies, or third-party tracking pixels, and the planner sets no cookies. Vessel profiles and the optional analytics consent/deletion key are stored locally in the browser. Product analytics remain disabled unless the operator enables the feature and you then opt in through the planner.

Your Rights

Where GDPR applies, you may request access, correction, deletion, restriction, portability, and objection to processing based on legitimate interests. You may also complain to your local data protection authority. Email a.lazinski99@gmail.com to exercise these rights.

Processor And Hosting

Hetzner is used as infrastructure host for the beta deployment. Before any wider public or paid launch, the operator should complete the appropriate data-processing agreement and document the final controller and processor details in this notice.

Security

The service uses HTTPS, access control, route request limits, ephemeral route job retention, and disabled public API documentation. No system is perfectly secure, and this beta should not be used to store sensitive personal information beyond what is needed for route calculation.

Changes

This notice may be updated as the service changes, especially if accounts, payments, analytics, cookies, or persistent route history are introduced.