Privacy policy
This is a courtesy translation. In case of any discrepancy, the German version is authoritative. Read the German version
This privacy policy applies to the Bordcrew app (iOS and Android) and to the website bordcrew.app.
1. Controller
The controller within the meaning of the GDPR is:
Kai Wolfram
Schönbachstrasse 63g
04299 Leipzig
Email: support [at] bordcrew.app
No data protection officer has been appointed because the legal requirements for doing so are not met. Please send any data protection questions to the address above.
2. Purposes of processing and legal bases
Bordcrew processes personal data only to the extent necessary to provide the app's features - trip planning, crew coordination, route planning, logbook, chat and tracking. The legal basis is Art. 6(1)(b) GDPR (performance of a contract) and, in addition, Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation).
For optional services - Firebase Analytics and GPS background tracking - processing only takes place after explicit consent (Art. 6(1)(a) GDPR). Push notifications are likewise only sent with consent.
No automated individual decision-making, including profiling, takes place. Special categories of personal data within the meaning of Art. 9 GDPR are not processed.
Our principle: Bordcrew is funded by its paid plans, not by your data. We do not sell personal data, show no advertising and create no advertising or usage profiles across different services.
3. Website access and hosting
When the website bordcrew.app is accessed, technically necessary connection data is processed - in particular the IP address, date and time of access, the URL requested, the referrer, and the browser type and operating system. This data is used to deliver the content and to keep the service secure.
Hosting is provided by IONOS SE, Elgendorfer Straße 57, 56410 Montabaur, Germany. Processing takes place in Germany or the EU.
The legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation of the online service).
Language cookie
If you choose a language using the language switcher (DE | EN) in the header of the website, the website stores the cookie bordcrew_lang in your browser. It contains only the language you have chosen (de or en) and is used to show you the home page in that language on your next visit. The cookie is only set after you click the language switcher, not when you simply open the website.
The cookie contains no personal data and is not used for advertising, analytics or tracking purposes. It is stored for 12 months, after which your browser deletes it automatically. You can delete it at any time in your browser settings. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in showing the website in the language you have chosen). Storage on your device is based on § 25(2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act), as it is strictly necessary for the language choice you have expressly requested.
Contact form
When you write to us using the contact form on the Contact or About pages, we process your first name, your email address, the subject and your message in order to answer your enquiry. The message is delivered via the mail server of our host IONOS to support [at] bordcrew.app; your email address is set as the reply-to address. To protect against automated spam, the form checks a field that is invisible to people and the time until submission; no additional data is stored for this.
The legal basis is Art. 6(1)(b) GDPR where your enquiry concerns the use of Bordcrew, otherwise Art. 6(1)(f) GDPR (legitimate interest in answering enquiries). We do not use any analytics, tracking or advertising services on the website itself.
4. Categories of data processed
Trip data: trip name, travel dates, region, yacht and booking details, crew list (name, role), tasks, route and stage details, provisions and packing lists, the kitty for shared expenses and expense entries, chat messages, logbook entries, GPS tracks, uploaded files and invitation and sharing information (e.g. invitation links).
Profile data: display name, email address and - if provided - a profile picture. When signing in with Apple or Google, the display name and profile picture may be taken from the respective account.
Sensitive crew data: for crew lists and registrations with a harbour or charter company, the following details can be stored - for yourself as well as for crew members: title, first name and surname, date of birth, place of birth, country of birth, nationality, passport or ID card number and its expiry date, telephone number and the address (street, house number, postcode, town). These details are stored encrypted with AES-256-GCM - only after explicit entry by the user, never collected automatically.
GPS location data: in the foreground (logbook entries), coordinates are recorded at the time of entry. In the background (track recording), continuous position data is recorded - only while the track function is active.
Authentication data: when registering with email and password, the email address and password are processed; the password is stored exclusively in encrypted (hashed) form with our processor Supabase and cannot be viewed by us in plain text. To confirm the registration, we send a verification email to the address provided. When signing in with an Apple ID or Google account, the email address and name from the respective account are processed.
Analytics and device data: with consent, Firebase Analytics collects anonymised app usage data (device type, operating system version, app events such as screen views and feature usage).
Push token: a device-specific token is stored to deliver push notifications.
Subscription and purchase data: when a paid storage subscription is taken out, a pseudonymous user ID (a random string that does not allow any conclusions about the person), the purchased product ID, the time of purchase, the end of the term and the status of the subscription are processed, as well as technical details about the device and store that the store supplies with the purchase. Name, email address and payment data are not processed in this context - payment is handled exclusively by Apple or Google. Data is only transmitted once the “Plan & storage” area is opened in the app or a subscription is taken out; if you never open this area, your data does not reach the subscription service provider.
Third-party data: if you enter details about other people (e.g. crew members), you may only do so if there is a legal basis for it and the data subjects concerned have been properly informed where necessary.
5. Map and geodata services
For map, route and location features (itinerary, nautical chart, place search and harbour and anchorage data), entered place names or coordinates are transmitted to external services, or their content is loaded into the app. In particular, the IP address may be processed by the respective provider:
- OpenStreetMap (map tiles, tile.openstreetmap.org) - OpenStreetMap Foundation
- OpenSeaMap (seamark tiles, tiles.openseamap.org)
- Nominatim (place search/geocoding, nominatim.openstreetmap.org) - OpenStreetMap Foundation
- Overpass API (harbour and anchorage data, overpass-api.de)
Depending on the provider's location, processing may also take place outside the EU or the EEA. The legal basis is Art. 6(1)(b) GDPR (provision of the requested features) and, in addition, Art. 6(1)(f) GDPR.
Weather services
For the weather features (point forecast and weather map), only the coordinates you have chosen (region or current position) are processed:
- MET Norway (point forecast) - retrieved server-side via a Supabase Edge Function proxy in the EU region Frankfurt; the device or client IP address is not passed on to MET Norway.
- DWD (Deutscher Wetterdienst) (weather map) - the map layers (WMS) are loaded directly from your device; in the process, your device IP address is transmitted to the DWD (a German public authority).
Sources and licences: the weather map uses geodata from the German Meteorological Service (Deutscher Wetterdienst, DWD) (CC BY 4.0 / GeoNutzV); the point forecast is based on data from MET Norway (CC BY 4.0).
The legal basis is Art. 6(1)(b) GDPR (provision of the requested features). If you optionally open the external services Windy or Windfinder from within the app, the chosen coordinates are transmitted to these third-party providers; their own privacy policies apply.
6. Recipients and third parties
Supabase (Supabase Ireland Limited, Dublin, Ireland): backend infrastructure for data storage and authentication. Server location: EU Frankfurt (AWS eu-central-1). A data processing agreement pursuant to Art. 28 GDPR is in place with Supabase.
Google Firebase Analytics (Google LLC, Mountain View, CA, USA): app analytics only after consent. Google processes anonymised usage data on the basis of the Google Data Processing Amendment.
Apple (Apple Inc., Cupertino, CA, USA): when signing in with an Apple ID, authentication data is forwarded via Apple.
Google OAuth (Google LLC, Mountain View, CA, USA): when signing in with a Google account, authentication data is forwarded via Google.
Expo (Expo Platform, Inc., San Francisco, CA, USA): sending of push notifications via the Expo Push Service. Technical delivery takes place via the Apple Push Notification service (APNs, iOS) or Firebase Cloud Messaging (FCM, Google LLC, USA - Android).
RevenueCat (RevenueCat, Inc., 1032 E Brandon Blvd #3003, Brandon, FL 33511, USA): management of in-app subscriptions taken out via the App Store and Google Play. RevenueCat verifies the purchase and tells us whether a subscription is active. A pseudonymous user ID, the product ID, the time of purchase, the end of the term and the status of the subscription are transmitted, as well as technical details about the device and store - but not name, email address or payment data. The legal basis is Art. 6(1)(b) GDPR (provision of the booked storage allowance). A data processing agreement pursuant to Art. 28 GDPR is in place with RevenueCat: RevenueCat's Data Processing Addendum is incorporated into its terms of service and has applied since registration on 10 August 2026. Privacy information: revenuecat.com/privacy
Apple and Google (payment processing) (Apple Inc., Cupertino, CA, USA; Google LLC, Mountain View, CA, USA): the purchase itself is handled exclusively via the App Store or Google Play. These companies are independently responsible for it; we receive no payment data and learn neither the name nor the payment method. The privacy information of Apple or Google applies.
Map and geodata services (OpenStreetMap Foundation, OpenSeaMap, Overpass API): transmission of place names/coordinates and the IP address to load map and geodata - see section 5.
Weather services (MET Norway, DWD (Deutscher Wetterdienst)): point forecast via MET Norway retrieved server-side via a Supabase Edge Function proxy in the EU region Frankfurt (without passing on the client IP); the weather map (DWD WMS layers), by contrast, is loaded directly from the device, which transmits the device IP address to the DWD (a German public authority). If Windy or Windfinder is optionally opened, the chosen coordinates are transmitted to these third-party providers - see section 5.
7. Transfers to third countries and safeguards (SCC)
Supabase processes data exclusively within the EU (Frankfurt) - no transfer to third countries.
Firebase Analytics, Firebase Cloud Messaging (FCM), Apple and Google are based in the USA. Data transfers to the USA take place on the basis of EU standard contractual clauses (Art. 46(2)(c) GDPR) and - where applicable - the EU-US Data Privacy Framework. Expo transfers push tokens to the USA on the basis of standard contractual clauses. For map and geodata services, data may be transferred outside the EU/EEA depending on the provider's location; where necessary, standard contractual clauses are used for this.
RevenueCat processes data in the USA. The transfer is based on the standard contractual clauses of the EU Commission (Art. 46(2)(c) GDPR), supplemented by a data processing agreement pursuant to Art. 28 GDPR.
8. Local storage on the device
The app stores technically necessary information locally on your device (e.g. display and selection states, drafts and the status of dismissed hint texts). This data remains on the device and is not used for advertising or tracking purposes. The legal basis is Art. 6(1)(b) or (f) GDPR.
9. Storage period
Trip-related data is stored until the user deletes it manually or closes the account. When the account is deleted, all personal data is deleted completely.
Firebase Analytics automatically deletes aggregated usage data after 14 months (Google default). Push tokens are removed on sign-out or account deletion.
The status of a storage subscription is stored for as long as the account exists - it determines how many photos can be stored. When the account is deleted, this data is deleted.
We keep enquiries sent via the contact form or by email until your matter has been dealt with and delete them afterwards, unless statutory retention obligations apply.
10. Data subject rights
As a data subject, you have the following rights: access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection to processing (Art. 21).
To exercise these rights: support [at] bordcrew.app
11. Right to withdraw consent
Consent given can be withdrawn at any time with effect for the future - without giving reasons.
Firebase Analytics: in the app under More → Tracking & analytics → Disable tracking.
GPS tracking: on iOS in Settings under Privacy & Security → Location Services → Bordcrew; on Android in the app settings under Permissions → Location.
Push notifications: on iOS in Settings under Bordcrew → Notifications; on Android in the app settings under Notifications.
12. Right to lodge a complaint with a supervisory authority
You have the right to lodge a complaint with a data protection supervisory authority. Competent authority (place of jurisdiction Leipzig, Saxony):
Saxon Data Protection Commissioner (Sächsischer Datenschutzbeauftragter)
Devrientstraße 5
01067 Dresden
www.datenschutz.sachsen.de
13. Account deletion
The account can be deleted completely at any time. All personal data - trip-related data, crew lists, chat messages, GPS tracks and authentication data - is irrevocably deleted.
Deletion in the app: Profile & personal data → Delete account. Alternatively by email: support [at] bordcrew.app
Ongoing subscription: a paid storage subscription exists between the user and Apple or Google and is not ended by deleting the account. It can only be cancelled in the App Store or on Google Play - otherwise it will continue to be billed. The app points this out before deletion and leads directly to the subscription management of the respective store.
14. Who sees what in a trip
Bordcrew is an app for the whole crew. What you add to a trip is therefore visible to the members of that trip, in particular:
- your display name, your profile picture and your role in the crew,
- chat messages, tasks, votes and lists of the trip,
- logbook entries, photos, routes and recorded tracks of the trip,
- entries in the kitty for shared expenses.
This content is not visible to people outside the trip, including other Bordcrew users. Your other trips are only seen by their respective crews. Please only add details about other people if you are entitled to do so.
15. Data security
Data is only ever transmitted in encrypted form (TLS) between the app, the website and the servers. The database is located in the EU (Frankfurt) and access is restricted to the authorised accounts in each case. Passwords are only stored as a hash. We adapt our technical and organisational measures to the state of the art.
16. Children and young people
Bordcrew is not aimed at children. An account may be created from the age of 16. If we learn that a younger person is using an account without the consent of their parents or guardians, we delete that account.
17. Changes to this privacy policy
We update this privacy policy when the app, the services used or the legal situation change. The version published here with the date shown is authoritative. We also announce significant changes in the app.
Last updated: November 2026