Skip to content

add notes for complying user data policy in 4.10.1 #2333

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 12, 2022

Conversation

wenxi-zeng
Copy link
Contributor

Proposed changes

this pr add a note to warn about the latest android changes. in analytics-android 4.10.1, we no longer pulls ANDROID_ID to comply Google's user data policy.

Merge timing

  • ASAP once approved

Related issues (optional)

@wenxi-zeng wenxi-zeng requested a review from a team as a code owner January 11, 2022 22:52
@wenxi-zeng wenxi-zeng requested review from rchinn1 and prayansh and removed request for a team January 11, 2022 22:52
@@ -24,7 +24,10 @@ Naturally the Analytics SDK needs a unique ID for each user. The very first time

The Segment SDK also collects the [Advertising ID](https://developer.android.com/google/play-services/id.html) provided by Play Services. Make sure the Play Services Ads library is included as a dependency for your application. This is the ID that should be used for advertising purposes. This value is set to `context.device.advertisingId`.

Segment also collects the [Android ID](http://developer.android.com/reference/android/provider/Settings.Secure.html#ANDROID_ID) as `context.device.id`. Some destinations rely on this field being the Android ID, so double check the destinations' vendor documentation if you choose to override the default value.
Segment also generates an unique ID by using the [DRM API](https://source.android.com/devices/drm) as `context.device.id`. Some destinations rely on this field being the Android ID, so double check the destinations' vendor documentation. If you choose to override the default value, make sure the identifier you chose complies with Google's [User Data Policy](https://support.google.com/googleplay/android-developer/answer/10144311).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️ the writeup

Co-authored-by: stayseesong <[email protected]>
@stayseesong stayseesong merged commit eb48405 into develop Jan 12, 2022
@stayseesong stayseesong deleted the wenxi/address-android-user-data-violation branch January 12, 2022 17:50
@github-actions
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants