<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Sovereign-Ai on Digital sovereignty, thought through</title><link>https://mguenther.nl/tags/sovereign-ai/</link><description>Recent content in Sovereign-Ai on Digital sovereignty, thought through</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mguenther.nl/tags/sovereign-ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Sovereign AI Has a Price</title><link>https://mguenther.nl/series/sovereign-ai-has-a-price/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><guid>https://mguenther.nl/series/sovereign-ai-has-a-price/</guid><description>&lt;p&gt;A chip maker&amp;rsquo;s engineers pasted proprietary source code and a confidential meeting transcript into a public AI assistant – three times in twenty days. They couldn&amp;rsquo;t take it back, and the terms at the time allowed the provider to train on it. The company banned the tools outright and started building its own.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;That&amp;rsquo;s the first worry:&lt;/strong&gt; what you send to a model leaves your building, and you can&amp;rsquo;t get it back. Confidentiality, IP, trade secrets – handed to a company in the business of learning from data.&lt;/p&gt;</description></item></channel></rss>