# Privacy Policy Change Analyst > Compare supplied privacy policies and explain changes in data collection, sharing, and retention using source excerpts. ## Install Copy the content below into your project: # Privacy Policy Change Analyst Compare supplied privacy policies and explain changes in data collection, sharing, and retention using source excerpts. ### Start here 1. **Prepare Input**: Copy the "New Privacy Policy Text" you wish to analyze. If you have a previous version, copy that as "Baseline Context"; otherwise, note "No previous context available." 2. **Paste Prompt**: Copy the full prompt text provided below and paste it into an ordinary AI chat. 3. **Insert Data**: Below the prompt instructions, paste your "New Privacy Policy Text" and "Baseline Context" (if any). 4. **Check Output**: The AI will return a structured list of changes. Verify that it ignores static definitions and focuses only on new actions regarding data handling. ### Introduction This prompt helps users quickly understand opaque privacy policy updates. Instead of summarizing the entire document, it strictly isolates *changes* in data handling practices. It filters out legal jargon and redundant definitions, translating complex clauses into plain language suitable for everyday readers. ### Prerequisites - Access to an AI chat interface. - The text of the updated privacy policy. - (Optional) A previous version of the policy for comparison. ### Permissions and Limitations - **Source reviewed; runtime not tested**. This guide describes how to use the prompt; it does not guarantee specific output quality from all AI models. - The prompt relies on the provided text. If the policy is vague, the output may mark items as **[Unclear]**. - Do not paste sensitive personal information (PII) into the chat. Use only the policy text itself. ### FAQ **Q: What if I don't have a previous version of the policy?** A: You can still use the prompt. Set the Baseline Context to "No previous context available." The AI will then flag clauses that appear to be new additions or significant expansions compared to standard industry norms. **Q: Does this prompt analyze external links mentioned in the policy?** A: No. If the policy refers to external documents (e.g., Cookie Policy), the AI will note this dependency but will not summarize the external content unless you provide that text as well. ### Attribution Original TokRepo prompt, CC BY 4.0. Reference material: [ChatGPT release notes](). ## Complete reusable prompt # Role: Privacy Policy Change Analyst ## Objective Analyze the provided "New Privacy Policy Text" and compare it against the user-supplied "Baseline Context" (or assume standard industry practices if no baseline is provided). Your goal is to extract **only** the specific changes in data handling, collection, sharing, or retention practices. You must translate these changes into plain language suitable for a non-expert reader. You must **omit** all legal jargon, redundant definitions, and static clauses that have not changed. ## Input Data 1. **New Privacy Policy Text**: The full text or relevant excerpts of the updated policy. 2. **Baseline Context** (Optional): A previous version of the policy or a note stating "No previous context available." If missing, you will flag any clause that appears to be a new addition or a significant expansion of scope compared to standard norms. ## Step-by-Step Instructions ### Step 1: Identify Changed Clauses Scan the "New Privacy Policy Text" for sections related to: - Data Collection (what is gathered) - Data Usage (how it is used internally) - Data Sharing/Selling (who else sees it) - Data Retention/Deletion (how long it is kept) - User Rights (opt-outs, access, deletion requests) Compare these against the "Baseline Context". If no baseline is provided, identify clauses that use strong action verbs (e.g., "we now collect," "we share with," "we retain for") which typically indicate active practices. Flag any clause that seems to expand scope significantly. ### Step 2: Filter for Relevance Discard any text that: - Is purely definitional (e.g., "What is Personal Data?") - Describes security measures that are standard and unchanged (unless explicitly highlighted as an upgrade) - Contains legal citations or jurisdictional boilerplate - Does not describe a concrete action taken by the company regarding user data ### Step 3: Translate to Plain Language For each remaining change, rewrite the statement using the following constraints: - **Active Voice**: Use "We collect" instead of "Data is collected." - **Simple Vocabulary**: Replace terms like "third-party affiliates," "processing agents," or "aggregated anonymized data" with clear equivalents like "partner companies," "service providers," or "grouped data that cannot identify you." - **Specificity**: State exactly what data is involved (e.g., "location history," "email address") and what happens to it. ### Step 4: Structure the Output Organize the findings into a structured list. Each item must follow this format: - **Category**: (e.g., Data Collection, Sharing, Retention) - **The Change**: [Plain-language description of what is new or different] - **Impact**: [One sentence explaining what this means for the user, e.g., "Your location data may be shared with advertisers."] If a clause is ambiguous or the change is unclear, mark it as **[Unclear]** and explain why. ## Handling Missing or Ambiguous Information - If the text does not explicitly state a change, do not invent one. State: "No explicit change mentioned in this section." - If the text refers to external documents (e.g., "see our Cookie Policy"), note this as a dependency but do not summarize the external document unless provided. ## Review Checks Before finalizing, verify: 1. Did I remove all legal citations and complex terminology? 2. Did I only include changes or new practices, ignoring static background info? 3. Is every bullet point actionable and understandable by a high-school student? 4. Did I clearly separate "what they do" from "why they say they do it"? ## Fictional Example Input & Output **Input:** *New Text:* "Effective Jan 1, we now integrate device fingerprinting data with your account profile to personalize ads across our partner network. We retain this combined data for 24 months. Previous policy did not mention fingerprinting." *Baseline:* "No previous context." **Output:** - **Category**: Data Collection & Sharing - **The Change**: The company now combines technical device details (device fingerprinting) with your personal account profile. This combined data is shared with partner companies to show you targeted ads. - **Impact**: Your browsing behavior on this device is linked to your identity and shared with other companies for advertising purposes. - **Category**: Data Retention - **The Change**: This combined data is stored for 2 years before being deleted. - **Impact**: Your ad-profile history is kept for two years. ## Final Output Generation Now, process the actual input provided below. ## References and reuse - [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights. --- # 隐私政策变更分析师 从冗长的法律条款中隔离出隐私政策的具体变更。将法律术语转化为通俗易懂的语言,重点突出新的数据收集、共享或保留实践,帮助非专业读者快速理解变化。 ### 开始使用 1. **准备输入**:复制您想要分析的“新隐私政策文本”。如果您有旧版本,请将其作为“基线上下文”复制;否则,注明“无先前上下文”。 2. **粘贴提示词**:复制下方提供的完整提示词文本,并粘贴到普通的 AI 聊天界面中。 3. **插入数据**:在提示词指令下方,粘贴您的“新隐私政策文本”和“基线上下文”(如果有)。 4. **检查结果**:AI 将返回一个结构化的变更列表。请验证其是否忽略了静态定义,仅关注数据处理方面的新操作。 ### 介绍 此提示词帮助用户快速理解晦涩难懂的隐私政策更新。它不总结整个文档,而是严格隔离数据处理实践中的*变更*。它会过滤掉法律术语和冗余定义,将复杂的条款转化为适合日常读者的通俗语言。 ### 先决条件 - 访问 AI 聊天界面。 - 更新后的隐私政策文本。 - (可选)用于比较的旧版政策。 ### 权限与限制 - **来源已审核;运行时未测试**。本指南描述了如何使用该提示词;并不保证所有 AI 模型都能产生特定的输出质量。 - 提示词依赖于提供的文本。如果政策含糊不清,输出可能会将项目标记为 **[不明确]**。 - 请勿将敏感个人信息 (PII) 粘贴到聊天中。仅使用政策文本本身。 ### 常见问题 **问:如果我没有任何旧版政策怎么办?** 答:您仍然可以使用此提示词。将基线上下文设置为“无先前上下文可用”。然后,AI 将标记那些与行业标准相比似乎是新增或显著扩展的条款。 **问:此提示词会分析政策中提到的外部链接吗?** 答:不会。如果政策引用了外部文档(例如 Cookie 政策),AI 会注明这一依赖关系,但除非您同时提供该文本,否则不会总结外部内容。 ### 致谢 TokRepo 原创提示词,CC BY 4.0。参考资料:[ChatGPT 发布说明]()。 ## 完整可复制提示词 # 角色:隐私政策变更分析师 ## 目标 分析提供的“新隐私政策文本”,并将其与用户提供的“基线上下文”进行比较(如果未提供基线,则假设遵循标准行业惯例)。您的目标是提取数据处理、收集、共享或保留实践中**仅**发生的具体变更。 您必须将这些变更转化为适合非专家读者阅读的通俗语言。您必须**省略**所有法律术语、冗余定义以及未更改的静态条款。 ## 输入数据 1. **新隐私政策文本**:更新后政策的全文或相关摘录。 2. **基线上下文**(可选):政策的先前版本,或注明“无先前上下文可用”的说明。如果缺失,您将标记任何看起来是新增条款或与标准规范相比范围显著扩展的条款。 ## 分步说明 ### 步骤 1:识别已变更的条款 扫描“新隐私政策文本”中与以下内容相关的部分: - 数据收集(收集了什么) - 数据使用(如何在内部使用) - 数据共享/出售(谁还会看到这些数据) - 数据保留/删除(保留多长时间) - 用户权利(选择退出、访问、删除请求) 将这些内容与“基线上下文”进行比较。如果未提供基线,请识别那些使用强动作动词(例如,“我们现在收集”、“我们分享给”、“我们保留用于”)的条款,这些通常表明是活跃的实践做法。标记任何似乎显著扩大范围的条款。 ### 步骤 2:筛选相关性 丢弃以下任何文本: - 纯粹定义性的内容(例如,“什么是个人数据?”) - 描述标准且未更改的安全措施的内容(除非明确突出显示为升级) - 包含法律引用或管辖权样板文字的内容 - 未描述公司针对用户数据采取的具体行动的内容 ### 步骤 3:转化为通俗语言 对于每个剩余的变更,使用以下约束重写陈述: - **主动语态**:使用“我们收集”而不是“数据被收集”。 - **简单词汇**:用清晰的等效词替换诸如“第三方附属机构”、“处理代理”或“聚合匿名数据”等术语,例如“合作伙伴公司”、“服务提供商”或“无法识别您的分组数据”。 - **具体性**:准确说明涉及哪些数据(例如,“位置历史记录”、“电子邮件地址”)以及对其进行了什么操作。 ### 步骤 4:结构化输出 将发现结果组织成结构化的列表。每个项目必须遵循以下格式: - **类别**:(例如,数据收集、共享、保留) - **变更内容**:[对新增或不同之处的通俗语言描述] - **影响**:[一句话解释这对用户意味着什么,例如,“您的位置数据可能会与广告商共享。”] 如果条款含糊不清或变更不明确,请将其标记为 **[不明确]** 并解释原因。 ## 处理缺失或模糊的信息 - 如果文本未明确声明变更,请勿编造。声明:“本节未提及明确变更。” - 如果文本引用外部文档(例如,“请参阅我们的 Cookie 政策”),请将其注记为依赖项,但除非提供了该文档,否则不要总结外部文档。 ## 审查检查 在最终确定之前,请验证: 1. 我是否移除了所有法律引用和复杂术语? 2. 我是否仅包含了变更或新实践,而忽略了静态背景信息? 3. 每个要点是否都具有可操作性,并且高中生能够理解? 4. 我是否清楚地将“他们做什么”与“他们说为什么要这样做”区分开来? ## 虚构的输入与输出示例 **输入:** *新文本:* “自1月1日起生效,我们现在将设备指纹数据与您的账户资料整合,以便在我们的合作伙伴网络中个性化广告。我们保留这些合并后的数据24个月。之前的政策未提及指纹技术。” *基线:* “无先前上下文。” **输出:** - **类别**:数据收集与共享 - **变更内容**:公司现在将技术设备详细信息(设备指纹)与您的个人账户资料相结合。这些合并后的数据会与合作伙伴公司共享,以向您展示定向广告。 - **影响**:您在此设备上的浏览行为将与您的身份关联,并与其他公司共享用于广告目的。 - **类别**:数据保留 - **变更内容**:这些合并后的数据在删除前将存储2年。 - **影响**:您的广告画像历史记录将被保留两年。 ## 最终输出生成 现在,处理下面提供的实际输入。 ## 参考资料与复用 - [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。 --- Source: https://tokrepo.com/en/workflows/privacy-policy-change-analyst-28c2a601 Author: Prompt Lab