Privacy policy

This is an English reading version of the German original. Only the German version is legally binding. Where this translation and the German text differ, the German text prevails. References to statutory provisions are to German law and to the GDPR; German section numbers (§) are kept unchanged so they can be looked up.

1. Privacy at a glance

General information

The following notes give a simple overview of what happens to your personal data when you visit or use our website sailto.app or our application Sailto at app.sailto.app (together the "Service"). Personal data is any data that can be used to identify you personally. Detailed information is set out in the privacy policy below.

Data collection on our website / in our Service

Who is responsible for data collection?

Data is processed by the operator of the Service. You will find the operator's contact details in the section "Controller".

How do we collect your data?

Some data is collected because you give it to us, for example when you register an account or fill in your crew profile. Some data is entered by other people, for example by whoever organises a trip. Other data is collected automatically by our IT systems when you visit. This is mainly technical data (e.g. browser, operating system or time of the page request).

What do we use your data for?

Part of the data is collected to ensure the Service is provided without errors. Other data is used in statistical form to see which content is used. If you enter into contracts with us, your data is used to perform them.

What rights do you have regarding your data?

You have the right at any time to receive information free of charge about the origin, recipients and purpose of your stored personal data. You also have the right to have this data corrected or erased; you can delete your account yourself in the app. If you have given consent, you can withdraw it at any time with effect for the future. You also have the right, under certain circumstances, to request that processing be restricted, and the right to lodge a complaint with the competent supervisory authority.


2. Controller

The controller responsible for data processing is:

Kilo Moana UG (haftungsbeschränkt)

Heidestraße 49g 25462 Rellingen Germany

Managing director: Alexander Siemer-Schmetzke Telephone: +49 151 42323196 E-mail: info@kilo-moana.com

Commercial register: Amtsgericht Pinneberg, HRB 19590

Data protection officer:

We are not required to appoint a data protection officer, because we do not as a rule employ at least 20 people constantly in the automated processing of personal data (§ 38(1) BDSG) and we carry out no processing that requires a data protection impact assessment under Art. 35 GDPR. If you have questions about data protection, please write to the e-mail address above.


3. Hosting and e-mail delivery

External hosting

Our Service is hosted by an external service provider (hoster). The personal data collected in this Service is stored on the hoster's servers. This may include IP addresses, contact requests, meta and communication data, contract data, contact details, names, website access and other data generated through the Service.

We use the hoster to perform our contracts with prospective and existing users (Art. 6(1)(b) GDPR) and in the interest of providing our online service securely, quickly and efficiently (Art. 6(1)(f) GDPR). The hoster processes the data on our behalf under a contract pursuant to Art. 28 GDPR.

Services used:

Service Provider Location
Web hosting of the website sailto.app STRATO GmbH, Berlin Germany
Virtual server (app, database, sign-in service, file storage, analytics) STRATO GmbH, Berlin Germany
E-mail delivery for the app and the sign-in service (section 5) STRATO GmbH, Berlin Germany

We do not use a content delivery network ourselves. Fonts are loaded from our own server, not from a third party.

For context: the app, database, sign-in, uploaded files, e-mail delivery and analytics run on these servers in Germany. For individual, clearly defined functions, data is also transmitted to third parties — to Anthropic for the AI features (section 8), to OpenStreetMap and OpenSeaMap for the maps (section 9), to the push service of your browser manufacturer for notifications (section 10) and to Stripe for payment and invoicing (section 12). These transfers are described in the respective sections and summarised in section 13.


4. General information and mandatory information

Data protection

The operators of this Service take the protection of your personal data seriously. We treat your personal data confidentially and in accordance with the statutory data protection regulations and this privacy policy.

Please note that data transmitted over the internet (e.g. by e-mail) may have security gaps. Complete protection of data against access by third parties is not possible.

Retention periods

Unless a more specific retention period is stated in this privacy policy, your personal data remains with us until the purpose of processing no longer applies. If you make a justified request for erasure or withdraw consent, your data will be deleted unless we have other legally permissible reasons for keeping it (e.g. retention periods under tax or commercial law); in that case it is deleted once those reasons cease to apply.

The specific retention periods at a glance:

Category of data Retention period
Account data and profile details Until the account is deleted; deletion takes effect immediately (exceptions: see "Deleting your account")
Health and crew-list details Until you change or delete them or withdraw your consent, at the latest with the account
Record of your consent to health details (time, version and language of the text, time of withdrawal if any) Until the account is deleted; it is deleted with the account
Trip, crew and kitty data, logbook, polls, events Until the trip is deleted. If you delete your account, your entries in shared trips remain without your name
Uploaded files (photos, documents, receipts, profile pictures) Until deleted by the users or with the trip; documents and profile picture also with the account
Location data (tracks, positions) Until deleted by the users or with the trip
Results of the AI features (cruising-area info, trip recap) Until regenerated, at most until the trip is deleted
AI usage counters (no content) Lifetime of the trip
E-mail address from a crew invitation Until the person joins, at most until the placeholder or the trip is deleted
Invitations to an organisation (e-mail address) Until the organisation is deleted
Addresses for push notifications Until you switch notifications off or the push service reports the address as invalid, at the latest with the account
Record of consent to the terms and this privacy policy IP address and browser identifier: 6 months; the record itself: 3 years after use ends
Record of the withdrawal consent 3 years from the end of the year of the order
Contract confirmations sent (§ 312f BGB) and cancellation declarations with their confirmation of receipt (§ 312k BGB) 6 years from the end of the calendar year in which they were created (business letters, § 257 HGB, § 147 AO)
Purchase records in the app (which trip pass or subscription, amount, time) Indefinitely; after your account is deleted, without reference to you
Invoices and payment receipts At Stripe, for as long as commercial and tax retention obligations require (§ 147 AO, § 257 HGB, § 14b UStG)
Feedback 2 years
Support requests by e-mail Until resolved, then at most 3 years (limitation period)
Server log files Website: 6 weeks (at STRATO, IP address shortened); app: at most 90 days
Analytics statistics (Umami) 12 months
Database backups up to 56 days (see below)

Backups

We back up the Service's database regularly. Deleted data remains in these backups until they are deleted after 56 days at the latest (daily backups after 14 days, weekly ones after 8 weeks); until then we use them only to restore the Service after a failure. Uploaded files are not covered by this backup (see section 11).

General information on the legal bases of processing

Where you have consented to processing, we process your personal data on the basis of Art. 6(1)(a) GDPR, or Art. 9(2)(a) GDPR where special categories of data under Art. 9(1) GDPR are processed. Where you have expressly consented to the transfer of personal data to third countries, processing is also based on Art. 49(1)(a) GDPR. Where processing is necessary to perform a contract or to take pre-contractual steps, we process your data on the basis of Art. 6(1)(b) GDPR. Where processing is necessary to comply with a legal obligation, it is based on Art. 6(1)(c) GDPR. Processing may also be based on our legitimate interest under Art. 6(1)(f) GDPR.

Withdrawing your consent

Many processing operations are only possible with your express consent. You can withdraw consent you have given at any time. The lawfulness of processing carried out before the withdrawal remains unaffected.

Right to object to data collection in special cases (Art. 21 GDPR)

WHERE PROCESSING IS BASED ON ART. 6(1)(E) OR (F) GDPR, YOU HAVE THE RIGHT AT ANY TIME TO OBJECT TO THE PROCESSING OF YOUR PERSONAL DATA ON GROUNDS RELATING TO YOUR PARTICULAR SITUATION. THE LEGAL BASIS FOR EACH PROCESSING OPERATION IS SET OUT IN THIS PRIVACY POLICY. IF YOU OBJECT, WE WILL NO LONGER PROCESS THE PERSONAL DATA CONCERNED UNLESS WE CAN DEMONSTRATE COMPELLING LEGITIMATE GROUNDS FOR THE PROCESSING WHICH OVERRIDE YOUR INTERESTS, RIGHTS AND FREEDOMS, OR THE PROCESSING SERVES THE ESTABLISHMENT, EXERCISE OR DEFENCE OF LEGAL CLAIMS.

Right to lodge a complaint with the competent supervisory authority

In the event of infringements of the GDPR, data subjects have the right to lodge a complaint with a supervisory authority, in particular in the member state of their habitual residence, their place of work or the place of the alleged infringement.

Competent supervisory authority for Schleswig-Holstein: Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein (ULD) Holstenstraße 98, 24103 Kiel, Germany https://www.datenschutzzentrum.de

Right to data portability

You have the right to have data that we process automatically on the basis of your consent or in performance of a contract handed over to you or to a third party in a common, machine-readable format. If you request direct transfer of the data to another controller, this is done only where technically feasible.

You can export part of it yourself: any crew member can download the kitty statement as CSV; the trip's organisers can export the crew list. With a trip pass, the logbook and statement are also available as PDF. Anything else we compile for you on request to the e-mail address above.

Access, correction and erasure

Within the applicable statutory provisions, you have the right at any time to free information about your stored personal data, its origin and recipients and the purpose of processing, and, where applicable, a right to correction or erasure of this data. You can change or delete most details yourself in the app.

Deleting your account

You can delete your account yourself at any time: Profile → at the bottom → "Delete account". Before you confirm, the app shows you what will happen. Alternatively, an informal message to the e-mail address above is enough.

  • Deleted: your profile, your health and crew-list details including the record of your consent to health details, your documents including the files, your profile picture, your personal templates, your notification devices, your memberships in organisations and your account with the sign-in service. A running Plus subscription ends immediately. Trips and organisations in which nobody but you has an account are deleted together with their content.
  • Your entries in shared trips remain — kitty expenses, logbook entries, photos, comments and poll votes — so that the others' accounts and records stay correct. They then appear as "Former crew member", without a name and without a link to you.
  • Kept without reference to you: purchases (a trip pass stays valid for the crew), AI usage counters, feedback texts, the record of the withdrawal consent, and contract confirmations and cancellation declarations — each until the end of the period stated in the table. A cancellation submitted through the form without signing in contains the details you entered there (name, e-mail address); they are kept as part of the declaration until the end of the period.
  • The record of your consent to the terms and this privacy policy is kept together with your identifier at the sign-in service (see section 5), because its purpose is to show what was agreed.
  • If you are the only organiser of a trip with other crew, or the only admin of an organisation with other members, you must hand over that role first.

Deleted data disappears from the backups after 56 days at the latest.

Right to restriction of processing

You have the right to request that the processing of your personal data be restricted. You can contact us about this at any time. The right to restriction applies in the following cases:

  • If you dispute the accuracy of your personal data stored by us, we usually need time to check this. For the duration of the check you have the right to request restriction.
  • If the processing of your personal data was/is unlawful, you can request restriction instead of erasure.
  • If we no longer need your personal data but you need it to exercise, defend or establish legal claims, you have the right to request restriction instead of erasure.
  • If you have lodged an objection under Art. 21(1) GDPR, your interests and ours must be weighed. As long as it has not been determined whose interests prevail, you have the right to request restriction.

If you have restricted the processing of your personal data, this data may — apart from being stored — only be processed with your consent or for the establishment, exercise or defence of legal claims, for the protection of the rights of another natural or legal person, or for reasons of important public interest of the European Union or a member state.

SSL/TLS encryption

For security reasons and to protect the transmission of confidential content, this Service uses SSL/TLS encryption.


5. Data collection in the app

Registration and sign-in

Sign-in to Sailto runs through a central sign-in service that we operate ourselves on our server in Germany (Keycloak at auth1.kilo-moana.com). It manages your e-mail address, your name and the security credentials needed to sign in; only the sign-in service knows your password, Sailto itself never receives it. Sign-in uses a standard protocol (OpenID Connect). After you sign in successfully, Sailto creates a profile that is linked to your identity at the sign-in service by an identifier. We take over your e-mail address, your name and whether the e-mail address has been confirmed.

Name and e-mail address are mandatory for an account. Without them no account can be created. The data entered at registration is processed in order to perform the user relationship (Art. 6(1)(b) GDPR).

So that we can tell whether an account is still in use, we store a timestamp of the last access, updated at most once an hour (Art. 6(1)(f) GDPR). We also store the language you chose.

Minimum age: Sailto is intended for people aged 16 and over. Younger crew members are added by the organiser as placeholders without an account of their own.

Record of your consent to the terms and this privacy policy

We store your consent to the terms and conditions and to this privacy policy as a record in our database: your identifier at the sign-in service, document and version, time, IP address and browser identifier (user agent). Your account at the sign-in service additionally carries a note of the versions you accepted (e.g. agb:v6).

The legal basis is Art. 6(1)(c) GDPR (accountability) and Art. 6(1)(f) GDPR (evidence against claims). We remove the IP address and browser identifier after 6 months. We delete the record itself 3 years after use ends; until then it is kept even after your account has been deleted.

Crew profile

In your crew profile you can voluntarily add further details: telephone number, profile picture, sailing licences and radio certificate, experience and preferred cruising areas, skills and swimming ability, dietary habits, allergies and intolerances, food dislikes, drink preferences including whether you drink alcohol, emergency contact, cabin preference, a snoring flag and learning goals.

For the crew list the charter company requires, you can also store your first and last name, gender, date and place of birth, place of residence, nationality and the type, number and expiry date of your ID document. For emergencies on board you can add health details: pre-existing conditions, medication (including where it is stowed) and emergency measures.

The only mandatory field is the name. The legal basis is Art. 6(1)(b) GDPR, for the health details your consent (see below).

Special categories of personal data: details of allergies, intolerances and dietary habits as well as the health details for emergencies may allow conclusions about your health — dietary habits (such as halal or kosher) also about your religion — and are therefore special categories within the meaning of Art. 9(1) GDPR. These details are voluntary. Before you enter them for the first time, we ask for your explicit consent in your profile (Art. 9(2)(a) GDPR): directly above the fields, a separate text explains what we use the details for, who sees them, and that details of allergies, intolerances and dietary habits are transmitted without your name to Anthropic in the USA when a crew member starts the meal planner (section 8). You confirm it with a separate checkbox that is not pre-ticked; only then can the fields be filled in. As a record we store the time, version and language of the text. Without your consent we do not store any such details. You can withdraw your consent at any time in your profile; we then delete your health details. The lawfulness of processing carried out until then remains unaffected (Art. 7(3) GDPR). We keep the record itself, with the time of withdrawal, until your account is deleted, because it shows that processing up to that point was lawful.

If you entered health details before this consent was introduced in October 2026, nobody but you sees them until you consent, and they are not passed to the meal planner. The next time you open your profile, we ask whether you want to consent or delete the details.

Visibility: only members of your trips see your profile details. By default, health details and crew-list data are visible only to the organisers; you can also release them to co-skippers or the whole crew. You also decide in your profile who sees your allergies. Others see health details only while your consent is in place. The crew of your trips sees your dietary habits. Nobody but you sees personal packing lists unless you share them with the crew.

Invitation links: anyone holding a trip's invitation link sees — before joining and without signing in — the trip's name, cruising area and dates and the crew's display names, and for trips of an organisation also its logo and welcome text. Share the link only with people who are meant to sail. Beyond that, Sailto has no publicly accessible content.

Location data

If you allow your browser to access your location, you can record the track sailed; positions are stored with a timestamp and are visible to the trip's crew. Logbook entries and events may carry a position.

When you upload a photo, your browser reads the location and time it was taken from the file so that the photo can appear on the map. We remove the remaining embedded metadata (EXIF) from the stored file.

The legal basis is Art. 6(1)(b) GDPR. You can withdraw location access in your browser at any time.

Data entered by other people (Art. 14 GDPR)

Whoever organises a trip can create placeholders for crew members and record trip data that also concerns other people — such as kitty expenses, cabin assignments, logbook entries or uploaded documents and photos. Such data then does not come from you but from other members of the trip.

Invitations by e-mail: if someone invites you to a trip or an organisation by e-mail, we store your e-mail address with the placeholder or the invitation and send you the invitation link. Invitations to an organisation expire after 14 days. You only become a member once you accept.

The legal basis is our legitimate interest in providing the Service you are using together with others and the organiser's legitimate interest in planning the trip (Art. 6(1)(f) GDPR). The person entering the data is responsible for doing so lawfully; you can object to the processing under section 4 and request erasure.

Test access

For press, clubs and agencies we create test access. These are trips with invented sample data; the crew placeholders in them are fictitious and do not concern real people. Anyone joining through the invitation link of a test access signs in with their own account. A test access is time-limited (normally 30 days, at most 90 days); we delete expired test access together with its content.

Feedback

Using "Give feedback" you can send us your comments. We store your message, the optional rating and category, the page you are writing from, your language setting, your browser identifier, the app version and — if you name it and are a member — the trip, together with your account so that we can follow up. We are notified of new feedback by e-mail. From time to time the app points out this option; when it may do so again is stored with your profile.

The legal basis is Art. 6(1)(f) GDPR (improving the Service). We delete feedback after 2 years. If you delete your account before then, the text remains until that time without any reference to you.

E-mails from the app and the sign-in service

We send e-mails through the mail server of STRATO GmbH (section 3):

  • from the sign-in service: confirmation of your e-mail address and password reset,
  • invitations to a trip or an organisation, to the address given by the person inviting,
  • after a purchase, a contract confirmation with the order details, the full text of the terms and of the withdrawal information, and your declarations on the immediate start of performance (§ 312f BGB),
  • after a cancellation, a confirmation of receipt and, if the date was not yet known on receipt, a second e-mail with the date on which the cancellation takes effect,
  • to us: notifications about new feedback.

We do not send advertising e-mails or a newsletter. The legal basis is Art. 6(1)(b) GDPR, for contract and cancellation confirmations Art. 6(1)(c) GDPR, for invitations Art. 6(1)(f) GDPR.

Server log files

Website sailto.app: When the website is accessed, our host STRATO automatically logs browser type and version, operating system, referrer URL, time and the IP address. STRATO partly replaces the IP address with a hash value already when logging; the hash stays the same for at most 24 hours, and STRATO shortens the host name to its domain part. The logs are available to us for six weeks and serve security and troubleshooting only.

App app.sailto.app: We do not write access logs containing IP addresses. The app's services keep operational and error logs; in individual cases they may contain an IP address, for example for a rejected connection attempt. We delete these logs after 90 days at the latest.

This data is not combined with other data sources. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is the secure and error-free operation of the Service.

Contact by e-mail

If you send us enquiries by e-mail, your details, including the contact details you provide, are stored by us for the purpose of handling the enquiry and in case of follow-up questions. We do not pass this data on without your consent. The legal basis is Art. 6(1)(b) GDPR if your enquiry relates to a contract, otherwise Art. 6(1)(f) GDPR. We keep the enquiry until it is resolved and then for at most 3 years.


6. Cookies and browser storage

We only set what is needed for operation or what you set yourself (§ 25(2) no. 2 TDDDG):

What Where Purpose Duration
Sign-in and security cookies app.sailto.app Your session, protection against forged requests, a secure sign-in flow Session or until you sign out
Cookies of the sign-in service auth1.kilo-moana.com Sign-in and sign-in session Session or until you sign out
sailto_locale app.sailto.app Your language choice 1 year
Browser local storage app.sailto.app Display settings such as sorting, whether you have closed hints or the introduction, hand-over during sign-in Until you clear it; parts only until the tab is closed
App shell in the browser cache app.sailto.app So that the app starts without a connection and shows a notice page; content of your trips is not stored there Until the next app version

We do not set advertising or tracking cookies. On Stripe's payment page, Stripe's information applies (section 12).


7. Analytics

Umami (self-hosted)

On the website sailto.app and in the app app.sailto.app we use Umami, open-source analytics software. We run it ourselves on our virtual server at STRATO GmbH in Germany; website and app are analysed separately. The data collected does not leave this server, is not passed on to third parties and is not transferred to third countries. We do not use an external analytics provider such as Google Analytics.

Umami sets no cookies and stores nothing on your device. For each page view it records: the address visited, the previous page (referrer), country, region and city (derived from the IP address on our server), browser, operating system, device type, screen resolution and browser language. In addition, we count how often individual buttons and links are used — for example switching to the app, downloading a template, creating a trip or joining through an invitation link. Only the event is counted, not who triggered it.

In the app we shorten addresses before they are even sent. App addresses contain identifiers — an invitation link is itself the key to a trip. Only the page pattern is therefore stored, not the actual address: a trip page becomes /trip/[tripId], an invitation link /join/[token]. We also strip appended parameters; only campaign tags such as utm_source and ref and via are kept. The statistics therefore do not show which trip, organisation or invitation was accessed.

To group visits by the same browser, Umami derives a non-reversible hash from your IP address, the browser identifier and a secret value that changes every calendar month. Your IP address itself is not stored. Visits by the same browser can thus be matched within a calendar month, but not beyond it or across other websites. We do not build user profiles and do not link the statistics to your account.

The legal basis is our legitimate interest in data-minimising statistical analysis (Art. 6(1)(f) GDPR). The tracking script stores nothing on your device. It only checks whether you have switched measurement off in your browser — through the "Do Not Track" setting or through an entry umami.disabled in local storage, which only you set yourself. We therefore consider that no consent under § 25 TDDDG is required and do not show a consent banner.

If your browser has "Do Not Track" enabled, no measurement takes place. Regardless of this, you can object to the processing at any time under section 4. We delete the statistics after 12 months.


8. AI features (Anthropic)

Three Sailto features use a large language model: the meal planner, the cruising-area info and the narrated trip recap. They are only available with a trip pass, Sailto Plus, in trips of an organisation with a subscription or in a test access, and they only run when a crew member actively triggers them. Any crew member can start the meal planner and the recap; cruising-area info can be requested by the trip's organisers.

Provider: our contractual partner is Anthropic Ireland, Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland; processing is also carried out by Anthropic PBC, 548 Market St, PMB 90375, San Francisco, CA 94104, USA. Anthropic processes the data as a processor under a contract pursuant to Art. 28 GDPR (Data Processing Addendum, part of the Commercial Terms).

What is transmitted:

Feature Data transmitted
Meal planner Number of crew members with an account, cruising area, trip length and the meals requested; from the crew profiles dislikes, drink preferences and how many people drink alcohol; from crew members who have consented to the processing of their health details, also the dietary habits (as counts, e.g. "2 vegetarians") and allergies and intolerances; plus whatever you type into the additional-wishes field. Profile details are sent without names and without being attributed to individuals. The planner takes into account the details of everyone who has consented, even if someone has restricted who sees their allergies in the crew list. The person planning is told, as a number and without names, how many crew members have not consented.
Cruising-area info Name, type (e.g. marina, anchorage) and coordinates of the route stop. To find current information, the model runs web searches through Anthropic's search tool; it forms the search terms from these details.
Trip recap Name, cruising area and dates of the trip, crew size, nautical miles, places visited and longest passage, and the logbook entries (date, place, miles, wind, title and text). Logbook entries are free text and may contain names if the crew writes them in.

No account data, e-mail addresses, payment data, emergency health details, ID data, documents or photos are transmitted to Anthropic.

Legal basis: Art. 6(1)(b) GDPR (providing the service purchased). Where details of allergies and intolerances are transmitted, this is based on your consent under Art. 9(2)(a) GDPR, which you give explicitly in your profile and can withdraw at any time (see section 5). Without your consent we do not transmit any of your health details.

Third-country transfer: processing may take place in the USA. It is based on the European Commission's standard contractual clauses under Art. 46(2)(c) GDPR, which are part of the contract with Anthropic.

Retention at Anthropic: according to Anthropic, inputs and outputs are deleted within 30 days. If Anthropic's automated safety systems classify a request as a violation of its usage policy, Anthropic may keep inputs and outputs for up to 2 years and the classification for up to 7 years; longer retention is also possible where required by law.

No use for model training: under the contract, Anthropic may not use content transmitted through the programming interface to train its models. We do not use your content for training either.

Storage on our side: for each request we store that it took place (trip, triggering account, feature, time) to check quotas. Cruising-area info and the trip recap are stored with the trip and visible to its crew, the recap together with the name of the person who generated it. Meal-planner results are stored only if you adopt them, e.g. into the shopping list. We do not store the requests themselves.

More information: https://www.anthropic.com/legal/privacy


9. Maps (OpenStreetMap, OpenSeaMap)

OpenStreetMap

In a trip's map view and for logbook entries with a position, we load map tiles from OpenStreetMap (tile.openstreetmap.org). The provider is the OpenStreetMap Foundation, St John's Innovation Centre, Cowley Road, Cambridge, CB4 0WS, United Kingdom.

Your IP address is transmitted to the servers delivering the tiles; this is technically necessary for the tiles to reach your browser. The OpenStreetMap Foundation delivers the tiles through a worldwide network of cache servers operated by a provider it has engaged (content delivery network); which server responds is determined by that network — it may be a server outside the EU. We have no influence on further processing.

More information: https://osmfoundation.org/wiki/Privacy_Policy

OpenSeaMap

In the map view we also overlay seamarks from OpenSeaMap (tiles.openseamap.org). For this your browser loads tiles from that server, transmitting your IP address to its operator. According to its imprint, the provider of openseamap.org is Olaf Hannemann, Dorfstraße 17, 23847 Stubben, Germany. The overlay is on by default and can be switched off in the map view with the "Seamarks" switch.

Common information

What is transmitted: When a tile is loaded, the respective provider receives what any web server receives with a request: your IP address, date and time, browser identifier (user agent) and the address of the requested tile. The tile address shows which map section you are looking at. We do not pass on any further information to the providers, in particular neither names nor trip data; to our knowledge the tile servers do not set cookies.

Providers' own responsibility: The OpenStreetMap Foundation and the operator of OpenSeaMap process this data under their own responsibility; they are not our processors, and there is no processing agreement. The OpenStreetMap Foundation is based in the United Kingdom, for which an adequacy decision of the EU Commission exists (Art. 45 GDPR); it is itself responsible for servers of its content delivery network outside it.

Legal basis and balancing: The legal basis is our legitimate interest in a working map display (Art. 6(1)(f) GDPR). A map without map tiles does not exist, and for sailing areas the seamarks are the essential content. This is set against a small burden: only technically necessary connection data is transmitted, only when you yourself open a map view or a logbook with located entries, and we link it with nothing. Consent under Section 25 TDDDG is not required because nothing is stored on or read from your device for this beyond loading the displayed tile.

Your choice: You can switch off the seamark layer in the map view with "Seamarks"; then no requests go to OpenSeaMap. If you do not want to load any map tiles at all, do not open the map view and logbooks with positions — all other features remain available. You can object to the processing under Art. 21 GDPR (section 4).


10. Push notifications

You can allow Sailto to send you notifications — for example about new polls, expenses or calendar entries. This only happens if you expressly grant permission in your browser.

Technically, delivery runs through the push service of your browser or device manufacturer (Google, Apple, Mozilla or Microsoft). When setting up, your browser creates an address with this service, which we store together with the browser identifier (for the device list in your profile) so that we can deliver messages to you. The content of the messages is encrypted; the push service learns that and when a message is delivered to your device, but not its content. Depending on the manufacturer, delivery may run through servers outside the EU.

The legal basis is your consent (Art. 6(1)(a) GDPR and § 25(1) TDDDG for storage on your device). If you switch notifications off in the app, we delete the stored address immediately. If you only withdraw permission in your browser, we delete it as soon as the push service reports it as invalid, at the latest with your account.


11. Uploaded files

In Sailto you can upload files: profile pictures, trip photos, receipts for expenses, documents such as charter contracts, proof of insurance and licences, photos taken at the charter handover, and organisation logos.

These files are stored on our server in Germany and are delivered only through protected addresses: without signing in and without membership of the trip concerned, no file can be retrieved. The only exception is an organisation's logo, which appears on its invitation pages (section 5). There are no publicly accessible storage locations. When storing photos we remove their embedded metadata (section 5, "Location data").

When a trip is deleted, its files are deleted with it. If you delete your account, your documents and profile picture are deleted; photos you shared in shared trips remain there (section 4, "Deleting your account").

Please note: before uploading, consider who should see the file — all members of the trip concerned have access. Of ID documents, upload only what the charter company actually requires. Uploaded files are currently not included in a separate backup; please keep your own copies.

The legal basis is Art. 6(1)(b) GDPR (providing the Service), for documents of third parties additionally Art. 6(1)(f) GDPR.


12. Payment, invoicing and contract confirmation

Stripe

We use Stripe as our payment service provider. For customers in the EEA the provider is Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland; the parent company is Stripe, Inc., 510 Townsend Street, San Francisco, CA 94103, USA.

When you purchase a paid service, we transmit to Stripe your name or the name of your organisation, your e-mail address and an internal identifier of your account. You enter your payment details (e.g. bank account or credit card number) directly with Stripe; they never reach our servers. Stripe sends us a customer identifier, the payment status and the receipt data.

Invoices and tax: Stripe creates invoices on our behalf and makes them available to you. To calculate VAT (Stripe Tax), Stripe records the billing-address details needed for this at checkout (at least the country, for organisation plans the full address) and — if you buy as a business and provide it — your VAT identification number. In Stripe's customer portal you can change these details and manage or cancel your subscription.

The legal basis is Art. 6(1)(b) GDPR (performance of the contract), for invoice and tax data Art. 6(1)(c) GDPR (tax obligations), and Art. 6(1)(f) GDPR (secure payment). Where data is transferred to the USA, Stripe relies on standard contractual clauses under Art. 46(2)(c) GDPR.

More information: https://stripe.com/privacy

Record of the withdrawal consent

Before a paid purchase we ask you for two confirmations under § 356(5) BGB (immediate performance and acknowledgement that you lose your right of withdrawal). For this we store which version of the withdrawal information was shown to you, in which language, which order it belonged to and when. The legal basis is Art. 6(1)(c) GDPR in conjunction with our obligation to provide evidence. We delete the record 3 years after the end of the year in which you ordered (end of the regular limitation period).

Contract and cancellation confirmation

After a purchase we send you a contract confirmation by e-mail with the order details, the full text of the terms and of the withdrawal information, and your declarations on the immediate start of performance; after a cancellation, a confirmation of receipt and, where applicable, a second e-mail with the effective date (section 5, "E-mails from the app"). As a record we store the text of the e-mails sent, the delivery status and the time, and for a cancellation also which contract was cancelled and when. If you cancel through the form without signing in, we additionally store your name, the e-mail address you entered, your further details on the contract and a hash of your IP address — not the IP address itself. We use the hash only to limit the number of confirmation e-mails and delete it after one day; we accept your cancellation in any case.

The legal basis is Art. 6(1)(c) GDPR (§ 312f BGB, § 312k BGB, retention obligations under § 257 HGB and § 147 AO). Contract confirmations and cancellations are business letters: we keep them for 6 years from the end of the calendar year in which they were created and delete them afterwards.


13. Recipients and third-country transfers at a glance

Recipient Purpose Location Basis of the transfer
STRATO GmbH Hosting, e-mail delivery (section 3) Germany Processing on our behalf (Art. 28 GDPR)
Anthropic Ireland, Limited / Anthropic PBC AI features including web search (section 8) Ireland / USA Processing on our behalf; standard contractual clauses (Art. 46 GDPR)
Stripe Payments Europe, Ltd. / Stripe, Inc. Payment, invoicing, tax calculation (section 12) Ireland / USA Standard contractual clauses (Art. 46 GDPR)
OpenStreetMap Foundation and its CDN provider Map tiles (section 9) United Kingdom; delivering servers worldwide Adequacy decision for the United Kingdom (Art. 45 GDPR); for servers outside the EU, the provider's safeguards
Operator of OpenSeaMap Seamark tiles (section 9) Germany —
Push service of the browser manufacturer (Google, Apple, Mozilla, Microsoft) Delivery of notifications (section 10) depends on the manufacturer Consent (Art. 49(1)(a) GDPR) or the provider's safeguards

Hosting, database, sign-in service, file storage, e-mail delivery and analytics take place exclusively on servers in Germany.


14. Necessity of providing data (Art. 13(2)(e) GDPR)

Providing certain personal data is necessary to conclude a contract and use the Service:

  • At registration (mandatory): name and e-mail address. Without them no account can be created and the Service cannot be used.
  • For paid services: the details Stripe requires for payment and invoicing, including billing-address details. Without them the payment cannot be made.

All other details — in particular licences, dietary habits, allergies, health details, ID data, emergency contact, cabin preference, the snoring flag and your location — are voluntary. Not providing them has no effect on the use of the core features; without ID data you are merely missing from the exported crew list for the charter company.


15. Automated decision-making / profiling (Art. 13(2)(f) GDPR)

We do not use automated decision-making, including profiling, under Art. 22 GDPR that produces legal effects concerning you or similarly significantly affects you.

The results of the AI features (section 8) are suggestions without legal effect — a meal plan, a cruising-area tip or a recap. The crew reviews them and adopts or discards them. Decisions concerning you as a user are made by people.


16. Changes to this privacy policy

We reserve the right to amend this privacy policy so that it always meets current legal requirements or to reflect changes to our services. The new privacy policy then applies to your next visit. If the version changes, the app asks you for your consent again.

The binding version is the German privacy policy.

As at: 12 October 2026 — Applies to: Sailto (https://sailto.app)