Privacy Policy

Andeor Partner Calendar is an optional connection in Andeor Partner, operated by ANDEOR LIMITED. Andeor uses Google account and Calendar data only to provide, maintain, secure and improve the calendar connection, booking synchronization, availability and boat-assignment features that a partner requests, and to comply with applicable law. These limits apply to raw Google user data and to any information derived from it. Nothing else in the Andeor Privacy Policy or the Andeor Terms and Conditions, including any content licence, permits any other use, transfer, disclosure or retention of that data.

Permissions Andeor requests

Every partner who connects is asked to let Andeor identify the Google account by its email address and to create and manage a separate Andeor bookings calendar. A partner whose listings include a private-charter fleet is also asked, on the same Google consent screen, for read-only access to the calendar list and to calendar events, because the optional booking import needs it. A partner who approved only the first permissions can approve read-only import access later from the Calendar screen. Andeor never asks for permission to change or delete events in calendars it did not create.

Information we access and store

When you authorize the connection, we store your Google account email address, the permissions you granted, the connection and synchronization dates, an encrypted authorization token, and the identifier and name of the Andeor bookings calendar. If a synchronization fails, we keep a short error message so that you can see what needs attention. Short-lived access tokens are requested when needed and are not stored. We do not receive your Google password.

When you open the import settings or save a source, Andeor reads the names, including any name you gave a calendar yourself, identifiers, time zones, your access role and which calendar is your primary one, for the calendars you can read, so that you can choose a source. That list is shown to you and is not stored. For each calendar you select as a source, we store its identifier, name, time zone and your access role, how its events are matched to your listings, either through the listing and default boat you chose or through each event's Excursion field, and a Google synchronization marker that lets Andeor request only changed events.

Andeor reads events only from the source calendars you select. For each event it requests the identifier, creation and update times, cancellation state, start and end times, and description. It does not request event titles, attendee lists or locations. Use a dedicated booking calendar and avoid personal or sensitive notes in its event descriptions.

Descriptions are processed to recognize the supported booking templates and are never stored. From an accepted event, we keep the event identifier, its creation and update times, the booking start and end times with the boat turnaround time, the booking status, the total and the adult, child and infant counts, and the listing, option and boat identifiers that match your Andeor listing. Template fields for names, contact details, captains, prices and payment are discarded, and an option or boat that your listing does not define is not stored.

The optional Needs field can record fleet-assignment categories, limited to accessibility needs, pregnancy, travelling with an infant, premium options and returning guest. Andeor also records the infant category when the infant count is above zero, the premium options category when a selected option is set to prefer particular boats, and a marker that orders assignments by booking time. These categories are used only to assign boats, calculate fleet availability and show the reason for an assignment in your Andeor Partner workspace.

Events that do not follow a supported template are not imported. If such an event was imported before, its reservation is released. When an event follows a template but has a count, time, field, excursion or option name that Andeor cannot read, Andeor keeps the last valid import for that event and tells you how many events need correcting, without storing their contents. When an event names a boat that your listing does not define, Andeor imports the reservation without that boat and marks it as a conflict in your Andeor Partner workspace until you correct the event.

What we write to Google Calendar

Andeor adds paid or confirmed Andeor marketplace bookings to the separate Andeor bookings calendar. Each event shows the experience, the date and time, the guest count, the Andeor booking reference, the booking location and a link to the Andeor Partner bookings page. The booking location is the listing's meeting point, or the pickup or service address the traveller gave, which can be their accommodation or home. Listings that use the operator template also show the selected option, the assigned boat, the booking amount, the payment status, the departure time and Andeor's booking identifier. Each event carries Andeor's booking and partner identifiers in hidden event properties, and its event identifier is derived from the booking identifier, so that Andeor can update the right event later. Customer names, email addresses and phone numbers are not copied into these events.

Andeor refreshes an event when a booking is paid, when you respond to it in Andeor Partner or from its email link, when the Andeor team changes its date or time, when a boat is assigned to it, and when a traveller changes or cancels an unpaid booking that is on your calendar. It removes the event when the booking is no longer eligible at one of those moments. Connecting the account or pressing Sync now refreshes every booking dated from thirty days ago onward, and it also catches up any change that could not reach Google at the time. Andeor never changes or deletes events in your source calendars. Google processes the events in your account under your Google account settings and Google's own privacy policy.

How imported reservations affect availability

When you save an import source, you choose to include its reservations in the availability Andeor publishes. Imported reservations reduce the availability of the listing they are matched to and of any of your other listings that use the same boats. Andeor uses the result to decide whether a marketplace booking can be accepted and which boat can serve it. The listing's public page and its public availability feed then show each published departure's status, capacity, booked places and remaining places, and those figures include imported reservations.

Every Andeor service that shows or answers questions about availability uses the same published figures. This includes Andeor staff tools for bookings and Travel Agency itineraries, the Andeor website chat, the Andeor voice booking assistant, Andeor's automated replies to booking messages on Instagram, Facebook Messenger and WhatsApp, and the Andeor apps in ChatGPT and Claude. The website chat, message replies and itinerary assistant use OpenAI, the voice assistant uses ElevenLabs, and in ChatGPT or Claude the answer is part of the traveller's conversation with OpenAI or Anthropic. Message replies are delivered through Meta, including on social accounts owned by Andeor's distribution partner Mauritius Explored, whose team can read those replies. Answers that were already given can remain in those conversation records. None of these services receives imported event descriptions, event identifiers, individual imported reservations, source calendar names or Needs categories.

Limited Use and sharing

Andeor Partner Calendar's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs, including Google Calendar, will also adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.

Google user data, whether raw or derived, is never sold or transferred to advertising platforms, data brokers or other information resellers. It is never used to serve advertising, including personalized, interest-based or retargeted advertising, to build marketing or user profiles, or to assess creditworthiness or make lending decisions. Andeor does not use Google user data, whether raw or derived, to create, train or improve any artificial intelligence or machine-learning model.

Transfers are limited to what is necessary to provide the calendar, availability and booking features described in this section with your consent, to comply with applicable law, or to protect against abuse, fraud or security threats. Vercel and Supabase host and store this data on Andeor's behalf under access controls. Google receives the events Andeor writes to the Andeor bookings calendar. Andeor discloses Google user data to a regulator, court or law-enforcement body only when applicable law requires it or when it is needed to protect against abuse, fraud or security threats. No other service provider receives raw calendar data or imported reservation records, and published availability is shared only as described above.

People at Andeor do not read your connected Google account details, calendar list or imported reservations unless you have given documented, explicit consent for specific data, it is necessary to investigate a bug, abuse or a security incident, applicable law requires it, or the data has been aggregated and anonymized for internal operations. Andeor staff do see published availability figures, which combine all reservations and do not identify an imported event, when they manage bookings or read answers Andeor's assistants gave. Every member of your partner workspace can see its Calendar screen. Andeor administrators can also add a person to a partner workspace, for example when you ask. An Andeor staff member in a partner workspace opens its Calendar screen only with your documented consent for that specific data, or for the security and legal reasons above.

Security, retention and your controls

Connections use encrypted transport. Stored authorization tokens are protected with AES-256-GCM authenticated encryption and used only by Andeor's servers. Public and signed-in database access to connection, source calendar and imported reservation records is blocked. Only Andeor's servers and a small number of authorised administrators with infrastructure access can reach these records, and those administrators follow the limits above.

You can remove an import source or disconnect in the Calendar screen of Andeor Partner. When the connection shows an authorization error, Disconnect is still available there. Disconnecting turns off your source calendars, releases imported reservations from availability, attempts to revoke Andeor's access at Google and deletes the stored authorization token. If releasing reservations cannot finish, Andeor tells you and you can run Disconnect again. After you disconnect, Andeor no longer updates the events in its bookings calendar, so later changes or cancellations are not shown there.

You can also revoke access in your Google Account connections. That stops Andeor from reaching Google. The Calendar screen shows that the connection needs attention the next time Andeor tries to reach Google, for example when one of your Andeor bookings is synced. Revoking at Google does not by itself delete the stored token or release reservations that were already imported, so also use Disconnect in Andeor Partner.

Disconnecting does not delete the Andeor bookings calendar or its events in Google, which you can delete in Google Calendar. It also does not automatically delete the connection details, source calendar settings, cancelled imported reservations or their boat assignment history in Andeor. We keep these records until you ask us to delete them. To request deletion, contact info@andeor.travel and identify your partner workspace and connected Google email. Do not send passwords or tokens. When you ask, we delete your connection, source calendar and imported reservation records unless a specific legal obligation or security investigation requires us to keep them, and we explain any such exception in our reply. Deleted tokens and records can remain in Andeor's database backups until those backups are deleted, and backups are used only to restore the service. Andeor marketplace booking records are separate from imported calendar records and follow the booking retention terms of the Andeor Privacy Policy.

If Andeor wants to use Google user data in a way this section does not describe, we will update this policy first and ask for your consent in Andeor Partner before that use begins.