Last updated: 27 October 2026
This policy explains what personal data Foyard collects when you search for and book travel with us, why we use it, who we share it with, how long we keep it and what your rights are. If you use Foyard through ChatGPT, Codex or Claude, section 5 describes exactly what our plugin receives.
Foyard (www.foyard.ai) is operated by BNBWELCOME d.o.o., Medvedgradska ulica 49, 10000 Zagreb, Croatia, registered with the Commercial Court in Zagreb under company reg. no. 081154746, OIB 28460718905, VAT ID HR28460718905. In this policy "Foyard", "we", "our" and "us" mean Foyard and its operator BNBWELCOME d.o.o., which is the controller of the personal data described here, except where we say that another company decides how it uses your data.
For any question or request about your personal data, e-mail admin@foyard.ai or write to BNBWELCOME d.o.o., Medvedgradska ulica 49, 10000 Zagreb, Croatia. We reply within one month.
This policy applies when you use any of the following:
It does not cover how OpenAI or Anthropic handle your conversations with ChatGPT, Codex or Claude, or how airlines, hotels and other travel providers handle your data once they have it. Their own privacy policies apply (sections 5 and 6).
If you book for other people, you give us their details. Please make sure they know that their details are shared with us and with the travel providers as this policy describes.
For each kind of data: what it is, why we use it and our legal basis under Article 6 of the GDPR. Section 4 explains the legal bases.
Do you have to give us personal data? You don't need to give us any personal details to search. To book, the contact and traveller details the checkout page asks for are needed to make the booking, including dates of birth where the provider needs them and travel documents where the carrier requires them: without them we cannot complete it. Where we issue an invoice, Croatian law requires the details it must contain. Other details, such as special requests, loyalty cards or saving your details for your next booking, are optional, and so is everything you tell our chat assistant beyond what your search or booking needs.
What: The details of your searches, made on the website, in the app, in the chat or through an AI assistant using our plugin: origin and destination (cities, stations or airports), travel dates, the number of travellers and any ages you give, including children's ages, cabin class and transport modes. For stays: the place you search near, dates, number of adults, children's ages, rooms, filters and any hotel name you type. For car hire and airport transfers: the places, dates and times you search for. For rail passes: each traveller's country of residence and nationality, which our chat assistant asks for because they decide which passes you can buy.
We record each search in our search analytics: what was searched (for stays, also the map coordinates of the place), when, which suppliers returned which results, whether it succeeded, how long it took and the channel it came from (website chat, search page, ChatGPT, Claude and so on). The record also carries an internal request id that matches our server logs, a search id and, where they apply, the website chat conversation it came from and the organisation you are signed in under. If you book on the website or in the app, the order records the search id, so a search can be linked to a booking.
Why: To run the search and show the results; to understand demand and which suppliers cover which routes and places (aggregate analytics); to find and fix faults; and to link a booking made on the website or in the app to the search it came from.
Legal basis: contract (running a search you ask for); legitimate interests (analytics and fault finding).
What: Entered by you on the checkout page. For the lead booker: title, first and last name, e-mail address, phone number (some low-cost airlines, such as Ryanair, need two numbers) and billing address. For each traveller or guest: their name. For hotels: the names of the guests in each room. For car hire: the driver's name.
Why: To make and manage the booking, send confirmations, tickets and vouchers, tell you about changes (for example a schedule change made by the airline), give you support and issue invoices.
Legal basis: contract; legal obligation for invoices.
What: Flights: the date of birth and gender of every passenger. Trains and buses: dates of birth, and gender when the carrier asks for it. Car hire: the driver's date of birth (Duffel receives it; Flexible Autos receives only the age). Some hotels: the lead guest's date of birth (we pass on the age).
Why: The airline, rail or bus operator, hotel or rental company needs it to issue tickets and to price fares that depend on age (child, infant, youth, senior, driver age).
Legal basis: contract.
What: Only when the carrier requires it, for example advance passenger information for flights to the United States: passport or national ID number, expiry date, issuing country, nationality and country of residence, and, where an airline asks for them, a Known Traveler Number, Redress Number or tax ID. Some bus and train operators ask for a government ID type and number.
Passport, ID and other travel-document numbers are entered only on the checkout page. Our chat assistant is instructed not to ask for them, and our plugin for ChatGPT, Codex and Claude has no field for them and never asks for them. Nationality and country of residence can also come up in the chat when you look for a rail pass (section 3.1).
Why: The carrier needs it to issue the ticket and to meet border-control and passenger-information rules.
Legal basis: contract; the carrier uses it to meet its own legal obligations.
What: Frequent-flyer numbers and corporate account codes (some airlines); loyalty and discount cards (some bus and train operators).
Why: To apply your benefits and fares.
Legal basis: contract.
What: Routes, dates and times, carriers, flight numbers (for transfers and car hire), pick-up and drop-off addresses with their map coordinates (transfers), hotel, rooms and occupancy, seats, bags and other extras, prices, booking references, airline booking codes, tickets, vouchers, Apple Wallet passes, and any special requests you write.
Special requests are free text that we pass to the provider. They can reveal health or accessibility needs, so please write only what the provider needs to know.
Why: To provide and service the booking, handle cancellations and changes, give you support and issue invoices.
Legal basis: contract.
What: Card details are typed into a form provided by Stripe, which processes the payment; we do not see or store your card number. If you pay with PayPal, your PayPal account details stay with PayPal. Crypto payments for our own apartments go through Coinbase Commerce. We keep the payment status and payment references. We give Stripe your name and e-mail address, the amount, what you are paying for (for example the hotel name or the flight route) and order references; section 6 lists what PayPal and Coinbase receive.
For hotel rates paid at the hotel, your card is encrypted in your browser by Evervault. We keep the encrypted card details (without the security code), together with your IP address and browser user agent, for at most one hour, and Evervault passes them to Amadeus and the hotel to guarantee the booking. For some flights we pay the airline with our own company card rather than yours, and some hotel bookings can be paid the same way; the lead guest's name then goes with our card to RateHawk's payment service, Payota.
Why: To take payment, guarantee hotel bookings, make refunds and prevent fraud.
Legal basis: contract; legal obligation (accounting records); legitimate interests (fraud prevention).
What: If you create an account: your e-mail address, password (handled by our sign-in provider), full name and, optionally, the organisation you ask to join or create. In your account settings: your phone number. Accounts created before October 2026 may also hold a personal identification number entered in an earlier version of the settings. We also keep your role, approval status, when you accepted the terms, e-mail verification records and, if you ask us to delete your account, its deletion status. If you sign in with Google or Apple, we receive your name and e-mail address from them.
Why: To run your account and sign-in, your organisation membership and order history, and account deletion.
Legal basis: contract.
What: Organisation name, business address, phone, registration number, VAT ID, members and the e-mail addresses of people invited to join. For hosts who manage their own properties in our back office: property details, the guest bookings for those properties and calendar (iCal) entries synced from other platforms, which can include guest names.
Why: To run company, agency and host accounts and to attribute orders to an organisation. An order a member places while signed in under an organisation is visible to the other members of that organisation, including the traveller details.
Legal basis: contract with the organisation; legitimate interests for the data of its members and guests.
What: Your messages and the assistant's replies, the result cards it shows, internal records of the searches it ran, images and documents you attach (PDF, Word, Excel, text, Markdown, CSV) and, if you use voice input, your voice recording. If you ask the assistant to cancel or change a booking, or to add extras such as bags, it uses your booking reference and the booking e-mail address; to confirm a cancellation or a change, we send a code to that address.
If you are signed in, conversations are linked to your account; if not, to an anonymous id stored in your browser. Voice recordings are sent to OpenAI to be transcribed and are not stored by us. The assistant runs on OpenAI's models; section 6 lists what OpenAI receives.
The assistant is instructed not to ask for personal details other than those described here; you enter the rest on the checkout page. Anything you type is stored, so please don't type card numbers, passport numbers or health information into the chat.
Your messages reach our servers inside the request, not in the web address, so they are not part of the request logs our servers and hosting provider keep. The start of each voice transcript is logged, and so are the web searches the assistant makes, together with the start of your message.
Why: To provide the assistant, let you come back to a conversation, and find and fix faults.
Legal basis: contract (providing the assistant you choose to use); legitimate interests (fault finding).
Why: security, rate limiting and fraud prevention, finding and fixing faults, push notifications, and keeping an anonymous chat across visits.
Legal basis: legitimate interests; consent for push notifications (you allow them in iOS and can turn them off there).
What: The e-mails we send you (confirmations, tickets, vouchers, invoices, verification and cancellation codes), copies of some booking e-mails kept in our reservations inbox, cancellation and change requests with their verification codes, a log of the actions taken on each order (which user or staff member did what), the text of push notifications, and older messages between hosts and guests.
Why: Booking communications, support and an audit trail.
Legal basis: contract; legitimate interests (support and audit trail).
What: Buyer details, invoice numbers, amounts, VAT, payment method and reference, fiscalisation codes (ZKI and JIR), invoice PDFs and the e-mail address an invoice was sent to.
Why: Croatian accounting, VAT and fiscalisation law requires them.
Legal basis: legal obligation.
What: If you accept analytics cookies, Google Analytics 4 records page views and events on our home, sign-in, registration and list-your-property pages, and on pages you go on to open in the same tab, using a cookie with a random client id. Google receives your IP address and browser details when its script loads. Analytics never runs in the app.
Why: To understand how the website is used.
Legal basis: consent, which you can withdraw at any time with "Cookie Settings" in the website footer (section 11).
We do not receive the following:
In the app, the camera, photo library and microphone are used only when you choose to attach a photo or record a voice message in the chat.
We use personal data for these purposes, on these legal bases:
What the legal bases mean:
We do not use personal data for advertising, we have no advertising cookies or trackers, and we do not build profiles of you across searches. We do not sell personal data.
Our AI assistant and plugin only make suggestions. The supplier confirms the price and availability, and you choose and pay on a checkout page. We make no decision about you by automated means that has legal or similarly significant effects (GDPR Art. 22).
Some abuse protections are automatic: a limit on requests per IP address, a guard against repeating the same search many times, and a limit of three airport-transfer bookings per e-mail address in 24 hours. If one of these stops you, contact us.
The Foyard plugin for ChatGPT and Codex and the Foyard connector for Claude (together, "the plugin") let the AI assistant you use search Foyard and open a Foyard checkout page. You need no Foyard account and no sign-in.
Our tools have fields only for the details listed above. If an assistant puts something else into one of them, for example into a place or hotel name, it reaches our server like any other search text, and our server logs and search analytics can record it.
Legal basis: contract (the searches and checkout you ask for); legitimate interests (security, rate limiting, error monitoring and analytics). We do not use plugin data for advertising or build profiles across searches.
The results we return become part of your conversation: offers, prices, hotel details, image links through our proxy and checkout links, together with the search details you gave (route or place, dates, number of travellers, children's ages and rooms) and a search reference. When you press Book on a result card, the card also tells the assistant that you opened checkout for that option at that price. On Claude, the results also carry the time of the search, and a checkout result carries the pending order's reference and the supplier; the card's note includes that order reference.
OpenAI (ChatGPT, Codex) and Anthropic (Claude) handle your conversation as independent controllers under their own privacy policies; we do not control what they keep.
We share personal data only as needed for the purposes in section 4.
During a search, suppliers receive your search details, not who you are. When you book, the supplier of that offer receives the traveller details it needs:
These platforms pass on what is needed to the airline, rail or bus operator, hotel, rental company or transfer provider that delivers your trip, wherever in the world it is. The platforms and those providers use it as independent controllers under their own privacy policies.
Apartment bookings are shared with the host of that property: for our own apartments, that is us. Other hosts receive your name, e-mail, phone, number of guests, dates and special requests, and use them as independent controllers.
If you book while signed in under a company or agency account, the other members of that organisation can see the order, including the traveller details.
Stripe and PayPal also act as independent controllers for your payment data.
On the flight globe in the chat, your browser asks OpenStreetMap's Nominatim service to locate city names and loads a globe image from the unpkg service. On the website, airline logos and hotel photos load directly from our suppliers' and their partners' image servers (for example Kiwi.com, Duffel, RateHawk, Restel, Google and Amazon CloudFront), and the home page loads Apple's App Store badge from Apple. Checkout pages load scripts from Stripe, PayPal, Evervault, All Aboard and Duffel. All of these receive your IP address and user agent.
The checkout scripts are needed for the booking you ask for (contract). We load the maps, fonts, images and the globe to show you a working page (legitimate interests).
Invoice data goes to the Croatian Tax Administration for fiscalisation. We disclose personal data to courts, police or other authorities when the law requires it, or to protect our rights and safety.
We are based in Croatia, in the European Union, and our servers and database are hosted in the European Union.
Some recipients in section 6 are outside the European Economic Area (EEA) or may process data outside it:
Any other recipient outside the EEA that is not in a country the European Commission recognises as adequate is covered by the Standard Contractual Clauses. You can ask us for a copy of these safeguards.
When you book travel abroad, we send your details to the airline, hotel, rail or bus operator, rental company or transfer provider that delivers your trip, in the country concerned, because that is necessary to perform the booking you ask for (GDPR Art. 49(1)(b)). The booking platforms and payment providers in between are covered by the safeguards above.
When you use our plugin in ChatGPT, Codex or Claude, you share your conversation with OpenAI or Anthropic directly, and their policies say where they process it.
Result snapshots are emptied after 30 days, and the records are deleted after 13 months.
When you delete your account in your account settings, it is scheduled for deletion, and you can cancel by signing in within 30 days. After 30 days your profile is anonymised and your login deleted, together with your push tokens, e-mail verification records and chat conversations. Bookings are not deleted with the account; they are kept as described below.
Invoices, fiscal records and invoice PDFs: 11 years, as Croatian accounting law requires.
Cookies and browser storage are listed in section 11. Where the law requires us to keep data for longer, for example for a legal claim, we keep it for that time.
Under the GDPR you have the right to:
To use these rights, e-mail admin@foyard.ai. We may ask you to confirm that the request comes from you, for example from the e-mail address used for the booking. We reply within one month, or tell you within that month if a complex request needs up to two more months.
You can also do some of this yourself:
If you live outside the EU, you may have similar rights under your local law. Contact us to use them.
Searching through any of our channels is open to everyone, including teenagers, and needs no personal details. Making a booking or creating an account requires you to be 18 or over.
When an adult books for a child, the adult gives us the child's name, date of birth and, where the carrier requires it, passport details. We use them only to make and deliver that booking and share them only with the providers who need them. Searches can include children's ages, but not who the children are.
We do not knowingly collect personal data directly from children under 13. If you believe a child has given us personal data, contact us at admin@foyard.ai and we will delete it.
cookie-consent: remembers your cookie choice; 1 year (also kept in your browser's local storage).sidebar:state: remembers whether the back-office menu is open; 7 days.fy_autos: gives access to our car-hire preview page after you enter its password; 30 days.Google Analytics 4 sets its _ga cookies on our home, sign-in, registration and list-your-property pages, and on pages you go on to open in the same tab, and only after you accept analytics. They last up to 2 years.
We use no marketing or advertising cookies, pixels or trackers. The cookie settings panel also shows Marketing and Preference switches; nothing we use depends on them.
The cookie banner offers Accept all, Reject all and Customize. Until you choose, we use only essential cookies and storage. The banner is not shown on checkout pages. There we use only the cookies and storage the checkout needs, and the payment and booking services the page loads (Stripe, PayPal, Evervault, All Aboard and Duffel) may set their own cookies, for example for payment and fraud prevention. You can change your choice at any time with "Cookie Settings" in the website footer, or by deleting cookies and site data in your browser.
The app shows no cookie banner because it runs no analytics and no advertising trackers.
The code of the plugin's result cards in ChatGPT, Codex and Claude sets no cookies and uses no browser storage; when the stays map opens, Google Maps runs in the card under Google's privacy policy.
Checkout pages load Stripe, PayPal, Evervault, All Aboard and Duffel; our pages load Google Maps and Google Fonts; airline logos and hotel photos load from our suppliers' image servers, and the App Store badge from Apple; the flight globe uses OpenStreetMap's Nominatim and unpkg. They receive your IP address and user agent and may set their own cookies under their own policies. Section 6 gives our legal basis for loading them.
Some of our booking e-mails and checkout links contain a private access code for that order, which does not expire. Anyone with such a link can see the order, so please do not forward them.
If a data breach puts your rights at risk, we will tell you and AZOP as the GDPR requires.
We will post any update on this page and change the "Last updated" date. If a change materially affects how we use data we already hold, we will tell you before it applies, by e-mail to account holders and with a notice on the website.
Privacy questions and requests: admin@foyard.ai
Post: BNBWELCOME d.o.o., Medvedgradska ulica 49, 10000 Zagreb, Croatia
Foyard is operated by BNBWELCOME d.o.o., company reg. no. 081154746, OIB 28460718905, VAT ID HR28460718905.