Privacy Policy
Draft a GDPR/CCPA-compliant privacy policy for "$ARGUMENTS". Generate a comprehensive privacy policy that satisfies major data protection regulations.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"legal-privacy-policy","workflow":"legal","phase":1,"project":"<project>","event":"skipped","artifact":"01-draft.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Draft) of the Legal Lifecycle workflow (legal); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or legal when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"legal-privacy-policy","workflow":"legal","phase":1,"project":"<project>","event":"refused","artifact":"01-draft.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"legal-privacy-policy","workflow":"legal","phase":1,"project":"<project>","event":"started","artifact":"01-draft.md","note":""}.
Check that .singularskills/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g. /legal-risk-assessment <project>) to generate the prerequisite assessment artifact."
Process
Read inputs:
- Read
.singularskills/legal/<project>/00-assess.md for risk, jurisdiction, and data practice context
Identify data practices:
- What personal data is collected (categories and specific examples)
- How data is collected (directly from users, automatically, from third parties)
- Purposes for processing each data category
- Lawful basis for processing under GDPR (consent, contract, legitimate interest, legal obligation, vital interest, public task)
- Data sharing relationships with third parties
- Data retention timelines per category
- International data transfer mechanisms
Draft GDPR Article 13/14 compliant sections:
- Data Controller Identity and Contact — legal name, address, contact details, EU representative (if applicable)
- Data Collected — categories with specific examples (identifiers, contact info, financial data, usage data, device data, location data, etc.)
- Purposes and Lawful Basis — per-category breakdown of why data is processed and the legal basis for each
- Data Sharing with Third Parties — who receives data, why, and in what capacity (processor vs. controller)
- Data Retention Periods — per-category retention periods with rationale
- User Rights — access, rectification, erasure, restriction, portability, objection, and how to exercise each right
- Automated Decision-Making and Profiling — whether used, logic involved, significance and consequences, right to opt out
- Cookie Usage — summary with link to full cookie policy
- International Data Transfers — transfer mechanisms (SCCs, adequacy decisions, BCRs) and safeguards
- Children's Privacy — age restrictions, COPPA compliance (if applicable), parental consent mechanisms
- Policy Updates Procedure — how changes are communicated, effective date handling
- DPO / Contact Information — Data Protection Officer details (if appointed), supervisory authority contact, complaint procedures
Add CCPA-specific provisions (if applicable):
- Categories of personal information collected (CCPA categories)
- Right to know, right to delete, right to opt out of sale/sharing
- "Do Not Sell or Share My Personal Information" link requirement
- Financial incentive disclosures (if any)
- Authorized agent procedures
- Non-discrimination statement
Write the artifact — append to .singularskills/legal/<project>/01-draft.md under a ## Privacy Policy section. Create the file with a # Draft — <project> heading if it does not exist; if a ## Privacy Policy section already exists, replace only that section.
Output
The privacy policy draft appended to .singularskills/legal/<project>/01-draft.md. Present a summary to the user highlighting:
- Regulations addressed (GDPR, CCPA, others)
- Number of data categories documented
- Third-party data sharing relationships identified
- User rights enumerated
- Areas flagged for attorney review (especially lawful basis determinations and transfer mechanisms)
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"legal-privacy-policy","workflow":"legal","phase":1,"project":"<project>","event":"finished","artifact":"01-draft.md","note":""}.
This artifact is shared by every skill of phase 1 (Draft). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Draft
workflow: legal
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Privacy Policy section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is legal-privacy-policy).
End your section with ### Decisions and ### Open questions (one level under your ## Privacy Policy heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>
1---2name: legal-privacy-policy3description: Draft a GDPR- and CCPA-compliant privacy policy — data collected, purposes and lawful basis, sharing, retention, user rights, transfers, children's privacy and Do Not Sell provisions. Use when the user needs a privacy policy written or updated for their website, app or product. Not for cookie-specific disclosures; see /legal-cookie-policy.4metadata:5 source: https://skillmd.com/skills/bromso/legal-privacy-policy6 argument-hint: "[project] [--skip-checks]"7 workflow: legal8 phase: 19 artifact: 01-draft.md10---1112# Privacy Policy1314Draft a GDPR/CCPA-compliant privacy policy for "$ARGUMENTS". Generate a comprehensive privacy policy that satisfies major data protection regulations.1516> **Note:** AI-generated legal content does not constitute legal advice. Consult a qualified attorney.1718**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"legal-privacy-policy","workflow":"legal","phase":1,"project":"<project>","event":"skipped","artifact":"01-draft.md","note":"<reason or \"none given\">"}`.1920## Prerequisites2122**Part of a workflow.** This skill is phase 1 (Draft) of the Legal Lifecycle workflow (`legal`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `legal` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2324Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"legal-privacy-policy","workflow":"legal","phase":1,"project":"<project>","event":"refused","artifact":"01-draft.md","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"legal-privacy-policy","workflow":"legal","phase":1,"project":"<project>","event":"started","artifact":"01-draft.md","note":""}`.2526Check that `.singularskills/legal/<project>/00-assess.md` exists. If it does not exist, stop and tell the user:2728> "Run an Assess skill first (e.g. `/legal-risk-assessment <project>`) to generate the prerequisite assessment artifact."2930## Process31321. **Read inputs:**33 - Read `.singularskills/legal/<project>/00-assess.md` for risk, jurisdiction, and data practice context34352. **Identify data practices:**36 - What personal data is collected (categories and specific examples)37 - How data is collected (directly from users, automatically, from third parties)38 - Purposes for processing each data category39 - Lawful basis for processing under GDPR (consent, contract, legitimate interest, legal obligation, vital interest, public task)40 - Data sharing relationships with third parties41 - Data retention timelines per category42 - International data transfer mechanisms43443. **Draft GDPR Article 13/14 compliant sections:**4546 - **Data Controller Identity and Contact** — legal name, address, contact details, EU representative (if applicable)47 - **Data Collected** — categories with specific examples (identifiers, contact info, financial data, usage data, device data, location data, etc.)48 - **Purposes and Lawful Basis** — per-category breakdown of why data is processed and the legal basis for each49 - **Data Sharing with Third Parties** — who receives data, why, and in what capacity (processor vs. controller)50 - **Data Retention Periods** — per-category retention periods with rationale51 - **User Rights** — access, rectification, erasure, restriction, portability, objection, and how to exercise each right52 - **Automated Decision-Making and Profiling** — whether used, logic involved, significance and consequences, right to opt out53 - **Cookie Usage** — summary with link to full cookie policy54 - **International Data Transfers** — transfer mechanisms (SCCs, adequacy decisions, BCRs) and safeguards55 - **Children's Privacy** — age restrictions, COPPA compliance (if applicable), parental consent mechanisms56 - **Policy Updates Procedure** — how changes are communicated, effective date handling57 - **DPO / Contact Information** — Data Protection Officer details (if appointed), supervisory authority contact, complaint procedures58594. **Add CCPA-specific provisions (if applicable):**60 - Categories of personal information collected (CCPA categories)61 - Right to know, right to delete, right to opt out of sale/sharing62 - "Do Not Sell or Share My Personal Information" link requirement63 - Financial incentive disclosures (if any)64 - Authorized agent procedures65 - Non-discrimination statement66675. **Write the artifact** — append to `.singularskills/legal/<project>/01-draft.md` under a `## Privacy Policy` section. Create the file with a `# Draft — <project>` heading if it does not exist; if a `## Privacy Policy` section already exists, replace only that section.6869## Output7071The privacy policy draft appended to `.singularskills/legal/<project>/01-draft.md`. Present a summary to the user highlighting:72- Regulations addressed (GDPR, CCPA, others)73- Number of data categories documented74- Third-party data sharing relationships identified75- User rights enumerated76- Areas flagged for attorney review (especially lawful basis determinations and transfer mechanisms)7778**Record the run.** After you have written your section, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"legal-privacy-policy","workflow":"legal","phase":1,"project":"<project>","event":"finished","artifact":"01-draft.md","note":""}`.7980This artifact is shared by every skill of phase 1 (Draft). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (`skill` is the phase title, `started` the time of that first write; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`); if it already exists, leave the block alone except to update `finished` and to set `gate` to the worst value among the sections (`skipped` over `passed`).8182```yaml83---84skill: Draft85workflow: legal86phase: 187project: <project>88started: <ISO timestamp>89finished: <ISO timestamp>90agent: <the agent you run in, or "unknown">91gate: <passed|skipped>92---93```9495Open your `## Privacy Policy` section with one italic line, `*<skill name> · <ISO timestamp> · gate: <passed|skipped>*` (your skill name is `legal-privacy-policy`).9697End your section with `### Decisions` and `### Open questions` (one level under your `## Privacy Policy` heading, so the section stays one block), in this shape:9899```markdown100### Decisions101- <what was chosen> — <why> — <what was rejected>102103### Open questions104- <what the next phase or a reviewer must settle>105```