Claude Code skill for automatically generating privacy policies and terms of service based on Korean laws. Reflects the April 21, 2025 drafting guidelines and laws revised in 2026.
A skill package for creating privacy policies and terms of service for South Korea, the European Union, the United States, or combined Korean and EU use. It covers South Korea's PIPA, the EU's GDPR, and US CCPA/CPRA requirements.
A generator for privacy notices, terms of service, consent windows, and cookie banners for services aimed at people in the European Union. It covers GDPR and several related EU consumer and digital-service rules.
A document generator for Korean services that also serve people in Japan. It creates Korean and Japanese privacy policies and terms of service while reflecting relevant rules in both countries.
A document-generation tool for creating privacy policies and terms of service for a Korean company serving users in both Korea and the European Union. It produces Korean documents based on Korean privacy rules and English documents based on EU rules such as the GDPR, the European data-protection law.
A Japanese-language document generator for services built with Next.js. It creates privacy policies, terms of service, consent dialogs, and cookie banners while considering Japan's personal-information and consumer-protection laws.
A document-generation tool for Korean services that creates privacy policies, terms of service, signup-consent dialogs, and cookie banners. It is designed for Korean privacy and online-commerce rules and targets Next.js 13–16 projects.
An entry point for generating privacy policies and terms of use for services operating in Korea, the EU, the United States, Japan, or selected combinations.
A guided tool for creating a US privacy policy based on the California CCPA/CPRA and several other state privacy laws. It asks about the service, the data collected, service providers, dates, and design preferences.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: