Role mapping before documents先弄清楚角色,再准备文件

Map who controls the data before choosing the legal tool.在挑选合适的法律工具之前,先弄清楚到底是谁在掌控这些数据。

Use this browser-only mapper to classify controller, joint-controller, processor, entrusted-processing, SDK/API, third-party sharing, and cross-border relationships. Save the result, then open the matching DPA, PIPIA, privacy policy, or contract review workflow.用这个完全在浏览器里运行的小工具,帮你判断各方属于哪种角色:控制者、共同控制者、处理者、受托处理方、SDK/API 提供方、第三方共享,还是涉及跨境。判断完保存结果,再打开对应的 DPA、PIPIA、隐私政策或合同审查流程。

Why start here?为什么从这里开始?

A processor DPA is useful only when the facts actually support processor status. SDKs, analytics, ad revenue, model training, cross-client reuse, or co-designed dashboards can change the document path.只有在事实确实支持处理者身份时,处理者 DPA 才有意义。SDK、分析、广告收入、模型训练、跨客户复用或共同设计的看板都可能改变所需文件的路径。

1. Business Context一、业务背景

2. Processing Activities二、处理活动

Use one row per activity in the result. Video-game mode starts from account, telemetry, and profiling because those are usually different legal relationships.结果里每个处理活动单独占一行。游戏模式会先列出账户、运行数据和用户画像这几项,因为它们通常属于不同的法律关系。

3. Data and Recipients三、数据与接收方

4. Role Gate四、角色判定

Answer about请就 your own company贵公司自身. Don't worry about legal labels — just describe what actually happens. We'll work out the role for you.作答。不必纠结法律术语——只需描述实际发生的情况,我们会为你判定角色。

5. Evidence五、证据

Result结果

Answer the role gate and run the analysis. The output will appear here and can be handed to the other tools.完成角色判定并运行分析。输出结果将显示在此处,并可交接给其他工具。