Privacy policy

How Railcation handles your data. As of 15 November 2026.

This English version is a translation for your convenience; only the German version is legally binding.

Controller

Sarah Hirt, Gubener Straße 1, 10243 Berlin, info@railcation.de

Key points

  • A user account is optional. Without an account, your saved list and last search are stored only in your browser.
  • With an account, we store your email address, your saved lists and the station or city of your last search on our own server in Germany.
  • We set cookies only for signing in, not for advertising or audience measurement.
  • Bookings always take place with the respective booking partner. From the moment you click on their offer, their privacy rules apply.

Hosting and server logs

Railcation runs on its own server at Hetzner Online GmbH (Falkenstein data centre, Germany): the site itself as well as the place, walking route and timetable services behind the search. When you visit the site, the server processes technically necessary connection data, in particular your IP address, the time, the address requested and your browser identifier, in order to deliver the site and fend off attacks. The server deletes these logs automatically after 30 days. This period is chosen so that even slowly developing attack patterns and errors can still be traced. We have a data processing agreement with Hetzner; your data does not leave the EU in the process. The legal basis is our legitimate interest in secure operation (Art. 6(1)(f) GDPR).

Audience measurement (Umami)

We use Umami, self-hosted software for audience measurement, to see which pages are visited how often and which features are used how often. Umami runs on the same server of ours in Germany, works without cookies and does not create cross-device profiles; no data flows to third parties. For each visit, Umami stores a pseudonymous session identifier without the IP address, as well as country, city, device, browser and the pages visited with their full address. For a search, this also includes the start and destination with their coordinates, the travel dates and the number of guests. Umami also counts individual clicks, for example on an offer or on “Ticket on bahn.de”, saving a place to stay, the choice in the window that offers you an account, sharing a link, opening the filters or choosing travel dates. As attributes of a click we send Umami only fixed values such as the position on the page, the provider or the region, never anything you enter. We keep the counts for 14 months and then delete them. The legal basis is our legitimate interest in audience measurement (Art. 6(1)(f) GDPR).

User account

If you create an account, we store your email address, your saved lists with the places you saved (section “Your saved lists”) and when the account was created and last changed. We also record when you last used the account and when we sent you the confirmation email after it was created or an email before deletion. We do not store a name, even if Google sends us one.

For each sign-in we create a session: a random identifier, its expiry date and when it was created and last extended. We delete expired sessions, at the latest together with your account. We do not store your IP address or your browser's identifier in the process.

So that nobody requests a large number of sign-in emails or guesses codes in a short time, the server counts requests per IP address and per email address in its working memory for up to 24 hours; this is not saved. If this limit takes effect, the operations log contains a truncated hash value of the email address or the truncated network part of the IP address, not the full details (30 days, see Hosting). The legal basis for this is our legitimate interest in preventing misuse (Art. 6(1)(f) GDPR).

We need this data to give you the account you asked for: your saved lists on all your devices. The legal basis is the performance of the contract for the account (Art. 6(1)(b) GDPR). The account terms are on the terms of use page. Without an email address we cannot give you an account. Everything else on Railcation also works without an account.

The data is held in a database on our own server at Hetzner Online GmbH in Germany, the same server as the rest of the site.

You can delete your account at any time on the “Account” page. We then immediately delete your account, your sessions, the connection to Google or Apple, your saved lists, your starting point, your setting “I travel with a Deutschlandticket” (with it, we always search local and regional transport only), your reminders and your contact at Brevo (section “Emails with travel ideas and news from Railcation”). What remains is the record of your consents (section “Record of your consent”), the backup copy for up to 14 days (section “Backups”) and, at Brevo, the logs of the emails we have sent you. We delete accounts that have not been used for 24 months; we email you 30 days beforehand.

If you delete your account on the “Account” page or ask us to by email, we then send an email to the account's address saying that it has been deleted. It states the date, what we deleted with the account, what remains and where to write if you did not want it deleted. After the deletion, our server uses your email address only to hand over this one email to Brevo (section “Account emails (Brevo)”); it is not stored for this. The legal basis is the performance of the contract for the account, which includes its end (Art. 6(1)(b) GDPR). If we delete an account because it has not been used for 24 months, we do not send this email.

Your saved lists

With an account you can keep several saved lists. For each list we store in your account its name, the IDs of the places to stay in it with the date on which you saved them, when the list was created and when a place to stay was last added. If you enter travel dates, the number of people and rooms or a starting point for a list, we store that too. As a starting point we only store a station or a city (name and coordinates), never an address. This way your lists are available on all your devices. The legal basis is the performance of the contract for the account (Art. 6(1)(b) GDPR).

We delete a saved place to stay from the list 180 days after you saved it. If the list has travel dates, the place to stay remains in it at least until the check-out day. You can delete a list at any time together with all the places to stay in it. Only the list “Saved list” cannot be deleted; it belongs to every account. When the account is deleted, we delete all lists.

If you share a list, your browser builds a link with the IDs of the places to stay, the name of the list and, if you entered them, its travel dates. The link does not contain the number of people and rooms, the starting point or your email address. We do not store anything for sharing. Anyone who opens the link sees the places to stay and, above them, the name and dates of the list, even without an account. Like any address visited, the link then remains in our server log for 30 days (section “Hosting and server logs”) and in our audience measurement for 14 months (section “Audience measurement (Umami)”).

Your starting point

If you are signed in, we store in your account the station or city you last searched from (name and coordinates), how many people and rooms you entered and when you last changed either of them. This way both are also available on your other devices. We do not store an address you enter as a starting point in your account; it stays only in your browser. The legal basis is the performance of the contract for the account (Art. 6(1)(b) GDPR). You can remove the starting point and number of people on the “Account” page; when the account is deleted, we delete both completely.

If you turn on the “I travel with a Deutschlandticket” switch on the “Account” page, we store this setting in your account. Every search then starts with “Local and regional transport only”, on all your devices, as long as you are signed in. Here too the legal basis is the performance of the contract for the account (Art. 6(1)(b) GDPR). You turn the setting off again with the same switch; when the account is deleted, we delete it completely.

Timetable reminder

If you cannot find a timetable for a travel day on our site yet, you can ask to be reminded. For this we store in your account the arrival day, the name of the region, place to stay or search, the page you were on (without your starting point, but for example with the number of guests) and when you requested the reminder. As soon as our timetable covers that day, we send you exactly one email via Brevo (section “Account emails (Brevo)”) and then delete the reminder. If the timetable is not out by your travel day, we delete it without an email. You can have at most five reminders at a time.

The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time: with “Undo” directly after requesting it, on the “Account” page or via the link in the email. When the account is deleted, we delete all reminders. We record that you consented as described in the section “Record of your consent”.

If you tap the button without being signed in, your browser remembers the reminder for up to 30 minutes so that it is created after you sign in without a second tap. If you close the sign-in window before you sign in or request a sign-in email, it forgets the reminder immediately.

Sign-in cookie

After you sign in, our server sets a cookie called __Secure-railcation-konto.session_token. It contains your session identifier, cannot be read by scripts on the page and is only sent over encrypted connections. It is valid for 60 days. If you use the site, it is extended, at most once a day. We remove it when you sign out and when you delete your account. If you sign in with Google or Apple, the server sets a second cookie for the duration of the redirect, __Secure-railcation-konto.state, which expires after 5 minutes and only checks that the return belongs to your request.

These cookies are strictly necessary to keep you signed in, which is what you asked for (§ 25(2) no. 2 TDDDG). They therefore do not require consent. The processing is based on Art. 6(1)(b) GDPR.

Signing in with Google

You can sign in with your Google account. Only when you tap “Continue with Google” does the site redirect you to Google; before that, the site loads nothing from Google, no script and no image. Google asks you there whether you give us access to your basic data. We request exactly three things: your Google ID (openid), your email address (email) and your basic profile with name and profile picture (profile). Google also tells us whether the email address is verified; without a verified address we do not create an account.

With the account we store your Google ID. We do not store the access tokens that Google issues at sign-in, your name or the address of your profile picture. If an account already exists for your Google address, we link the two.

The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. What Google itself processes during sign-in is governed by Google's privacy policy. The legal basis on our side is the performance of the contract for the account for which you chose this route (Art. 6(1)(b) GDPR). Google may also process this data in the USA. Google LLC is certified under the EU-US Data Privacy Framework; the European Commission's adequacy decision for the USA therefore applies (Art. 45 GDPR).

Signing in with Apple

You can sign in with your Apple ID. Only when you tap “Continue with Apple” does the site redirect you to Apple; before that, the site loads nothing from Apple. We only request your email address from Apple, not a name. Apple also tells us whether the address is verified. At Apple you can choose for us to receive a forwarding address from Apple instead of your real address. Apple forwards emails sent to this address to you.

With the account we store your Apple identifier, but no access tokens from Apple. If an account already exists for your address, we link the two.

The provider is Apple Distribution International Limited in Ireland. What Apple itself processes during sign-in is governed by Apple's privacy policy. The legal basis on our side is the performance of the contract for the account (Art. 6(1)(b) GDPR). Apple may also process this data in the USA. According to Apple's privacy policy, such transfers from the EU are safeguarded by standard contractual clauses (Art. 46(2)(c) GDPR).

Account emails (Brevo)

We send the sign-in email with code and link and the other emails about your account, such as the confirmation after it is created, via Brevo (Brevo GmbH, Köpenicker Str. 126, 10179 Berlin). Brevo receives your email address and the content of the email for this. Code and link are valid for 10 minutes; we hold them only in encrypted form or as a hash value. Brevo processes this data on our behalf (Art. 28 GDPR). The email is sent to Brevo by our server, not by your browser. The legal basis is the performance of the contract for the account (Art. 6(1)(b) GDPR).

Brevo places an invisible tracking pixel in these emails and redirects the links in them via its own addresses. We have instructed Brevo to record opens and clicks only as totals, without any connection to you. We do not analyse these figures.

If you request a sign-in email and do not sign in, no account is created. Your address then remains in our database only until the code and link have expired, and is deleted by the next day at the latest. It then remains in the backups for up to 14 days.

Record of your consent

Each time you sign in and whenever you agree to a new version, we record which version of the account terms you agreed to, with the time and a hash value of the text, and which version of this privacy policy was linked at that point. The same applies when you subscribe to emails with travel ideas and news from Railcation, when we then sign you up for these emails at Brevo, and when you unsubscribe on the “Account” page or delete your account. If you unsubscribe via the link in an email, Brevo records it. We also record when you request a timetable reminder and when you remove it again (section “Timetable reminder”). Instead of your email address we store a hash value for this, which only we can derive from the address using a secret key.

If you delete your account, these entries remain without any connection to the account. We delete them three years after the last entry for your address, because claims are generally time-barred after three years (§ 195 BGB). As long as we base emails on your consent, we must be able to demonstrate it (Art. 7(1) GDPR, Art. 6(1)(c) GDPR). After that, and for your agreement to the account terms, we have a legitimate interest in being able to prove them in the event of a dispute (Art. 6(1)(f) GDPR).

Emails with travel ideas and news from Railcation

After your first sign-in we ask you: “Shall we send you travel ideas and news from Railcation now and then?” With “Yes, please” you agree, with “No, thanks” you do not. You can also do this at any time on the “Account” page with the “Get travel ideas” button under “Emails with travel ideas and news from Railcation”: “Send me travel ideas and news from Railcation now and then.” Nothing is preselected. If you agree, we sign you up for these emails straight away, without a confirmation email: your address is already verified, because you only get an account with the code or link from our email or via Google or Apple with a verified address. Our record is our proof that you agreed (section “Record of your consent”). Your address is then on our list for these emails at Brevo. It stays there until you unsubscribe from the emails or delete your account. If you unsubscribe on the “Account” page, we take you off the list; if you use the link in an email, Brevo blocks your address for these emails. In both cases your address remains at Brevo as an unsubscribed contact so that the unsubscription takes effect and nobody writes to you again by mistake. If you delete your account, we delete the contact at Brevo completely. If you want this sooner, an email to info@railcation.de is enough.

The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time: with the “Unsubscribe from travel ideas” button on the “Account” page, via the link at the end of every email or by email to info@railcation.de. We keep the record of your consent for a further three years afterwards (section “Record of your consent”).

Backups

We back up the account database every night on our server and keep the last 13 backups. We also store an encrypted copy of each backup in storage at Hetzner Online GmbH in Finland (EU). We delete older backups automatically in both places. After your account is deleted, your data therefore remains in these backups for up to 14 days. We only need the backups to restore the database after a fault. The legal basis is our legitimate interest in secure operation (Art. 6(1)(f) GDPR).

Storage in your browser

Some features store data only in your browser (localStorage or sessionStorage). Whatever is in sessionStorage disappears when you close the tab. You can delete everything at any time in your browser settings. Without an account, the saved list stays only there. With an account, your browser syncs it with our server (section “User account”). Storage in the browser is necessary for the features you have requested (§ 25(2) no. 2 TDDDG).

When you open your saved list, your browser sends the IDs of the places you saved and, if available, the dates and number of people of the list or of your last search to our server, because we are not allowed to store prices and availability and instead fetch them fresh from the provider each time you open the list. This information is only processed for that purpose, not stored; if the provider does not recognise an ID, it appears in an error line in our operations log (30 days, see Hosting).

Until you delete them or they expire (localStorage):

  • Last search: Start and destination with their coordinates, including a starting address you entered, plus the number of people and rooms and the type of accommodation, so that the home page can fill them in. For the starting point it notes whether it is a station, a city or an address, and when you last changed the starting point and number of people. Expires after 60 days. With an account, we sync the station or city and the number of guests with your account, but not an address.
  • Saved list: Only the IDs of the places you saved, no names and no prices. Expires after 180 days.
  • Filter tip seen: So that the tip bubble on the filter button does not appear every time.
  • Continued without an account: So that we do not ask you about an account again after you save a place.
  • Account tip hidden: The time at which you tapped “Later” on the saved list, so that the tip stays hidden for 30 days.
  • Sync with the account: Your account ID and the saved list at the last sync, so that your browser knows what you have since removed on another device. If you sign out on the “Account” page, we delete this entry and the saved list in this browser; it remains in the account.
  • Starting point in the account: Starting point and number of guests as they were in your account at the last sync. If you sign out on the “Account” page, we delete this entry and, in this browser, the starting point and guests insofar as they come from your account.
  • Deutschlandticket in the account: Whether your setting “I travel with a Deutschlandticket” is turned on in your account, as at the last sync, so that the pages apply it as soon as they load. If your sign-in ends or you sign out, we delete this entry.
  • Reminder noted: Arrival day, page and name of the timetable reminder you requested without being signed in, so that we can create it after you sign in. Valid for 30 minutes. If you close the sign-in window before you sign in or request a sign-in email, we delete it immediately.
  • List choice noted: ID and name of the place to stay you saved before signing in, so that we can then show you the choice of list for it. Valid for 30 minutes. We delete it immediately after you sign in.
  • Sign-in in progress: A time 15 minutes after a sign-in is started, so that the browser asks for your account during that time.

Until you close the tab (sessionStorage):

  • Filters: Your filters for each search.
  • Sorting: The sort order you chose for each search.
  • Position in the results list: So that when you come back you continue reading where you left off.
  • Travel dates: Check-in and check-out of your current search.
  • Landscapes and themes: What you selected on the home page.
  • Home page tab: Which search tab you last selected.
  • Last saved list response: The places to stay shown, kept for one minute so that nothing has to be reloaded when you come back.
  • Reloaded after an update: A time, so that the page reloads itself at most once a minute after an update.

Location request

Only if you click “My location” and your browser agrees do we process your coordinates to work out a starting address from them. For this, the coordinates go to our server and from there as a search request to the geocoding service; we do not store them. The legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time in your browser.

Search requests to data services

For the search and the journey calculation we process search parameters: places, coordinates, travel dates, number of people. Place suggestions, walking routes and train connections are calculated by our own services on the server named above; for this, the data no longer leaves our systems. Search parameters go to external services only for places to stay and prices. The first is Stay22. Availability, prices and the offers of the booking sites come from there. Here too we do not transmit your IP address: the requests are made by our server, not by your browser. Stay22 is based in Canada; the search parameters therefore go to a country outside the EU. The European Commission has adopted an adequacy decision for Canada: it certifies that the country provides an adequate level of data protection for commercial organisations subject to the Canadian data protection law PIPEDA (Art. 45 GDPR). The legal basis is the provision of the feature you have requested (Art. 6(1)(b) and (f) GDPR).

The second is the Emerging Travel Group (RateHawk/ZenHotels), from which our accommodation catalogue comes. The names, descriptions and amenity details of the places to stay are held as a dataset on our server. For names and descriptions, no request goes outside while you browse. When a photo is shown for the first time, our server fetches it once from the provider, stores it and shows it from there afterwards, as described further below. Only if you open a place to stay with travel dates selected do we additionally request the price for exactly that one property there. What is transmitted is the ID of that one place to stay, the travel dates and the number of adults per room, plus three fixed details that say nothing about you: language German, currency euro and “Germany” as the assumed country of residence, on which the prices depend. This request is also made by our server: the provider does not receive your IP address, your starting address or your contact details. Our contractual partner is Emerging Travel Inc., based in Dover in the US state of Delaware; this information therefore also goes to a third country. As described, the request itself consists of information with no connection to you as a person.

Content from other providers

Your browser loads two types of content directly from the respective provider, which receives your IP address in the process: map tiles from OpenFreeMap as soon as you open a map view, and photos from the image servers of the booking sites if a photo in the search results or on a page for a place to stay comes from there. The legal basis is our legitimate interest in displaying the content (Art. 6(1)(f) GDPR).

Our server fetches three further types of content from the source and passes them on to your browser: the photos of the places to stay from our accommodation catalogue, on a page for a place to stay the preview images of sights in the area (image server upload.wikimedia.org of the Wikimedia Foundation), and on maps with relief the elevation data for the relief shading (a storage service of Amazon Web Services). These providers are based in the USA. They only see our server: they do not receive your IP address, your browser's identifier or your cookies. We store the photos of the places to stay on our server when they are first fetched and show them from there afterwards. We do not store any information about you in the process. We do not store preview images and elevation data. Your browser keeps them in its cache for up to 30 days so that it does not have to reload them the next time. Relief is shown on the results map of the search, the two maps on a page for a place to stay, the map view of the destinations, the reach map and the Deutschlandticket city maps.

Forwarding to partners and to Deutsche Bahn

If you click on an offer or on “Ticket on bahn.de”, the respective provider's site opens (e.g. Booking.com or bahn.de). Booking links contain an affiliate ID through which bookings are attributed to us, as well as an identifier of the part of our site you clicked from (e.g. results list, region page including the position in the list). It describes our site, not you. The providers set their own cookies under their own responsibility. Such links are marked as “sponsored”. What happens to your data from then on is governed by the respective provider's privacy policy.

The same applies to excursions: on the destination pages we refer to our excursion partner GetYourGuide. The link leads to a search on getyourguide.de and carries our partner ID alongside the name of the place, so that a click is attributed to us. Only when you click does your browser open the page there, and only then does GetYourGuide receive your IP address; nothing is loaded from their servers before that. These links are also marked as “sponsored”.

Emails to us

If you write to us at info@railcation.de, we process your email address and the content of your message in order to reply. Our mailbox is hosted by Apple (iCloud Mail); your message is processed and stored there. Apple may also transfer it to the USA and, according to its privacy policy, bases such transfers on standard contractual clauses of the European Commission (Art. 46(2)(c) GDPR). The legal basis is our legitimate interest in answering enquiries (Art. 6(1)(f) GDPR).

Your rights

You have the right of access, the right to rectification, erasure and restriction of processing, the right to data portability and the right to object (Art. 15 to 21 GDPR). An informal email to info@railcation.de is enough. You can also lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Berlin Commissioner for Data Protection and Freedom of Information.

Right to object

We process some data on the basis of our legitimate interest (Art. 6(1)(f) GDPR): the server logs, the audience measurement, the maps and photos loaded directly, the rate limit that protects sign-in from misuse, the backups of the account database and the record of your consents. You can object to this processing at any time on grounds relating to your particular situation (Art. 21(1) GDPR). An informal email to info@railcation.de is enough; you do not need to give a reason. We will then no longer process the data concerned unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or we need the data to establish, exercise or defend legal claims.

Changes

When Railcation gets new features with new data flows, we update this policy. The version published here at any given time applies.