Skip to main content
plugin official · Anthropic

privacy-legal — Claude Code plugin: features and installation

The privacy-legal Claude Code plugin handles privacy workflows, from DPA review to PIA drafting. It also prepares DSAR response drafts and checks for gaps between policy and practice.

Apache-2.0 ★ 10,060 updated 2026-10-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/claude-for-legal
/plugin install privacy-legal@claude-for-legal
Open on GitHub

What privacy-legal does

privacy-legal classifies data-processing activities, reviews DPAs against a team's playbook, creates PIAs, and drafts responses to data subject access requests (DSARs). Separate workflows compare new regulations with current policy and scan for drift between written policy and actual practice. Outputs are drafts for attorney review, not legal conclusions.

Setup starts with an interview about the organisation's role and applicable regulations. The plugin then reads a privacy policy, a standard DPA, and a reference PIA; those documents shape its working profile. The setup needs a public policy URL, the standard DPA, and one reference PIA. Settings live in ~/.claude/plugins/config/claude-for-legal/privacy-legal/CLAUDE.md. A configured outputs folder is needed for recurring policy-drift scans; direct queries work without one.

What it helps with

  • classify a processing activity and determine whether it needs a PIA
  • review a DPA against the team's positions and draft redlines
  • prepare a first response to a DSAR
  • compare a new regulation with current policy
  • spot drift between written policy and practice

Example prompts for the agent

  • Set up the plugin using our privacy policy, standard DPA, and reference PIA: /privacy-legal:cold-start-interview
  • Review customer-dpa.pdf against our playbook: /privacy-legal:dpa-review customer-dpa.pdf
  • Draft a response to this data subject access request: /privacy-legal:dsar-response

How to install privacy-legal

Plugin marketplace

/plugin marketplace add anthropics/claude-for-legal
/plugin install privacy-legal@claude-for-legal

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about privacy-legal

How do I install privacy-legal in Claude Code?

Run these commands in order: /plugin marketplace add anthropics/claude-for-legal, then /plugin install privacy-legal@claude-for-legal.

What does privacy-legal do?

It reviews DPAs, triages processing activities, generates PIAs, drafts DSAR responses, and checks for policy drift. Its outputs are drafts for attorney review.

What does privacy-legal need to work?

Setup uses a public privacy policy URL, a standard DPA, and a reference PIA. Recurring policy-drift scans also need a configured outputs folder.

Source text

privacy-legal · Apache-2.0
# Privacy Counsel Plugin

In-house privacy counsel workflows: DPA review, DSAR response drafting, PIA generation, and regulation-to-policy gap analysis. Built around a team practice profile learned from your actual privacy policy, DPA template, and a reference PIA.

**Every output is a draft for attorney review — cited, flagged, and gated — not a legal conclusion.** The plugin does the work: reads the documents, applies your playbook, finds the issues, drafts the memo. A lawyer reviews, verifies, and decides. Citations are tagged by source so you know which ones came from a research tool and which ones need checking. Privilege markers are applied conservatively so nothing waives by accident. Consequential actions — filing, sending, executing — are gated behind explicit confirmation.

## Who this is for

| Role | Primary workflows |
|---|---|
| **Privacy counsel** | DPA review, PIA sign-off, reg gap analysis |
| **Privacy program manager** | DSAR handling, PIA intake, vendor privacy review |
| **Product counsel** | PIA generation for launches |
| **Support / CS** | DSAR first-line response (with escalation) |

## First run: the cold-start interview

The plugin interviews you to learn: are you a controller or processor, which regulations actually apply, what you will and won't agree to in a DPA. Then it reads three seed documents — your privacy policy, your DPA template, one PIA you're happy with — and learns your real positions and house style.

Your configuration is stored at `~/.claude/plugins/config/claude-for-legal/privacy-legal/CLAUDE.md` and survives plugin updates.

```
/privacy-legal:cold-start-interview
```

## Commands

| Command | Does |
|---|---|
| `/privacy-legal:cold-start-interview` | Cold-start interview |
| `/privacy-legal:use-case-triage [activity]` | Does this need a PIA? Quick classification + conditions |
| `/privacy-legal:dpa-review [file]` | Review a DPA against your playbook (auto-detects direction) |
| `/privacy-legal:dsar-response` | Walk through a DSAR and draft the response |
| `/privacy-legal:pia-generation [feature]` | Generate a PIA in your house style |
| `/privacy-legal:reg-gap-analysis [regulation]` | Diff a new reg against current policy/practice |
| `/privacy-legal:policy-monitor` | Weekly sweep for policy drift, or direct query for a proposed new practice |
| `/privacy-legal:matter-workspace` | Manage matter workspaces (multi-client private practice only) — new, list, switch, close, none |

## Skills

| Skill | Purpose |
|---|---|
| **cold-start-interview** | Writes CLAUDE.md from interview + seed docs |
| **use-case-triage** | Does this need a PIA / DPIA / can it proceed? Policy conflict check + handoffs |
| **dpa-review** | Bi-directional (processor/controller) DPA term-by-term review |
| **dsar-response** | Identity verification → system walk → exemptions → response draft |
| **pia-generation** | PIA in house format, with policy consistency check |
| **reg-gap-analysis** | New reg vs. current state, remediation plan |
| **policy-monitor** | Crawls outputs for practice drift; drafts policy language updates |
| **matter-workspace** | Create, list, switch, and close matter workspaces for multi-client practices; isolates each client/matter so context does not leak across them |

## Quick start

### 1. Setup

```
/privacy-legal:cold-start-interview
```

Have ready: your public privacy policy URL, your standard DPA, one reference PIA.

### 2. Triage a new feature or processing activity

```
/privacy-legal:use-case-triage "Marketing wants to use behavioral data for ad personalization"
```

Output: PROCEED / PIA REQUIRED / DPIA MANDATORY / STOP — with conditions table, lawful basis
question, and offer to kick off the PIA in the same conversation.

### 3. Review a customer DPA

```
/privacy-legal:dpa-review customer-dpa.pdf
```

Output: direction auto-detected, term-by-term vs. playbook, proposed redlines, policy consistency check.

### 4. Handle a DSAR

```
/privacy-legal:dsar-response
```

Walks you through: classify → verify → locate → exemptions → draft. Uses your systems list from the config CLAUDE.md.

### 5. PIA a new feature

```
/privacy-legal:pia-generation "Location sharing feature"
```

Intake questions → PIA in your house format → policy diff → conditions list.

## How it learns

Your practice profile at `~/.claude/plugins/config/claude-for-legal/privacy-legal/CLAUDE.md` isn't static — it improves as you use the plugin. Skills tell you when an output used a default you should tune. The `policy-monitor` skill watches for drift between your policy and your practice and proposes updates. You can re-run setup, edit the file directly, or tell a skill to record a new position.

## File structure

```
privacy-legal/
├── .claude-plugin/plugin.json
├── .mcp.json
├── CLAUDE.md
├── README.md
├── skills/
│   ├── cold-start-interview/
│   ├── use-case-triage/
│   ├── dpa-review/
│   ├── dsar-response/
│   ├── pia-generation/
│   ├── reg-gap-analysis/
│   ├── policy-monitor/
│   └── matter-workspace/
└── hooks/hooks.json
```

## Notes

- DPA review is bi-directional: same skill handles customer DPAs (defend operational flex) and vendor DPAs (protect data). Direction auto-detected, or ask.
- PIA format comes from your seed PIA. If you didn't provide one during setup, it uses a generic structure — re-run setup with a reference PIA to fix.
- Gap analysis (`reg-gap-analysis`) handles incoming regulations. Policy monitor handles internal practice drift. Different tools for different directions of change.
- Policy monitor requires an outputs folder to be configured (set during setup) for the sweep to work. Direct-query mode works without it.

© Anthropic · Apache-2.0 · anthropics/claude-for-legal

Similar plugins

All plugins for Finance and business →
privacy-data-security JoelLewis privacy-data-security guides privacy and cybersecurity compliance for SEC-registered firms under Regulation S-P, Regulation S-ID, and SEC standards. CX Codex +1 757installs legal-risk-assessment official anthropics The legal-risk-assessment skill scores legal risks on a severity-by-likelihood matrix and flags when a matter needs senior counsel. Useful for contract and deal review. CX Codex +1 5,500installs legal-response official anthropics The legal-response skill drafts replies to common legal inquiries from configured templates and checks when a matter needs counsel. Use it for DSRs, NDAs, vendor questions, and subpoenas. CX Codex +1 3,600installs legal-advisor VoltAgent Community legal-advisor is a Claude Code subagent that reviews contracts, compliance requirements, and legal risks for technology businesses. It also helps draft service terms and IP materials. CX Codex 1,776installs OffshoreProz — A legal home for AI agents offshoreproz OffshoreProz — A legal home for AI agents is an MCP server for Claude Code that assesses an AI agent owner’s liability and compares legal structures. Its free diagnostic needs no API key. CX Codex +1 473installs linkfox-zhihuiya-legal-status linkfox-ai linkfox-zhihuiya-legal-status — a skill for Claude Code and Codex that inspects patent legal status using PatSnap records. It retrieves validity, expiration dates, litigation, and assignment changes by patent ID or publication number. CX Codex +1 395installs

From the same set174

The whole set →
law-student law-student — a plugin for Claude Code provides Socratic drilling and legal exam preparation. Runs during case briefing, outline drafting, and IRAC essay reviews. ★ 10,060repo stars litigation-legal litigation-legal — a plugin for Claude Code organizes litigation matters, tracks dispute portfolios, and drafts legal documents for attorney review. Handles intake logs, chronologies, legal holds, and outside counsel updates. ★ 10,060repo stars ai-governance-legal ai-governance-legal — a plugin for Claude Code automates AI legal governance workflows, impact assessments, and vendor AI contract reviews. ★ 10,060repo stars regulatory-legal The regulatory-legal Claude Code plugin monitors regulatory updates and compares new rules with a policy library. It tracks open gaps and comment deadlines, then prepares a digest. ★ 10,060repo stars employment-legal employment-legal — a Claude Code plugin for employment law workflows: reviews hires and terminations, classifies workers, and tracks leave deadlines. ★ 10,060repo stars corporate-legal This Claude Code plugin handles corporate legal work, from M&A document review to governance drafts and entity deadlines. Its commands launch diligence extraction, closing checklists, and other matter workflows. ★ 10,060repo stars product-legal product-legal is a Claude Code plugin that reviews product launches, marketing copy, and feature risks against company risk calibration. ★ 10,060repo stars commercial-legal commercial-legal — a Claude Code plugin that automates legal document and contract review. It analyzes agreements, tracks renewal deadlines, and generates summaries for business stakeholders. ★ 10,060repo stars

Project sponsors

Companies that keep this analytics open