raisl apps
Routen / Privacy

Privacy Policy of the “Routen” app

Last updated: 7 November 2026 · Deutsche Fassung (in case of doubt, the German version prevails)

1. Controller

Philipp Raisl (Raisl Apps)
Düsseldorfstraße 17/3/6
1220 Vienna, Austria
Email: office@raisl-apps.at

2. General

The “Routen” app does not require a user account. We do not collect names or email addresses. Location data is only processed when you use “Stops near me” or “My location” (see below). Favourites, saved routes and settings are stored exclusively on your device and removed when you delete the app. The exceptions are commuter mode and the delay alert (see section 7).

3. Timetable information

When you search for stations or connections, your input (station names, desired date/time) is sent to our server at Render (Render Services, Inc., USA) and forwarded from there to the ÖBB timetable information service – for connections and departures within Switzerland, to the timetable interface of opentransportdata.swiss (Open Data Platform Mobility Switzerland on behalf of the Swiss Federal Office of Transport) instead. For technical reasons, your IP address is processed. The data is used only to answer the request and is not stored permanently. To protect the server from overload, it counts requests per IP address in memory for at most one minute; after that the address is discarded (Art. 6(1)(f) GDPR, legitimate interest in a stable service). The legal basis is Art. 6(1)(b) GDPR (provision of the requested feature).

The same applies to the “Day trip – How far can I get?” feature (Routen Pro): the app sends your starting point (rounded to roughly 100 m for “My location”) and the chosen time range to our server, which determines the reachable places via the timetable service and caches the result – without any link to your device – for up to three hours. The list of destinations is our own public list of places on our server.

4. Location (“Stops near me”, “My location”, meeting point)

The app only uses your location when you trigger it and allow location access: when you tap “Stops near me” in the departure board, or choose “My location” in the route search or the meeting point feature. For the stop search, the coordinates are rounded on the device to about 100 metres; for the route search and meeting point to about 10 metres, so that the walk to the nearest stop can be calculated. They are only sent to our server to make the request to the ÖBB timetable information service or, in Switzerland, to opentransportdata.swiss (see section 3). They are not stored, not combined with other data and not used for advertising. There is no background location access. You can revoke the permission at any time in your device settings. The legal basis is Art. 6(1)(a) GDPR (consent).

5. Disruption notices

Notices about disruptions and out-of-service lifts come from the ÖBB timetable information service and from the open real-time data of Wiener Linien (Open Government Data). Our server retrieves this data in general; no data about you is sent to Wiener Linien.

6. Reminders and notifications

Reminders before departure, the get-off alarm and delay notices during a trip are scheduled as local notifications directly on your device. No data is sent to us or third parties for this. The exceptions are the notices of commuter mode and the delay alert (Routen Pro): they arrive as push notifications from our server (see section 7). You can revoke the notification permission at any time in your device settings.

7. Commuter mode, delay alert, widget and lock screen

Commuter mode (Routen Pro): When you switch on commuter mode, we store on our server at Render: the start and destination of your route, the usual departure time, the selected weekdays, a push identifier of your device (Expo push token) and the anonymous RevenueCat user ID to check the Pro subscription (see section 12). On the selected days, from about 60 minutes before the usual departure, our server queries the connections from the ÖBB timetable information service (in Switzerland from opentransportdata.swiss) and sends you a notification in case of a delay or cancellation – or once if everything is on time – including a faster connection if there is one. The notification is delivered via the Expo push service (650 Industries, Inc., USA) and from there via the Apple Push Notification Service (Apple Inc.) or Firebase Cloud Messaging (Google Ireland Limited); these receive the push identifier and the text of the notification. If you switch off commuter mode, we delete the entry immediately. Entries that have not been renewed for 60 days – the app renews them every time it starts – and entries of devices on which the app is no longer installed are deleted automatically. The legal basis is Art. 6(1)(b) GDPR (provision of the requested feature).

Delay alert (Routen Pro): If you have switched on the delay alert for a journey, the app registers that journey with our server when you tap “Start journey”: the legs (line, boarding and alighting stops, planned and current times, platforms), the connection identifier of the timetable service, your device’s push token, your anonymous RevenueCat identifier (to verify the subscription, see section 12) and the “accessible” setting. Every two minutes the server asks the timetable service (ÖBB or opentransportdata.swiss) for the current state of this journey and sends you a notification via Expo’s push service in case of a delay, cancellation, platform change or a connection at risk – even when the app is closed. Your location is not transmitted. The entry is deleted automatically 30 minutes after arrival, or immediately when you tap “End journey”. Server logs contain no places, routes or identifiers. The legal basis is Art. 6(1)(b) GDPR (providing the feature you switched on).

Widget: If you use the “My route” widget, the app also checks the next connections in the background – roughly every 15 minutes or less often, as the operating system allows. As with any timetable request, start, destination and time are sent to our server (see section 3) but not stored. If commuter mode cannot be registered with the server, the app checks the route itself in the same way.

Lock screen: The display of the current trip on the lock screen (iOS: Live Activity, Android: notification) is created directly on the device; no additional data is transmitted for it. You can switch off commuter mode, the widget and the lock screen display at any time in the app or in your device settings.

8. Disruption alerts “My lines” (our own server)

If you follow up to three Wiener Linien lines in the app (“My lines”), the app registers those line names together with your device’s push token and your app language with our server at Render. Every minute the server checks the public disruption reports of Wiener Linien (open data, see section 5) and, as soon as a new report affects one of your lines, sends you a notification with the official text via Expo’s push service (see section 7). For this, the server remembers which reports it has already sent you. Your location, your routes and your searches are not transmitted; no subscription is required. If you remove the last line, the entry is deleted immediately; otherwise it is deleted automatically 60 days after the last registration (the app re-registers the lines each time it starts). Server logs contain no identifiers. The legal basis is Art. 6(1)(b) GDPR (providing the feature you switched on).

9. Calendar and sharing

If you add a connection to your calendar, on iOS start, destination and times are sent to our server, which creates a calendar file from them; on Android the Google Calendar event template opens, and this information is sent to Google. We do not store the data. When sharing your arrival time, you decide yourself who receives the message.

10. Maps

For the live map and the full-screen map, the app uses the map services of the operating system: Apple Maps on iPhone (Apple Distribution International Limited, Ireland) and Google Maps on Android (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). When map sections are loaded, your IP address, the displayed map section and technical device information are transmitted to the respective provider; the position of your train is drawn on the device only. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in a working map display). More information: apple.com/legal/privacy, policies.google.com/privacy.

11. Advertising (Google AdMob)

In the free version we show banner ads via Google AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). Device identifiers (e.g. the advertising ID/IDFA), IP address, device information and interactions with ads may be processed.

More information: policies.google.com/privacy. With a Pro subscription, no ads are shown.

12. In-app purchases (RevenueCat)

Subscriptions are handled via the App Store or Google Play. To manage the subscription status we use RevenueCat (RevenueCat, Inc., USA). A randomly generated, anonymous user ID and purchase information (product, purchase date, expiry date) are processed. We do not receive payment data. If you use commuter mode or the delay alert, our server uses this anonymous ID to ask RevenueCat whether a Pro subscription is active. The legal basis is Art. 6(1)(b) GDPR. More information: revenuecat.com/privacy.

13. Transfers to third countries

Some of the providers mentioned are based in the USA. Transfers are based on the EU-US Data Privacy Framework or the EU Standard Contractual Clauses.

14. Your rights

You have the right of access, rectification, erasure, restriction of processing, data portability and objection, as well as the right to withdraw consent at any time. Please contact the address above. You can also lodge a complaint with a data protection supervisory authority, in Austria the Data Protection Authority (dsb.gv.at).

15. Children

The app is not specifically directed at children under 13.

16. Changes

We update this privacy policy when the app or the legal situation changes. The version published here applies.