/ Diretório / Playground / Privacy & Terms
← Todos os servidores ↗ GitHub
● Comunidade kimlawtech ⚡ Instantâneo

Privacy & Terms

por kimlawtech · kimlawtech/korean-privacy-terms

An interactive privacy-policy & ToS generator that encodes Korean PIPA (2025 rev.), EU GDPR, and US CCPA/CPRA — one interview, compliant output.

A Claude Code skill for generating privacy policies and terms of service. It reflects the Korean government's updated 개인정보 처리방침 작성지침 (2025.4.21) and recent regulatory moves globally. V3's modular architecture routes /privacy-terms to privacy-kr, privacy-eu, or privacy-global based on your company/user-base. Ships React UI components (consent modals, cookie banners) alongside the legal text. Disclaimer: informational/drafting aid, not legal advice.

▶ Ver demo 📦 Instalar 💡 Casos de uso

Por que usar

Principais recursos

Demo ao vivo

Como fica na prática

privacy-terms-skill.replay ▶ pronto
0/0

Instalação

Repositório do autor · Documentação oficial de Skills do Claude

Casos de uso

Usos do mundo real: Privacy & Terms

Ship a Korean-compliant privacy policy for a SaaS launching in Korea

👤 Teams launching a product targeting Korean users ⏱ ~45 min intermediate

Quando usar: You're live in Korea within a week and need a PIPA-compliant 개인정보 처리방침 that reflects the 2025.4.21 guideline.

Fluxo
  1. Kick off the interview
    /privacy-terms — jurisdiction: Korea. Service type: B2C SaaS. Begin the interview.✓ Copiado
    → Skill asks about data categories, legal basis, third parties — one at a time
  2. Answer and iterate
    We collect email + login metadata. Retention: 3 years or on account deletion. Processors: AWS Seoul, Slack.✓ Copiado
    → Skill incorporates answers; conditional sections light up (e.g. cross-border transfer disclosure)
  3. Export
    Export the final 개인정보 처리방침 as /legal/privacy-ko.md and the consent modal as React component.✓ Copiado
    → Two artifacts on disk; consent modal compiles

Resultado: A draft privacy policy that matches the current KR guideline — your lawyer reviews, you ship.

Armadilhas
  • Copying last year's template — The 2025.4.21 update changed several required disclosures; rely on the skill's current template, not archived PDFs
  • Treating as legal advice — Have a Korean privacy counsel review before publish — this is a drafting aid
Combine com: filesystem

Add a GDPR companion policy for EU visitors

👤 Teams with a primary market but EU traffic ⏱ ~30 min intermediate

Quando usar: Your main privacy policy covers KR or US, and you need a GDPR-focused companion for EU users.

Fluxo
  1. Route to EU module
    /privacy-terms — jurisdiction: EU (GDPR). Service type: SaaS. We already have a KR policy; generate a companion.✓ Copiado
    → Skill produces an EU-focused doc; cross-references the KR one where appropriate
  2. Handle transfers
    Data flows KR ↔ EU. Add the SCC-based transfer disclosure and DPO contact placeholder.✓ Copiado
    → Transfer section filled; DPO contact is a placeholder you override
  3. Ship
    Export to /legal/privacy-eu.md and add a locale switcher component for the Privacy page.✓ Copiado
    → Locale switcher added; user language detected client-side

Resultado: Multilingual privacy surface without rewriting your KR policy.

Armadilhas
  • Assuming GDPR adequacy for KR-EU — Korea was granted adequacy (2021); skill reflects this but check current status before relying
Combine com: filesystem

Combinações

Combine com outros MCPs para 10× de alavancagem

privacy-terms-skill + filesystem

Write policy files and components to /legal and /src/components

Save /privacy-terms output to /legal/privacy-ko.md; components to src/components/consent/.✓ Copiado
privacy-terms-skill + github

Open a PR with the legal update

Commit the new policy + components and open a PR 'legal: adopt 2025.4.21 KR template' tagged @legal-review.✓ Copiado
privacy-terms-skill + web-design-skill

Style consent components to match your DESIGN.md tokens

Style ConsentModal per DESIGN.md primary/accent tokens; keep WCAG AA contrast.✓ Copiado

Ferramentas

O que este MCP expõe

FerramentaEntradasQuando chamarCusto
/privacy-terms jurisdiction, service_type → routed to /privacy-kr | /privacy-eu | /privacy-global Top-level entry; routes to the correct jurisdiction module Claude API calls only
/privacy-kr business details Direct Korea-only invocation free + Claude API
/privacy-eu business details Direct EU-only invocation free + Claude API
/privacy-global business details US / global-default invocation free + Claude API

Custo e limites

O que custa rodar

Cota de API
None beyond normal Claude usage
Tokens por chamada
Moderate — final policy is long-form prose
Monetário
Free (check repo license)
Dica
Interview once; re-run only the sections that change. The modular split lets you regenerate EU without re-doing KR.

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: None
Saída de dados: Your business details are sent to Anthropic as part of normal Claude calls. Don't paste full customer lists or raw PII into answers.

Solução de problemas

Erros comuns e correções

EU policy missing SCC transfer section

You answered 'no transfers'. If data touches AWS us-east-1 or similar, say yes — the section only generates when triggered.

Verificar: Re-interview with the correct transfer flag
Consent modal doesn't respect jurisdiction defaults

useJurisdiction() hook requires IP or locale detection; default is conservative (off) when unknown. Wire in a geoIP lib or Accept-Language fallback.

Alternativas

Privacy & Terms vs. outros

AlternativaQuando usarTroca
Iubenda / TermlyYou want a hosted, legally-warranted servicePaid; less editable; less dev-friendly
Hand-written policyYou have in-house counsel drafting from scratchMost rigorous; most expensive; slow
copying a friend's policyDon'tWorst option — templates fall out of sync with your actual practices

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills