3 ms·
Are you kidding? The UDID and the phone owner's name are easily correlated. As soon as you register for an account on a game or app, you will connect UDID to
by davidu 16y ago
Are you kidding?
The UDID and the phone owner's name are easily correlated. As soon as you register for an account on a game or app, you will connect UDID to your email or first/last name. As soon as that happens, it could easily end up in Rapleaf or another system for other data brokers to get access to.
The connection just has to happen once, in one app, for all of them to benefit from it.
On the plus side, an app getting this data could auto-register you since it knows you based on your UDID as soon as you install the app, just sending you an email confirmation and a password. :-)
- gyardley 16y agoIn order to get any online data broker interested in your data, you have to tie it to their browser cookie. On iOS, this is hard, thanks to sandboxing. You pretty much have to redirect the user to the Safari browser with the UDID in the query string - which is a pretty crap experience for the user, which is why it's rarely done. Even then you've only gotten the data into the mobile browser, which is not what the data market wants to pay for right now. People still predominantly buy things through their desktop computers. I don't know if it's vanity or narcissism or what, but everyone assumes their 'data' has a lot of commercial value. It doesn't. Back when I was running an iPhone analytics startup, I looked into all of this stuff. Wasn't even worth the development work to monetize it.
- michaelbuckbee 16y agoWould you have to actually redirect them to Safari or could you do something like load a hidden webview? (not quite sure of the right terminology here) I was thinking the iOS equivalent of a webpage with a hidden iFrame.
- gyardley 16y agoCookies are sandboxed, so the cookie you write in your in-app 1x1 pixel webview can't be read by the Safari browser, making it useless. If we could cookie the user properly it's what I'd use for analytics instead of the UDID.
- rgrieselhuber 16y agoLaunch Safari to have them complete registration online?
- michaelbuckbee 16y agoThanks, that makes sense.
- davidu 16y agoWhy do you think you need safari or a browser? There are plenty of other (and easier) ways to make HTTP connections in iOS and implement account registration.
- gyardley 16y agoImplementing account registration, collecting an e-mail, and then using that e-mail as a unique ID to append data to the data broker's database -- this is possible, but rightly considered PII, so no data broker does this without user opt-in. (In this case the risk exceeds the rewards anyway, but that's another discussion.) If you're talking about setting a cookie with the data broker's user ID, which then can be read by the data broker on other websites - which is the standard way of shuffling non-PII data around in the absence of an explicit user opt-in - then this doesn't work due to iOS' application sandboxing. You can set a cookie with the data broker's user ID, but the data broker won't be able to retrieve it when the user's off elsewhere surfing the web, when it matters.
- davidu 16y agoUsing a cookie doesn't make something non-PII... Your user-agent and request details are enough for me to tie you to an existing account: https://panopticlick.eff.org/ https://panopticlick.eff.org/
- nitrogen 16y agoNice. According to the panopticlick, I'm the only one with my exact plugin details. None of the other data is even needed to identify me, though being one of the .005% of people using Firefox 3.6.13 on Ubuntu 10.10 probably helps.