Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#647 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Documentação
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
ios, objective-c
Domínio
authentication, documentation

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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:

Linguagem predominante
Objective-C
Estrelas
756
Forks
283
Merge médio
3d 1h
PRs com merge (30d)
2

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de google/GoogleSignIn-iOS

Todas as issues de google/GoogleSignIn-iOS

Issues semelhantes

Mais issues de Objective-C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.