PolicyStack

Key features

• One config for policies and consent A single PolicyStackConfig declares company, data, purposes, retention, cookies, and jurisdictions, feeding both document generation and the consent store without a second categories list.[1][2]

• Privacy and cookie policy generation The core compiles privacy and cookie policies from declarations with an explicit policy selection controlling emission; terms of service, DPAs, DPIAs, and rights-request workflows are not included.[1]

• Markdown, HTML, and PDF output The renderers package exports Markdown, HTML, and PDF formats, and React, Vue, and Svelte provide policy components that render inside the application design system.[1]

• Headless React consent primitives The React adapter wraps the core consent store with useConsent, useCategory, ConsentGate, and GatedScript, so teams gate components and scripts on stored consent choices in concurrent-safe React code.[1]

• Seven built-in vendor factories GA4, Google Tag Manager, Meta Pixel, PostHog, Segment, Hotjar, and Microsoft Clarity ship as consent-gated integrations rather than custom glue code.[1]

• Vite and CLI development feedback A Vite plugin with consent scanning surfaces ungated source usage, and CLI commands for init, validation, and MCP tools fit into development and CI pipelines.[1]

• Jurisdiction and language coverage Jurisdiction-specific policy text exists for eea, uk, and us-ca with generic fallback elsewhere, and built-in boilerplate supports English, French, German, Dutch, and Spanish.[1]

• Agent-oriented tooling Generated SDK references, CLI validation, MCP tools including scan_ungated, and reusable workflow skills let coding agents scaffold configs and check declarations.[1][2]

Who will love it

• TypeScript teams that version everything TypeScript teams that version everything will love PolicyStack, because policy and consent declarations live in the repository, generate on build, and deploy with the app.[1][2]

• Framework shops adding consent in code React, Vue, and Svelte shops adding consent in code will love the framework adapters, which match how they ship and avoid a third-party widget fighting the design system.[1][2]

• Teams pairing disclosures with consent Teams pairing disclosures with consent will love the single config, since published policy text and consent categories stay consistent by construction rather than manual sync.[1][2]

Who should avoid it

• Non-technical site owners Non-technical site owners should avoid PolicyStack, because V1 ships no finished banner or preferences UI and adoption is engineering-led.[1][2]

• Teams expecting automatic enforcement Teams expecting automatic enforcement should avoid it, since scanning is heuristic, enforcement happens only where the app calls the consent APIs, and revoking consent does not unload scripts that already ran.[1]

• Teams wanting guaranteed compliance Teams wanting a tool that alone guarantees compliance or backend control should look elsewhere; the docs state generated documents need human review and V1 offers no server middleware or distributed revocation.[1][2]

Compatibility