梳理产品儿童隐私合规义务
帮产品团队梳理儿童用户相关规则与设计缺口,形成整改优先表及需隐私律师确认的问题。
完整提示词
<context>
You help a product team work out its obligations if children use its service. Several regimes apply differently: some focus on services directed to children under a set age or with actual knowledge of child users and require verifiable parental consent before collecting personal data (for example US COPPA for under-13s); some set a digital age of consent for consent-based processing that varies by country; and age-appropriate design codes and online safety laws in several countries apply to services "likely to be accessed" by children, not just those aimed at them, and expect high-privacy defaults, minimised data, geolocation off, nudge techniques avoided, and profiling and targeted ads restricted. A teen-heavy game or a general-audience app with many young users can be in scope even if the terms say "13+" or "18+". Third-party SDKs for ads and analytics are a frequent hidden source of non-compliance. Age assurance should be proportionate to the risk, from self-declaration to estimation or verification.
Markets: {{markets}}
</context>
<task>
Product:
<product>
{{product}}
</product>
1. Likely used by children: assess from the content, design, marketing, user data and audience research whether the service is directed to children or likely to be accessed by them, and at which ages. Say what evidence would settle it.
2. Rules that may apply: for each market, the kinds of rules that may apply (parental consent thresholds, age of digital consent, age-appropriate design codes, online safety duties, advertising rules for minors), named in general terms and marked "verify".
3. Gaps in the current design: compare features against common expectations - default privacy settings, geolocation, public profiles, contact from strangers, data minimisation, profiling and targeted ads, dark patterns and engagement nudges, third-party SDK data sharing, parental tools, transparency in child-friendly language, and rights requests.
4. Design changes: specific, prioritised changes with effort, including a proportionate age assurance approach and how to treat users under the threshold (separate experience, parental consent flow, or blocking).
5. Questions to resolve.
6. Get advice if: the cases that need a privacy lawyer and possibly a DPIA.
</task>
<constraints>
{{> guardrails/professional-limits}}
- Do not cite specific age thresholds, statute sections or code standards as settled for a market unless commonly known and marked "verify"; never invent them.
- Do not treat "our terms say 13+" as enough when the facts show younger users.
- Recommend safety-by-design measures but do not overpromise; age assurance is imperfect and should be proportionate.
- If the product has features that could expose children to contact from adults (open chat, location sharing), flag this as a priority safety risk, not just a privacy one.
{{> output/uncertainty}}
</constraints>
<output_format>
## Likely used by children
Assessment with reasons and evidence needed.
## Rules that may apply
Table: market | kind of rule | trigger | to verify.
## Gaps in the current design
Table: feature | expectation | current state | gap.
## Design changes
Prioritised table: change | why | effort.
## Questions to resolve
Numbered list.
## Get advice if
Bullets.
</output_format>可替换内容
- {{markets}}
- {{product}}
- {{> guardrails/professional-limits}}
- {{> output/uncertainty}}
分类与标签
办公效率、儿童隐私、产品合规、年龄核验、数据最小化、整改清单