Privacy Policy & Terms — Draft in Minutes

I draft launch-ready privacy policies and terms of service from your real setup — matched to what you actually collect — and flag exactly where you need a lawyer. This is document drafting, not legal advice.

When to Use

• Launching a site or app: You need a privacy policy live before you can go public.
• App Store / Play Store submission: The store requires a privacy policy URL to approve you.
• Setting up payments: Stripe, PayPal, or a processor wants terms and a privacy policy first.
• Adding analytics or pixels: You added GA, Meta Pixel, or other tracking and need the cookie/privacy disclosure to match.
• Selling to EU or California users: You need GDPR / CCPA-style disclosures.
• Collecting emails or accounts: Newsletter signups, logins, or checkout all trigger privacy obligations.
• Outdated policy: You shipped new features (AI, new SDKs, new vendors) and your policy no longer reflects reality.
• Need terms to set the rules: Acceptable use, refunds, accounts, and liability limits.
• Pre-fundraise / due diligence: You're cleaning up before investors look.

Example

Input:

"Shopify store selling skincare, ship to US + EU. Collect name, email, shipping address, payment via Stripe. Use Google Analytics and Meta Pixel. Email list via Klaviyo. No accounts, no children's products. Need privacy policy + terms."

Output:

• A full privacy-policy draft with sections matched to the setup (data collected, Stripe/GA/Meta/Klaviyo as processors, retention, security, contact)
• Cookie/tracking disclosure covering GA and Meta Pixel
• GDPR rights section (access, deletion, objection) for EU shoppers
• CCPA/CPRA notice including a "Do Not Sell or Share" line given Meta Pixel use
• A terms-of-service draft (refunds, acceptable use, IP, liability limits, governing law placeholder)
• A clearly marked placeholder list: [LEGAL ENTITY NAME], [BUSINESS ADDRESS], [CONTACT EMAIL], [GOVERNING JURISDICTION]
• Lawyer-checkpoint flags: cross-border EU data transfer, and confirming Meta Pixel "sale/share" treatment under CCPA

Why This Skill is Different

• Matches what you actually do: It asks intake questions first, so the policy reflects your real data practices instead of a blank template you might misuse. Trade-off: only as accurate as what you disclose.
• Honest about limits: It flags the spots that need a lawyer rather than pretending to be legal advice — safer for you.
• Two documents, one pass: Privacy policy and terms together, kept consistent.
• Region-aware: GDPR, CCPA/CPRA, and cookie disclosures get included based on where your users are.
• Paste-ready: Plain English with every fill-in placeholder clearly marked.

Who It's For

Indie developers and app makers, Shopify and ecommerce store owners, SaaS founders, small business website owners, marketers launching landing pages and newsletters, freelancers and agencies setting up client sites, and startup founders prepping for launch or fundraising.

Disclaimer

This Skill provides AI-assisted document drafting based solely on the information you provide and is for general informational purposes only. It is NOT legal advice, is NOT a substitute for a licensed attorney, and using it does not create an attorney-client relationship. It does not guarantee compliance with the GDPR, CCPA/CPRA, or any other law, and does not guarantee protection from fines or penalties. You are responsible for verifying the accuracy of all content, filling in all placeholders, and having a qualified lawyer in your jurisdiction review any document before you publish or rely on it. Laws vary by region and change over time.