4 ms·
> No one can say for certain how, and when they delete the data. Even the person from the privacy team said as much. You and I read very different comments. No
by joshuamorton 8y ago
> No one can say for certain how, and when they delete the data. Even the person from the privacy team said as much.
You and I read very different comments. Not being able to tell you, a random HN commented, the exact procedure by which a specific piece of data's lifetime is managed is different than not being able to, in the abstract, describe, monitor, and alert on the intended lifecycle of a piece of data.
> I wonder how much of this is related to GDPR,
Probably not at all: Google was already GDPR compliant (it was already possible to manually delete your data), this goes beyond the GDPR mandate, and allows you to set a ttl on your data, essentially.
It's becoming more apparent to me that you, either intentionally or not, aren't clear on what the status quo was, or what this change changed. To be clear, deleting your location data has always been possible (or at least, has been possible for a long time). There's a UI for it. This is, in addition to being able to manually delete data, have Google automatically delete any data older than a certain time.
- dmitriid 8y ago> It's becoming more apparent to me that you, either intentionally or not, aren't clear on what the status quo was, or what this change changed. It's becoming more apparent that the whole conversation kinda derailed from "privacy engineering team" which engineers privacy (whatever that means at Google) does a shitty job to "we should celebrate them for doing just the minimum amount of work for something that has already been possible, if spread across many UIs". Literally despite multiple complaints about how Google handles data with regards to location and activity tracking (original complaint: https://news.ycombinator.com/item?id=19809168 https://news.ycombinator.com/item?id=19809168, summary: https://news.ycombinator.com/item?id=19812861 https://news.ycombinator.com/item?id=19812861), the "privacy engineering team" answers "just disable it": https://news.ycombinator.com/item?id=19810083 https://news.ycombinator.com/item?id=19810083 This is what I'm talking about, and this is the status quo that was, is, and is going to be in the future.
- joshuamorton 8y ago> derailed from "privacy engineering team" which engineers privacy (whatever that means at Google) does a shitty job to Actually no, it was you who derailed an otherwise unrelated conversation to that topic. > we should celebrate them for doing just the minimum amount of work for something that has already been possible, if spread across many UIs The "minumum amount of work possible" was doing nothing. Let's isolate this: is this change a good thing, or a bad thing, in your opinion? That is, all else equal, would you prefer Google provide this specific privacy control, or not? If not, why not? What is bad about this feature? If yes, why are you attacking the very people implementing features that you think are good? Isn't it better to support the people doing work you support?
- dmitriid 8y agoI’ve already answered that here: https://news.ycombinator.com/item?id=19811270 https://news.ycombinator.com/item?id=19811270