<?xml version="1.0" encoding="UTF-8"?>
<!--
  Hand-maintained — nothing generates this file. A shipped route with no entry
  here is a route no crawler is told about, which is what /contact/ was.

  lastmod is the date the route's served HTML last changed, read out of git for
  the files that render it, and not the day this file was last edited. The root
  layout, its JSON-LD and the footer are on every route, so a change to any of
  the three moves every date below together.

  It is not the same claim as the "Last updated" line the legal pages print.
  That one is an editorial statement about a document's substance; this one is a
  fact about the bytes, so the two are free to disagree — a change to the footer
  or the layout moves this and leaves those alone.

  Whether a given pair agrees is therefore not something this file can state
  once and for all. They move together when a page changes what it asserts —
  the scope clause naming the corporate portal moved both of /privacy/'s dates
  to 2026-08-13 — and apart when only the bytes change, which is why the home
  page moved then and prints no date of its own to move. Read each route
  against its own pair rather than expecting the column to be uniform.

  /disclaimer/ carried 2026-08-12 here for a day while the page itself printed
  2026-08-13: the liability commit moved the page and left this file behind.
  Corrected. That is the failure mode this file invites — the date lives here
  and the change that earns it lives elsewhere — so it is worth looking for
  after any commit, not only when a page prints a date to contradict.

  /contact/ looked like the same case and was not. It stood a day behind the
  two above it because the imprint commit had touched it the day before, and
  every file that rendered it — its page, the legal shell, the layout, the
  stylesheet, the footer, the JSON-LD, the nav — last changed on 2026-08-12.
  That gap was correct while it lasted. The route prints no date of its own, so
  nothing here was visible to contradict; the only way to check it was the one
  above, against git.

  2026-09-07 closes that gap by moving every line at once. Three routes are new
  — /terms/, /withdrawal/, /subprocessors/ — three were rewritten, and the
  change reaches the rest through the parts that sit on every route: the root
  layout, its JSON-LD, and the footer, which has to carry the new links. The
  home page holds no legal text and moves anyway, for exactly that reason. It
  is the clearest case of what the third paragraph above describes: a date here
  that no printed date anywhere confirms, because the bytes changed and the
  substance did not.

  Order follows FOOTER_LEGAL in src/config/nav.ts: privacy, disclaimer,
  contact. The three new routes are appended after those, in the order of the
  documents themselves — the contract, the right to undo it, the register —
  because when these lines were written FOOTER_LEGAL did not yet list them and
  there was no footer order to follow. Whoever adds them there should re-sort
  this block to match. Nothing breaks if the two diverge, which is precisely
  why the divergence will go unnoticed.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url><loc>https://xpanion.com/</loc><lastmod>2026-09-07</lastmod><changefreq>monthly</changefreq><priority>1.0</priority></url>
  <url><loc>https://xpanion.com/privacy/</loc><lastmod>2026-09-07</lastmod><changefreq>yearly</changefreq><priority>0.3</priority></url>
  <url><loc>https://xpanion.com/disclaimer/</loc><lastmod>2026-09-07</lastmod><changefreq>yearly</changefreq><priority>0.3</priority></url>
  <url><loc>https://xpanion.com/contact/</loc><lastmod>2026-09-07</lastmod><changefreq>yearly</changefreq><priority>0.3</priority></url>
  <url><loc>https://xpanion.com/terms/</loc><lastmod>2026-09-07</lastmod><changefreq>yearly</changefreq><priority>0.3</priority></url>
  <url><loc>https://xpanion.com/withdrawal/</loc><lastmod>2026-09-07</lastmod><changefreq>yearly</changefreq><priority>0.3</priority></url>
  <url><loc>https://xpanion.com/subprocessors/</loc><lastmod>2026-09-07</lastmod><changefreq>yearly</changefreq><priority>0.3</priority></url>
</urlset>
