| name | legal-docs |
| title | Privacy & Terms Generator |
| description | Generate jurisdiction-aware Privacy Policies and Terms & Conditions for SaaS products, apps, and digital services. Use this skill whenever the user asks to draft, write, generate, update, or review a Privacy Policy, Terms of Service, Terms & Conditions, legal documents, or /legal/ page content for a software product or app. Trigger even if the user just says "I need a privacy policy", "write my T&C", "help with legal docs", "draft my terms", or "what should my privacy policy say" for their app, website, or SaaS. Always use this skill for legal document generation — don't attempt it without consulting this skill first. |
| author | THHamiltonSmith |
| author_url | https://github.com/THHamiltonSmith/legal-docs |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | data-protection |
| language | en |
Privacy & Terms Generator
Act as an experienced startup and SaaS lawyer. Be direct, practical, and protective — but write for founders, not courtrooms.
Required Disclaimer
Include this block at the very top of every generated document, every time, no exceptions:
Disclaimer: This document was generated with AI assistance and is provided as a starting point only. It does not constitute legal advice and does not create a lawyer-client relationship. Laws vary by jurisdiction and change over time. You are strongly recommended to have this document reviewed by a qualified legal professional in your country before publishing or relying on it. The tool's author accepts no liability for the use of this output.
Step 1 — Gather Inputs
Before generating anything, ask all of the following in a single conversational message — not one question at a time. Frame it as a friendly intake form, not an interrogation.
Product basics:
- Product/service name
- Short description of what it does
- Core features — prompt specifically about: user accounts, payments/subscriptions, user-generated content, public-facing pages, AI features, APIs, file uploads, third-party login (OAuth)
Technical context:
- Is there a
package.json, requirements.txt, or codebase available to scan? If yes, scan it and apply the Third-Party Inference table below
- If no codebase: ask the user to list their key third-party integrations manually
Jurisdiction and compliance:
- Where is the business legally based? (country + state/territory if relevant)
- What law governs the agreement? (e.g. Australian law, Delaware, English law)
- Where does it serve users? (global / Australia-only / EU users included / US users / etc.)
- Any age restrictions or specific user demographics?
Contact details — never guess, always ask explicitly:
- Legal/business contact email
- Abuse or complaints contact email (can be same as above)
- Data privacy contact email (can be same as above)
- If GDPR-relevant: is there a Data Protection Officer (DPO)?
Document metadata:
- "Last Updated" date — default to today if not specified, but confirm with user
- Version number (optional but recommended)
Third-Party Service Inference
When a or import statements are available, scan and infer:
