Privacy Policy

Last updated: 17 November 2026

This Privacy Policy explains what personal data Exploras collects when you use exploras.do (including www.exploras.do and its subdomains — the “Service”), why we collect it, who we share it with, how long we keep it and what rights you have. It applies to visitors, to travellers who contact a host through the Service, to account holders and to the hosts listed on the Service.

The Service is operated under the trade name Exploras from the Dominican Republic, and the operator is the party responsible for your data (the “data controller”). We process personal data in accordance with Dominican Law 172-13 on the protection of personal data and, where it applies to visitors from the European Economic Area, the United Kingdom or Switzerland, the General Data Protection Regulation (GDPR) and its equivalents. You can reach us for anything in this policy at contacto@exploras.do or through the contact form.

1. In short

  • Exploras never handles the payment for the experience itself. Any card payment made to Exploras is taken by Stripe on its own payment page, and Exploras never sees the card number.
  • You can browse everything and contact a host without an account.
  • When you contact a host, you write to them on Exploras. We store the conversation, translate it automatically, and show it to the host and to our team. Your phone number and e-mail stay hidden from the host until the booking is confirmed.
  • We do not sell personal data. If you accept cookies, the Meta pixel tells Meta which of our ads on Facebook and Instagram led to a visit or an enquiry (section 2.6).
  • Analytics and advertising measurement (Google Analytics, Microsoft Clarity and the Meta pixel) only load if you accept cookies. Before you choose, no such request is made and no such cookie is set.
  • Our servers and database are in the United States. See section 7 on international transfers.
  • If you are a host and buy Plan Visibilidad, we keep the billing details the fiscal invoice needs and pass them to our accountant, who issues it (section 2.8).

2. What we collect, and when

2.1 When you browse. Our hosting provider records standard server logs for each request: your IP address, browser and device type, the page requested, the referring page and the time. We use them for security, debugging and abuse prevention. The Service also counts how many times a listing, article or guide page is opened; that counter stores only the page and the day, nothing about you. Your language choice is kept in a cookie and, if you have answered the cookie banner, your answer is stored in your browser.

2.1b When you ask a question in the box on a guide or a place page, we keep your question, our answer, the page and the hosts we showed you for 12 months, to improve the answers. We do not store your IP address or your name with it. To limit abuse, we keep a pseudonymised (hashed) form of your IP address separately for up to a day. The question is sent to our AI provider, Anthropic, to write the answer. If you then send an enquiry, we note which question it came from.

2.2 When you contact a host. The contact button on a listing or host profile opens a short form. Depending on the kind of listing it may ask for your first name (optional), the number of people, a preferred date and time of day, a transfer route, a vehicle type and a number of rental days. It also asks for a WhatsApp number or an e-mail address, so we can tell you when the host replies, and lets you write a first message. We record all of this with the listing or host concerned, the language you were browsing in and the time, and open a conversation between you and the host on Exploras. Everything either of you writes in it is stored. Before the booking is confirmed, phone numbers, e-mail addresses and links typed into a message are hidden from the other side (our team still sees them); once the host confirms the booking, each of you sees the WhatsApp number or e-mail address the other gave. You open the conversation with a private link we send you; anyone holding that link can read it, so do not share it.

2.2a Translation and alerts. Each message is translated automatically into the other person’s language by Anthropic’s AI models; the translation is stored next to the original, and either of you can read the original. We alert the host and you of new messages by WhatsApp from Exploras’s own number, or by e-mail. Reply STOP to our WhatsApp messages and we stop writing to you there.

2.2b Your booking ticket. When a host confirms, your conversation page shows a ticket with a booking code and a QR code. Anyone who scans the QR or types the code sees the experience, the date and time, your first name, the size of your group and whether the ticket is valid, so the host can check it when you arrive; nothing else. We also send you the ticket, a reminder the day before and any change, by WhatsApp or e-mail. When you open an activity suggested under your booking, we record which suggestion you opened and from where (the chat, the e-mail or your trip page), linked to that booking, to count how useful the suggestions are.

2.3 When you use the contact form. We collect your name, e-mail address, the subject you choose and your message. We send you an automatic confirmation and forward the message to our team.

2.3a When you ask for your trip plan by e-mail. On the trip planner you can have your plan sent to your e-mail address without contacting any host. We keep that address with the plan and its dates, send you the plan at once and, if your trip is more than four weeks away, one reminder about four weeks before it. We send nothing else to that address and share it with no host.

2.3b When you plan a trip with your group. If you open a trip room on the trip planner, the people you share its link with type a first name and choose Add or Skip on the same experiences. We keep each first name and those choices with the room, show them only to the people in that room, and never send them to any host or use them for marketing. The person who opened the room is the only one who can send the plan to hosts.

2.4 When you create an account. We collect your name, e-mail address and password (stored only as a cryptographic hash by our authentication provider), your chosen role (traveller or host) and, for hosts, the business WhatsApp number, which we use to check whether the business is already listed. Account holders can save listings as favourites; we store which listings you saved. We send transactional e-mails only: e-mail confirmation, password reset, and replies to your messages. We do not send newsletters.

2.5 If you are a host. A host page shows, by design, the business’s public details: business name, description, town and service areas, WhatsApp number, spoken languages, cover photo, listings with photos, prices and conditions, and the rating and number of reviews that Google publishes about the business. To create or improve a page we may collect that information from you directly (by WhatsApp, phone, e-mail or the host dashboard) and from public sources: the business’s own website and its Google Business Profile, retrieved through Google’s Places API and through an automated crawler. Internally we also keep: notes on our contact with you and on verification of your page; the state of any follow-up we are waiting on; your answers to short surveys about the Service; the enquiries your listings received (section 2.2); and a log of edits made to your page, including which member of our team made them and when.

2.6 Analytics, only with your consent. If you accept cookies, we load Google Analytics 4 and Microsoft Clarity. They use cookies and similar identifiers to measure visits, pages, events (such as opening a listing, filtering, searching or tapping a WhatsApp button), approximate location derived from your IP address, and device and browser information. Clarity also records how a page is used (scrolling, clicks, mouse movement) and can replay a session; text you type into forms is masked. The Meta pixel, from Meta Platforms, records that you opened a page or a listing, searched, or started an enquiry, with the listing’s or host’s id and category, so that we can measure our advertising on Facebook and Instagram and show it to people likely to be interested; Meta may link these events to a Meta account you hold, under Meta’s own privacy policy. We never send the pixel your name, phone number or e-mail, and we switch off its automatic reading of forms and buttons. Like any request from a web page, it does see the address of the page you are on, which includes any words you typed into our search box. If you reject cookies, none of this runs and no analytics or advertising request leaves your browser.

If you accept cookies, the analytics and advertising tools described above may also run on the conversation pages and on the one-tap login links we send hosts.

2.7 Rate limiting. To stop abuse of the contact form and enquiry endpoints we keep a short-lived counter keyed to your IP address; it expires within a day.

2.8 If you are a host and buy Plan Visibilidad. To sell you the plan and invoice it, we collect your e-mail address and billing address, and the business or billing name and the RNC or cédula that go on the fiscal invoice (NCF), and we keep the category and dates of your plan and, for each payment, its amount, date and status. For a plan paid by card we also keep the Stripe customer and subscription references; you enter your card details on Stripe’s payment page, and we never see or store the card number.

We do not knowingly collect special categories of data (health, religion, etc.). Please do not include such information in a message or enquiry unless it is necessary for the host to serve you safely; if you do, remember that the conversation is stored and that our team can read it.

3. Why we use your data, and on what basis

To sell Plan Visibilidad to a host who buys it, take and record the payments and issue the fiscal invoices (NCF) — our contract with the host and our legal obligations under Dominican tax law.

  • To operate the Service and show you listings, in the language you chose — our legitimate interest in running the Service, and where you have an account, our contract with you.
  • To pass your enquiry to the host and to let the host recognise it — steps taken at your request before any agreement with the host, and our legitimate interest in showing hosts that Exploras works.
  • To reply to your messages and support requests — our legitimate interest in answering you, and where relevant our contract with you.
  • To run your account, save your favourites and secure your login — our contract with you.
  • To create, verify and keep host pages accurate, and to contact hosts about their listings and the quality of their service — our legitimate interest in running a reliable directory, and the host’s agreement to be listed.
  • To measure how the Service is used and improve it — your consent for analytics cookies; our legitimate interest for the cookieless page counter and server logs.
  • To measure and target our advertising on Facebook and Instagram — your consent for advertising cookies.
  • To prevent fraud, spam and abuse and to keep the Service secure — our legitimate interest and, where applicable, legal obligations.
  • To comply with the law, respond to lawful requests and establish, exercise or defend legal claims — legal obligation and legitimate interest.

Where we rely on legitimate interests we have balanced them against your rights; you can object at any time (section 8). Where we rely on consent, you can withdraw it at any time without affecting what was done before.

4. Who we share your data with

4.1 Hosts. The host receives what you write in the conversation, its translation, your first name and the details of your enquiry. Your WhatsApp number and e-mail are shown to the host only once the host confirms your booking, so you can find each other on the day; the host may use them only for that booking. We may also tell a host, in aggregate, how many enquiries their listing received.

4.2 Service providers (processors) that act on our instructions:

  • Supabase (United States) — database, file storage and account authentication.
  • Vercel (United States) — hosting, content delivery, server logs.
  • Resend — sends our transactional and notification e-mails.
  • Google — Google Analytics (only with consent); Google Maps Platform / Places API to retrieve public business data, ratings and reviews of hosts; Google Business Profile.
  • Microsoft — Clarity heatmaps and session replay (only with consent).
  • OpenStreetMap Foundation — map tiles on listing pages; loading a tile sends your IP address to their servers.
  • Unsplash — hosts some of the photos on blog articles; loading a photo sends your IP address to their servers.
  • Anthropic — artificial-intelligence models we use to translate listing and host descriptions, to draft articles, and to translate the messages travellers and hosts write to each other, and to write the answers in the question box on guides and place pages. Message text and box questions are sent only for that purpose and are not used to train models. We never send account data.
  • Apify — automated retrieval of public information from Google Maps and hosts’ websites when we create or update host pages.
  • Meta (WhatsApp Business) — carries our alerts that a message is waiting for you or for the host, from Exploras’s own number.
  • Meta (advertising) — the Meta pixel, only with consent, to measure and target our ads on Facebook and Instagram.
  • Stripe (United States) — processes card payments for Plan Visibilidad. The host enters the card details on Stripe’s page; we receive the payment status and Stripe references, never the card number.
  • Our accountant (Dominican Republic) — receives each month the list of Plan Visibilidad payments (business or billing name, or the e-mail address when no name was given; RNC or cédula; amounts and dates) to issue the fiscal invoices (NCF) and keep the accounts.

4.3 Affiliates. The operator of Exploras also operates other businesses in Las Terrenas. We may share data with them only as processors supporting the Service (for example shared staff or tools), never for their own marketing, unless you ask us to introduce you.

4.4 Authorities and legal claims. We may disclose data where the law requires it, in response to a valid request from a court or authority, or where necessary to establish, exercise or defend legal claims or to protect the rights, safety or property of Exploras, hosts or travellers.

4.5 Business transfers. If the Service or its operator is sold, merged or reorganised, data may be transferred to the successor, who will be bound by this policy. We will post notice here.

We do not sell personal data and we do not share it with data brokers. The only advertising network we use is Meta, and only with your consent (section 2.6).

5. How long we keep it

  • Enquiry records (section 2.2): 24 months from the enquiry, then deleted or anonymised. Aggregated counts are kept indefinitely.
  • Contact-form messages: 24 months from our last exchange with you.
  • Trip plans sent to you by e-mail (section 2.3a): until 30 days after the trip’s arrival date, or 12 months after you asked when the plan has no date.
  • Trip rooms (section 2.3b): until 30 days after the trip’s arrival date, or 60 days after the last activity when the plan was never sent or has no date.
  • Account data: for as long as your account exists, then deleted within 30 days of your request to close it, except for records we must keep by law.
  • Favourites: until you remove them or close your account.
  • Host pages and internal host notes: for as long as the business is listed, then up to 24 months for records of past enquiries and edits.
  • Questions asked in the question box on guides and place pages (section 2.1b): 12 months, then deleted.
  • Server logs and rate-limit counters: logs for a short period set by our hosting provider (typically days); rate-limit counters expire within a day.
  • Page-view counters: indefinitely (they contain no personal data).
  • Analytics data: as set in Google Analytics (currently 14 months for user-level data), Microsoft Clarity (up to 12 months) and Meta (as set by Meta for pixel events).
  • E-mails and messages exchanged with hosts and travellers by our team: as long as needed for the purpose, generally no more than 36 months.

Conversations and their translations (section 2.2): deleted together with the enquiry they belong to, 24 months after the enquiry.

Plan Visibilidad billing and payment records (section 2.8): 10 years, the period Dominican tax law requires accounting records to be kept. Your rights in section 8 apply, except that we cannot delete these records before that period ends.

Backups may retain copies for a further short period before they are overwritten. Where a legal claim or an authority’s request requires it, we keep data for as long as necessary.

6. Cookies and similar technologies

Strictly necessary (no consent required):

  • NEXT_LOCALE — remembers the language you chose. Cookie, 1 year.
  • sb-* (authentication) — keeps you signed in to your account. Cookies set by our authentication provider; they last up to 400 days, so you stay signed in until you sign out.
  • cookie_consent — your answer to the cookie banner. Stored in your browser’s local storage, not sent to us.
  • Per-tab view markers — prevent a page from being counted twice in the same tab. Session storage, cleared when the tab closes.
  • wa-reply — remembers that you already answered whether a host replied to your enquiry, so the question is not asked again. Local storage, kept in your browser.
  • xm_contact — remembers the WhatsApp number or e-mail address you gave in a message or trip-plan form, so you do not have to type it again. Local storage, kept in your browser until you clear it; anyone who uses this browser can see it.
  • exploras.stay.v1 — remembers your name, group size and children’s ages, the last day you asked for, your stay dates, hotel and arrival details (airport, landing time, flight, suitcases) from your last request, so the next form starts filled in. Local storage, kept in your browser for 60 days after your last request, or until you tap «Forget my details»; anyone who uses this browser can see it.
  • xm_thread:* — remembers the private link to a conversation you started from a listing or host page, so that page can take you back to it for 7 days. Local storage, kept in your browser until you clear it; anyone who uses this browser can open that conversation.
  • xm_trip — remembers the private link to your trip page (all your requests on one page), so the menu can take you back to it and new requests join it. Local storage, kept in your browser until you clear it or press «Forget this trip on this device»; anyone who uses this browser can open that page.
  • exploras.rooms.v1 — remembers the private links to the trip rooms (section 2.3b) you opened or joined on this browser, so you come back as yourself; for a room you opened, it is the link that lets you send the plan for your group. Local storage, kept in your browser until you clear it (at most 10 rooms); anyone who uses this browser can open those rooms as you.
  • exploras.plan.draft.v1 and exploras.plan.sent.v1 — remember the link to the last trip plan you built and did not send, so the planner can offer «Continue your plan», and the links of the last 10 plans you sent, so a sent plan is not offered again. A plan link holds your stay dates, group size and children’s ages and the experiences you picked, never your name or contact. Local storage, kept in your browser: the unsent plan for 30 days; anyone who uses this browser can see it.
  • exploras.map.trip.v1 — remembers the experiences you added on the Samaná map, so the trip planner can start with them already in your trip. It holds the experiences only, never anything about you. Session storage, cleared once the planner takes them or when you close the tab.
  • exploras.plan.ab, exploras.plan.party and exploras.plan.ask — the first remembers which version of the trip planner this browser was given for a test (one letter, a or b), so you always see the same one; the other two carry your group size and the chosen experience from the planner to the listing form you open with «Ask about this one», so the form starts filled in and we can count a message sent from there. None holds anything about you. The first is local storage, kept in your browser until you clear it; the other two are session storage, cleared once used or when you close the tab.

Visit source (first-party, no identifier; our legitimate interest in knowing which of our links bring enquiries):

  • fb_src — if you arrived through one of our links in a Facebook group, records which group and topic, and an enquiry you send in the same browser session is marked with it, so we can count enquiries per group. It holds nothing about you and is never shared. Session cookie: your browser deletes it when the session ends.
  • idea_src — if you opened an activity from the ideas under your booking, records whether the idea was in the chat, the e-mail or your trip page, and an enquiry you send in the same browser session is marked with it, so we can count those enquiries. It holds nothing about you and is never shared. Session cookie: your browser deletes it when the session ends.
  • ask_id — if you tap a host suggested in the question box on a guide or a place page, marks an enquiry you send in the same browser session as coming from that box, so we can count those enquiries. It is used for nothing else. Session cookie: your browser deletes it when the session ends.
  • ai_src — if you arrived from an AI assistant (such as ChatGPT, Perplexity, Claude, Gemini or Copilot), records which one, and an enquiry you send in the same browser session is marked with it, so we can count enquiries per assistant. It holds nothing about you and is never shared. Session cookie: your browser deletes it when the session ends.
  • ref_src — if you arrived through a partner’s QR card or link (a hotel, a driver, a rental host), records that partner’s code, and an enquiry you send within 72 hours is marked with it, so we can count what each partner brings. It holds nothing about you and is never shared. Cookie, 72 hours.
  • first_src — records where your first visit came from (the site that linked to us, the page you landed on and the campaign named in the link, if any) and its day, for 30 days, and an enquiry you send in that time is marked with it, so we can see which channels bring travellers. It is not used for advertising; besides our team, only the host who receives that enquiry can see it. Cookie, 30 days.

Analytics and advertising (only after you click “Yes”):

  • _ga, _ga_* — Google Analytics: distinguishes visitors and sessions. Up to 2 years.
  • _clck, _clsk, CLID, ANONCHK, MUID, MR, SM — Microsoft Clarity: distinguishes visitors and sessions and links them to a replay. Up to 1 year.
  • _fbp, fr — Meta pixel: recognises the browser so an ad can be matched to a visit or an enquiry. Up to 90 days.

Card payments to Exploras are made on Stripe’s payment page, on stripe.com. Stripe sets its own cookies there, for fraud prevention, under Stripe’s privacy policy; none of them are set on exploras.do.

Choosing “No” is a real choice: analytics and the Meta pixel never load. You can change your mind at any time with the button below, which clears your stored answer and shows the banner again; you can also delete cookies and site data in your browser settings. Rejecting or deleting cookies does not affect your ability to use the Service.

7. International transfers

Our database, file storage and hosting are located in the United States, and several of the providers in section 4 process data there or in other countries outside the Dominican Republic. If you are in the European Economic Area, the United Kingdom or Switzerland, transfers of your data to those countries rely on the providers’ certification under the EU-U.S. Data Privacy Framework where available, and otherwise on standard contractual clauses approved by the European Commission or equivalent safeguards. You can ask us for details of the safeguards used.

8. Your rights

Under Dominican Law 172-13 you have the right to access the personal data we hold about you, to have it corrected, to have it deleted (“cancelled”) and to object to its processing. If the GDPR or similar law applies to you, you additionally have the right to restrict processing, to receive your data in a portable format, to withdraw consent at any time and to lodge a complaint with the data-protection authority of your country of residence.

  • To exercise any right, write to contacto@exploras.do or use the contact form. Tell us which right you are exercising and, so that we can find your records, the e-mail address, name or listing involved.
  • We may ask you to confirm your identity before acting, and we will respond within 30 days. We do not charge for a request unless it is manifestly unfounded or excessive.
  • Account holders can also update their name from their account settings; to change the e-mail address on an account, write to us.
  • Hosts can ask at any time to correct, take control of or remove their page (see section 9).

How to delete your account and data

9. Hosts: public information and public sources

A host page is public by design: its purpose is to let travellers find and contact your business, and the business name, WhatsApp number, description, photos, prices and Google rating on it are published for everyone to see, including search engines. Where we created a page from public sources before you asked us to, we did so on the basis of our legitimate interest in providing a complete directory of the peninsula and of the information you had already made public. You can at any time ask us to correct the page, to take control of it, or to remove it, by writing to host support on WhatsApp (number in the footer), to contacto@exploras.do or through the contact form. We will act within a reasonable time, and search engines and cached copies may take longer to update. Ratings and review counts come from Google; to change or remove a review, contact Google.

If you are a host, we also keep a record of your acceptance of the Host Agreement — the account, the business, the version, the date and time, your IP address and browser — as evidence of the contract, for as long as you are listed and for 5 years afterwards. If you offer boat, sea or transport services, the licence and insurance documents you upload are stored privately, seen only by our team to check that they are current, never published, and kept while you are listed and for up to 24 months afterwards.

10. Security

All traffic to the Service is encrypted (HTTPS). Passwords are stored only as hashes. Our database enforces row-level access rules so that each account can only reach its own data, and our staff’s access to the administration panel is limited to what their role requires and logged. Public forms are rate-limited and protected against bots. No system is perfectly secure, and we cannot guarantee that unauthorised access will never occur; if we learn of a breach affecting your data, we will inform you and, where required, the authorities.

11. Children

The Service is not directed at people under 18, and we do not knowingly collect personal data from them. If you believe a child has given us data, write to us and we will delete it.

12. Changes to this policy

We may update this policy from time to time. The date at the top shows when it last changed. If a change materially affects how we use your data we will draw attention to it on the Service or by e-mail where we have your address. The current version always applies.

13. Contact

For any question, request or complaint about your personal data, write to contacto@exploras.do or use the contact form. Hosts can also reach host support on WhatsApp at the number shown in the footer.

This policy is also published in Spanish and French. If the versions differ, the English version prevails.