Security

FarePath is built so that the safest data is the data it never has. This page says what it reads, what it keeps and why, in plain words. The legal detail is in the privacy policy.

What FarePath reads

Only what an agent pastes. FarePath has no connection to Sabre, Amadeus or Travelport, never logs in to them, and never sees the rest of your agency’s bookings.

What we never store

Passenger names, record locators, ticket numbers, and hotel or car lines. FarePath keeps only the flight lines. Record locators are stripped before anything is saved, and the database refuses any row that still contains one.

What we keep, and why

For each check: the flights as FarePath read them, the dates, the waiver it was checked against, the airline rule text the answer rested on, and which agent ran it. This is your evidence if an airline disputes the change later.

Who can see it

Only your agency. Each record is sealed to the agency that created it, so no other agency can read it, and records are never edited after they are written.

How long we keep it

Twelve months after the last flight in the record, which covers the airlines’ debit-memo dispute windows.

Where it lives

In Frankfurt, Germany, at Northflank, in a Google Cloud data centre.

No AI on your data

Answers come from the airlines’ published rules, not from a model trained on your bookings.

Questions

Write to our data protection officer at datenschutz@zusammenstromen.de, or to estefano@fare-path.com.