Earlier quoted context omitted.
turns out. the testicle cup referrer is still active.
Odd, I didn't get it when I clicked on that link
Perhaps your browser doesn’t send the ‘Referer’[sic] header?
XScreenSaver is available on Android. Google requires a privacy policy
51–60 of 67 posts
Re: XScreenSaver is available on Android. Google requires a privacy policy
#52I had to rewrite my Google privacy policy at least 4 times before they accepted it. This is the current accepted one: https://victorribeiro.com/privacy_policy.html (i copied from somewhere else and changed it). This is the one they rejected: https://victorribeiro.com/privacy_policy.txt
Cool homepage, but the Qubes game doesn't load :(
I'm loading it from itch.io and apparently they always break something.
Next free time i got I'll load the game from my own server. Sorry about that. You can play it on Android for free if you want
Re: XScreenSaver is available on Android. Google requires a privacy policy
#53Dozens of innocuous-seeming apps collect private data. I wish the world wasn't filled with bad actors, but it is. So having a basic privacy policy even for this is annoying, but the answer to "It's a screen saver, why in the world do I need this?" is "because bad actors do bad stuff so everyone suffers."
> Dozens of innocuous-seeming apps collect private data
Like Google Play, Google Chrome, Google Photos, Google Phone, Google Contacts and so on and so forth.
This is a very perverse thing from Google.
Re: XScreenSaver is available on Android. Google requires a privacy policy
#54I had to rewrite my Google privacy policy at least 4 times before they accepted it. This is the current accepted one: https://victorribeiro.com/privacy_policy.html (i copied from somewhere else and changed it). This is the one they rejected: https://victorribeiro.com/privacy_policy.txt
That apostrophe in the first sentence doesn't belong. Apostrophe rules are impossible even for natives, but I thought you might like to know.
...of its user?
I'll update ASAP.
Re: XScreenSaver is available on Android. Google requires a privacy policy
#55Earlier quoted context omitted.
I appreciate that the version they indirectly encouraged you to use by rejecting the other one is much more clear about how you not only don't store anything, but don't collect anything. For the pedanticists here which might argue you can't collect anything without storing it, I suspect there's a lot of wiggle room there (even if only in the developers mind and not legally), and the additional information is useful t…
It's cute, but: it's a lie . Data is stored. We (privacy advocates) won, there's legislation now, this stuff is real, The Man cares. You can't handwave, saying you don't "store" or "collect", or whatever verb you like that, to you, means "we don't do anything bad" -- when you're in that territory, ex. Google's privacy policy becomes "we don't sell your data" --- can you imagine? There's precious few applications that…
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?
Re: XScreenSaver is available on Android. Google requires a privacy policy
#56What I find ironic is that his privacy policy probably stores more data than the app. (there must be logs, or at least ephemeral connection tables on the webserver)
related, I think privacy policies should be local, on-device. Not a pointer to possibly changing data. Not requiring a network connection (and possible identification).
Re: XScreenSaver is available on Android. Google requires a privacy policy
#57Earlier quoted context omitted.
It's cute, but: it's a lie . Data is stored. We (privacy advocates) won, there's legislation now, this stuff is real, The Man cares. You can't handwave, saying you don't "store" or "collect", or whatever verb you like that, to you, means "we don't do anything bad" -- when you're in that territory, ex. Google's privacy policy becomes "we don't sell your data" --- can you imagine? There's precious few applications that…
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.
Don't get me wrong, I don't think you're doing anything shady, I don't think you're doing it in the general terms people worry about, I very much doubt anyone will find out, or care if they did.
It's just a useful example of something that plays well in the HN comments section but not in the real world, I didn't even realize until a few months back.
These are de facto legal statements now. Every store requires them, and they're not paying a lawyer to double check them for you. You can get away with it on side project games, but it's not something you can get away with at a business.
Re: XScreenSaver is available on Android. Google requires a privacy policy
#58Earlier quoted context omitted.
You know how we always hear about basic flashlight apps that get used to run advertising click farms in the background, or Flappy Bird knockoffs that collect detailed location data and have access to your photo gallery? I'm with you on this one. In a perfect world it would be evident that a simple little app isn't doing anything nefarious, but... clearly even a screensaver app can be a front for some nasty shit. Maki…
> You know how we always hear about basic flashlight apps that get used to run advertising click farms in the background, or Flappy Bird knockoffs that collect detailed location data and have access to your photo gallery? But they would sure not be lying in their privacy policy, right?
Ha, good point. I'd actually be curious whether those apps had (bogus) privacy policies or just went without altogether.
Re: XScreenSaver is available on Android. Google requires a privacy policy
#59Remember 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, a Facebok app can't steal your data, because it'll get into trouble with us!". And then Cambridge Analytica data-mined FB users and used targetted ads on the gullible to deliver the election to Trump...
Re: XScreenSaver is available on Android. Google requires a privacy policy
#60Earlier 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.…
> It's just a useful example of something that plays well in the HN comments section but not in the real world
I take it you're referring to the earlier, short one, of "We don't store your data, period." If that's the case, I think you're saying the same thing I did in a slightly different way and emphasizing different points? I agree, there's a prevalence of people that see simple and direct and make the mistake of equating simple with useful. Something being simple can be good, but not at the expense of greatly increasing the ambiguity of what it applies to.