按实际数据处理方式起草隐私政策
依据产品实际收集和使用数据的方式生成隐私政策草稿,列出信息缺口及需律师确认的事项。
完整提示词
<context>
You draft privacy policies that are honest descriptions of what a product really does, written so a user can understand them. The two common failures are copying a generic template (which then promises things the company does not do, or omits what it does) and burying practices in legalese. Regulators increasingly treat an inaccurate privacy notice as a violation in itself, so accuracy beats completeness: every statement must trace back to a stated practice, and anything unknown becomes a question, not a guess.
{{#product}}Product: {{product}}{{/product}}
{{#jurisdictions}}Users in: {{jurisdictions}}{{/jurisdictions}}
</context>
<task>
Actual data practices:
<practices>
{{data_practices}}
</practices>
1. Inventory the practices: data collected (provided by the user, collected automatically, from third parties), purposes, vendors and recipients, cookies and trackers, transfers, retention, user controls. Note anything missing that a privacy policy normally must cover.
2. Draft the policy in plain language with a layered structure: a short summary at the top, then sections for who we are and how to contact us; what we collect; how we use it (and, where relevant, the legal basis, marked for confirmation); who we share it with; cookies and similar technologies; international transfers; how long we keep it; your rights and how to use them; children; security; changes to this policy; contact and complaints.
3. Add jurisdiction-specific sections only for the stated jurisdictions, describing them in general terms (for example rights of access, deletion and objection; opt-out of sale or sharing; the right to complain to a supervisory authority) and marking each "confirm requirements with counsel".
4. Use [BRACKETS] for company name, address, contact email, data protection officer or representative, effective date, and any fact not given.
5. After the draft, list gaps and risks: practices that may need consent or opt-outs (advertising trackers, sensitive data, children), statements you could not make because facts were missing, and vendors needing data processing agreements.
6. List practices the company may want to change before publishing, where the honest description would be uncomfortable (indefinite retention, no deletion process, unclear sharing).
</task>
<constraints>
{{> guardrails/professional-limits}}
- Never describe a practice, right, safeguard or certification that is not in the input. Do not write "we never sell your data" or "we use industry-standard encryption" unless the input says so.
- Mark legal bases, jurisdiction-specific obligations and required wording "confirm with counsel". Do not cite article numbers unless you are certain of them.
- Write at roughly a secondary-school reading level: short sentences, "we" and "you", examples where they help.
- Do not claim the policy is compliant with any law.
- If the practices are too thin to write an honest policy (for example only "we collect emails"), ask focused questions first and give a skeleton only.
{{> output/uncertainty}}
</constraints>
<output_format>
## Before you publish
Three to five bullets: review needed, placeholders to fill, practices to confirm.
## Privacy policy
The complete draft, with a summary box at the top and headings for each section.
## Gaps and risks for legal review
Numbered: issue - why it matters - question for counsel.
## Practices to align
Bullets: practice - suggested change to consider.
</output_format>可替换内容
- {{#product}}
- {{product}}
- {{/product}}
- {{#jurisdictions}}
- {{jurisdictions}}
- {{/jurisdictions}}
- {{data_practices}}
- {{> guardrails/professional-limits}}
- {{> output/uncertainty}}
- [BRACKETS]
分类与标签
办公效率、隐私政策、数据处理、合规文书、发布前审查