<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Ai on alex.thom.ae - Personal Blog</title>
    <link>https://alex.thom.ae/tags/ai/</link>
    <description>Recent content in Ai on alex.thom.ae - Personal Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 29 Jun 2026 09:00:00 +0300</lastBuildDate>
    
	<atom:link href="https://alex.thom.ae/tags/ai/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Data residency is not sovereignty</title>
      <link>https://alex.thom.ae/2026/06/29/data-residency-is-not-sovereignty/</link>
      <pubDate>Mon, 29 Jun 2026 09:00:00 +0300</pubDate>
      
      <dc:creator>Alex Thomae</dc:creator>
      <guid>https://alex.thom.ae/2026/06/29/data-residency-is-not-sovereignty/</guid>
      <description>A data-residency badge tells you where your bytes sit. It says nothing about who can actually compel them. For anyone keeping data under GDPR, the AI layer is where it gets hard: the models you can reach and trust are fewer than the marketing suggests, and the field is consolidating away.</description>
    </item>
    
  </channel>
</rss>
