thinkhard.SI

Prompt repository Legal & compliance

Draft a privacy notice from your actual data practices

Your website or service needs a privacy notice, and you want a plain draft built from what you really collect and do, ready for a lawyer to check.

Registry no.
LEG-015
Collection
Legal & compliance
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
10
Added

Legal & complianceAny chat

The prompt

Score 10 of 10, Excellent

Use it when Your website or service needs a privacy notice, and you want a plain draft built from what you really collect and do, ready for a lawyer to check.

  • {{business}}
  • {{where}}
  • {{data_collected}}
  • {{purposes}}
  • {{sharing}}
  • {{storage_and_retention}}
  • {{choices}}
  • {{contact}}
  • {{changes}}
  • {{jurisdictions}}
Full prompt and why it works
Prompt
Draft a privacy notice for {{business}} from the facts below, for a qualified lawyer or privacy professional to review before it is published on {{where}}. The notice should tell customers in plain words what we collect, why, who we share it with, how long we keep it and how to contact us. It must describe only what we actually do, because a notice that promises more or less than our practice is a problem in itself.

What we collect, from whom, and how (forms, accounts, orders, cookies and analytics, emails, calls):
"""
{{data_collected}}
"""

Why we use each kind of data:
"""
{{purposes}}
"""

Who we share it with, or which services handle it for us: {{sharing}}
Where data is stored, and how long we keep it: {{storage_and_retention}}
Choices and rights we offer, and how people use them: {{choices}}
Contact for privacy questions: {{contact}}
When the notice takes effect, and how we will announce changes: {{changes}}
Where we operate, and any laws our lawyer has told us apply: {{jurisdictions}}

Write:
1. The notice, 500 to 900 words, under these headings: Who we are, What we collect, How we use it, Who we share it with, How long we keep it, Your choices, Cookies and similar tools, Contact us, Changes to this notice. Use "we" and "you", short sentences and no legal jargon.
2. A table for our records with the columns Data, Collected from, Purpose, Shared with, Kept for, Notice section, linking each item in the notice to the fact it came from.
3. For the reviewer: gaps and questions, such as data with no stated purpose or retention period, or a right the notice mentions without saying how we honor it.

Rules:
- Use only our facts. Do not add legal bases, rights, retention periods, transfer safeguards or promises such as "we never sell your data" unless they are in the facts above. If two facts seem to conflict, such as that promise next to an advertising tool, leave the promise out of the draft and list the conflict for the reviewer.
- If a service appears in our facts but not under sharing, list it under sharing marked [TO CONFIRM].
- Do not say the notice complies with any law. If our facts name a law, do not describe what it requires; add "check the notice against this law" to the reviewer's list.
- Mark the top of the draft "DRAFT FOR LEGAL REVIEW".

If a section, or an item within it, has no facts behind it, keep it and write [TO CONFIRM: ...] rather than filling it with typical wording.

Variables

{{business}}
Your business or organization name.
{{where}}
Where the notice will appear, for example "our website and booking app".
{{data_collected}}
Every kind of personal data you collect, from whom and how, including cookies and analytics tools.
{{purposes}}
What you use each kind of data for, for example "email address: order updates and, if they opt in, our newsletter".
{{sharing}}
The services and partners that receive or process data, for example "Stripe for payments, Mailchimp for email".
{{storage_and_retention}}
Where data is held and how long you keep each kind, or "not decided".
{{choices}}
What people can ask for and how, for example "unsubscribe link; email us to see or delete their data".
{{contact}}
The email or address for privacy questions.
{{changes}}
The date the notice takes effect and how you will tell people about changes, or "not decided".
{{jurisdictions}}
Where you and your customers are, and any laws your lawyer has named, or "not yet checked".

Why it works

  • What to avoid. It adds no legal bases, rights or promises you have not stated, and drops a promise your other facts contradict, because a notice that misdescribes your practice creates the problem it is meant to prevent.
  • Format. A record table links every statement in the notice to the fact and section it came from, which is what the reviewing lawyer needs to check it.
  • If unsure. Sections and items without facts keep their place with [TO CONFIRM], so gaps stay visible instead of being filled with boilerplate.

How to use it

  1. Press Fill in variables and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.
Use it from code

Get this prompt as JSON from the free REST API, with your own text in the blanks, or let an AI assistant fetch it through the MCP server. No key.

curl -s https://thinkhard.si/api/v1/prompts/privacy-notice-from-practices

With the MCP server added to Claude, ChatGPT, Cursor or VS Code, call get_prompt with {"prompt": "privacy-notice-from-practices"}, or just ask for it by name.