/ 目錄 / 演練場 / 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 搭配，撬動十倍槓桿

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
每次呼叫 Token 數
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