Skip to main content
7 events
when toggle format what by license comment
May 12, 2017 at 15:30 comment added Izzy I'm not aware of that, and rather deal with it "by my guts" (e.g. with Xprivacy, randomizing things like location, device IDs etc.). But what data exactly is sent in which context is beyond my knowledge. If you really want to investigate that, you'd have to "snoop" the network packets I'm afraid – unless someone had already done exactly that, and you can turn up the results. Though even that might change with new versions of the services/apps…
May 12, 2017 at 15:23 comment added Stilez Thanks - that really is clear! One last question (optional) - is there anywhere a list of exactly what data and/or tracking capability is inevitable, for each Google library function, to get a sense of "Using feature/API X, isn't possible unless one lets Google have data Y; however you can randomise the tokens or wipe them each time for at least data Z"? That would be very wonderful, but if it exists, I can't find it
May 12, 2017 at 15:19 vote accept Stilez
May 12, 2017 at 7:06 comment added Izzy See my update, hope it's clear now. Speaking of "clear": I will clear out the now redundant comments which I integrated with the answer already :)
May 12, 2017 at 7:06 history edited Izzy CC BY-SA 3.0
integrated facts from comments
May 11, 2017 at 22:06 comment added Stilez That's really helpful basics, thanks. Thinking about it, what's not clear to me (and matters) is, how much each of these just re-implements as FOSS the same Google API calls (and hence still raises the same basic issues just via different middleware), or needs a Google login, etc), and how much they do detach you from Google. I'm realistic, if you want Google notifications/email/search/voice/calendar, it's realistic that Google will datamine it en route. But there's no clear information for most of these about what's been detached from Google vs what's relayed to them, which would help loads
May 11, 2017 at 10:19 history answered Izzy CC BY-SA 3.0