/ ディレクトリ / プレイグラウンド / Privacy & Terms
← 全サーバー ↗ GitHub
● コミュニティ kimlawtech ⚡ 即起動

Privacy & Terms

作者 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.

▶ デモを見る 📦 インストール 💡 ユースケース

なぜ使うのか

主な機能

ライブデモ

実際の動作

privacy-terms-skill.replay ▶ 準備完了
0/0

インストール

作者のリポジトリ · Claude Skills の公式ドキュメント

ユースケース

実用的な使い方： Privacy & Terms

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

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

使うタイミング： You're live in Korea within a week and need a PIPA-compliant 개인정보 처리방침 that reflects the 2025.4.21 guideline.

フロー
  1. Kick off the interview
    /privacy-terms — jurisdiction: Korea. Service type: B2C SaaS. Begin the interview.✓ コピーしました
    → 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.✓ コピーしました
    → 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.✓ コピーしました
    → Two artifacts on disk; consent modal compiles

結果： A draft privacy policy that matches the current KR guideline — your lawyer reviews, you ship.

注意点
  • 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
組み合わせ： filesystem

Add a GDPR companion policy for EU visitors

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

使うタイミング： Your main privacy policy covers KR or US, and you need a GDPR-focused companion for EU users.

フロー
  1. Route to EU module
    /privacy-terms — jurisdiction: EU (GDPR). Service type: SaaS. We already have a KR policy; generate a companion.✓ コピーしました
    → 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.✓ コピーしました
    → 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.✓ コピーしました
    → Locale switcher added; user language detected client-side

結果： Multilingual privacy surface without rewriting your KR policy.

注意点
  • Assuming GDPR adequacy for KR-EU — Korea was granted adequacy (2021); skill reflects this but check current status before relying
組み合わせ： filesystem

組み合わせ

他のMCPと組み合わせて10倍の力を

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/.✓ コピーしました
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.✓ コピーしました
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.✓ コピーしました

ツール

このMCPが提供する機能

ツール入力呼び出すタイミングコスト
/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

コストと制限

運用コスト

APIクォータ
None beyond normal Claude usage
呼び出しあたりのトークン
Moderate — final policy is long-form prose
金額
Free (check repo license)
ヒント
Interview once; re-run only the sections that change. The modular split lets you regenerate EU without re-doing KR.

セキュリティ

権限、シークレット、影響範囲

認証情報の保管： None
データ送信先： Your business details are sent to Anthropic as part of normal Claude calls. Don't paste full customer lists or raw PII into answers.

トラブルシューティング

よくあるエラーと対処法

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.

確認： 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.

代替案

Privacy & Terms 他との比較

代替案代わりに使う場面トレードオフ
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

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る