Generally, legal pages are required for websites to inform users about their rights and obligations. This includes Terms of Service and Privacy Policy pages. However, you can use the following prompts to generate a Terms of Service or Privacy Policy page for your website.

You should contact a legal expert to ensure that your legal pages are compliant with the laws in your country. This is a starting point and should not be considered legal advice.

​
Terms of Service

You can use this prompt to generate a Terms of Service page for your website. Customize your project details and legal requirements of course.

You are a skilled software engineer specializing in React, TypeScript and Tailwind CSS but also an experienced lawyer.

I need you to create a comprehensive Terms of Service page for digital goods/services. Please generate TSX code with Tailwind styling. It should be a static page without any generated dates. The date should be hardcoded. Everything should be inside the tsx. No content in variables outside.

PLEASE FILL IN ALL THESE REQUIRED FIELDS:
- Website URL: https://YOURDOMAIN
- Website/Company Name: YOURPROJECT
- Company Legal Form: COMPANY_LEGAL_FORM (e.g., GmbH & Co. KG)
- Company Address: YOURADDRESS
- Contact Email: contact@YOURDOMAIN
- Contact Phone: YOURPHONE
- VAT Number: YOUR_VAT_NUMBER
- Commercial Register: YOUR_REGISTER_DETAILS
- Company Representatives: YOUR_REPRESENTATIVES
- Governing Law Country: YOURCOUNTRY
- Last Updated Date: DD.MM.YYYY
- Website Description: DESCRIBE YOUR PROJECT
- Digital Product/Service Description: DESCRIBE_YOUR_DIGITAL_PRODUCTS
- Usage Rights: DESCRIBE_WHAT_USERS_CAN_DO_WITH_DIGITAL_GOODS
- Refund Policy: DESCRIBE_YOUR_REFUND_POLICY
- Payment Methods: LIST_AVAILABLE_PAYMENT_METHODS
- License Terms: DESCRIBE_LICENSE_TERMS
- Account Requirements: DESCRIBE_ACCOUNT_REQUIREMENTS
- Termination Conditions: DESCRIBE_TERMINATION_CONDITIONS
- Intellectual Property Rights: DESCRIBE_YOUR_IP_RIGHTS
- User Restrictions: DESCRIBE_PROHIBITED_USES
- Dispute Resolution: DESCRIBE_DISPUTE_PROCESS

Create a Terms of Service with these sections:

1. Basic provisions
   - Define terms like 'consumer' and 'businessman'
   - Specify scope of terms (website/platform)

2. Contract conclusion
   - How purchases/agreements are made
   - Online purchase process
   - Order confirmation details
   - Email communication requirements

3. Payment methods and special agreements
   - Available payment options
   - Special terms for specific payment methods
   - Payment processing partners

4. Digital goods and services
   - Description of digital products/services
   - Delivery of digital content
   - Access and download information

5. Intellectual property and usage rights
   - Ownership of digital content
   - License terms and limitations
   - Prohibited uses

6. Warranty and limitation of liability
   - Statutory warranty rights
   - Limitation of liability
   - Requirements for consumers

7. Account terms
   - Account creation and maintenance
   - User responsibilities
   - Termination conditions

8. Refund policy
   - Conditions for refunds of digital goods
   - Process for requesting refunds
   - Exceptions to refund policy

9. Choice of law, place of fulfillment, jurisdiction
   - Governing law
   - Jurisdiction for business customers
   - Application of UN Convention on Contracts
   - Benefit-of-doubt principle for consumers

10. Customer information
    - Seller identity
    - Alternative dispute resolution
    - ODR platform link: https://ec.europa.eu/odr
    - Willingness to participate in dispute resolution

11. Contract conclusion information
    - Technical steps for contract conclusion
    - Error correction options

12. Contract language and saving
    - Specify contract language
    - Information about contract text storage

13. Prices and payment arrangements
    - Total price information
    - Digital delivery fees if applicable
    - International tax considerations
    - Payment methods and due dates

14. Terms updates
    - How users will be notified of changes

Also, create a Imprint with these sections. Give me the code for the Imprint as well in a seperate file:
1. Imprint (Legal website operator identification)
    - Full company details
    - VAT number
    - Commercial register information
    - Company representatives
    - Person responsible for content
    - Alternative dispute resolution options

Technical implementation:
- Use TypeScript and React
- Style with Tailwind CSS only
- Make it responsive
- Include a table of contents
- Add print styles
- Include the last updated date
- Structure content with proper headings
- Add hover states for links
- Make it mobile-friendly
- Do not use containers and do not set a h1, as we will embed this component into an existing page

Please generate a single Terms of Service component implementing these requirements. Use proper semantic HTML. Generate only the code, no explanations needed.

​
Privacy Policy

You can use this prompt to generate a Privacy Policy page for your website. Customize your project details and legal requirements of course.

You are a skilled software engineer specializing in React, TypeScript and Tailwind CSS but also a GDPR/DSGVO compliance expert and experienced lawyer.

I need you to create a comprehensive Privacy Policy page that is fully GDPR/DSGVO compliant. Please generate TSX code with Tailwind styling for a Next.js application using App Router and React Server Components. It should be a static page without any generated dates. The date should be hardcoded. Everything should be inside the tsx. No content in variables outside.

Information about the project:
- Website URL: https://YOURDOMAIN
- Website Name: YOURPROJECT
- Company Name: YOURCOMPANY
- Company Address: YOURADDRESS
- Contact Email: contact@YOURDOMAIN
- Contact Phone: YOURPHONE
- Governing Law Country: YOURCOUNTRY
- Supervisory Authority Name: YOURAUTHORITY
- Supervisory Authority Address: AUTHORITYADDRESS
- Supervisory Authority Phone: AUTHORITYPHONE
- Supervisory Authority Email: AUTHORITYEMAIL
- Last Updated Date: DD.MM.YYYY
- Website Description: DESCRIBE YOUR PROJECT

Create a privacy policy with these sections:

1. Introduction to data protection
   - Explain that providing personal data is usually not obligatory unless stated otherwise
   - Define "personal data" briefly

2. Contact information
   - Responsible person/controller (full name, address, phone, email)
   - Data protection officer if applicable (name, address, phone, email)

3. Proactive contact and communication
   - Explain data collection when user contacts you
   - Legal basis (Art. 6(1)(b) GDPR for pre-contractual/contractual matters)
   - Legal basis (Art. 6(1)(f) GDPR for other inquiries)
   - Mention right to object for data processed under legitimate interest

4. Customer account and orders
   - Explain what data is collected through Supabase Auth (email, name, etc.)
   - Mention storage in Supabase Database
   - Legal basis (Art. 6(1)(a) GDPR for consent-based registration)
   - Legal basis (Art. 6(1)(b) GDPR for fulfilling contracts)
   - Mention data transfer to Supabase (specify data storage location)

5. Advertising
   - Explain use of personal data for postal advertising
   - Email marketing for similar products (Art. 6(1)(f) GDPR)
   - Newsletter subscription with consent (Art. 6(1)(a) GDPR)
   - Mention withdrawal rights

6. Cookies and storage technologies
   - General explanation of cookies and local storage
   - Explain that technically necessary cookies are used for authentication and website functionality
   - Do not list specific cookie names
   - Legal basis (Art. 25 para. 2 TTDSG and Art. 6(1)(f) GDPR)
   - Information about cookie consent management
   - Browser-specific information on managing cookies

7. Third-party services:
   - Supabase (Auth and Database)
     - Purpose: User authentication and data storage
     - Data collected: Email, name, account data
     - Link to Supabase privacy policy: https://supabase.com/privacy
     - Legal basis (Art. 6(1)(b) GDPR for contract fulfillment)

   - Posthog Analytics
     - Purpose: Website analysis and improvement
     - Data collected: Usage data, IP address
     - Link to privacy policy: https://posthog.com/docs/privacy
     - Legal basis and opt-out options

   - Google Analytics & Tag Manager
     - Purpose: Website analysis, marketing, and advertising
     - Data collected: IP address, date/time, pages visited, etc.
     - Data transfer to USA (mention standard contractual clauses)
     - Legal basis and opt-out options
     - Link to their privacy policy

   - Stripe (Payment processing)
     - Purpose: Processing payments
     - Data shared: Order information, payment data
     - Link to privacy policy: https://stripe.com/privacy
     - Legal basis for sharing data (Art. 6(1)(b) GDPR)
     - Mention use of Stripe Elements or Checkout

8. Rights of persons affected and storage duration
   - Duration of storage (general explanation)
   - Rights according to GDPR Art. 15-20
   - Right to complain to the regulatory authority with full contact details
   - Right to object to processing based on Art. 6(1)(f) GDPR

Technical implementation:
- Use TypeScript and React
- Style with Tailwind CSS only
- Make it responsive
- Include a table of contents
- Add print styles
- Include the last updated date
- Structure content with proper headings
- Add hover states for links
- Make it mobile-friendly
- Do not use containers and do not set a h1, as we will embed this component into an existing page

Please generate a single Privacy Policy component implementing these requirements. Use proper semantic HTML. Generate only the code, no explanations needed. The content should follow all GDPR/DSGVO requirements for transparency and clarity.

If you need to have a data protection officer, you need to include this information. Therefore, add to Ensure that also the following requirements are met::

- Data protection officer:
    - Name: YOURNAME
    - Contact: contact@YOURDOMAIN
    - Address: YOURADDRESS

For B2B, it should be okay to have a single language version of your legal pages. For B2C, you should consider having translations for your legal pages in all languages, you are offering.

If you’re located outside of the EU and you’re not targeting EU customers, you might not need to comply with GDPR. Therefore, you may remove the GDPR requirements from the Privacy Policy prompt.