Cookie policy
The six cookies this site may write, and which ones wait for your permission.
What this site stores in your browser
A cookie is a short string of text that a website asks your browser to keep and send back with the next request. Three of the six below are the plumbing: without them the site cannot tell a reader from a crawler, does not know whether your browser accepts cookies and cannot remember the answer you already gave to the notice. The other three are for measurement and advertising, and none of them is written before you accept. Behind the design there are no tracking pixels, embedded players or social media buttons adding anything to this list.
Cookie table
The category column is the one that matters: it tells you whether that cookie is written regardless or is waiting.
| Cookie | Set by | Category | Purpose | Expiry |
|---|---|---|---|---|
cf_clearance, __cf_bm | Cloudflare | Necessary | Tells a person apart from a script, which is what keeps the site available while it is being crawled or attacked | Up to 1 year / 30 minutes |
wordpress_test_cookie | WordPress | Necessary | Writes a value and reads it back to find out whether your browser accepts cookies, before anything depends on it | Ends with the session |
cmplz_* | This site (Complianz consent notice) | Necessary | Stores the answer you gave to the notice, purpose by purpose; without it the notice would reappear on every page | Up to 12 months |
_ga, _ga_* | Google Analytics | Measurement, with consent | Tells one visit apart from the next so the same page is not counted twice; the IP is truncated before it is stored | Up to 2 years |
__gads, __gpi, __eoi | Google AdSense | Advertising, with consent | Limits how often the same ad is repeated, detects click fraud and, if you allow it, chooses the ad | Up to 13 months |
IDE, DSID | Google, via doubleclick.net | Advertising, with consent | Measures what happens after an ad is clicked and personalises the next one | Up to 13 months |
How consent is given and withdrawn
The first time you visit, the notice offers three buttons of the same size and weight (Accept all, Reject all and Settings), and under «Settings» all the optional purposes start unticked. Until you answer, or if you reject, Google Analytics receives only a cookieless signal that a page has been viewed, with no identifier linking it to you. The «Privacy and cookie settings» link in the footer reopens the notice from any page, so a yes from a month ago can be a no today. Withdrawal takes effect immediately: it deletes the _ga cookies already stored, stops the measurement and advertising cookies from being written and does not lock you out of any page; here, consent is not the price of reading. If you reject advertising, the ad slots still appear, with ads chosen on the basis of the page in front of you and not of you. This obligation to ask you first comes from Article 22.2 of Spain’s Law 34/2002 on information society services (LSSI), as interpreted in the cookie guidance of the Spanish Data Protection Agency (Agencia Española de Protección de Datos).
Blocking them from your browser
Any browser can block or delete the cookies of a single site, and that decision overrides whatever is decided on this page. One consequence is worth knowing beforehand: if you block the Cloudflare cookies, the contact form may be rejected as suspicious traffic. Reading the station pages, timetables and fares is not affected.
Last updated: October 2026.