Legal pages written in plain, readable language

GDPR Art. 12 explicitly requires that privacy disclosures be provided in "clear and plain language" — dense legalese or unmodified boilerplate with unreplaced placeholders ([COMPANY NAME], [DATE]) does not satisfy this requirement. The FTC considers burying material terms in hard-to-read fine print a deceptive practice. Beyond regulatory risk, users who cannot understand what they are agreeing to are more likely to dispute charges, file complaints, and leave negative reviews. Unfilled template placeholders — "We retain data for [PERIOD]" — are evidence in regulatory investigations that the business deployed legal pages without review, which courts treat as bad faith.

Search legal page source files for common placeholder strings before shipping and replace every instance with real values.

# Run this on your legal page content files
grep -r "\[COMPANY\|\[DATE\|INSERT_DATE\|COMPANY_NAME\|\[YOUR COMPANY\|\[PERIOD\" \
  app/terms app/privacy app/refund-policy content/legal/

For readability, restructure dense paragraphs by adding descriptive <h2> subheadings for each section, breaking sentences at natural points, and adding a plain-language summary at the top of each page:

<section className="bg-muted rounded p-4 mb-8 text-sm">
  <strong>Plain English summary</strong>
  <ul>
    <li>You keep ownership of content you create.</li>
    <li>We can cancel accounts that violate these terms.</li>
    <li>Disputes are resolved in Delaware courts under Delaware law.</li>
  </ul>
  <p className="mt-2 text-muted-foreground">This summary does not replace the full terms below.</p>
</section>