<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <!-- Three pages, so this is hand-maintained — there is no build step to
       generate it from.

       KEEP <lastmod> HONEST, IN BOTH DIRECTIONS. It was wrong on 2026-08-14 in
       the direction that actually costs something: all three pages had changed
       on 08-10 (the reprice, the artificial-flowers wording, the per-event
       rental period, and terms §§5/10/11) while this file still claimed 08-09
       and 08-05. A lastmod OLDER than the truth tells Google there is nothing
       to re-crawl, which is the opposite of what you want after a change — and
       at that moment we were specifically waiting for the stale
       „Доставяме и монтираме" snippet to drop out of the index.
       The opposite error is just as bad: bumping every date on every deploy
       makes lastmod a value Google learns to ignore. Bump it when the page's
       content genuinely changed, and leave it alone for asset-only deploys.

       The comment lives INSIDE <urlset> deliberately. It sat between the XML
       declaration and the root element, which is legal XML but is the only
       unusual thing about this file — not worth keeping while debugging a
       "Sitemap could not be read" status in Search Console. -->
  <url>
    <loc>https://arki.ibtechnologies.eu/</loc>
    <lastmod>2026-08-10</lastmod>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://arki.ibtechnologies.eu/terms.html</loc>
    <lastmod>2026-08-10</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>https://arki.ibtechnologies.eu/privacy.html</loc>
    <lastmod>2026-08-10</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
</urlset>
