Three commitments. All three go in the agreement.
You get guests who already decided, requests that arrive complete, and your name in front of people who would otherwise book whoever came up first. You give up nothing you use today.
Two or three partners per category
Two operators per activity, three at most. You are not the twelfth listing nobody scrolls to. You are one of two or three answers, on the screen where the question gets asked.
The guest pays you, same as always
Boka takes no money and holds no deposit. Price, contract and payment stay with you. That also means nothing here conflicts with the terms you signed with Booking or GetYourGuide. Same business as today — with a guest who already said yes.
Commission only when someone shows up
Not on confirmation. Not on a click. A guest who never arrives costs you nothing. Once a month you get a list of booking IDs and check off who turned up. That is the entire admin.
One email. Three links. Done.
Nothing to install. No dashboard, no calendar to sync. The request arrives complete, and you answer it in the time it takes to read it.
The request arrives complete
Dates, vehicle class or tour, number of people, first name, booking ID. No haggling buried in paragraphs. No three emails to find out what someone wants.
One click is enough
Confirm, decline, or send back a different price — straight from the email. No account, no app on your phone, nothing new to learn in high season.
From there the guest is yours
The moment you confirm, the guest gets your number and your email and deals with you directly. Nothing routes through an inbox in between. The relationship is yours to keep.
This is where guests find you.
Your listing carries what people actually decide on. For a rental: vehicle class, handover point, whether your contract allows the national park. For a dive center: tank packages, courses, what is included. Everything a guest would otherwise call to ask — which is why the ones who do write already know what they want.
Design preview, July 2026 · rates blurred — placeholders, not offers
Operator names are examples
Where a partner slot is open.
Guests think in activities, not company names. So the app is organized by activity, with two or three partners behind each one. These are the slots I am filling first.
The name was already standing by the road.
Boka Onima. Boka Kokolishi. Boka Slagbaai. The island writes its coast in black stencil letters on yellow signs. Boka is the Papiamentu word for an inlet.
That is where the name comes from, and the yellow with it. Not an invented brand — a word taken off the roadside. This is built for one island, not for a catalog of destinations.
I come from the travel business. As Head of Marketing at Turbopass, a city-pass company selling attraction bookings internationally, I did exactly what matters here: sell tourist offers, drive demand to an operator, scale the channel. Boka is the same craft on one island I know.
I have been coming to Bonaire since 2017 — five stays, usually three weeks, always with my own vehicle. I snorkel rather than dive. My favorite place on the island is Boka Kokolishi. What was missing on every trip was one source for the practical things: which bay is worth it, where to shop, where to find a doctor, how to get a car.
Anything safety-related about shore entries goes in only after a dive center confirms it.
Three questions, and we both know whether this fits.
Does a commission on referred bookings work for you in principle?
Would you accept a booking ID shown at pickup?
Does the guest pay you on site, and do you need a card?
One line per question is enough. I am not asking for a number here — what a commission looks like belongs in a conversation, not on a website. Prefer to talk? Call, WhatsApp, or a video call. I am on the island regularly and happy to come by.
Imprint
Details as required by § 5 of the German Digital Services Act (DDG) and § 18 of the German Interstate Media Treaty.
Agnes-Miegel-Weg 47a
33813 Oerlinghausen
Germany
Address as above
What Boka is — and what it is not
Boka passes requests between travelers and operators on Bonaire. The contract for a dive, a rental car, a tour or a place to stay is made solely between the traveler and that operator. Payment happens on site with the operator; no money moves through Boka. Boka is neither a tour operator nor a party to the contract, and is not liable for the services operators provide.
Liability for content and links
Prices, opening hours and availability are supplied by the operators themselves and can change. Only the operator’s confirmation is binding. Operators of linked sites are responsible for their own content — links come down once an infringement is known.
Dispute resolution
Boka is neither obliged nor willing to take part in dispute resolution proceedings before a consumer arbitration body.
Online dispute resolution
The European Commission runs a platform for online dispute resolution at ec.europa.eu/consumers/odr. Boka is not a party to consumer contracts and does not use it.
Copyright and trademarks
Texts, layout and the Boka name and logo on this site belong to the provider named above. Reuse needs written permission. Operator names, logos and photos shown in previews belong to those operators and appear as examples only.
Notices and takedown requests
If something on this site infringes your rights, write to the email address above and name the page and the passage. Anything justified is corrected or taken down promptly.
Privacy
How the site handles personal data — server logs, contact by email or WhatsApp, and what happens once the app starts passing requests to operators on Bonaire — is set out separately.
Image credits
Photos: Boka Onima taken by the author; other Bonaire images by Leo, Attie and Vince Colson via Pexels. Map rendering in the design based on OpenStreetMap data. The sample request, booking ID and all rates shown are placeholders.
Privacy policy
This explains what happens to personal data on this website, and what will happen once the Boka app starts passing requests to operators on Bonaire. Controller is the provider named in the imprint.
Who is responsible
David Lindner, Agnes-Miegel-Weg 47a, 33813 Oerlinghausen, Germany. Contact: david@bokabonaire.com, +49 175 711 27 33. There is no separate data protection officer — the site is run by one person and the legal threshold for appointing one is not reached.
Visiting this site
Every request to the server writes a log entry: IP address, time, page requested, referrer, browser and operating system. This is necessary to deliver the page and to detect attacks, and rests on a legitimate interest under Art. 6(1)(f) GDPR. The entries are not merged with other data and not used to identify anyone. They are kept only as long as the hosting provider retains them, currently around 30 days.
Hosting: Netlify
The site is hosted by Netlify, Inc., 512 2nd Street, San Francisco, CA 94107, USA, as a processor under a data processing agreement (Art. 28 GDPR). Netlify is a US company, so the log data described above may be processed in the United States. That transfer is covered by the EU Standard Contractual Clauses included in Netlify’s agreement, and Netlify is certified under the EU–US Data Privacy Framework.
Fonts and cookies
This site sets no cookies, uses no tracking, runs no analytics and shows no consent banner — there is nothing to consent to. The two typefaces are served from the same server as the site, so no request goes to Google or any other font service while you read this page.
Writing to me
If you send an email, your address, your name and the content of your message are processed to answer you — Art. 6(1)(b) GDPR where a partnership is being discussed, otherwise Art. 6(1)(f). Outgoing mail from the site is sent through Resend, Inc., 2261 Market Street, San Francisco, CA 94114, USA, as a processor under a data processing agreement with Standard Contractual Clauses in place; delivery data may therefore be processed in the United States. Business correspondence is retained for as long as commercial and tax law require and deleted afterwards.
The number given also works on WhatsApp, which belongs to Meta Platforms Ireland Ltd. If you write there, Meta processes the contact and its content under its own terms, and data may be transferred outside the EU. Nobody has to use it: email and an ordinary phone call reach exactly the same person.
Requests through the app
This is not live yet and is described here in advance so it holds no surprises. When a traveller sends a request, the operator receives a first name, the dates, what is being asked for and a booking ID — not the email address and not the phone number. The legal basis is Art. 6(1)(b) GDPR: without passing the request on, there is nothing to arrange.
Transfers to Bonaire
Bonaire is a Dutch special municipality but not part of the European Union, and there is no adequacy decision for it. Sending request data to an operator there is therefore a transfer to a third country. Two safeguards apply together: Standard Contractual Clauses in every partner agreement, and the traveller’s explicit consent for that specific request under Art. 49(1)(a) GDPR, given before the request is sent. Without that consent, nothing is passed on.
Your rights
You can request access to the data held about you (Art. 15), have it corrected (Art. 16) or erased (Art. 17), have processing restricted (Art. 18), receive it in a portable format (Art. 20), and object to processing based on legitimate interest (Art. 21). Where processing rests on consent, you can withdraw it at any time with effect for the future. One email to the address above is enough — no form and no particular wording.
Complaints
You can lodge a complaint with a supervisory authority at any time. The competent authority here is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, Kavalleriestraße 2–4, 40213 Düsseldorf, Germany.
No automated decisions
Nothing on this site or in the app makes automated decisions about you, and there is no profiling. Which operators appear is a curation decision made by hand.
Changes
When the site or the app changes what it does with personal data, this page changes with it. The version date at the top states which version you are reading.