Transform complex privacy policies into clear, plain-language documents that build user trust and improve transparency compliance.
📝 The Prompt
Rewrite and simplify the following privacy policy (or create one from scratch) for [COMPANY NAME], a [TYPE OF BUSINESS] that operates [WEBSITE/APP NAME]. The goal is to make the privacy policy easy to understand for everyday users while remaining accurate and comprehensive.
Original privacy policy or key data practices to cover: [PASTE ORIGINAL POLICY OR DESCRIBE DATA PRACTICES, e.g., 'We collect email addresses, browsing behavior via cookies, and payment information. We share data with analytics partners and payment processors.']
Follow this structure:
**1. Introduction (2-3 sentences)**: Explain in plain English what this policy covers and why the user should care. Set a transparent, trustworthy tone.
**2. What We Collect**: List each type of data collected in a simple bullet-point format. Next to each item, add a brief parenthetical explaining WHY it's collected (e.g., 'Your email address (so we can send you order confirmations)').
**3. How We Use Your Data**: Describe each use case in one clear sentence. Avoid vague phrases like 'to improve our services' — be specific.
**4. Who We Share It With**: Name the categories of third parties and explain the purpose of each sharing arrangement in simple terms.
**5. Your Rights & Choices**: Clearly outline what users can do — opt out, delete data, access data — with step-by-step instructions using [PLACEHOLDER ACTION STEPS].
**6. Cookies & Tracking**: Explain what cookies are in one sentence, then list the types used and their purpose.
**7. Contact Us**: Provide a template for the contact section with [EMAIL] and [ADDRESS] placeholders.
Tone: [TONE, e.g., friendly, warm, straightforward]. Reading level: aim for 6th-8th grade. Use short sentences, everyday words, and headers that are questions (e.g., 'What information do we collect?'). Add a 'TL;DR' summary box at the top with 3-5 bullet points capturing the key takeaways.
Disclaimer: Note that this is a simplified version and recommend legal review before publishing.
💡 Tips for Better Results
Always include a disclaimer that the simplified version should be reviewed by a legal professional before going live. Use the 'so what' test for every sentence — if a regular person wouldn't understand why it matters to them, rewrite it. Compare your output against GDPR and CCPA requirements to ensure no critical sections are missing.
🎯 Use Cases
Startup founders, small business owners, and content strategists use this when they need a user-friendly privacy policy that complies with transparency principles without requiring expensive legal fees upfront.