Privacy policy
What we keep about you when you book here, why, for how long, and what you can do about it.
1 · Who is responsible
The data controller is [PENDIENTE: registered name of the landlord], registered with the Dutch Chamber of Commerce under [PENDIENTE: KvK number], established at [PENDIENTE: registered address]. Questions about your data go to [PENDIENTE: contact address for privacy questions].
The apartments are in Islantilla (Huelva, Spain) and the management is Dutch. Which law applies and which authority supervises follows from those details. While they are missing it does not say so here, because naming the wrong authority is worse than naming none.
2 · What we ask for
Everything we hold about you, you typed in yourself. We buy no data and we fetch nothing from anyone else.
- First and last name
- E-mail address
- Phone number — optional, only if you fill it in
- The number of adults and children
- The arrival and departure dates and the apartment you chose
- The language you booked in
- Your message, if you leave one
- The payment method and whether it has been paid
3 · What we deliberately never see
Your card details are not on that list, and that is not an oversight. Card payment happens on the Stripe page: the number, the expiry date and the security code never reach our server. We are told whether the payment went through, for how much, and a reference to find it again.
We also ask for no identity document when you book. Whether Spanish tourist-letting rules require one on arrival depends on the establishment in point 1, and will be stated here once that is settled.
4 · What we use them for
Three things, each with its own legal basis.
- Running the booking: holding the nights, calculating the price, processing the payment and sending you the e-mails that belong to it — confirmation, payment details, a reminder for the balance, information before arrival. Basis: performance of the contract.
- Keeping the records we are legally required to keep. Basis: legal obligation.
- Keeping the system accountable: every change to a booking is recorded with its timestamp. Basis: legitimate interest in records where it can later be established what happened.
5 · Who else sees them
As few parties as possible, and not one of them for advertising.
Booking, Airbnb and Agoda receive nothing about you. The calendar we send them says only that an apartment is occupied on certain nights: no name, no e-mail address, no amount. That is not a promise but a test — it fails if anything about a guest ever ends up in that file.
- Stripe, for card payment. Your details go straight to their payment page, not through us.
- The party that sends our e-mail: it sees your address and the contents, because otherwise it cannot deliver it.
- The party where this site and the booking system run.
- As soon as those two suppliers are settled, they will be named here with their country.
6 · How long we keep them
A booking stays on file while it runs, and after that for as long as the retention duty of the party in point 1 lasts. We will fill that term in together with those details.
The e-mails we sent you we keep with their exact text. That is on purpose: it makes it possible to establish later what we actually told you — which amount, which date, which account number.
If you ask for erasure, we remove what we are not legally required to keep, and we tell you which part stays and why.
7 · What you can ask of us
Access to what we hold, correction of anything wrong, erasure, restriction of use, objection, and your data back in a readable file. Write to the address in point 1; we answer within a month.
If you disagree with what we do, you can complain to the supervisory authority. Which one that is follows from the establishment still missing in point 1.
8 · How we protect them
The admin panel is protected by a key that expires, not by a password left lying around. Every change to a booking — price, status, refund — is recorded with its timestamp, and that record cannot be altered from the panel itself.
9 · Changes
This is the first version, written while the site was being built. If what we collect or who receives it changes, this text changes with it — beforehand, not quietly afterwards.