Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

XScreenSaver is available on Android. Google requires a privacy policy

chaos.social

Post reply on HN
Print view View original

61–67 of 67 posts

Re: XScreenSaver is available on Android. Google requires a privacy policy

#61

Post by atum47 »

refulgentis wrote: post #57
atum47 wrote: post #55

Earlier quoted context omitted.

I honestly packed all the code inside of a APK and distribute it via Google app store. I make no request to get out send any data. How am I collecting or storing any data?

> no request to get out send any data Correct: that means you are not relaying data to a network, or retrieving data from a network. Your claim was "We don't store your data, period." I can't know for sure, but for the vast majority of applications, data is stored somewhere, be it on the device, or on the server. High scores? Game state? Levels completed? You sure you're not storing data? That's why it was rejected.…

Not on my device or my server. On yours? Sure, you've downloaded the app, it stores both code and assets, also highscores.

Re: XScreenSaver is available on Android. Google requires a privacy policy

#62

Post by Marsymars »

GuB-42 wrote: post #33
Marsymars wrote: post #31

Earlier quoted context omitted.

Right, but if an app agrees not to exfiltrate data via the app submission process, and then proceeds to do so, it's basically the same as the app having a privacy policy and then not adhering to it. If an explicit "privacy policy" is required (for legal reasons or w/e), when an app submits "no data to be exfiltrated", the app store could say "here is the privacy policy you're agreeing to follow, no further action req…

I don't know the Play Store app submission process, but if it isn't the case, it would be nice to have a bunch of pre-written privacy policies for common cases. Ideally hosted by Google, vetted by lawyers and explained in simple terms to both users and developers. And "we don't store any data" would be an obvious one, as well as those that use Google services exclusively (ads, ...). That would make it easier for ever…

Agreed, that would be good. Someone at Apple/Google should take a note.

Re: XScreenSaver is available on Android. Google requires a privacy policy

#63

Post by SpaghettiCthulu »

netsharc wrote: post #59
izacus wrote: post #20

Remember when "just a flashlight" apps outright stole user data? That's why.

I had the chance to develop on BlackBerry in the early 00's, and they prompted their user if the app wants to access things like the user's calendar or address book. If the user denied it, an exception would be thrown and a good app would be able to deal with it... And then iPhone came along and Apple said "Trust us, our store review policy will save you.". And Android did the same. And Zuck said "Your data is safe,…

Part of the problem is that many users will be just click "Yes" without thinking.

The other part of the problem is that the apps receive an exception or equivalent at all. IMO, they should receive fake access that returns either no items or garbage data as applicable.

Re: XScreenSaver is available on Android. Google requires a privacy policy

#64

Post by metadat »

kragen wrote: post #48
tonyhart7 wrote: post #14

Earlier quoted context omitted.

Anything that connect internet that means you send IP addresses over to make request You think only website do this ???

you could send it to someone who you already trust, like google, instead of someone you are trying to decide on whether to trust or not

Do we really trust google? Why? Lol, as an entity it's proven it only cares about itself and making moar $$$$$$.

Re: XScreenSaver is available on Android. Google requires a privacy policy

#65

Post by kccqzy »

Marsymars wrote: post #22
kccqzy wrote: post #6

I don't get this complaint. Of course I expect to find a privacy policy. And of course you can choose to write it in an unconventional way. Saying no data sent out of your device is a privacy policy. Saying it in a fancy way that contrasts between this app and something else is also a privacy policy.

> Of course I expect to find a privacy policy. If the app store allowed you to specific in app metadata that no data leaves the device, and that was enforced by device policy, I wouldn't expect a privacy policy.

"No data leaves the device" is such a vague policy that it means nothing.

At a minimum, your app displays some UI containing its data. Bravo, information from the app now leaves the device through the photons emitted by the screen. Same for speakers.

Now consider the clipboard. The user copies some text from your app and pastes it into an online forum. Bravo, information from the app now leaves the device through the clipboard.

Re: XScreenSaver is available on Android. Google requires a privacy policy

#66

Post by kragen »

metadat wrote: post #64
kragen wrote: post #48

Earlier quoted context omitted.

you could send it to someone who you already trust, like google, instead of someone you are trying to decide on whether to trust or not

Do we really trust google? Why? Lol, as an entity it's proven it only cares about itself and making moar $$$$$$.

the context of this discussion is people installing apps from the google play store (something i do not do myself), so, yes, those people do trust google and indeed have already informed it in a personally identifiable way that they are pondering installing the app. having google provide them with the privacy policy for the app would be a pure improvement

Re: XScreenSaver is available on Android. Google requires a privacy policy

#67

Post by hakfoo »

SpaghettiCthulu wrote: post #63
netsharc wrote: post #59

Earlier quoted context omitted.

I had the chance to develop on BlackBerry in the early 00's, and they prompted their user if the app wants to access things like the user's calendar or address book. If the user denied it, an exception would be thrown and a good app would be able to deal with it... And then iPhone came along and Apple said "Trust us, our store review policy will save you.". And Android did the same. And Zuck said "Your data is safe,…

Part of the problem is that many users will be just click "Yes" without thinking. The other part of the problem is that the apps receive an exception or equivalent at all. IMO, they should receive fake access that returns either no items or garbage data as applicable.

This always seemed the right answer.

Prompt the user "App Foo wants to use calendar/pictures/location" and then you have options like "Allow", "Deny", "Allow with filtered data" (i. e. select just a few photos out of the gallery), or "Allow with bogus data" (generated gibberish that goes away after use)

Post reply on HN