Terms of Service or Terms of Use exists and accessible from website

Operating a web application without Terms of Service exposes you to unlimited liability for user disputes, leaves your intellectual property unprotected, and violates GDPR Art. 13 and CCPA §1798.100 obligations to inform users of how their data is used. Without a ToS, users have no binding agreement on acceptable use, dispute resolution, or liability limits — meaning any user can bring an uncapped claim against you in any jurisdiction they choose. FTC endorsement guides also require disclosure of material terms before users engage with commercial services. A missing or placeholder ToS is not a paperwork gap; it is an enforceable legal exposure that grows with every user who signs up.

Create an app/terms/page.tsx route that renders actual terms content — not a stub — and link it from your footer. Use a legal template generator (Termly, Terms.io, privacypolicies.com) as a starting point, then have a lawyer review the liability, dispute resolution, and jurisdiction sections before launch.

// app/terms/page.tsx
import type { Metadata } from 'next'

export const metadata: Metadata = {
  title: 'Terms of Service',
  description: 'The terms and conditions governing use of our service.',
}

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">Last updated: February 2026</p>
      {/* Actual terms content — not a placeholder */}
    </main>
  )
}

Add to your footer component: <a href="/terms">Terms of Service</a>. The page must be publicly accessible without authentication.