Privacy policy for the FarePath application
Controller
The controller under the GDPR is ZusammenStromen GmbH, Holzdamm 40, 20099 Hamburg, Germany, email info@zusammenstromen.de. FarePath is a project of ZusammenStromen GmbH. All provider details are in the legal notice.
ZusammenStromen GmbH has appointed an external data protection officer, Dr. Marschall (GDPC – Marschall und Blazy GbR, Ludwig-Erhard-Straße 12, 34131 Kassel). You can reach the data protection officer by email at datenschutz@zusammenstromen.de, or by post with the note “Datenschutzbeauftragter (vertraulich)”.
What this policy covers
This policy is for the FarePath application at app.fare-path.com, which travel agency staff sign in to. We are completing it. For now it describes how you sign up for a test account and how the application reports errors. The website fare-path.com has its own privacy policy.
Signing up for a test account
You can sign up for a test account on the application’s sign-up page. We then store:
- the name of your agency, your name and your email address
- the campaign tags of the link that brought you to us, if it had any:
utm_source,utm_mediumandutm_campaign, which name the ad or newsletter, never you - a code we email you to confirm the address, stored only in a form that cannot be read back, and how many times it was tried
We send the code to your email address. Nothing is created until you type the right code. With a work email address, your test account is created at once: an account for your agency and a user account for you. With a free email address, such as Gmail, we create nothing yet: we look at the request first and email you when your account is ready. We tell our team in our internal Slack workspace about each sign-up, with the details above.
We use the data to create and run your test account, to contact you about it, and to see which of our campaigns brought you. The legal basis for the account is Art. 6(1)(b) GDPR, steps you asked for before a contract. For the campaign tags and the note to our team it is Art. 6(1)(f) GDPR: our legitimate interest is to know which advertising works and to answer new agencies quickly.
A request you never confirm is deleted after one day. A request we decline is deleted after 30 days. Once your test account exists, the request is kept with the account and deleted with it.
Error reporting with PostHog
When the application fails, we want to know so we can fix it. If our server hits an unexpected error, or a script error happens in your browser while you use the application, a report goes to PostHog.
A report from our server contains:
- the type of error, its message and the places in our code where it happened
- the part of the application that was called (for example
/evaluate), the request method and the response status - whether it was the test or the live application, and which version of our code ran
- the internal ID of your account, if you were signed in
- if the request came from the application in your browser, the random session ID described below
A report from your browser contains:
- the type of error, its message and the places in our code where it happened
- the address of the page, without anything after a
?or# - a random visitor ID, a random session ID and a random tab ID, which live in the page’s memory and are gone when you close or reload the tab
- whether it was the test or the live application, and which version of our code ran
- the internal ID of your account, once you are signed in
The account ID is a random string. It contains no name and no email address. Before a report is sent, we remove the text an error quotes from input it could not read, and replace email addresses, numbers of six or more digits and long quoted passages with fixed markers such as “[email]”.
What is not sent: the content of requests, headers, anything you type or paste into the application, itineraries, passenger data, your name or email address. The browser part sends nothing about your device: no browser or operating system, no screen size, no language or time zone, no page you came from. Apart from the two counts in the next section, the live application sends no page views, no clicks and no other usage events. It makes no session recordings and creates no user profile at PostHog.
Nothing is left on your device for this: no cookies, no local storage. The script keeps what it needs in the page’s memory only. When it starts, it checks once whether your browser’s storage works, by writing a test entry and removing it at once, and looks for an opt-out entry. It sends the error our own code produced and the page address, and none of your device’s properties. We hold that this needs no consent under § 25 TDDDG. Where it is seen as access to your device, it is strictly necessary to provide the application you asked to use, because without error reports we cannot keep it working (§ 25(2) no. 2 TDDDG).
Each time the application opens in your browser, the browser loads two small parts of the error reporting script from PostHog (eu-assets.i.posthog.com), and sends each report to PostHog directly. PostHog therefore receives your IP address and your browser’s identification string with these connections, as every server you connect to does. We have set PostHog to discard the IP address of reports without storing it and not to derive a location from it. Our server does not pass your IP address to PostHog; for the server’s reports PostHog sees our server’s address.
We use PostHog’s EU cloud (PostHog Inc., USA), which stores the data on servers in Frankfurt, Germany. PostHog processes it on our behalf as a processor, under a data processing agreement we have concluded with it (Art. 28 GDPR). PostHog Inc. may access the data from the USA. That transfer is based on PostHog Inc.’s certification under the EU-U.S. Data Privacy Framework (Art. 45 GDPR). We keep error reports for at most 25 months and then delete them. It is the period our PostHog project keeps all its data, and it lets us see whether an error that returns is one we had fixed before.
The purpose is to detect, trace and fix faults and to keep the application secure and available. The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is an application that works and stays secure for the agencies that use it (see also Art. 32 GDPR). We weighed it against your interests. The reports identify you only by a random account ID, are built to carry no content you entered, are used for nothing else, build no profile of you and are stored in the EU.
You can object to this processing at any time under Art. 21(1) GDPR by writing to info@zusammenstromen.de. Because the reports carry your account ID, we can find the reports linked to your account and delete them when you ask.
Counting sign-ups and upgrades with PostHog
We want to know how many travel agencies sign up for a test account, which of our campaigns brought them, and how many later move to a paid plan. For that, our server sends PostHog two events and no others:
- When someone confirms the email address of a sign-up for a new agency: that a sign-up happened, whether the address belongs to a company or to a free email service, and the campaign tags of the link the person came from (
utm_source,utm_mediumandutm_campaign, for example “linkedin”). A tag longer than 64 characters, or with spaces or signs other than-,_,.and:, is left out. Our campaign links name a channel or a campaign, never a person. - When we move an agency from the test plan to a paid plan: that an upgrade happened.
Each event also names our server and says whether it came from the test or the live application, and which version of our code ran.
The events contain no name, no email address, no agency name and no account or agency ID. Our server sends them under its own fixed ID, so PostHog cannot link them to you or to your other reports, and builds no profile from them. Your browser sends nothing for them and nothing is stored on your device. PostHog sees our server’s address, not yours. In our own database we keep the sign-up with its campaign tags. Because we could match an event to that record by its time, we treat the events as personal data.
PostHog receives and stores the events as described for error reports above: EU cloud with servers in Frankfurt, as our processor under a data processing agreement, with access from the USA under the EU-U.S. Data Privacy Framework. We keep them for at most 25 months.
The purpose is to measure which campaigns bring agencies to FarePath and how many become customers, so we spend on the ones that work. The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is measuring our own marketing (Recital 47 GDPR). We weighed it against your interests: the events are counts without any ID, are used for nothing else and are stored in the EU.
You can object to this processing at any time under Art. 21 GDPR by writing to info@zusammenstromen.de. The events carry no ID, so we cannot pick out a single one afterwards. We then remove the campaign tags from your sign-up in our database.
Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR) and data portability (Art. 20 GDPR). You may also lodge a complaint with a data protection supervisory authority (Art. 77 GDPR).
No automated decision-making, including profiling under Art. 22 GDPR, takes place.
Right to object. Where we process your data on the basis of Art. 6(1)(f) GDPR, you may object at any time on grounds relating to your particular situation (Art. 21 GDPR). We then stop, unless we can show compelling legitimate grounds that override your interests, or the processing serves legal claims. An email to info@zusammenstromen.de is enough.
The supervisory authority responsible for ZusammenStromen GmbH is the Hamburg Commissioner for Data Protection and Freedom of Information (Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit), Ludwig-Erhard-Straße 22, 20459 Hamburg, datenschutz-hamburg.de. You may also complain to the authority where you live or work.
This policy was last updated on 13 November 2026.