Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

Leaking device model to Google play #137

Closed
miraxi opened this issue Jul 4, 2013 · 3 comments
Closed

Leaking device model to Google play #137

miraxi opened this issue Jul 4, 2013 · 3 comments

Comments

@miraxi
Copy link

miraxi commented Jul 4, 2013

How to reproduce:

  • install XPrivacy on device A
  • configure (under "settings") the IMEI of another device B (of a different model)
  • restrict "identification (device)" for every application (including Google play, etc.)
  • register a new Google play account from device A
  • sign into Google play with the newly created account and take a look at the registered devices section
  • the listed device model corresponds to device A and not as expected to device B

Question: Is the "true" IMEI leaked to Google play or does Google play use other means to identify the device model?

@M66B
Copy link
Owner

M66B commented Jul 4, 2013

The device model isn't restricted, so this is to be expected.
http://developer.android.com/reference/android/os/Build.html
I don't really consider this as privacy sensitive data, like names, phone numbers, etc.

@miraxi
Copy link
Author

miraxi commented Jul 4, 2013

Hello M66B,

Thank you very much for the quick reply and above all for the awesome XPrivacy.

Another observation I made is that Google play identifies a device using the GSF ID (as opposed to Settings.Secure.ANDROID_ID, cf. http://forum.xda-developers.com/showthread.php?t=1860405). If I am right, XPrivacy does not offer a possibility to restrict the GSF ID (I am not sure whether this is related to #134).

Do you have any plans to restrict the GSF ID as well?

Regards,
miraxi

@M66B
Copy link
Owner

M66B commented Jul 4, 2013

@M66B M66B closed this as completed Jul 4, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants