New name, same site: FareDice is now also at MultiTripScanner.com
Currency: EUR

Prices in euros.

FareDice / Privacy

Privacy

Last updated November 14, 2026

FareDice is run by Buretto Technologies Inc., a British Columbia company, 422 Richards St, Suite 170, Vancouver, BC V6B 2Z4, Canada.

Without an account it keeps only your own choices, in your browser:

  • Cookie cur: the currency you pick, for a year.
  • Cookie rg: whether you last looked at Europe or Southeast Asia, for a year.
  • Cookie sid: keeps you signed in, if you sign in, until 90 days pass without a visit (a year at most) or until you sign out.
  • Cookie signin: while you sign in, lets only this browser use the emailed code, for 15 minutes or until you sign in.
  • Booked flights: on a trip page, the flights you tick as booked, kept in your browser's local storage until you clear it; it never reaches us.
  • Signed in on this browser: that this browser was signed in when you last opened your account page or saved a trip, so the header can show its Saved link; removed when you sign out or your account page shows you signed out.
  • Trips saved on this device: trips you save while signed out (each trip's link, places and dates), kept in your browser's local storage until you sign in and choose to move them into your account, or until you clear it.
  • Booking details: on a trip page, the booking references, sites and times you type for flights you've booked, kept in your browser's local storage until you clear it; it never reaches us and is never put in a link.
  • Set every detail: once you change a setting under Set every detail in the search, a note to open it on your next visit, kept in your browser's local storage until you clear it; it never reaches us.
  • Words on the cards: on a trip page, which of the three word lists you picked for the cards, kept in your browser's local storage until you clear it; it never reaches us.
  • Where your visit began: the address of the first page you opened and where you came from (a search engine, an AI assistant's link, a shared trip), kept in your browser's session storage until you close the tab, and sent with a price-check click.

We collect as little as we can:

  • Searches: we don't keep a log of who searched for what. For the flights between a home airport and the long flight, there and back, we count each day how often a price was found, and we count how many searches waited because many people were searching at once, with nothing about who asked.
  • Flights from home: to price the flight between your home airport and the long flight, we look up that route's fares for the month on Aviasales' fare data (through Travelpayouts). The lookup holds the two airports and the month, nothing about you.
  • Check these prices again: on a trip page, Cloudflare Turnstile first checks that a person pressed it (Cloudflare sees your browser and IP address for that); then we ask Aviasales' fare data (through Travelpayouts) for each flight's two airports and date, nothing about you. To keep it to 10 a day each, we count rechecks under a scrambled form of your IP address and browser, kept until the day ends, and a daily total with no addresses for 30 days. Signed in, the same button asks Google Flights through SerpApi for each flight's two airports and date first, nothing about you; we count those checks under your account until the day ends.
  • AI-assistant calls: when an assistant searches through our MCP server, we count the call, which of its tools it used and the first word of its browser string (the software's name), and keep a one-way hash of its IP address and browser string for 30 days, to count how many different callers use it. For a caller that comes back on 5 or more days in those 30, we also keep its browser string, which names the software calling, to tell automated checkers from assistants. Never the search itself or the IP address.
  • Price-check clicks: when you click Check price or another partner link, the page tells us a click happened, with the first page of your visit and where you came from. We keep only which kind of page that was (a city's trips, a route, a month), what kind of place you came from (a search engine, an AI assistant, a shared trip, or none), and a one-way hash of your IP address and browser string, for 30 days, to count how many different people click and from where. Never the trip, the link, the page's full address, the other site's name or the IP address.
  • Sent trips: when you press Send this trip, or open a trip someone sent you, the page tells us so and we keep a one-way hash of your IP address and browser string for 30 days, to count how many different people send and open trips. Never the trip, who it went to or the IP address.
  • Trips opened from our card on another site: when you follow a trip from a FareDice card on someone else's page, the trip page tells us so, with the name of the site the card was on, and we keep a one-way hash of your IP address and browser string for 30 days, to count how many different people come that way. Never the page's full address or the IP address. The card itself sets no cookies.
  • Arrivals from other sites: when you open a page from another site, such as a search engine or an AI assistant, the page tells us the name of that site and which kind of page you landed on (a city's trips, a route, a month), and we keep your browser's first language setting (such as en or de) and a one-way hash of your IP address and browser string for 30 days, to count how many different people come to each kind of page and which languages they read first. Never the page's full address, what you searched for or the IP address.
  • Links from AI assistants: when you open one of our pages from a link an AI assistant tagged with its name (such as ChatGPT's utm_source=chatgpt.com), we count the assistant and the kind of page, and your browser's first language setting (such as en or de), with the same one-way hash for 30 days. Never the page's full address or the IP address.
  • Link previews: when an app fetches a trip's or page's preview image (WhatsApp, iMessage, Telegram and the like), we count which app it was, with a one-way hash of the fetching app's IP address and browser string for 30 days. Not who sent the link or to whom.
  • Searches: when you search for trips, we count whether it was a search, a Surprise me or a Roll again, with a one-way hash of your IP address and browser string for 30 days. Never what you searched for or the IP address.
  • Visit statistics: Cloudflare Web Analytics counts page views without cookies or tracking you across sites.
  • Error reports: if a page breaks, Sentry receives the error and basic browser details so we can fix it.
  • Your rough location: from the approximate location Cloudflare reads from your IP address, the home page preselects the start city nearest you, prices show in your country's currency, and a first visit opens Europe or Southeast Asia, whichever is nearer. It isn't stored or logged.
  • Server logs: Cloudflare, which hosts the site, processes IP addresses to deliver pages and block abuse, and keeps short-lived logs.
  • Search engines: when each day's new pages are ready, we send their addresses to search engines through IndexNow, so new trips are found sooner. Only page addresses, nothing about visitors.
  • Partner links: when you follow a partner link, the partner (Aviasales, Yesim, Welcome Pickups, Expedia and 12Go) and Travelpayouts, which runs their affiliate programmes, receive the visit with our partner code, under their own privacy policies.
  • Email: if you write to us, we keep the conversation in Google Workspace to reply.
  • Accounts: signing in is never needed. If you make an account we keep your email address, when you made it and last signed in, and the trips you save (their links and what their flights cost when saved, and for a trip you ask us to watch, the price we last emailed and the currency to write it in), in Cloudflare's database; the sign-in email and any watch email go through Resend. Before a sign-in email goes out, Cloudflare Turnstile checks that a person asked for it (Cloudflare sees your browser and IP address for that). To limit sign-in emails, we count each hour's requests under a scrambled form of the address and of your IP address, deleted each night once the hour is over, so kept a day at most. A sign-in you don't finish keeps the address with its code for 15 minutes, and it is deleted that night. Your account page lists the trip alerts kept for your address, and one you make while signed in with it starts without a confirmation email. "Delete my account" on your account page removes it at once, with its saved trips and those alerts.
  • Trip alerts: if you save a search for email alerts, we keep your email address, the search, the consent you gave, when you gave it and a one-way hash of your IP address, so we can email you new trips and show we had your consent. Each day we run the search and, when new trips match, send one email through Resend, our email provider. A fare alert on a route page keeps the route and your price in place of a search, and the days and fares it has emailed you, and its email lists new fares at or under your price. Unsubscribing, or deleting the alert, deletes it at once; an alert never confirmed is deleted after 7 days, and one whose dates have passed or with nothing new for 60 days ends with one last email and is deleted.

Processors: Cloudflare (hosting, analytics), Sentry (errors), Google Workspace (email), Resend (trip alert emails). We don't sell or share personal information. Questions or requests: hello@faredice.com.