1. Controller
Privacy requests can be submitted through the secure contact form.
2. Website and service access
The web server processes technically necessary information such as IP address, time, requested file, referrer, browser and operating system. This is required for secure delivery, fault analysis and abuse prevention under Art. 6(1)(f) GDPR. Logs are retained only as long as necessary.
3. Account, logbook and contact data
When used, SailLogOne processes account details, trips, log entries, precise GPS tracks, anchor-watch positions, crew information, photos, settings and subscription status to provide the requested service under Art. 6(1)(b) GDPR. Contact and deletion forms process the submitted name, reply address, message, time and security information for handling the request.
4. Trip preparation and private shopping lists
Checklists, completion state, an optional skipper confirmation including name, time and template version, and shopping lists are stored locally first and, where cloud sync is enabled, on our server for the relevant account and trip.
The skipper may voluntarily create a random, time-limited and revocable shopping-list link. Anyone holding it can see the trip name and list and, if enabled, edit it without signing in. Before making a change they enter a display name of their choice. It is stored with the changed item and change time and shown to the trip crew as an editing note. The display name is also stored locally only in that browser. The link must be treated as a confidential access key. We store only a cryptographic hash of its token; technically necessary access data may be processed for secure operation and abuse prevention. Sharing ends automatically at the selected time or immediately when revoked.
5. Storage, recipients and deletion
Local data remains on the device. Enabled cloud data is stored on servers in Germany/the EU and transmitted using TLS. Necessary providers include hosting, Google authentication and the relevant app store. We do not sell data or use it for advertising. Account and related cloud data can be deleted through the documented deletion process, subject to statutory retention duties.
6. Location and device permissions
Foreground location supports entries; optional background location supports route tracking and anchor watch while the screen is locked. Camera, media, notification and audio permissions support the corresponding functions. Permissions can be withdrawn in device settings, after which those functions may no longer work.
7. Optional audience measurement
Only after explicit consent, website and dashboard use self-hosted Umami for aggregated, cookieless audience measurement. It receives no form content, user ID or email, and is not used for advertising or session replay. Consent can be withdrawn in consent settings.
8. Legal grounds and rights
Processing is based on performance of a contract (Art. 6(1)(b) GDPR), consent where requested (Art. 6(1)(a) GDPR), legal duties (Art. 6(1)(c) GDPR) and secure operation or abuse prevention (Art. 6(1)(f) GDPR). Subject to the GDPR, you have rights of access, rectification, erasure, restriction, portability, objection and complaint to a supervisory authority. Use the contact form or Delete account and data.
9. Legal-document record
At first login and after material changes we store the user ID, accepted terms version, noted privacy version and time. Optional consent remains separate.
10. Version
Last updated and version: 7 September 2026 / 2026-09-07.2.