Privacy and use of your information
2026-11-07
Information we need
Your profile includes your legal name, optional nickname, phone with country code, email and basic login-provider identifiers. Your legal name and phone prefill booking forms for you to review and edit. Each order keeps its confirmed contact details, activities, prices and status. Phone numbers are not SMS-verified. We do not collect passport numbers.
Login and payment
Google and Facebook login verify your identity; they do not give this website access to your Gmail messages. Card details are handled on OEN’s payment page. We do not collect or store full card numbers.
Tickets and notifications
The website stores orders and issuance notifications. Booking staff send actual tickets separately by email. Orders are visible only to their member and authorized administrators.
Cookies and managing your information
Necessary cookies support login, verification and the price-check flow. This version loads no advertising trackers. You can request access, correction or deletion through your original booking contact; transaction records subject to mandatory retention are handled separately.
Recently viewed experiences
We keep the IDs and viewing times of up to eight recently viewed activities so you can continue browsing. Guest history stays in this browser; signed-in history is saved to your account and guest entries are merged when you sign in. Only entries from the last 90 days are displayed. You can remove individual activities or clear the history. Travel search terms may be sent to Microsoft Translator through the isolated translate.js service to search Viator in English. Account details, payment information and booking references are not sent to this translator.
Support email and Google authorization
We use the support mailbox Gmail API to send email verification and password-reset notifications; this authorizes sending from our support mailbox only and does not request access to members' Gmail or read their inboxes; recipient addresses and message content are sent to Google for delivery, while authorization credentials remain server-side