ShipNext

Replace terms, privacy, refund, and cookie policies, then connect them to routes, footer links, and SEO.

ShipNext includes legal MDX pages to demonstrate routing and layout. They are not legal advice. Replace them with text that matches your company, product, jurisdiction, and purchase flow before launch.

Current implementation

Capability	File
Legal content	`content/legal/*.mdx` or localized legal content where present
Enabled pages	`config/website.ts` `legal.pages`
Dynamic route	Marketing legal slug route
Page component	`components/legal/legal-document-page.tsx`
Footer links	Landing footer components

Default legal pages usually include:

Page	Slug	Default path
Privacy Policy	`privacy`	`/privacy`
Terms of Service	`terms`	`/terms`
Cookie Policy	`cookie`	`/cookie`
Refund Policy	`refund`	`/refund`

MDX frontmatter

Legal pages use the schema from source.config.ts:

---
title: Privacy Policy
description: How Your Product collects, uses, and protects personal information.
lastUpdated: "2026-06-01"
---

title and description are used by metadata and page headers.

Configure legal pages

config/website.ts:

const legalConfig = {
  pages: [
    {
      slug: "privacy",
      href: "/privacy",
      labelKey: "privacy",
      title: "Privacy Policy",
    },
  ],
};

Field	Description
`slug`	Content slug
`href`	Footer link path
`labelKey`	Footer translation key
`title`	Default title for config use; MDX frontmatter controls page display

Slugs not listed in legal.pages should return 404.

Add a legal page

For an Acceptable Use Policy:

Create content/legal/acceptable-use.mdx or the localized equivalent.
Add an entry to websiteConfig.legal.pages:

{
  slug: "acceptable-use",
  href: "/acceptable-use",
  labelKey: "acceptableUse",
  title: "Acceptable Use Policy",
}

Add links.acceptableUse to each footer translation file if your footer uses i18n keys.
Visit the new route and confirm the page, footer link, and metadata work.

Content recommendations

Page	Should cover
Terms	Service scope, account responsibilities, subscriptions, IP, liability limits, disputes
Privacy	Data collected, purposes, processors, retention, user rights, contact
Refund	Refund window, subscription cancellation, non-refundable cases, request process
Cookie	Necessary cookies, analytics/support scripts, user controls

AI, UGC, or upload-heavy products should consider an Acceptable Use Policy. Platforms hosting user content may also need DMCA pages.

Product flow links

Registration and checkout should link to Terms and Privacy.
Stripe, Paddle, and Lemon Squeezy reviews often require public Terms, Privacy, and Refund pages.
Cookie Policy should disclose Crisp and similar third-party scripts.
Footer and email support/contact details should match.

Checklist

Placeholder legal text is replaced.
Every enabled slug has MDX content.
Footer legal links do not 404.
Effective or updated dates are accurate.
Payment, registration, cookies, and privacy disclosures agree.
websiteConfig.metadata.url is the production HTTPS domain.

Legal Pages