<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SubSync Guard Journal</title>
    <link>https://subsync-guard.pages.dev</link>
    <description>SubSync Guard is an advisory reconciliation control plane for the gap between subscription billing and application entitlements.</description>
    <language>en</language>
    <lastBuildDate>Sat, 14 Nov 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://subsync-guard.pages.dev/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What subscription revenue leakage actually means</title>
      <link>https://subsync-guard.pages.dev/blog/what-subscription-revenue-leakage-means</link>
      <guid isPermaLink="true">https://subsync-guard.pages.dev/blog/what-subscription-revenue-leakage-means</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
      <category>Fundamentals</category>
      <description>Revenue leakage is not a single number. It is a class of gaps between what a customer was billed and what the product actually allowed. This piece defines the categories and the evidence needed to investigate them.</description>
    </item>
    <item>
      <title>How to detect premium access without an active subscription</title>
      <link>https://subsync-guard.pages.dev/blog/premium-access-without-active-subscription</link>
      <guid isPermaLink="true">https://subsync-guard.pages.dev/blog/premium-access-without-active-subscription</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
      <category>Detection</category>
      <description>Stale premium access is one of the clearest revenue leaks — and one of the easiest findings to get wrong. The difference is policy and evidence, not a clever query.</description>
    </item>
    <item>
      <title>Mapping Stripe customers to application users without guessing</title>
      <link>https://subsync-guard.pages.dev/blog/mapping-stripe-customers-to-app-users</link>
      <guid isPermaLink="true">https://subsync-guard.pages.dev/blog/mapping-stripe-customers-to-app-users</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
      <category>Architecture</category>
      <description>A billing audit is only as reliable as the link between a Stripe customer and an application account. Email matching is not an identity strategy.</description>
    </item>
    <item>
      <title>Designing a signed Supabase entitlement export</title>
      <link>https://subsync-guard.pages.dev/blog/signed-supabase-entitlement-export</link>
      <guid isPermaLink="true">https://subsync-guard.pages.dev/blog/signed-supabase-entitlement-export</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
      <category>Integration</category>
      <description>The entitlement side of the audit needs a trustworthy snapshot. A narrow, signed, customer-owned export is safer than collecting a service-role key.</description>
    </item>
    <item>
      <title>Trials, grace periods, and dunning: decide the policy first</title>
      <link>https://subsync-guard.pages.dev/blog/trials-grace-periods-and-dunning</link>
      <guid isPermaLink="true">https://subsync-guard.pages.dev/blog/trials-grace-periods-and-dunning</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
      <category>Policy</category>
      <description>Most “billing mismatches” are actually policy mismatches. The database is doing what it was told; the policy was never written down.</description>
    </item>
    <item>
      <title>Why billing audits produce false positives</title>
      <link>https://subsync-guard.pages.dev/blog/false-positives-in-billing-audits</link>
      <guid isPermaLink="true">https://subsync-guard.pages.dev/blog/false-positives-in-billing-audits</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
      <category>Quality</category>
      <description>A false positive is not harmless. It trains the team to ignore the audit. Here are the failure modes worth designing against.</description>
    </item>
    <item>
      <title>Read-only Stripe keys: scopes, verification, and rotation</title>
      <link>https://subsync-guard.pages.dev/blog/read-only-stripe-keys</link>
      <guid isPermaLink="true">https://subsync-guard.pages.dev/blog/read-only-stripe-keys</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
      <category>Security</category>
      <description>The right integration is narrow, read-only, and revocable. A key prefix is not a permission model — verify the actual reads you need.</description>
    </item>
    <item>
      <title>How to audit an access-control migration</title>
      <link>https://subsync-guard.pages.dev/blog/auditing-an-access-control-migration</link>
      <guid isPermaLink="true">https://subsync-guard.pages.dev/blog/auditing-an-access-control-migration</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
      <category>Engineering</category>
      <description>Access-control migrations fail quietly. The old path keeps working, the new path has an exception, and a subset of users lands in the gap. Audit the transition, not just the destination.</description>
    </item>
  </channel>
</rss>
