FLIGHTBRIEF

Privacy Policy

Privacy Policy

FlightBrief is operated from Switzerland. This page explains what personal data we collect, how we use it, and the limited circumstances in which it is processed.

Data Controller

The data controller for FlightBrief is FlightBrief, Switzerland. If you have questions about this policy or your personal data, you can contact us atcontact@flightbrief.news.

What We Collect

  • Email addresses you choose to submit through our Beehiiv newsletter signup forms.
  • Aggregate analytics collected by FlightBrief's own measurement, described in detail below.
  • Anonymous analytics collected through Cloudflare Web Analytics, used as a cross-check on our own traffic figures.

We do not ask you to create an account and we do not intentionally collect more personal data than is needed to operate the newsletter and understand which articles are read.

Our Own Analytics

FlightBrief runs its own measurement rather than sending reader data to an advertising network. It records the page visited, the page you arrived from, how long the page was on screen, how far down it you scrolled, clicks on links leaving the site, terms typed into the site search, newsletter signups, and how quickly pages loaded. Your country, region, city, device type, browser and operating system are derived from the connection.

We never store your IP address. It is used only in memory, to compute the identifier described below, and is then discarded. We do not build advertising profiles, we do not track you across other websites, and we do not sell or share this data with anyone.

This data is stored on Cloudflare infrastructure operated by FlightBrief and is retained indefinitely so that long-term trends remain comparable. You may ask us to delete data associated with you at any time.

Cookies and Your Choice

When you first visit, you are asked whether you accept an analytics cookie. Your choice is remembered in your browser and you can change it at any time using the buttons below.

If you accept, we set two first-party cookies:fb_vid, a random identifier that lasts one year and lets us recognise a return visit, and fb_sid, which expires after 30 minutes of inactivity and groups pages into a single visit. Neither contains your name, email, or IP address, and neither is readable by any other website.

If you decline, or have not yet answered, no cookie is set and nothing is stored in your browser. You are counted using a one-way cryptographic hash of your IP address, browser and the current date. It cannot be reversed into an IP address, it cannot be linked to anything else, and it changes every day at midnight UTC — so from our side you are a new, unrecognisable reader tomorrow.

We also honour the Global Privacy Control browser signal. If your browser sends it, no cookie is set and you are never shown the banner.

Checking your current setting…

How We Use Data

  • To deliver the FlightBrief newsletter to subscribers who request it.
  • To see which articles are read, which are finished, and which bring subscribers, so we can decide what to cover next.
  • To review aggregate traffic trends and site performance.

We do not use personal data for profiling, resale, or unrelated marketing activities.

Newsletter and Unsubscribe Rights

If you subscribe to the newsletter, you may unsubscribe at any time by using the unsubscribe link included in any email or by contactingcontact@flightbrief.news.

Sharing and Third Parties

FlightBrief does not sell your personal data to third parties. Our own analytics data is not shared with anyone and never leaves infrastructure we control. Limited processing may be carried out by service providers that operate the newsletter infrastructure or hosting on our behalf, including Beehiiv for newsletter delivery and Cloudflare for hosting, storage and anonymous traffic measurement.

Data Protection Standards

FlightBrief aims to process personal data in accordance with the Swiss Federal Act on Data Protection (FADP) and, where applicable, GDPR-equivalent principles including transparency, purpose limitation, and data minimization.