Configuration

PolicyGen uses a policygen.json configuration file to customize your generated privacy policy and terms of service. This reference covers all available options.

Configuration Overview

The configuration file has four main sections:

{
  "$schema": "https://policygen.xyz/schemas/0.7/schema.json",
  "output": { /* Output configuration */ },
  "entity": { /* Your organization details */ },
  "privacy": { /* Privacy policy options */ },
  "terms": { /* Terms of service options */ }
}

Output Configuration

Controls how and where policies are generated.

Example

{
  "output": {
    "privacyFilePath": "./src/pages/privacy.html",
    "termsFilePath": "./src/pages/terms.html",
    "fileType": "html",
    "cssFramework": "tailwind",
    "locales": ["en"]
  }
}

Entity Configuration

Information about your organization.

Example

{
  "entity": {
    "name": "Acme Corp",
    "website": "https://acme.com",
    "address": "123 Main St, San Francisco, CA 94102"
  }
}

Privacy Configuration

All options for customizing your privacy policy.

Contact & Basics

Data Collection

Third-Party Data

Tracking & Analytics

Security & Compliance

Data Protection Officer

Browser Extension (v0.5+)

For browser extension privacy policies.

Omit the disclosure overrides to retain the default extension disclosures. Custom values replace those paragraphs in HTML and Astro output; they are escaped plain text, not HTML or executable templates. Empty values use the defaults. Other extension disclosures remain generated from the configuration, so review that the complete section accurately describes your practices.

{
  "privacy": {
    "browserExtension": {
      "name": "Acme Links",
      "permissions": ["tabs"],
      "hostPermissions": ["<all_urls>"],
      "dataCollected": ["currentTabUrl"],
      "runsLocally": true,
      "dataHandling": "We use authenticated operational signals for onboarding and customer support.",
      "dataSharing": "Operational records are available to authorized support personnel."
    }
  }
}

AI Usage (v0.7+)

Set privacy.aiUsage when a service uses AI systems. Policygen names the configured providers and renders the factual disclosures you supply; it does not infer provider retention, training, residency, or compliance terms.

New in v0.6

CPRA Compliance

VCDPA Compliance

Cookie Consent

Data Breach Notification

Cross-Border Data Transfers

COPPA Compliance

Terms Configuration

All options for customizing your terms of service.

Basic Settings

Payments & Subscriptions

User Content

Legal

Service Level Agreement

Liability

New in v0.6

Force Majeure

DMCA Takedown

Tax Liability

Migration Guide: v0.6 to v0.7

Existing v0.6 configurations remain valid. Update the schema URL to https://policygen.xyz/schemas/0.7/schema.json to use astroShell or privacy.aiUsage. AI data-handling and automated-decision text must describe your service’s actual behavior.

Migration Guide: v0.5 to v0.6

Breaking Changes

None. v0.6 is backward compatible with v0.5 configurations.

New Features

1. Update your schema URL:

   "$schema": "https://policygen.xyz/schemas/0.6/schema.json"

2. Add new privacy features (optional):

   {
     "privacy": {
       "cpraCompliance": true,
       "vcdpaCompliance": true,
       "cookieConsent": true,
       "cookieConsentProvider": "OneTrust",
       "dataBreachNotification": true,
       "dataBreachTimeframe": "72 hours",
       "crossBorderTransfers": true,
       "transferMechanisms": ["scc", "adequacy"],
       "coppaCompliance": true,
       "childrenMinAge": 13
     }
   }

3. Add new terms features (optional):

   {
     "terms": {
       "forceMajeure": true,
       "dmcaTakedown": true,
       "dmcaEmail": "dmca@example.com",
       "taxLiability": true,
       "taxJurisdiction": "United States"
     }
   }

Regenerate Policies

After updating your configuration:

npx policygen generate