<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Privacy In Design</title><link>https://privacyindesign.com/posts/</link><description>Recent content in Writing on Privacy In Design</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 09 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://privacyindesign.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>"No backend" is the foundation, not only a feature</title><link>https://privacyindesign.com/posts/no-backend-is-the-foundation/</link><pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate><guid>https://privacyindesign.com/posts/no-backend-is-the-foundation/</guid><description>&lt;p&gt;Most privacy claims are about restraint: we &lt;em&gt;could&lt;/em&gt; collect this, but we choose
not to. That framing is worth distrusting, because a choice can be revisited the
moment the incentives change. The stronger version is structural — there is no
collected information, so there is nothing to revisit.&lt;/p&gt;
&lt;p&gt;Four apps in, here is what that has actually meant.&lt;/p&gt;
&lt;h2 id="it-removes-the-easiest-answer-to-every-hard-problem"&gt;It removes the easiest answer to every hard problem&lt;/h2&gt;
&lt;p&gt;&amp;ldquo;Sync it through our backend&amp;rdquo; solves an enormous number of design problems at
once. Take it away and each one comes back individually.&lt;/p&gt;</description></item></channel></rss>