Generate Compliant Legal Documents
Drafts GDPR/CCPA/LGPD-compliant privacy policies, ToS, DPAs, and other tech-law documents with jurisdiction-specific variations.
Why it matters
Automate the creation of essential legal documents for technology businesses, ensuring compliance with global privacy regulations and legal standards.
Outcomes
What it gets done
Draft privacy policies, terms of service, and cookie policies.
Generate data processing agreements and intellectual property notices.
Provide jurisdiction-specific legal clause variations.
Create compliance checklists and implementation notes.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-legal-advisor | bash Overview
Legal Advisor
Drafts technology-law compliance documents - privacy policies, terms of service, cookie policies, data processing agreements, and licensing terms - mapped to GDPR, CCPA/CPRA, LGPD, PIPEDA, COPPA, CAN-SPAM, and ePrivacy, with jurisdiction-specific variations and a compliance checklist. Use when drafting privacy policies, ToS, DPAs, or other tech-law compliance documents; always treat output as an informational template requiring qualified attorney review.
What it does
Acts as a legal advisor specializing in technology law, privacy regulations, and compliance documentation - drafting privacy policies, terms of service, cookie policies, data processing agreements, and other legal documents that map to specific regulatory regimes.
When to use - and when NOT to
Use this skill when working on legal advisor tasks or workflows that need guidance, best practices, or checklists for compliance documentation. Do not use it for tasks unrelated to legal advising, or when a different domain or tool is actually needed.
Inputs and outputs
Focus areas: privacy policies compliant with GDPR/CCPA/LGPD, terms of service and user agreements, cookie policies and consent management, data processing agreements (DPA), disclaimers and liability limitations, intellectual property notices, SaaS/software licensing terms, e-commerce legal requirements, email marketing compliance (CAN-SPAM, CASL), and age verification/children's privacy (COPPA).
Approach: identify which jurisdictions and regulations actually apply, write in clear accessible language while maintaining legal precision, include all mandatory disclosures and clauses for the applicable regulations, structure documents with logical sections and headers, provide options for different business models, and flag areas that require specific legal review rather than guessing.
Key regulations covered: GDPR (EU), CCPA/CPRA (California), LGPD (Brazil), PIPEDA (Canada), the Data Protection Act (UK), COPPA (children's privacy), the CAN-SPAM Act (email marketing), and the ePrivacy Directive (cookies).
Output produced: complete legal documents with proper structure, jurisdiction-specific variations where regulations differ, placeholder sections for company-specific information, implementation notes covering technical requirements (e.g. consent-management mechanics), a compliance checklist per regulation, and update tracking for regulatory changes over time. Every output always includes the disclaimer: "This is a template for informational purposes. Consult with a qualified attorney for legal advice specific to your situation."
Who it's for
Founders and product teams drafting privacy policies, terms of service, DPAs, or other tech-law compliance documents across GDPR/CCPA/LGPD/COPPA and similar regimes, who need comprehensive, jurisdiction-aware templates as a starting point - understanding the output is informational and still needs review by a qualified attorney before relying on it.
This is especially useful for teams operating across multiple regulatory regimes at once, where a single generic template understates the actual compliance burden - a SaaS product serving both EU and California users, for instance, needs GDPR-specific consent mechanics alongside CCPA-specific opt-out language in the same policy, and the jurisdiction-specific variations this skill produces are meant to surface exactly those differences rather than papering over them with one-size-fits-all boilerplate.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.