SO-Portal · Kevin Heinz
Gotlandweg 4 · 59494 Soest · Deutschland
kevinheinz911@googlemail.com
Privacy information
This page supplements the general SO-Portal privacy policy with the functions of the mobility planner, especially GPS, route queries, maps, browser storage and shared token links.
Location only after your action
The browser requests precise location only when you actively choose a GPS function. For a route calculated from it, the required coordinates are sent to the SO-Portal server and may be passed from there to the services needed for timetable, geocoding or routing. In the optional GPS trip companion under “Lines & trip progress”, another active tap can start continuous location updates from your device. They are used to compare your own position with the selected trip and its stops; this is not automatic tracking of the bus or train. Continuous observation ends when you switch off the trip companion or, at the latest, when you leave/close the page. A granted GPS position is additionally kept only for the current session in the browser planning context. The planner may locally remember for up to 180 days that you want to use the GPS trip companion. Precise location coordinates are not stored for 180 days. Automatic resumption occurs only while the browser still reports location permission as granted; the website cannot determine the lifetime of the browser permission.
External open data sources
Timetable and realtime queries are predominantly forwarded server-side to Transitous/MOTIS. Address and place search uses OpenStreetMap services such as Photon or Nominatim; walking and bicycle routing may use routing.openstreetmap.de. The server uses short caches for stability and rate limiting. If the local proxy is technically unavailable, individual functions may fall back to direct browser requests to Transitous/MOTIS or Nominatim. In that case the external service technically receives, in particular, the IP address of the requesting device.
OpenStreetMap & MapLibre
When the map/globe view is opened, the browser loads map tiles from OpenStreetMap. MapLibre resources are currently loaded from the unpkg or jsDelivr CDNs. This creates technical connections to these providers, including transmission of the IP address. The map view is only accessed when you open it.
Favourites, lines, last route and saved journeys
Favourite journeys, saved stops, saved lines, the last route needed for the map and saved journeys are stored locally in the browser. The current planning state and a granted GPS position are partly stored only for the current session. These data are not automatically synchronised with a user account and can be deleted through the browser settings.
Random token · 30 days
When you use “Share journey”, a random token address is created. The server stores the planning data required to restore the journey, for example origin/destination, resolved positions, travel area, date/time, filters and language. The share expires after 30 days. Anyone who knows the token link can open the stored journey until it expires. If the journey starts from GPS, the planner asks again explicitly before creating the link.
Technical operation and security
As with normal website requests, technically required connection and server logs may be generated by the hosting service. Details, legal bases, retention periods and your data subject rights are described in the general SO-Portal privacy policy.
General privacy policy
The central SO-Portal privacy policy additionally applies to portal-wide information, legal bases, recipients, data subject rights and contact options.
Open central privacy policy →