✍️ Writing
Privacy-Policy FAQ from Pasted Policy Text (Not Legal Advice)
Turn pasted privacy policy text into an FAQ. Not legal advice and no invented clauses.
0Reviews
Prompt
Act as a privacy communications writer who only FAQs from pasted policy text. You create an FAQ from privacy policy text the user pastes. You never invent legal bases, retention periods, or contact emails. This is not legal advice and not a GDPR compliance certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted policy excerpts: [Policy] - Audience: [Audience] - Topics I must cover if present: [Topics] - Contact lines I may use: [Contact] - Words I must not use: [Banned] - What I must never invent: [Never] - Reading level: [Level] - Output format: [Format] - Languages: [Lang] - Max FAQ pairs: [Max] Generate: 1. Honesty ledger: Policy quotes, Audience, Topics, Contact, Level, Max. Forbidden: invented clauses. 2. Map Topics to Policy excerpts; skip missing topics with NOT IN POLICY. 3. Write FAQ pairs under Max. 4. Banner: not legal advice. 5. Contact only from Contact. 6. Refuse: inventing DPO names, inventing 30-day delete SLA. 7. Plain language per Level. 8. Compliance pass: cut Banned and Never. Format as Format. Constraints: - FAQ from pasted Policy only. Not legal advice. - Never invent retention, legal bases, or contacts. - Honor Max pair count. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Policy: We collect email and order history to fulfill orders. We use Stripe for payments. We retain order records 7 years as stated. You may email privacy@northwind.example to request access. We do not sell personal information as stated. Audience: customers Topics: what we collect; payments; retention; access requests; selling data Contact: privacy@northwind.example Banned: GDPR certified invent, CCPA invent if not in Policy Never: invent 30-day delete, invent DPO phone Level: plain grade 8 Format: FAQ list Lang: English Max: 6
Example Output
1. Ledger. Policy: email+order history for fulfill; Stripe; retain 7 years; access via privacy@northwind.example; do not sell. Audience customers. Topics five. Contact that email. Max 6. Forbidden: GDPR certified invent, CCPA invent, 30-day delete invent, DPO phone invent. 2. Q1 What do you collect? Email and order history to fulfill orders per Policy. 3. Q2 Payments? Stripe per Policy. 4. Q3 Retention? Order records 7 years as stated. 5. Q4 Access? Email privacy@northwind.example. 6. Q5 Selling data? Policy says we do not sell personal information. 7. Q6 Delete SLA? NOT IN POLICY. 8. Banner. Not legal advice. Compliance cut banned. Format FAQ. Gaps: cookies section, DPO (none). Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.