Confidentialité

What this site records about you, who else gets to see it, and why a demonstration still collects real data.

Ce passage est en anglais pour l’instant.

A demonstration that collects real data

FareSky sells nothing. No ticket is issued, no money moves, and the flights are generated rather than real. What is real is the data you type into it: if you fill in the checkout form, a name, a date of birth and a phone number go into a database, and they are as much about you as they would be on any other site.

So this page is written the way it would be for a site that did sell tickets. There are no accounts. Everything the site knows you did is tied to a session cookie in your browser. A booking also keeps the internet address it was made from, and roughly where that address is.

What is recorded when you book

Completing the checkout form writes one row, holding:

  • the passenger’s first and last name, date of birth and gender;
  • a contact email address and phone number;
  • the language of the page you booked on;
  • the flights chosen, the fare, and the price;
  • the card’s brand and its last four digits;
  • the identifier of the browser session that made it;
  • the IP address it was made from, and the city and country that address is in, as Cloudflare places it, when it can tell.

That last one is what My bookings looks you up by. Clear your cookies and the booking stays in the database, but this site can no longer connect it to you — and neither can you.

Every request to this site passes through Cloudflare, which carries it here and says where it came from. The address, city and country are kept with the booking and deleted with it, 90 days after its flight departs.

Who else receives it

A trip from this site’s own made-up timetable is booked inside the site and sent nowhere. A trip from a flight supplier is booked with that supplier, which is one of two:

  • FareSource, our own flight supplier service, which runs apart from this site;
  • Duffel, a UK company, used here only in its test mode, where no airline is booked and nothing is paid.

The one that books the trip receives each traveller’s name, date of birth and gender, with a title where it asks for one, and the contact email address and phone number. It also receives the booking’s reference. It is sent nothing about the card. What it does with the rest is under its own terms, not this page.

The emails below are sent through Mailtrap, which receives the address each one goes to and what it says.

Your card number does reach this server

It has to be said plainly, because the opposite is what most sites say. When you submit the checkout form, or the page for paying with another card, the card number, the expiry date and the security code are sent to the server. They are checked there.

What is kept is the brand and the last four digits. The number itself, the expiry and the security code are never written to the database and never written to a log. If the form comes back with an error, the page is drawn again with what you typed still in the fields, including the number — that is the browser showing you your own form, not the site storing it.

Nothing is charged. The card provider here is a stand-in written for the demonstration: it runs inside this site, talks to no bank and moves no money. It is handed a placeholder made from the card’s last four digits, never the number, and approves every card except two test numbers that are declined on purpose. What is kept of a charge is the stand-in’s own reference for it. Please do not type a real card number into it.

What is emailed

These, and nothing else. Each is sent through Mailtrap, a service that delivers email for us.

  • A price alert for a route you asked to watch, with “Watch this route” on that route’s page. It goes to the address you gave there when the fare drops under the price you set. Every alert has a link to stop it, and most mail apps also show their own “Unsubscribe” button for it.
  • The booking confirmation, once, when a booking is confirmed. It holds the booking’s references, its flights, the travellers’ names and ticket numbers, and the price paid, with the card’s brand and last four digits.
  • A trip reminder, once, about two days before a confirmed booking’s first flight. It lists the flights, the booking’s reference and each airline’s check-in code.
  • A note about a booking when the airline changes its flights and the change is accepted. It lists the flights before and after the change, and the booking’s references.
  • A note, once, when a booking still “Confirming” at the end of checkout could not be completed. It lists the flights and says they were not booked and nothing was charged.
  • A note, once, when a booking is cancelled, whoever cancelled it. It lists the cancelled flights and says what comes back, in Canadian dollars.
  • A note, once, if the charge for a confirmed booking is declined. It lists the flights and the amount owed in Canadian dollars, with a link to a page where you can pay with another card. The link works for that booking only, for 72 hours, and stops once a card is charged through it; this site stores only a scrambled copy of it, never the link itself. Until November 2026, if you had allowed analytics, the link itself could also reach Google and Yandex: see Google and Yandex below. Our staff can send it again, with a new link that stops the old one.
  • A note our staff send about a booking when the airline cancels its flights or its tickets change. It lists the flights and the booking’s references, and the travellers’ ticket numbers when those changed. Only a person sends it, never the site on its own.

The booking emails go to the contact address you gave at checkout, in the language you booked in, and that address is used for nothing else. Our staff can send one of them again from the booking’s page. See ticket did not arrive.

A route you watch

Watching a route stores your address, the two cities, the cabin, the price you want to beat, the price of the last alert you were sent, when you started watching, and the language of the page you did it on, which the alerts are written in. Stopping the alert deletes all of it for that route; the stop page can also stop every alert for your address at once.

The fare-alert list

The subscribe box in the footer stores the address you type and the time you typed it. Nothing else, and nothing is sent to it. It is not the price alerts above: those are for one route and are emailed, this list is not.

What is recorded when you search

Every search adds to a count: the two airports, the dates, the trip type and the cabin, with a running total of how often that combination has been looked for. It is what the footer’s popular routes and most-searched cities are built from.

Each search also gets a row of its own. It holds what you asked for — the two airports, the dates, the trip type, the cabin and how many people are travelling — and how the results came out. With it go:

  • a scrambled copy of your browser session’s identifier, so each step of one search finds the same row;
  • the country you searched from, as Cloudflare places it, when it can tell;
  • whether you searched on a phone or a computer, read from what your browser says about itself;
  • the page the search started from, such as the home page or a route’s page, or that you came from another site.

The row also notes what you did next: when you chose a flight, what the price check at checkout found, and the booking, if the search led to one. So a search can be traced to the browser that ran it, and to the booking it led to. The row is deleted 14 days after the search.

Google and Yandex, if you let them

Two analytics scripts can load: Google Analytics and Yandex Metrika. Both set their own cookies and both send data to their own companies, under their own policies rather than this one. Neither loads until you have said yes to the notice, and declining is final — there is no second ask and nothing loads in the meantime.

Even with your yes, they load only on the public pages and on search. They never load at checkout, on a payment link, on My bookings or saved flights, or on a price alert’s stop page. Yandex Metrika’s session recording, Webvisor, is switched off. The cookies page lists what each one is.

It was not always so. Until November 2026, with your yes, both loaded on every page, and Webvisor was on: it recorded what you did on the page — mouse movement, scrolling, clicks, keystrokes and the text on screen — and replayed it. The checkout and the pay-with-another-card page draw your card as you type it, number and security code included, so a recording made then could hold them. And the address of each page went to both companies, including a payment link and a price alert’s stop link, which carry their own one-time code.

What is deleted, and when

A cleanup job runs once a day and deletes what this site no longer keeps:

  • a booking, 90 days after its flight departs, with its passengers, their tickets, its history and any notes on it;
  • the counters that limit how often one IP address can book, subscribe or vote, once they are a day old;
  • the working copies of search results, after 30 minutes;
  • a search’s own row, after 14 days;
  • the record of each call to a flight supplier, after 30 days;
  • a flight you saved from a supplier’s results, once its departure date has passed.

Cancelling a booking does not delete it sooner: it is marked as cancelled and kept until the same date. A price alert is deleted, with your address in it, when you stop it. The address on the fare-alert list and the search counts above have no end date.

What this page does not have

A real privacy policy names a company that answers for the data, and gives you a way to ask what is held about you and to have it removed. This project has none of those, and inventing them here would be worse than saying so:

  • there is no named data controller, and no address to write to;
  • there is no route in this app to request, correct or erase your data, apart from stopping a price alert;
  • there is no way to have a booking removed early: it stays for the full 90 days after departure.

The practical consequence is simple, and it is the one thing worth taking from this page: treat anything you type into FareSky as staying for as long as the rules above say, and use made-up details.

Écrit pour décrire ce que ce code fait réellement, et vérifié par rapport à lui. FareSky est un projet de démonstration, pas une entreprise, et ces pages n’ont fait l’objet d’aucune révision juridique.