Privacy notice for Retreat & Be Hotels in ChatGPT

Service snapshot: 7 October 2026 · Read-only hotel search and comparison

This notice explains the data flow of the ChatGPT hotel app. Read it together with the Retreat & Be privacy policy and terms of service. The service is operated by RETREAT AND BE FRANCE. The individual verified publisher on OpenAI Platform is LUCNER DINAS ZAPE.

Data used to answer your request

The tools use the destination query or destination identifier, hotel identifiers, arrival and departure dates, guests per room, children's ages when relevant, guest nationality as a two-letter code, currency and an optional total budget. Nationality and currency must be supplied or confirmed; they are not inferred from your language. The interface uses your selected language or the language context supplied by ChatGPT.

The app does not require a Retreat & Be account and does not ask for guest names, passport or identity-document numbers, contact details, card details or health information. It has no tool for reading your existing reservations, booking, prebooking or payment. Please do not include these details in a hotel request.

Recipients and purpose

ChatGPT sends the hotel tool parameters to the Retreat & Be MCP server. This server calls the public Retreat & Be hotel API to find destinations, hotel descriptions and indicative room offers. The active hotel supplier for the tested release is LiteAPI / Nuitée. The API sends the supplier the stay, occupancy, nationality, currency and destination coordinates or hotel identifier required for the search. The budget is used to filter the returned offers.

Supplier processing, operational records and transfers are described in Nuitée's API data-protection documentation and privacy policy. These documents do not give a fixed numerical retention period for all API records. The app does not use tool inputs for an advertising tracker or a model-training feature.

Storage and technical records

The MCP service processes parameters in memory for each request and does not create a user-account database or a persistent hotel-search history. Its MCP and health routes have access logging disabled. The upstream hotel API and supplier can maintain technical and security records; the absence of an app search-history database does not mean that no technical records exist anywhere in the service chain. The deployed Retreat & Be API has operational-log rotation configured for 30 days and security/authentication-log rotation configured for 365 days. These are technical-record retention windows, not a hotel-search-history retention period. The MCP request parameters are discarded when request processing ends. For LiteAPI/Nuitée, the supplier states that records are retained for the period needed to provide the service and satisfy legal obligations; its published notice does not specify one numerical limit for every API record. You can request information or deletion from Retreat & Be using the contact below. This service-specific notice describes the hotel app; broader site/account retention periods in the general policy apply to those separate services.

The widget is displayed within ChatGPT. Your conversation and ChatGPT memory settings are governed by OpenAI's policies and controls. Hotel photos can load from external image hosts; those requests can disclose ordinary connection metadata to the image service. The app has no embedded advertising or analytics tracker.

Your controls and contact

You can disconnect the app in ChatGPT and manage your ChatGPT conversations and memory there. For questions about Retreat & Be processing, access, correction or deletion requests, contact confidentialite@retreatandbe.com. The data-rights page and main privacy policy explain the rights-request process.