Re:Google Exposed User Data, Feared Repercussions of Disclos...
by advisedwang on Monday October 08, 2018 @06:05PM
(#18171735)
> Access logs with no profile data logged would not compromise privacy would it?
True, but access logs without profile data would prevent you know _which_ profiles were accessed. This matches with the actual claim in the article that they would be "unable to determine which users were affected"
Re:Google Exposed User Data, Feared Repercussions of Disclos...
by mashlol on Monday October 08, 2018 @06:33PM
(#18171901)
Right, but the only "profile data" they would need to add to the logs to know, would be a user ID. Not really any private info.
Re:Google Exposed User Data, Feared Repercussions of Disclos...
by halflings on Monday October 08, 2018 @08:24PM
(#18172415)
User IDs are definitely private info, since they'd allow you to follow a user's behaviour etc.
Re:Google Exposed User Data, Feared Repercussions of Disclos...
by flukus on Monday October 08, 2018 @08:55PM
(#18172557)
"user 1234567 viewed post 89564385943"
I can see how that's private info, but would this be:
"client x viewed user 1234567's profile"
Re:Google Exposed User Data, Feared Repercussions of Disclos...
by gdfasfklshg4 on Tuesday October 09, 2018 @04:01AM
(#18174095)
If the user id can be joined with other data to give a name or similar then it is considered personally identifying in terms of GDPR.
I am not a lawyer. You should hire an appropriately qualified lawyer to review your data hygiene practices.
Re:Google Exposed User Data, Feared Repercussions of Disclos...
by saagarjha on Monday October 08, 2018 @10:02PM
(#18172807)
Sure, if user 1234567 isn’t particularly popular.
Re:Google Exposed User Data, Feared Repercussions of Disclos...
by wolco on Monday October 08, 2018 @09:52PM
(#18172775)
Neither are private info. Private in theop law sense.
Re:Google Exposed User Data, Feared Repercussions of Disclos...
by masonic on Tuesday October 09, 2018 @09:04PM
(#18181138)
The wording of this is really pushing the boundary of plausibility.
Maybe Google is running short of disk space.
Re:Google Exposed User Data, Feared Repercussions of Disclos...
by MertsA on Tuesday October 09, 2018 @10:03AM
(#18176037)
>Goog is trying to avoid using the words Data breach as they may get into hot water in EU.
As far as GDPR goes technically this breach happened right before they would have faced large repercussions from it.
Re:Google Exposed User Data, Feared Repercussions of Disclos...
by sipos on Monday October 15, 2018 @10:20AM
(#18219878)
It sounds like it came up as a result of their Project Strobe audit. I would guess they launched this project precisely because the penalties were about to get bigger and they knew they had skeletons.
The wording of this is really pushing the boundary of plausibility.
I fail to understand the logic of how this would protect privacy? Access logs with no profile data logged would not compromise privacy would it?
Can anyone confirm the timing of the google blog post? It seems the WSJ article was posted at a similar time.
This leads me to believe that the most likely reason we are hearing about this now is due to comment requests from the WSJ. WHEN Goog realised it was out they published.
Goog is trying to avoid using the words Data breach as they may get into hot water in EU.
Love how it is buried in the article.
My guess is a similar thing has been happening with android permissions. Data has been leaking through that they have just not admitted to it.