Clarify four PrivacyInfo data categories for basic sign-in in GoogleSignIn-iOS 10.0.0
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 48/100
- Issue 類型
- 文件
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- ios, objective-c
研究方向
Start with the referenced PrivacyInfo.xcprivacy at commit 7823e518f5d4db765ccac3e140dd3265ef0a1cf1 and compare its four named categories with the linked iOS sign-in privacy guide and issue #646 comment. Clarify collection, component, purpose, linkage, tracking, and whether the manifest covers possible integrations for basic sign-in; done when official guidance answers each question for version 10.0.0.
由索引模型根據 Issue 內容生成。
描述
We use GoogleSignIn-iOS 10.0.0, pinned at commit 7823e518f5d4db765ccac3e140dd3265ef0a1cf1, for basic Google sign-in on iOS with email/profile only. We do not request phone-related or other additional scopes, and we do not implement phone/SMS authentication.
The SDK's PrivacyInfo.xcprivacy declares PhoneNumber, DeviceID, OtherUsageData, and OtherDataTypes in addition to categories discussed in the iOS sign-in privacy guide. The guide describes user identifiers and IP-derived location, but does not clarify how these four categories apply to a basic sign-in integration.
Could you clarify, for each of these four categories:
- Is the data collected in the basic sign-in flow described above, or only under additional configurations/scopes?
- Which component collects it: the embedded SDK, the Google-hosted sign-in experience, or another service?
- What examples, purposes, and conditions should an app developer use to determine the appropriate App Store App Privacy disclosure? Is it linked to the user, and is any such use considered tracking under Apple's definition?
- Is the manifest intentionally a superset of possible integrations? Is there updated official guidance mapping basic sign-in to the manifest categories?
We are preparing accurate privacy disclosures and want to avoid assuming either that an unused API means no collection, or that all declared SDK categories necessarily occur in our specific integration.
Related clarification: https://github.com/google/GoogleSignIn-iOS/issues/646#issuecomment-5974207621 explains the conservative phone-number declaration for version 8.0.0. Thank you for that explanation. Could you confirm how it applies to version 10.0.0 and provide the category-by-category clarification requested above, especially for DeviceID, OtherUsageData, and OtherDataTypes?
References:
- 主要語言
- Objective-C
- 星號
- 756
- 分支
- 283
- 平均合併
- 3 天 1 小時
- 30 天內合併 PR
- 2
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
google/GoogleSignIn-iOS 的其他 Issue
-
Revoke request uses GET instead of POST可能重新可做 關聯的 PR 已關閉且未合併。 未關閉enhancement triage
難度 2/5 1-3 小時 新手友好度 72/100
google/GoogleSignIn-iOS#621 ·
-
enhancement triage
難度 2/5 1-3 小時 新手友好度 76/100
google/GoogleSignIn-iOS#620 ·
-
難度 2/5 1-3 小時 新手友好度 68/100
google/GoogleSignIn-iOS#440 · 4 則留言 · 2 個 reaction ·
-
enhancement triage
難度 4/5 3-5 天 新手友好度 48/100
google/GoogleSignIn-iOS#611 ·
-
難度 4/5 3-5 天 新手友好度 45/100
google/GoogleSignIn-iOS#607 ·
查看 google/GoogleSignIn-iOS 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 79/100
joncampbell123/dosbox-x#6664 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 90/100
sparkle-project/Sparkle#2932 ·
維護者通常 1 天內回覆
-
Typo in installer: “addition protections” → “additional protections”可能已有人在做 @Jah-yee 於 1 天前認領。 未關閉
難度 1/5 1 小時以內 新手友好度 94/100
objective-see/BlockBlock#111 ·
-
s: need triage
難度 1/5 1 小時以內 新手友好度 88/100
Tencent-TDS/KuiklyUI#1786 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 82/100
DataDog/dd-sdk-ios#3293 ·
維護者通常 3 天內回覆