← Back to the map ESCAEUGLENFRITDE

Legal notice and privacy policy

Last updated: 31 October 2026

Free software developed on a non-profit basis, under the GNU AGPL v3 or later.

This is a courtesy translation. The legally binding version is the Spanish one.

2. Privacy policy

This policy explains what personal data are processed when you use Trenalia, in accordance with Regulation (EU) 2016/679 (General Data Protection Regulation, GDPR) and Spanish Organic Law 3/2018 on the Protection of Personal Data and the Guarantee of Digital Rights (LOPDGDD). Trenalia does not ask you to register, does not use third-party advertising or analytics, and does not sell or share your data.

2.1. Data controller

Andrés Marchante Tirado (Tax ID (NIF) ), . Contact for any privacy matter: info@trenalia.org.

2.2. What data are processed, why and for how long

Access log

Data: IP address (stored without its last block, that is, partially anonymised), date and time, page or service requested, response code, response time, browser and device type (derived from the user agent) and referring website.

Purpose: to keep the service secure, to detect and stop abuse and attacks, and to obtain aggregate usage statistics.

Legal basis: the controller's legitimate interest in the security and proper functioning of the service (Art. 6(1)(f) GDPR and Recital 49).

Retention: 90 days; after that they are deleted automatically. The full IP address is kept only for the first 7 days; after that it is stored without its last block.

Operations: to understand how Trenalia is used, the admin panel groups the requests in this log into operations (for example “looks for trains between Seville and Madrid” or “is on train 03141”) and stores them by day with the same IP, device, retention and anonymisation as the rest of the log. Only the controller can see it.

Usage statistics: every day this log is used to compute aggregated counts (approximate visitors, pages, features used, device and browser) and the approximate country, region and city of each IP address, worked out on the server itself with a local DB-IP database: no third party receives your IP address (“IP Geolocation by DB-IP”, CC BY 4.0 licence). To count visitors without cookies, an irreversible hash of the IP address without its last block and of the browser type is used, with a key that changes every month and is then deleted; these hashes never leave the server. Only the counts are kept (for up to 2 years), with no IP address or identifier. Some actions on the website (opening a train card, turning on a map layer…) send the server only the name of the action, with no identifiers, so they can be counted. None of this uses cookies or your browser’s storage.

Collaboration form

Data: name, email address, phone number (optional), type of collaboration and message. To prevent mass submissions, an irreversible fingerprint (cryptographic hash) of the IP address is also stored, not the IP address itself.

Purpose: to contact you in order to handle the collaboration you are offering.

Legal basis: your consent (Art. 6(1)(a) GDPR), which you give by ticking the box on the form and can withdraw at any time.

Retention: for as long as the collaboration is being handled and, at most, 24 months from the last contact, or until you ask for erasure.

Satisfaction survey

Data: the rating (0 to 5 stars), the reason you choose, the suggestion if you write one (emails, phone numbers, ID and IBAN numbers are removed automatically), the language and the page. Your IP is not stored, nor any identifier: it is anonymous.

Purpose: to know whether Trenalia is useful and what to improve.

Retention: 24 months.

Trip incidents and ratings

Data: the type of incident you choose (noise, strong vibration, impact, breakage, altercation…) or your trip rating (1 to 5 stars), your comment if you write one (emails, phone numbers, ID numbers, IBANs and links are removed automatically), the train number, the time and the estimated position of the train at that moment (between which stations and at which km of the route). Your IP, your location and any identifier are not stored: it is anonymous. The IP is only kept in memory for a few minutes to prevent mass submissions.

Purpose: letting other passengers know how each train is doing (shown on the train card, in timetables and in the quality ranking) and learning which problems repeat most.

Possible track or train problems: Trenalia looks for patterns in these reports (for example, bumps reported by several trains at the same spot) so the controller can review them and, if appropriate, pass them on to Adif or other bodies. To check them, it may ask people passing that area later a short question (“Have you noticed anything in the last few minutes?”); the answer is stored like a report, with no personal data. Passengers are only shown, where relevant, a neutral note; it is not a safety warning.

Retention: 24 months. The administrator can hide a submission from the public website.

Shared access to the development log

Only if someone sends you an access link to /desarrollo.

Data: email (required), name and reason (optional), IP address, browser and every question or lookup you make.

Purpose: to know who reads the development log, prevent abuse and assess possible collaborations. Questions are answered by the same AI provider as Trenalito.

Legal basis: your consent (Art. 6(1)(a) GDPR), given by ticking the box before entering.

Retention: 12 months; then deleted automatically.

Incident hypotheses and passenger votes

Trenalia publishes hypotheses computed from public data when a situation starts that resembles others that caused delays («hypothesis under study» or, once validated by the operator of this site, «possible incident»). They are estimates: they are not notices from Adif or the train operators and must not be used for safety or operational decisions.

Votes: you can say whether the hypothesis is happening on your train («I confirm» / «no»). The vote is anonymous: your IP is not stored; only an irreversible daily fingerprint (with a key that changes every day) to prevent repeated votes, and your vote is remembered in your browser (local storage trenalia.hypvotes).

Purpose: to check and improve the hypotheses. Retention: 7 days with the hypothesis; aggregated counts remain in each pattern's confidence.

Access to the simulation

Only if you request access to the simulation view (/simulacion).

Data: name, email, organisation and profile (optional), why you want access, language, and the IP address and browser of the request. If approved: your user account (the password is stored only as a cryptographic hash) and a log of sign-ins and simulations with date, IP and the simulated scenario.

Purpose: to decide whether to grant access, email you your credentials (with a temporary password you change when you first sign in), prevent abuse and understand how the tool is used.

“Data” permission: if the controller grants it to you to collaborate on the analysis, your data queries and downloads are also logged (date, IP and dataset). The datasets contain no personal data.

Legal basis: your consent (Art. 6(1)(a) GDPR), given by ticking the box in the request.

Retention: rejected requests, 6 months; user account, while you have access; usage log, 12 months. You can ask to be removed at any time.

Scenarios and custom models: if you save scenarios or upload a model (PMML file) with its data binding, they are stored with your user account and only other approved users see them if you share them (with your name and organisation, never your email). The model is only used to compute your simulations and validations; no code is executed, it is not shared with third parties and you can delete it at any time. If your access is revoked, they stop being shared.

Connecting Claude or other MCP clients: if you create a personal key or connect an app via OAuth (/mcp/sim), the following is stored with your user account: for each key, its name, a cryptographic hash (never the key itself) and its first characters so you can recognise it, its permissions and the dates it was created, last used and revoked; for each connected app, its name and return address (redirect), the permissions you authorised and the dates, with access tokens stored only as a cryptographic hash (they expire after one hour, refresh tokens after 30 days). Every call is logged (user, key prefix or app, tool, a short summary of the parameters, duration and whether it failed) for 90 days. You can revoke keys and connections on the simulation page; they stop working immediately, and also if your access is revoked. Trenalia receives nothing from your conversations with the app: only the calls it makes to the tools.

Trenalito in the simulation: the questions you ask Trenalito in the simulation view go to the same AI provider as the public Trenalito, together with the simulation state that is sent (corridor, day, changes, options and summary of the last result, if you leave the “Include the state of my simulation” box ticked), with the same safeguards and without being stored on the server.

Trenalito assistant

Data: the questions you type and the last few messages of the conversation, which are sent to generate the answer. Do not include personal data in your questions.

Purpose: to answer your questions about trains and about the project.

Legal basis: the provision of the service you request when you use the chat (Art. 6(1)(b) GDPR) and the legitimate interest in limiting abuse (Art. 6(1)(f)).

Retention: the Trenalia server does not store conversations. The conversation is kept only in your browser while the tab is open (session storage) and is deleted when you close it or press “restart”. The IP address is used only in memory, for one minute, to limit the number of questions.

Ratings (👍/👎): only if you press 👍 or 👎 under an answer, the server stores that question (without any personal data it detects), your vote, the language and the date, without your IP, to review mistakes and improve the assistant. This is the only exception to the server not storing conversations. Legal basis: legitimate interest in improving the service (Art. 6(1)(f) GDPR); if you prefer, just don't rate. Kept for 12 months at most.

Main provider: the answers are generated by the Claude model of Anthropic, PBC (United States), which receives the text of the question, the last lines of the conversation and the necessary railway data, but not your IP or any identifier of yours. Under the commercial terms of its API, Anthropic does not use this data to train its models.

Alternative provider: if the main provider is unavailable or not configured, the answers are generated by the artificial intelligence service of Cerebras Systems Inc. (United States), which receives the same text, but not your IP or any identifier of yours.

Minimisation: before sending your question, Trenalia automatically removes any email addresses, phone numbers, Spanish ID numbers (DNI/NIE), IBANs and card numbers it detects. Even so, please do not type personal data in the chat.

Backup service: if the main provider fails, an artificial intelligence server managed by the controller is used. It receives the text and a pseudonymous identifier derived from your IP address (a non-reversible hash) to organise the cache and limit usage.

«Stationmaster» game room

Playing requires no account. When you start, the server creates a game with a random identifier that only your browser keeps; the server stores only its non-reversible digest (hash), your points, level, medals, the solutions you submit and, if you choose, a public alias. Your IP is not stored with games: it is used only in memory to limit abuse and, as a digest with a salt that changes when the server restarts, to count how many different networks agree on a solution.

Recovery link: optional. If you ask us to email it to you, the address is used only for that delivery and is not stored.

Volunteer computing: only if you turn it on, your browser runs calculations while the page is visible: searches for better moves and runs of network simulations requested by Trenalia or by simulation users. It receives only an anonymous problem (public timetable and numbers), with no one's data, and sends back the result, which the server checks. You can turn it off at any time.

Games with other players («Missions»): the other players in a game see your alias (or «Player N»), your level, your progress and the orders you give; never your IP or any identifier. Games are deleted from the server's memory when they end; only your points and the summary of your orders remain, for 120 days.

«Travellers in a pickle»: your decisions in each story are stored (without your IP) to study, in aggregate, how travellers react to incidents. If you ask Trenalito for advice, only the story data (delay, options, invented trip purpose) is sent to its artificial intelligence provider, never your alias or your IP.

Sharing and social networks: the share and «Follow us» buttons are plain links; Trenalia does not load scripts, buttons or pixels from any social network and sends them nothing. A network's page only opens if you tap it (under its own terms and privacy policy). What is shared is public data (a train, an alert, a station, a game), never your alias or anything about you. We count anonymously how often things are shared and through which channel, without the content.

Volunteer computing karma: if you lend your device's processing power, your anonymous game profile stores how much verified work you have contributed (tasks, repetitions and confirmations), with no data about your device. It only appears in the hall of fame if you have set an alias, and it is deleted with your profile.

Trenalia's posts on social networks: Trenalia's Telegram, Facebook and Instagram profiles only post official notices from the operators and the infrastructure manager, the aggregated daily summary and the game challenges; never hypotheses under study or data about any user. The images are generated on Trenalia's server, and the credentials for those accounts are stored only there. When posting, Trenalia sends each network only that text, the link and the image. They also post Trenalia's news, major delays and cancellations reported by the operators in their real-time data (train number, route and minutes), and suspended-service notices; nothing about travellers.

Version and mode of use: when you open Trenalia, the site counts once per session whether it is used as an installed app or in the browser and whether its files are the latest version, without cookies or identifiers; the count of users connected right now does not store your IP either.

Legal basis: providing the service you request by playing (art. 6.1.b GDPR) and your consent for the alias and volunteer computing (art. 6.1.a). Retention: the game, until you delete it from «My game»; submitted solutions, 120 days. Solutions to real cases are used in aggregate, without identifying you, to check Trenalia's incident hypotheses.

Administration panel

Only the administrator logs in. A technical session cookie is used for this. Visitors do not have user accounts.

The rail data collected for the history (train positions and delays) are not personal data.

2.3. Recipients and processors

No data are disclosed to third parties unless required by law. The following process data on behalf of the controller, with the safeguards of Art. 28 GDPR:

The data sources (Renfe, ADIF, AEMET, etc.) are queried by the Trenalia server. Your browser does not connect to them, so they do not receive your data.

2.4. International transfers

Using Anthropic, PBC and/or Cerebras Systems Inc. involves sending the text of Trenalito questions to the United States. The transfer relies on the safeguards under Art. 46 GDPR offered by each provider (standard contractual clauses of the European Commission) or on its participation in the EU-U.S. Data Privacy Framework, if certified. You can ask for information about these safeguards at the contact email. If you do not want your questions to be transferred, do not use the chat: the rest of Trenalia works without it.

2.5. Your rights

You can exercise your rights of access, rectification, erasure, objection, restriction of processing and data portability, and withdraw your consent whenever you wish, without affecting the lawfulness of prior processing. Write to info@trenalia.org stating which right you are exercising. For access logs, include the IP address, the date and the approximate time, because there is no other way to identify you. You will receive a reply within one month at the latest.

If you believe your rights have not been respected, you can lodge a complaint with the Spanish Data Protection Agency (AEPD) (www.aepd.es).

2.6. Minors

The collaboration form is not intended for children under 14 (Art. 7 LOPDGDD). If you are under that age, do not submit it without permission from your parents or guardians.

2.7. Security

Appropriate technical and organisational measures are applied:

3. Cookies and storage in your browser

Trenalia does not use advertising, analytics or third-party cookies, and does not load third-party resources that track your visit (the fonts are those of your own device). That is why the notice you see on arrival is for information only: there is nothing to accept or reject.

It only stores the following technical and preference data in your browser. They are exempt from consent under Art. 22(2) LSSI-CE because they are necessary to provide the service as you configure it:

DataTypePurposeDuration
Light or dark themeLocal storageRemember your choiceUntil you delete it
Map layers, cab view preferences and welcome screen already seenLocal storageRemember which layers and options you have switched on, and not show the welcome screen againUntil you delete it
Cookie notice already seenLocal storageNot show this notice againUntil you delete it
Muted warningsLocal storageNot show again the warnings you mute12 hours per warning; general mute, until you change it
Conversation with TrenalitoSession storageKeep the chat while you browseUntil you close the tab
trenalia.followLocal storageTrains you follow and the alerts you chose (delay, track, arrival at your station, compensation), to alert you while Trenalia is open. Your browser may ask permission to show notifications. If you also get alerts with the site closed, see “Alerts with the site closed” below this table.Up to 12 hours, or 20 minutes after the train stops running; also when you tap “Stop following”
trenalia.tripLocal storageThe trip you set a course for (trains, stations, times and alerts already sent)Until you end the trip or 2 hours after arrival
trenalia.trip.geoLocal storageWhether you turned on location for the trip (used only on your device)Until you turn it off or end the trip
trenalia.linksLocal storageConnections you are watching (train, station and destination), to alert you if they are at riskUp to 3, for 12 hours
trenalia_survey and visit countTechnical cookie and local storageNot showing the satisfaction survey again once you answered or dismissed it, and only showing it from your second visit90 days (cookie); the visit count, until you delete it
trenalia.habits (“My habits”)Local storageRemembering the routes you search, the trains you ride and the stations you check (with weekday and time) to suggest your usual and help you plan the return. Never sent to the server. View, turn off and delete it in the ☰ menu → “My habits”180 days per item, until you delete it
trenalia_devTechnical cookieSession of someone who enters with an access link to the development log (/desarrollo)12 hours, or until logout or the link is revoked
trenalia_simTechnical cookieSession of someone who signs in to the simulation view with their credentials12 hours, or until signing out or access is revoked
trenalia.sim.tlSession storageKeep the conversation with Trenalito in the simulation viewUntil you close the tab or sign out of the simulator
trenalia.hypvotesLocal storageRemember in your browser which incident hypotheses you voted onUntil you delete it
trenalia.tipsLocal storageRemember which “Did you know…?” tips you have seen, when the last one appeared and whether you turned them offUntil you delete it
trenalia.tripsLocal storage“I’m on a train”: the trip in progress (train, station, delays and notices seen) and your trip history, only in this browserUntil you delete it (“Delete my history” button)
trenalia.hypseenSession storageAvoid repeating the notice of a hypothesis that affects a train you followUntil you close the tab
trenalia.upcomingLocal storage“My upcoming trips”: trains you save from a ticket (train, day, stations and times; never name, booking reference, seat or price)Until the day of the trip has passed or you remove it
trenalia.geoCenterLocal storageWhether you want the map to centre on your location when opened (yes/no; the location is not stored)Until you remove it
trenalia_adminTechnical cookieAdministrator session (only in the administration panel)Until logout or 8 hours at most, or 30 minutes of inactivity
Copy of the app (if you install or visit it)App cache (service worker)Load the site quickly and show an “offline” page when there is no connectionUntil you clear it or the app updates

Alerts with the site closed (“Follow my train” push notifications): if you allow notifications and your browser supports it, the Trenalia server stores the delivery address and encryption keys your browser creates for these alerts, the trains you follow with the alerts you chose, and your language. It does not store your IP address or anything that identifies you. This is deleted 12 hours after you stop following trains (each follow expires after 12 hours) and after 7 days at most. The encrypted message is delivered by your browser vendor’s push service (Google, Mozilla, Apple or Microsoft), which cannot read its content. You can withdraw it with “Stop following” or by removing the notification permission in your browser.

On-board sensor (train bumps and vibrations): optional; it only works if you turn it on in «I'm on the train» and tick the consent box. While it is on and the screen is on, your phone uses its motion sensors (accelerometer and gyroscope) to notice the train's bumps and vibrations, and sends Trenalia only the measurement (peaks, duration, energy by frequency and a short waveform), the time and the number of the train you are on. It does not use your phone's GPS, your name or any identifier of your phone, and we do not store your IP address (it is only used in memory, summarised, to limit abuse). Each trip gets a new random code that is forgotten when it ends. With that measurement, the Trenalia server records the train and its position at that moment from public data (train number, units and series, section, line and kilometre point), never yours. Purpose: to detect abnormal bumps and vibrations on the track and on trains and to characterise sections and units; the results are unverified indications. Legal basis: your consent (art. 6.1.a GDPR; art. 22.2 LSSI for accessing the phone's sensors), which you withdraw at any time with «Stop». You must be 14 or over to give consent. We keep the measurements for up to 400 days and, after that, only aggregated figures by section and by unit. To prove consent without identifying you we only keep the version of the text, the date and a random code stored on your phone. Aggregated figures may be shared with infrastructure managers or operators; never individual measurements that could be linked to a person. With the screen off the browser does not allow measuring: the sensor pauses. If you turn on the notice on Android, you will see a notification with the «I felt a bump» button to record it without opening the website. Mobile coverage: while measuring, the sensor also notes when your phone loses connection and how long each upload takes; the server places this using that train’s public position and only keeps totals per stretch of about 500 m (seconds online and offline, slow uploads and how many different trains), with no session or identifier. A stretch is shown once at least 2 different trains have measured it.

How many people follow a train and how full it was: to show how many people are following a train today in «I'm on the train» without counting the same person twice, a fingerprint of your IP and browser is computed in memory with a random key that changes every day and is never stored; only totals per train and day are written to disk, and below 3 people the figure is not published. If at the end of your trip you answer «How full was the train?», we keep only the answer (almost empty, normal or full), the train, the day and the hour, for up to 400 days. Legal basis: legitimate interest in reporting occupancy (art. 6.1.f GDPR); answering is voluntary. The same daily fingerprint is used to measure how long each trip lasts (from when you start following the train until you tap “End this trip” or the train reaches your station); only the day’s total minutes and trips per train are stored.

Reading your ticket (optional): if in “I’m on a train” you choose the PDF, the Wallet pass or a photo of your ticket (or share it with Trenalia from another app on Android), it is read on your device: the file, your name, the booking reference, the seat and the price are not sent to Trenalia or stored. Only the train’s timetable is requested from the server, as when searching by hand, using its number and the day. A ticket shared from another app is kept in a local browser cache only until it is read, and is deleted straight away.

Coach number (optional): if you tick the box when reading your ticket, only the train number, the day and the coach number are sent to Trenalia, without seat, name, booking reference or price. To avoid counting you twice, a fingerprint of your IP and browser is computed with a key that changes daily and is not stored; only counts per train, day and coach are written to disk and deleted after 35 days. Per train, only the breakdown for the last 30 days and upcoming trips is published, and only with 5 or more contributions.

Moving to another device and linking two (optional): what is moved (current trip, trip with changes, upcoming trips, followed trains, watched connections, usual trips, platform board, silenced alerts and, when moving, language and theme) is encrypted on your device with AES-GCM and a key derived from the code; the code is not sent to Trenalia. The server only keeps the encrypted block, which it cannot read, and a check value of the code, in memory and never on disk: when moving, it is deleted when read or after 10 minutes; when linking, 24 hours after the last use or when you tap “Stop syncing”. Your IP is only used in memory to limit attempts. The game session, the sensor and browser permissions are not moved.

Daily alert for your usual train (optional): if you turn it on in the “Your train” card, Trenalia stores, together with your browser’s push subscription (the same as “Follow my train”), only the train number, its time, the type of day and your stop, to tell you how it is doing 25 minutes before on the days that apply. It doesn’t store your name, email, location or IP. It is deleted when you tap “Remove”, when you withdraw notification permission or if the browser doesn’t renew it within 7 days.

Location to centre the map (optional): only if you tap “My location” on the map and allow it in your browser. Your location is used on your device to centre the map (at city scale) and is not sent to Trenalia, is not put in the page address and is not stored; only whether you want the map to centre itself on opening is remembered, and then only if the browser has already granted permission. When the map moves to your area, the browser downloads the maps for that area from the map service (as when you move it by hand). You can turn it off in the notice that appears or withdraw the permission in your browser settings.

“I’m on a train” links: if you create a link so someone can follow your journey, the Trenalia server stores only the train number, the day, the station where you are being met (if you choose one) and the creation and expiry dates. It does not store your name, phone number, location or IP address (the address is only used in memory, hashed, to limit links to 20 per hour). The link identifier is not written to the access log. The link expires 3 hours after the scheduled arrival and after 24 hours at most. Whoever opens it sees the train’s position, which comes from public data, never your phone’s.

Name or nickname (optional): if you type it when sharing the link or asking for the email notice for the person waiting for you, it is stored only with that link or notice, so the recipient knows who sent it, and it is deleted with them when the trip ends (at most 3 hours after the scheduled arrival). Only letters, numbers and spaces are allowed.

Email alerts: if you ask for email alerts about a journey or an arrival, the Trenalia server stores your email address encrypted (AES-256-GCM), the journey (trains, stations and times), your language, the alerts you chose and which ones have been sent. It does not store your name or IP address (the IP address is only used in memory, hashed, to limit sign-ups). Nothing is sent until you confirm with the link you receive; if you do not confirm, it is deleted after 24 hours. Everything is deleted 2 hours after the journey arrives. Every email includes a one-click unsubscribe link (also for all alerts). Emails are sent from the Trenalia mailbox through a mail server over an encrypted connection. Legal basis: your consent, which you can withdraw at any time by unsubscribing. If you choose “I don’t want any more emails from Trenalia”, we delete your alerts and keep only an encrypted fingerprint of your address (not the address itself) on a suppression list so we never write to you again; you can leave that list at trenalia.org/avisos/reactivar, confirming from your inbox. If you are travelling, you can enter the email of whoever is meeting you: they first get an email to accept, receive nothing without confirming, are only told about significant problems with your arrival, and their address is deleted when the journey ends. You can also subscribe to alerts for a line, a route between two stations or a train (for 6 months, renewable with one click) or to the weekly newsletter (12 months, renewable); the newsletter is written automatically by an AI system from our development notes and contains no data about you.

Recommending Trenalia: if you type someone else’s email address to recommend Trenalia to them, we send them a single email explaining what Trenalia is and, if you add it, your name (optional; it only goes in the message and is not stored). We do not keep their address: only an encrypted fingerprint for 30 days so we do not write again if someone repeats it, and that email’s unsubscribe link for 60 days. There are limits per connection and per day so it cannot be used to send unwanted email, and we never write to anyone who unsubscribed from all Trenalia emails. Only type the address of someone you know wants to receive it. On WhatsApp, you send the message yourself from your WhatsApp: the number never goes through Trenalia.

“Write to Trenalia” form: what you write (topic, message and, if you add them, your name and email) is emailed to info@trenalia.org from Trenalia’s mailbox and is not stored on the website. Your email, if you leave it, is only used to reply to you. To prevent abuse there is a limit of messages per connection, counted in memory with a shortened IP and forgotten after 24 hours.

You can delete all these data from your browser settings (“Clear site data”). Trenalia will keep working with the default settings.

4. Security and reporting vulnerabilities

If you find a security issue, write to us at info@trenalia.org (also listed in /.well-known/security.txt). We appreciate your report. Please do not run tests that degrade the service or access other people’s data.

Trenalia charges nothing and does not process payments or card data. Administrative access is protected by a hashed password, attempt lockout, optional second factor, inactivity timeout and an audit log.

5. Software licence

Trenalia's code is free software under the GNU Affero General Public License, version 3 or later (AGPL-3.0-or-later). You may use, study, modify and redistribute it, provided that any version you distribute keeps this same licence and makes its source code available to those who receive it. It comes with no warranty.

Additional terms (s. 7 of the AGPL): anyone who uses, modifies or offers this code as an online service must make its source code available to its users, keep the authorship notices and show on their site the notice “Based on Trenalia (https://trenalia.org)” with a link; modified versions may not be presented as Trenalia, and the licence grants no right to use the Trenalia name or logos. Details in the NOTICE file.

The licence covers the code. The data Trenalia displays belongs to its sources and is subject to their own terms (Renfe, Adif, AEMET, IGN, Copernicus, OpenStreetMap…), and the bundled third-party libraries keep their licences (MapLibre GL JS, BSD-3; Leaflet, BSD-2). Soon you will be able to download the code of each published version from Trenalia.

6. Changes to this text

This notice may be updated when the service or the regulations change. The date of the last update is shown at the top.