Version 1.0 | Prepared 13 September 2026
This notice explains how the individual operating the BOATARIDE pilot processes personal data. It is provided under Articles 13 and, where applicable, 14 of the General Data Protection Regulation. It is not a request for consent unless BOATARIDE expressly asks for consent for a specific optional purpose.
Scope. BOATARIDE is a free, limited-access pilot distributed by a forwardable direct link. It helps adults discover and contact people who may be travelling in the same direction by boat. It does not provide transport, bookings, payments or identity, skipper or vessel verification.
1 Controller and contact
The data controller is the individual identified in the BOATARIDE Legal Notice. The Legal Notice provides the controller's full legal name, geographic service address and monitored privacy contact. It must be completed and published before external users provide personal data.
Questions and requests concerning personal data should be sent through the privacy contact stated in the Legal Notice. BOATARIDE has not appointed a data protection officer because the current pilot does not involve processing that requires one.
2 Personal data processed
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Category Examples in the pilot
----------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Account and authentication User ID, first name, email address, authentication provider identifier, account status, login and security events.
Contact information Email address and/or telephone or WhatsApp number, selected contact method and contact-sharing confirmation.
Ride and request information Departure, destination, date, flexibility, preferred timing, group size, sailing experience, boat type or name, available places, passenger preferences, return possibility, notes and listing status.
Matching and connection activity Relevant journey or request IDs, match category, contact method selected and server-generated contact-click timestamp.
Legal records Terms version, Privacy Notice version, acceptance or acknowledgement time, account identifier and acceptance context.
Support and moderation Messages, complaints, reports, affected listing, evidence supplied, decisions and review history.
Technical and security data IP address, request time, device/browser information, session identifiers, error and security logs. BOATARIDE does not use these data for advertising or profiling.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Do not place health information, identity documents, exact meeting points or other sensitive personal information in free-text listing fields. BOATARIDE may remove unnecessary or unsafe information.
3 Purposes and legal bases
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Purpose Data and legal basis
----------------------------------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Provide accounts and member functions Account, authentication and contact data. Necessary to perform the user agreement and requested service, Article 6(1)(b) GDPR.
Publish, manage and match rides and requests Listing, ownership and matching data. Necessary to perform the requested service, Article 6(1)(b).
Enable direct contact Selected contact method, member identity and contact-click record. Necessary to perform the connection function requested by the user, Article 6(1)(b).
Send operational notifications Account, listing and match information. Necessary for requested service alerts or based on the legitimate interest in making active listings useful, Articles 6(1)(b) and 6(1)(f). Users can disable non-essential alerts.
Record legal acceptance Account identifier, versions and timestamps. Necessary to form and demonstrate the user agreement and for the legitimate interest in legal accountability, Articles 6(1)(b) and 6(1)(f).
Security and abuse prevention Technical logs, account events, reports and moderation information. Legitimate interests in protecting people and the Service, Article 6(1)(f), and legal obligations where applicable, Article 6(1)(c).
Respond to rights, complaints and authorities Account, support and legal records. Legal obligations, Article 6(1)(c), and establishment, exercise or defence of legal claims, Article 6(1)(f).
Understand the pilot Aggregated or minimised usage and connection counts. Legitimate interest in evaluating the free pilot, Article 6(1)(f). No advertising profiles are created.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BOATARIDE does not treat acceptance of the Terms as consent to unrelated data processing. If a future optional activity requires consent, it will be requested separately and can be withdrawn without affecting earlier lawful processing.
4 Information visible to others
Anyone who obtains the direct pilot link may search and view non-identifying cards without an account. Those cards may contain route, date or timing, boat type, available places, group size and other limited journey information. They must not display names, raw contact details, exact meeting points or identifying notes.
After authentication, a member may see a first name and relevant journey or request details. A contact action may open WhatsApp or email using the method selected by the listing owner. BOATARIDE prefers buttons rather than displaying raw contact details. Users decide independently whether to communicate or travel.
Publishing a listing requests this limited disclosure. The publish screen must explain it immediately before the Publish button and store the contact-sharing confirmation. It is not a marketing consent.
5 Sources of data
- Information entered directly by users in account, ride, request, contact and support forms.
- Authentication information returned by the login provider selected by the user.
- Technical and security information generated when the Service is accessed.
- Match, status and contact-click information generated by BOATARIDE from user activity.
- Reports or communications submitted by another user or a competent authority.
6 Recipients and service providers
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Recipient or provider Role in the MVP
--------------------------------------- -----------------------------------------------------------------------------------------------------------------------------------------------------------
Other BOATARIDE users Receive only the public or member-level information described above when using search, match and contact functions.
Airtable Current operational database and operator control room for users, journeys, requests, matches, contact methods and statuses.
Vercel Hosts the web application and secure server/API layer and may process network, request, error and security data.
Supabase Provides authentication, stable account identifiers, ownership controls, legal-document versions and legal-acceptance records in the completed M3 build.
Google or Apple Independent authentication providers only if the user selects the corresponding login option.
WhatsApp or the user's email provider Independent services opened only when a member chooses the relevant contact action. BOATARIDE does not receive the content of the resulting conversation.
Professional advisers and authorities Receive information only where reasonably necessary for advice, claims, safety, law enforcement or compliance with a binding legal duty.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Resend is not part of the current M3 processing description. If BOATARIDE activates Resend for the notification milestone, this notice and the processor register must be updated before live emails are sent.
BOATARIDE does not sell personal data and does not share it for behavioural advertising.
7 International transfers
Some service providers or their subprocessors may process personal data outside the European Economic Area. Where Chapter V GDPR applies, BOATARIDE will use an applicable adequacy decision, the European Commission Standard Contractual Clauses or another lawful transfer mechanism and will assess supplementary safeguards where required. Provider processing locations and subprocessor lists may change; the operator must keep the internal processor register current.
8 Retention
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Record Normal retention rule
---------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Active account and profile While the account remains active. Review accounts after 24 months without member activity; notify where practical before deletion.
Active ride or request Until closed, fulfilled, cancelled or deleted by the user or operator.
Closed ride, request and match Up to 12 months after closure for pilot evaluation, dispute handling and abuse prevention, then delete or irreversibly aggregate.
Contact-click records Up to 12 months after the recorded action, unless needed for a live complaint or legal claim.
Terms acceptance and document versions Minimal evidence for up to 10 years after the user agreement ends where reasonably necessary to establish, exercise or defend legal claims.
Reports and complaints Normally up to 5 years after closure, or longer only where a legal duty or active claim requires it.
Technical and security logs Normally no longer than 30 days, unless an event requires longer preservation for security investigation or legal obligations.
Deletion process and backups Active systems targeted within 30 days after a valid deletion request; residual backups overwritten in the ordinary cycle, normally within 90 days, unless lawful retention applies.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BOATARIDE may retain a smaller record for longer only when necessary for a binding legal obligation, fraud or safety investigation, or the establishment, exercise or defence of legal claims. Data no longer needed will be deleted or irreversibly anonymised.
9 Security
BOATARIDE uses measures appropriate to a small pilot, including server-side access to Airtable credentials, environment secrets, authentication, role and ownership checks, separate public and private data payloads, encrypted transmission, restricted operator access, Row Level Security where Supabase is used, and logging of security-relevant failures. No online service can guarantee absolute security.
If a personal-data breach occurs, BOATARIDE will investigate, contain and document it and notify the competent supervisory authority and affected people where Articles 33 and 34 GDPR require notification.
10 Automated matching
BOATARIDE may order possibilities using departure, destination, date, stated flexibility and indicated capacity. Labels such as Best Match or Could Also Work are relevance aids. They do not verify a person or vessel, assess safety, or produce a legal or similarly significant decision about a user. BOATARIDE does not conduct behavioural profiling for advertising.
11 Rights
Subject to the conditions in the GDPR, a person may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests. Where processing is based on consent, consent may be withdrawn for the future. A person also has the right not to be subject to a solely automated decision producing legal or similarly significant effects, where Article 22 applies.
Requests should be sent through the privacy contact in the Legal Notice. BOATARIDE may request information reasonably necessary to verify identity. It will normally respond within one month, subject to lawful extensions. Account deletion can also be initiated through My BOATARIDE when that function is available.
A complaint may be submitted to the Garante per la protezione dei dati personali or another competent supervisory authority, particularly in the Member State of habitual residence, place of work or alleged infringement.
12 Adults only
BOATARIDE accounts, publishing, identity unlock and contact functions are limited to adults aged 18 or over. BOATARIDE does not knowingly create accounts for children. If the operator learns that a child created an account, the account and associated data will be reviewed and deleted or restricted as appropriate.
13 Changes to this notice
The current version and effective date will be displayed on the Service. Material changes will be communicated to affected members where appropriate. A Privacy Notice update is normally information, not a request for contractual acceptance; any new consent-based processing will use a separate choice.
14 Sources and provider information
- General Data Protection Regulation
- Garante per la protezione dei dati personali
- Airtable Privacy and legal information
- Vercel Data Processing Addendum
- Supabase Data Processing Addendum
- Supabase available regions
- Resend Data Processing Addendum for future notification use