Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#647 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
ios, objective-c
Domaine
authentication, documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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:

Langage dominant
Objective-C
Étoiles
756
Forks
283
Merge moyen
3 j 1 h
PR mergées (30 j)
2

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de google/GoogleSignIn-iOS

Toutes les issues de google/GoogleSignIn-iOS

Issues similaires

Plus d'issues Objective-C

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.