NextFire main logoNextFire
Docs X
Introduction
Get Started
Clone repo
Run the app
Configuration
Firebase
Create firebase app
Authentication
Firestore
Storage
Functions
Global configuration
Public
Site config
Payments
Stripe
One time
Subscriptions
Webhooks
Usage
Project structure
Static pages
Public pages
Protected pages
Auth
Client auth
Server auth
Data fetching
Firestore client
Firestore admin
Functions
Storage
Content
Blog
Documentation
Components
Markdown
Cards
Diagrams
Filetree
Lists
Maths
Notes
Steps
Table
Tabs
Public
Deep
Deeper
Even deeper
  1. Project Structure
  2. Static Pages

Static Pages (Privacy & Terms)

Your project includes pre-generated static legal pages required for compliance with Stripe and general online business regulations.

These files are stored under:

/content/privacy/index.mdx
/content/privacy/terms.mdx

They are written in MDX format, allowing you to include both Markdown content and React components if needed (e.g., for layout, contact links, or styled sections).


1

Locate and Review Existing Files

Navigate to the following files in your project:

  • content/privacy/index.mdx → contains your Privacy Policy
  • content/terms/index.mdx → contains your Terms of Service

These files are already included in your build and automatically rendered by your Next.js or MDX page router.

2

2. Update Content for Your Application

Open each .mdx file and update the details to reflect your application’s operations, such as:

  • Company Name and Contact Info
  • Data collection practices (cookies, analytics, user accounts)
  • Subscription, billing, and cancellation terms
  • Refund and dispute resolution policies
  • Third-party integrations (Stripe, Firebase, etc.)

⚠️ Important: Stripe requires that your app provides accessible and transparent Privacy Policy and Terms of Service pages. You must include:

  • A clear description of how you handle user data.
  • Contact information for support or data removal.
  • A refund and subscription management policy.
3

3. Maintain Compliance with Stripe and Legal Requirements

Stripe’s verification and onboarding process may check for these pages to ensure:

  • You comply with global privacy regulations (e.g., GDPR, CCPA).
  • Users can understand their rights and obligations.
  • Subscription terms are transparent and accessible from your checkout or website footer.

To stay compliant:

  • Always include links to these pages in your checkout flow, footer, and support emails.
  • Keep the information up to date, especially if you change your pricing model or data policies.
4

4. Expert Prompt: Generate a Legal-Compliant Template

You can use the following prompt to generate professional legal templates tailored to your app:

**Prompt:**
"Generate a GDPR and Stripe-compliant Privacy Policy and Terms of Service for a SaaS application named [Your App Name], which offers subscription-based access to [briefly describe your app features]. Include sections about data collection, cookies, billing terms, refunds, and contact information."

After generating, copy the content into:

  • content/privacy.mdx
  • content/terms.mdx

Then adjust any placeholders (e.g., company name, address, contact email).


✅ Tip: Keeping your legal pages updated not only ensures Stripe compliance but also builds trust with your users and protects your business from disputes.

Project structurePublic pages

On this page

Static Pages (Privacy & Terms)

Content

FeedbackEdit page

© 2025 Ship IT.

Rubix Studios logo