Privacy

What the AI assistant does with your data — no more than we actually know.

This page describes what is genuinely in place in AtlasResa's code for the conversational AI assistant (website chat, WhatsApp, phone, email). It does not claim a compliance we have not had verified — see "Open points" below.

Last reviewed: August 30, 2026, against the repository's code as of that date.

What data is processed

When you write to the assistant, we keep the content of your messages, your name, email or phone number if you share them in the conversation, and technical metadata (channel used, language, timestamps).

No audio recording is kept for phone calls: the voice channel uses the phone carrier's live speech recognition, with no audio file stored on our side.

Every action the assistant performs for you (availability search, booking creation) is logged with its exact parameters and result, so the hotel can verify what actually happened.

Why we process this data

To carry out the booking you request: search, creation, lookup, cancellation.

To answer your questions and forward complaints to the hotel's team.

To follow up if you left a booking in progress — only if you explicitly consented. Without a recorded consent, no follow-up is sent: it's not an opt-out afterwards, it's a condition checked before sending.

How long we keep it

Conversations and everything attached to them (messages, assistant actions, handoffs to a human) are kept for 365 days by default, then automatically deleted every night by a scheduled job.

This period is a platform-wide setting, the same for every hotel — not a choice left to each property.

Who can see your conversations

The staff of the hotel you're talking to, through its management console — and only that hotel: a database-level separation prevents another property from accessing your exchanges, even by an application mistake.

The AtlasResa team, to operate the platform (for instance running the automatic purge described above).

Who else receives this data

The language-model provider generating replies receives the conversation content on every turn, with an explicit instruction not to use it to train its models.

Depending on the channel used: your phone carrier's speech recognition for calls, the WhatsApp platform for that channel, your payment provider to complete a booking.

  • We have not verified in which country these providers actually process the data — see "Open points".

How this data is protected

Each hotel can technically only access its own conversations: the rule is enforced by the database itself, not only by the screen that displays it.

Webhooks receiving inbound messages (phone, WhatsApp) verify a signature before any processing, to reject messages that don't genuinely come from the expected carrier.

Your rights

You can ask the hotel you talked to for access to, or correction of, information about you.

However, as of today, there is no self-service tool to request early deletion of a conversation before the 365-day period described above. This is a gap we document rather than stay silent about — see "Open points".

You will never be followed up on an abandoned booking without having consented to it.

Transparency

Open points — what we don't claim to have solved

As a matter of discipline, we prefer documenting what remains uncertain rather than displaying a compliance we haven't had verified.

  • Production hosting location: not documented in our deployment code as of today. We advertise no hosting location until it is verifiable.
  • Language-model, telephony, WhatsApp and payment subprocessors: their processing terms (location, data processing agreements) have not been audited as part of this work.
  • Early right to erasure for an individual conversation: not yet available as a self-service tool; only the automatic 365-day deletion exists today.

A question about your data?Contact the hotel you talked to, or our team directly.

Contact the team
AtlasResa — Booking engine & site officiel pour hôtels