<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>MNSTRY.org · Privacy</title>
    <link>https://mnstry.org/topics/privacy/</link>
    <description>Six rooms on what an honest privacy claim can and cannot say, walked from
one person deciding between two versions of a product to a company drawing
the edge of its own promise. The order is deliberate. Each room narrows what
the next one is allowed to claim, so that by the end the discipline looks
less like modesty and more like the only version that survives a reader who
checks. Underneath all six is a single argument, that a privacy claim is
worth exactly what it says about its own limits, and nothing at all without
them.</description>
    <item>
      <title>Privacy is a different product</title>
      <link>https://mnstry.org/writing/privacy-is-a-different-product/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/privacy-is-a-different-product/</guid>
      <description>Why a private version of a product is a second product rather than a setting, and what an honest presentation of that choice owes the person making it. The canonical treatment of the plaintext condition.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A vector of your words</title>
      <link>https://mnstry.org/writing/a-vector-of-your-words/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/a-vector-of-your-words/</guid>
      <description>Why an embedding is another copy of the text rather than a safe abstraction of it, and the deletion rule that follows from the difference. The canonical treatment of deletion reach.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Custody is not visibility</title>
      <link>https://mnstry.org/writing/custody-is-not-visibility/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/custody-is-not-visibility/</guid>
      <description>Why the party responsible for a shared container is not thereby entitled to read what is inside it, and the schema rule that keeps the two powers apart. The canonical treatment of the custody axis.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The revocation window</title>
      <link>https://mnstry.org/writing/the-revocation-window/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/the-revocation-window/</guid>
      <description>Why revoking access is a message that has to arrive rather than a state that changes, and what naming the gap costs against what hiding it costs. The canonical treatment of the revocation window.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Sovereignty relocates trust</title>
      <link>https://mnstry.org/writing/sovereignty-relocates-trust/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/sovereignty-relocates-trust/</guid>
      <description>What actually changes when an institution takes custody of its own data, argued from the section of our own architecture that concedes the point we would be assumed to resist. The canonical treatment of trust relocation.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What your claim excludes</title>
      <link>https://mnstry.org/writing/what-your-claim-excludes/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/what-your-claim-excludes/</guid>
      <description>The case for stating the edge of a protection claim in the claim itself, drawn from a company's list of words it forbids its own marketing. The canonical treatment of prohibited vocabulary.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
