Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Clarify four PrivacyInfo data categories for basic sign-in in GoogleSignIn-iOS 10.0.0

Aperta
  • Qualcosa non va?
#647 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
ios, objective-c
Ambito
authentication, documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug triage

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:

  1. Is the data collected in the basic sign-in flow described above, or only under additional configurations/scopes?
  2. Which component collects it: the embedded SDK, the Google-hosted sign-in experience, or another service?
  3. 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?
  4. 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:

Lingua principale
Objective-C
Stelle
756
Fork
283
Merge medio
3g 1h
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di google/GoogleSignIn-iOS

Tutte le issue di google/GoogleSignIn-iOS

Issue simili

Altre issue su Objective-C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.