Privacy Policy
Last updated: September 2026 · covers the SkillSea app and this website (skillsea.app)
1. Who is responsible
Rupert Ramsl, C/ Sindicat 69, 8º – E, 07002 Palma, Spain — rupertramsl@outlook.com. See also the Legal Notice and the Terms of Use.
2. The SkillSea app
SkillSea connects sailors: you can publish your skills and tools, optionally share your location, ask for help, and message other sailors. We collect only what these features need.
Account and profile
- Email address and password to sign in. The password is stored only as a salted hash by our authentication provider — we cannot read it.
- Display name, optional bio and profile photo, your chosen language, and your account type (sailor or business).
- Skills, tools and boat details you enter (for example boat name, type, dimensions, equipment, photos, and optionally MMSI or call sign). These are shown to other SkillSea users on your profile.
Location — only if you choose
- Location sharing is opt-in. You choose whether to share an approximate or exact position, who can see it, and how long it is shared. You can stop at any time.
- When you create a help request, its location is stored with the request and shown to nearby sailors who have the matching skill.
- Place notes (private notes pinned to a place) are visible only to you. Float plans and their stops are shared only as you configure, including optional share links.
- Your device location is requested only when you tap a location feature. The app does not track you in the background.
Content you create
Messages, help requests and their status, questions and answers, who you follow or block, and “coints” (community credits) you give or receive. Messages are visible to the people in that conversation; questions and answers are visible to other users of the app.
Push notifications
If you allow notifications, we store your device’s push token and platform so we can notify you about new messages, accepted message requests and nearby help requests. Notifications are delivered through Google Firebase Cloud Messaging. You can turn notifications off in your device settings.
Subscription
Pro subscriptions are processed by Apple or Google. We use RevenueCat to manage subscription status, linked to your account ID. We never see your payment card details.
Crash reports
If the app crashes, it can send a crash report through Google Firebase Crashlytics: the error and stack trace, device model, operating system version, app version and a Firebase installation ID. It contains no messages, location or profile content. This is on by default in release builds and you can switch it off any time in the app under Profile → “Send crash reports”. We use it on the basis of our legitimate interest in fixing bugs (Art. 6(1)(f) GDPR).
Maps and technical data
Map tiles are loaded from OpenStreetMap and OpenSeaMap servers, which therefore receive your IP address and the map area you view. Our hosting and backend providers process technical data such as IP addresses and request logs to operate and secure the service. The app contains no advertising and no analytics or tracking tools.
3. This website
- The “Get notified” waitlist form: if you submit it, we store the email address you enter, the date and time, and whether we have already sent you the launch notice. Every email we send you includes an unsubscribe link that removes your address in one click.
- An anonymous page-view log: page path, referring page (if any), timestamp, and how long you stayed and how far you scrolled. It is not tied to your email, IP address or any other identifier, and we use no cookies or third-party tracking scripts.
4. Why we process it (legal bases, GDPR)
- Providing the app you asked for — account, profile, messaging, help requests, subscription (Art. 6(1)(b)).
- Your consent — location sharing, push notifications, and the waitlist (Art. 6(1)(a)). You can withdraw consent at any time; this does not affect earlier processing.
- Legitimate interests — keeping the service secure, preventing abuse and handling reports, and counting website visits (Art. 6(1)(f)).
5. Who else sees it
Other users see what you choose to share, as described above. We also use these processors under data processing agreements:
- Supabase — database, authentication, file storage and server functions. Our project runs in the EU (Stockholm).
- Google (Firebase Cloud Messaging and Crashlytics) — push notification delivery and crash reports.
- RevenueCat — subscription status.
- Apple and Google — app stores and payment processing.
- Resend — sending emails such as the waitlist confirmation.
- Netlify — hosting this website.
- OpenStreetMap / OpenSeaMap — map tiles (see above).
Some of these providers are based in or transfer data to the United States. Such transfers rely on the EU Standard Contractual Clauses and/or the EU–US Data Privacy Framework. We don’t sell your data or share it with anyone else.
6. How long we keep it, and deleting your account
We keep your data while your account exists. You can delete your account yourself in the app (Profile → Delete account). When you do:
- Deleted: your bio and profile photo, boat details and photos, skills, tools, place notes, shared positions, float plans, follows, blocks, business profile, and push tokens.
- Anonymized, not deleted: messages, help requests, questions and answers, and coint transactions stay so other users’ conversations and history remain intact. They are shown as coming from “Deleted sailor”. If you want specific message content removed, contact us and we will review it.
- Your login is disabled and your email address is removed from the account.
- Copies may remain in encrypted backups for a limited period before being overwritten.
Waitlist entries are kept until the app launches and a reasonable period after, or until you ask us to delete yours. Website page-view counts are kept up to 12 months.
7. Your rights
Under GDPR you can ask us to access, correct, delete, restrict or export your data, object to processing based on legitimate interests, and withdraw consent at any time. Email rupertramsl@outlook.com. You can also lodge a complaint with your local data protection authority (in Spain: the AEPD).
8. Children
SkillSea is not intended for anyone under 16 and we do not knowingly collect their data. If you believe a child has registered, contact us and we will delete the account.
9. Changes
If we change how we handle data, we will update this page and, for material changes, tell you in the app before they take effect.