Legal
Privacy.
A charter booking needs a surprisingly small amount of information: who is coming, how many of you there are, and how the skipper reaches you at eight in the morning. This page sets out exactly what is collected, why, who sees it and how long it stays.
Last updated 2 August 2026GDPR · Malta
The short version
- We collect what a booking needs and very little else.
- Your details go to one operator: the one whose boat you booked.
- We do not sell data, and there are no advertising trackers on this site.
- Card numbers are handled by the payment processor and never reach us.
- You can ask for a copy of your data, or its deletion, and get an answer inside 30 days.
01
Who is responsible
SailSeeker Ltd, registered in Malta with its office at Ta’ Xbiex, is the data controller for the platform. Write to privacy@sailseeker.io for anything in this document.
The operator you book becomes a controller in their own right for the charter itself, and for the safety and licensing records they are required to keep. What we pass to them is listed below and nothing more.
02
What is collected, and why
Browsing the site collects nothing that identifies you. Everything in this table is triggered by an action: making a booking, sending a message or writing a review.
| What | Why | Lawful basis | Kept for |
|---|
| Name, email, phone | To confirm the booking, and so the operator can reach you on the morning of departure. | Performance of a contract | 6 years from the charter |
| Guest count and ages of children | Capacity is fixed by the vessel certificate, and the operator brings life jackets to size. | Performance of a contract | 6 years from the charter |
| Boating licence, where the boat requires one | Malta requires the operator to sight a valid certificate before the boat leaves the berth. | Legal obligation | 12 months from the charter |
| Booking details, dates and price | To run the booking, and because VAT and company records have to be kept. | Legal obligation | 6 years from the charter |
| Card payment, handled by the processor | To authorise the payment and release it to the operator on the day. | Performance of a contract | We never hold the card number |
| Messages between you and the operator | So there is a record of what was agreed, which matters when a charter is disputed. | Legitimate interests | 24 months from the last message |
| Reviews you write | Published on the boat and operator pages with your first name and the date. | Consent | Until you ask us to remove it |
03
Who it is shared with
Four parties, and no others.
- The operator you booked. Your name, phone number, guest count, ages where children are aboard, and your licence where the boat requires one. They do not receive your card details, and they do not get the details of anyone whose request they declined.
- The payment processor. Card data goes directly to them and is tokenised. We see the last four digits, the outcome and the amount.
- Hosting and email. Infrastructure providers inside the European Economic Area, acting on our instructions under a processing agreement.
- Authorities, where the law requires it. A Transport Malta or tax enquiry, or a court order. This is rare and we will tell you unless we are prohibited from doing so.
We do not sell personal data, and we do not share it with advertising networks or data brokers. There is no commercial arrangement under which anyone pays us for access to our guest list, and there will not be one.
04
How long it is kept
The retention column above is the whole policy. The six-year figure is not arbitrary: it is the period for which Maltese VAT and company records have to be retained. Once a record passes it, the booking is reduced to an anonymous line for reporting, holding the boat, the date and the value, with nothing that identifies a person.
Requests that an operator declined, and abandoned bookings, are deleted after 90 days.
05
Where it is stored
On servers in the European Union. Where a processor operates outside the EEA, the transfer runs on the European Commission’s standard contractual clauses and we hold the documentation. We do not transfer booking data outside the EEA for any purpose of our own.
06
Your rights
Under the GDPR you can exercise all of the following, free of charge, and we answer inside 30 days.
- Access. A copy of everything we hold about you.
- Rectification. Correction of anything wrong, which for most people means a phone number that has changed.
- Erasure. Deletion, subject to the records we are legally required to keep for tax. A guest can do this themselves under Account, Profile, Delete this account.
- Restriction and objection. Including objecting to anything we do on the basis of legitimate interests.
- Portability. Your booking history in a machine-readable file.
- Withdrawal of consent. For a published review, at any time, without affecting what was lawful before.
Write to privacy@sailseeker.io. We may ask you to confirm the email address a booking was made from before releasing anything.
07
Security
Traffic is encrypted in transit. Access to booking records is limited to the people who need it and is logged. Card data never touches our systems. If a breach occurs that is likely to put your rights at risk, we notify the Information and Data Protection Commissioner within 72 hours and tell you directly.
08
Children
The platform is not for use by children, and accounts are for adults. Children aboard are recorded only as an age, given by the person booking, so the operator brings correctly sized life jackets. That age is deleted with the rest of the booking record.
09
Complaints
Come to us first at privacy@sailseeker.io. If you are not satisfied, the supervisory authority in Malta is the Office of the Information and Data Protection Commissioner, at idpc.org.mt, and you may also complain to the authority in your own country of residence.
10
Changes
The date at the top of this page moves when the document does. A material change is emailed to anyone with a live booking rather than quietly published.
Proof of conceptThis build is a demonstration and takes no real bookings. Nothing typed into a form here is transmitted, stored or processed, and the addresses above are illustrative. The policy is written to the model the product would run on rather than as filler.