All legal pages display last-updated or effective date

GDPR Art. 13(1) requires that privacy notices state when they were last updated so users can determine whether they have seen the current version of the policy. CCPA §1798.130(a)(5)(B) requires the privacy policy to include the date it was last updated. A date-free legal page gives users and regulators no way to verify whether the policy reflects current data practices — which is itself a compliance gap. Placeholder dates (Last updated: [DATE], Month DD, YEAR) are evidence that the page was deployed without review and have been used by regulators as evidence of systematic non-compliance in enforcement proceedings.

Add a hardcoded LAST_UPDATED constant near the top of every legal page component and render it prominently. Update this constant whenever you make a substantive change to the page.

// app/terms/page.tsx — same pattern for /privacy, /refund-policy, etc.
const LAST_UPDATED = 'February 15, 2026'  // Update when content changes

export default function TermsPage() {
  return (
    <main className="max-w-3xl mx-auto px-4 py-12 prose">
      <h1>Terms of Service</h1>
      <p className="text-sm text-muted-foreground mt-1">
        Last updated: {LAST_UPDATED}
      </p>
    </main>
  )
}

For MDX-based legal pages, use frontmatter: lastUpdated: 2026-02-15 and render {frontmatter.lastUpdated} in the page header. Search all legal page files for [DATE], YYYY-MM-DD, and Month DD, YEAR to catch any remaining placeholders.