How EuroPlanner processes information when you browse, search for journeys or share a trip.
Draft revised: November 14, 2026. No effective date has been set.
This draft describes the information used by EuroPlanner's journey searches, city and airport pages, fare comparisons and optional shared-trip links. It reflects the current application features, but production infrastructure and operational practices still require confirmation.
Controller details pending: the operator's legal name, postal address, country and privacy contact email must be supplied before publication. The existing address [email protected] is a route-error and service-support contact; it has not been confirmed as the contact for exercising privacy rights.
The current journey-search and sharing features do not require a visitor account. EuroPlanner's fare lookup requests concern travel options; they do not ask for passenger identity or payment-card details. A separate booking provider may request those details when you choose to book.
Route searches are not confidential. A public recent-search endpoint currently makes recent search records available without signing in. The published fields include entered origin and destination names, travel dates and times, language and result information. The absence of an account name does not make these records anonymous: a home address or distinctive journey may identify someone.
Prefer town, airport or station names instead of private addresses. Do not enter another person's private travel details. The operator must review this public disclosure and its legal basis before publishing the final notice; this warning is not a substitute for appropriate privacy safeguards.
When you choose to share a trip, EuroPlanner stores the selected itinerary, the sharing timestamp and, where included, the searched origin and destination names and precise coordinates. This makes it possible to reopen the itinerary and populate its search form.
Anyone who obtains the link can view and forward it without signing in. A link is not an access-controlled private account. Shared-trip pages instruct search engines not to index them, but this does not prevent other people from copying, saving or republishing the information.
Shared trips can remain available after their travel date. The application does not currently define an automatic expiry or a self-service deletion control for stored shared trips. Do not share a trip containing a private address or other information you do not want link recipients to see.
Search inputs are used to find places, calculate journeys, retrieve fares and display results. Search records help inspect route demand and result quality. Shared-trip information is stored when you request a link. Technical information supports delivery, troubleshooting and security, and support correspondence is used to respond to enquiries.
Where the GDPR applies, each purpose needs an appropriate legal basis. Potential bases for review include taking steps at your request or providing a requested service (Article 6(1)(b)), legitimate interests in maintaining and securing the service and assessing its quality (Article 6(1)(f), subject to a necessity and balancing assessment), and compliance with a specific legal obligation where one applies (Article 6(1)(c)).
Pending legal review: the controller must confirm which basis actually applies to each activity, including public search records and shared trips. Choosing to search or share is not, by itself, a claim that GDPR consent has been obtained. Where consent is required, an appropriate choice and a way to withdraw it must be provided. These features do not make automated decisions about eligibility or other matters with legal or similarly significant effects.
Depending on the page and enabled features, information is handled by these types of recipient:
OpenStreetMap and Wikidata also provide public datasets; using a local copy of those datasets is different from sending a browser request to an external map or resource server.
csrftoken) is used to protect form
submissions. It may be set when you start an action rather than on every public page.django_language cookie for up to one year.theme in your browser's local storage. Local storage has no automatic expiry;
it remains until cleared or changed.You can remove cookies and local storage through your browser settings. Blocking security cookies can prevent forms from working; clearing preferences resets the saved language or theme. The current application does not include an advertising or behavioural-analytics script, but it does record searches as described above. External sites and resources have their own practices.
Before publication: verify production cookie lifetimes and any additional cookies or scripts introduced by infrastructure, and provide consent choices where required by applicable law.
Some operational caches expire automatically, but cache expiry is not the same as deleting database records, logs, backups or stored shared trips. The current application does not define an automatic deletion period for recorded route searches or shared-trip documents. This draft therefore makes no promise that those records are deleted when a search or journey ends.
Retention schedule pending: the controller must set and document periods or meaningful criteria for search records, public-feed availability, shared trips, support correspondence, logs and backups. Any deletion procedure must also account for copies and technical retention needs. Removing a shared trip from the service cannot remove copies already saved by recipients.
External providers can process information in countries other than your own. This draft does not assert that all processing stays in Switzerland or the European Economic Area.
Transfer details pending: confirm each production provider's processing locations and, where required, the applicable adequacy decision or other safeguards, such as standard contractual clauses and any supplementary measures. The final notice must explain how to obtain information about relevant safeguards.
The application uses measures such as request validation and protection against forged form submissions. Infrastructure security, access controls and backup practices require operational verification. No website or shared link can guarantee absolute security.
Where applicable, and subject to the conditions and exceptions in data-protection law, you may request access to your personal data, correction, erasure, restriction of processing and data portability. You may object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting the lawfulness of processing before withdrawal. You may also complain to a competent data-protection supervisory authority.
Privacy-request contact pending: a verified contact and a process for handling rights requests must be supplied before publication, together with the relevant supervisory-authority information. The service-support address in Section 1 has not been designated for that purpose.
When making a request through the confirmed contact, include only the information reasonably needed to identify the relevant record, such as a shared-trip link. Do not send identity documents unless a justified verification process specifically requires them.
The final notice should be reviewed whenever features, providers or processing practices change. Revisions will be identified by an updated date. This draft is not a confirmation of legal compliance; the outstanding operator, retention, legal-basis and provider details must be completed first.