Privacy policy

What personal data Converstay handles, why, who else processes it, how long we keep it, and how to exercise your rights. It covers hotel teams who use Converstay, visitors to converstay.com, and the guests of the hotels we work for.

Last updated 17 November 2026

1. Who we are

Converstay is a service operated by Rodrigo Valle Pinto, an individual entrepreneur registered in Mexico, with an address at Donceles 95, 06020 Cuauhtémoc, Mexico City, Mexico ("Converstay", "we", "us").

For any privacy question or request, write to contact@converstay.com.

2. Our two roles

We are responsible (the "controller") for the data of hotel staff who use Converstay, of people who contact us or request a trial, and of visitors to converstay.com.

For the data of a hotel's guests, the hotel is responsible and we act on its behalf and on its instructions (as its "processor", or encargado under Mexican law). If you are a guest, the hotel's own privacy notice applies to you, and the hotel is the first place to exercise your rights; we help the hotel answer, and you can also write to us and we will pass your request on.

3. Data about hotel teams and our customers

When a hotel uses Converstay, we handle:

  • Account data: name, email address, role in the hotel's team, a hashed password, passkeys and two-factor settings if you turn them on, and your language.
  • Sign-in sessions: the IP address and browser (user agent) of each session, to keep accounts secure.
  • Billing data: billing name, email, address and, if you give it, your tax ID (RFC). Payments are handled by Stripe; card numbers go directly to Stripe and we never see or store them.
  • Activity in the dashboard, such as settings changes, which we log so a hotel can see who changed what.
  • Your hotel's Cloudbeds connection. Its API key is stored encrypted (AES-256-GCM).

4. Data about visitors and people who contact us

Our public pages (the home page, our guides, sign-in and these legal pages) use Google Analytics to count visits, see where visitors come from and which pages lead to sign-ups; it sets cookies (_ga and _ga_*, up to two years) and receives your IP address and browser details. Google Analytics does not run in the signed-in dashboard, and we don't use advertising trackers. When you visit, we also set a cookie that remembers your language (converstay-locale, one year) and store your light or dark theme in your browser. Our pages load fonts from Google Fonts, which receives your IP address as part of that request.

If you request a trial or call, we keep the email address, website and call preference you give us, and email them to our team so we can reply.

5. Data about hotel guests

A hotel adds our script to its Cloudbeds booking engine. While a guest uses that booking engine, the script sends us:

  • The email address and first name the guest types into the booking form, as they type it, even if they don't finish the booking, and any email they enter in the hotel's "Send My Stay" box.
  • If the guest fills them in on the same form: their last name, phone number, the country they pick and whether they tick a box to receive the hotel's offers. We don't send texts or WhatsApp messages.
  • The stay they looked at: dates, number of adults and children, room, rate, price, currency, promo code and the booking engine's language.
  • How they arrived: the page address, the referring page and campaign tags (utm).
  • The kind of device and its operating system (for example mobile, iOS), read from the browser's user agent. We don't record the device model.
  • Identifiers our script stores in the browser's local and session storage to recognise the same visit (for example ba_booking_session_id). Once a guest has given that hotel their email, on the booking engine or by opening a link in one of its emails, the script also keeps a signed token (converstay_guest) for up to 90 days so their next visit to that hotel's booking engine is recognised as theirs. The token doesn't contain the email and works only for that hotel. We don't set cookies on the booking engine.

The guest's IP address is used for a moment to limit abuse and to look up where it is and which network it belongs to. We keep the country, city, an approximate location rounded to about 10 km and the network provider (for example, a mobile carrier), not the address.

From Cloudbeds, with the hotel's authorisation, we receive the hotel's reservations (guest name and email, dates, amount, status and source) so we can tell which guests came back and booked.

When we email a guest on the hotel's behalf, we record whether the email was delivered, opened and clicked. Opens are measured by our email provider; for clicks we store the browser (user agent) and a one-way hash of the IP address, not the address itself. Before the first email to an address, we check that it can receive mail with an address verification service.

If a guest unsubscribes, or an email bounces or is marked as spam, we keep the address on that hotel's do-not-email list so we don't write to it again.

6. Why we use it

  • To provide Converstay: find guests who left the booking engine, send the hotel's follow-up emails, and show the hotel which bookings came back.
  • To run accounts, security and support, and to send service emails such as invitations, trial reminders, weekly summaries and alerts.
  • To bill subscriptions and meet our tax and accounting obligations.
  • To answer people who contact us.
  • To keep the service working and fix problems, using technical logs.

We don't sell personal data, we don't use it for advertising, and we don't use guests' data for any purpose of our own other than providing the service to that hotel.

Where data protection law such as the GDPR requires a legal basis: for hotel teams and billing, we rely on our contract with the hotel and our legal obligations; for security and service emails, on our legitimate interest in running a reliable service; for guests, on the basis the hotel, as controller, has for its own guests.

7. Who else processes data

We use these providers, each only for the purpose listed:

  • Cloudflare: hosting, database, logs and sending our own emails (all data).
  • Amazon Web Services (Amazon SES): sending the hotel's emails to guests (guest email, name and the stay in the email).
  • Emailable: checking that a guest's email address can receive mail (the address only).
  • Stripe: subscriptions, payments and invoices (billing data).
  • Cloudbeds: the hotel's property management system, which we read with the hotel's authorisation.
  • Google Fonts: the fonts of our website and dashboard (visitors' IP addresses).
  • Google Analytics: visit statistics for our public pages (visitors' IP addresses, browser details and analytics cookies).

We may also disclose data when the law requires it, or to a buyer of the business, who would remain bound by this policy.

8. International transfers

Our providers process data in the United States and other countries. When data leaves Mexico, the European Economic Area or the United Kingdom, we rely on our providers' contractual safeguards, such as the European Commission's standard contractual clauses.

9. How long we keep it

  • Booking engine visits that didn't lead to a booking: deleted after 365 days without activity, together with their emails and clicks.
  • Phone numbers typed into the booking form: deleted 90 days after the guest's last visit.
  • Visits matched to a booking, the hotel's reservations and the results we report: kept while the hotel's account is open, because they are the hotel's record of recovered bookings.
  • Do-not-email lists: kept while the hotel's account is open, so unsubscribes keep working.
  • Technical diagnostics: 7 days. Copies of Cloudbeds notifications: 30 days.
  • Account and team data: while the account is open.
  • Invoices and billing records: as long as Mexican tax law requires (currently five years).

When a hotel closes its account, we delete its data within 30 days of its request, except what the law requires us to keep. A hotel can export its data as CSV files from the dashboard at any time.

10. Your rights

Depending on where you live, you can ask to access, correct or delete your personal data, to object to or restrict its use, to withdraw consent, and to receive it in a portable format. In Mexico these are the ARCO rights.

Write to contact@converstay.com, saying who you are and what you are asking for. We may ask you to confirm your identity. We answer within 20 business days. If you are a hotel's guest, we forward your request to the hotel and help it answer.

You can also complain to the data protection authority of your country.

11. Security

Data travels encrypted (HTTPS). Cloudbeds API keys are encrypted at rest, passwords are stored as hashes, staff accounts can use passkeys and two-factor authentication, and each hotel sees only its own data. No system is perfectly secure; if a breach affects your data, we will tell the affected hotels and people as the law requires.

12. Children

Converstay is a service for businesses and is not aimed at children. Hotels should not use it to email guests who are minors.

13. Changes to this policy

When we change this policy, we update the date at the top. If a change matters to how we use your data, we tell hotel accounts by email before it applies.