Skip to content

Commit 15e4cc6

Browse files
authored
add notes for complying user data policy in 4.10.1
1 parent a2362a9 commit 15e4cc6

File tree

1 file changed

+3
-0
lines changed
  • src/connections/sources/catalog/libraries/mobile/android

1 file changed

+3
-0
lines changed

src/connections/sources/catalog/libraries/mobile/android/index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,9 @@ The Segment SDK also collects the [Advertising ID](https://developer.android.com
2626

2727
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.
2828

29+
> warning ""
30+
> **Note:** From `4.10.1`, Segment no longer collects the `Android ID` to comply with Google's [User Data Policy](https://support.google.com/googleplay/android-developer/answer/10144311). Instead, `context.device.id` by default is generated by [DRM API](https://source.android.com/devices/drm). If the destination' vendor requires `Android ID` as the identifier, you will have to override this field manually. See [Best practices for unique identifiers]( https://developer.android.com/training/articles/user-data-ids) for more infomation.
31+
2932
## API call queuing in Analytics-Android
3033

3134
The Analytics-Android library queues API calls and uploads them in batches. This limits the number of network calls made, and helps save battery on the user's device.

0 commit comments

Comments
 (0)