11–20 of 67 posts
The point is that it is obvious to you. It's not obvious to your users. That's what the privacy policy helps with. An app of any kind can be doing more than you may think.
There are many things to complain about with Google. This isn't one of them.
I 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
Earlier quoted context omitted.
What is the value of the developer potentially knowing your IP address? They receive (1) a signal you were potentially interested and (2) can use GeoIP to learn your approximate location. This doesn't seem particularly valuable or egregious, what am I missing?
Until after you read the privacy policy, you can't know what they intend to do with that information. As a trivial example, they might be handing IP address information to third-parties--hell: the website itself might be hosted by a third-party (or might be behind a CDN provided by a third-party) or use frameworks/fonts hosted by third-parties, even if it isn't as ostentatious as "the website this policy is hosted on…
Earlier quoted context omitted.
What is the value of the developer potentially knowing your IP address? They receive (1) a signal you were potentially interested and (2) can use GeoIP to learn your approximate location. This doesn't seem particularly valuable or egregious, what am I missing?
Until after you read the privacy policy, you can't know what they intend to do with that information. As a trivial example, they might be handing IP address information to third-parties--hell: the website itself might be hosted by a third-party (or might be behind a CDN provided by a third-party) or use frameworks/fonts hosted by third-parties, even if it isn't as ostentatious as "the website this policy is hosted on…
You think only website do this ???
I had a small role in helping Jamie port XScreenSaver to Android. It was fun working with someone whose writings I have been reading for thirty years or so, and I learned a lot from him (like the difference between HAVE and USE in C, or how to architect and run a project). Patches are always welcome! Jamie (and/or other helpers) ported things like X11/Xlib to OpenGL, and then OpenGL to OpenGLES for iOS and Android. J…
> For a screen saver. A privacy policy. For a screen saver. The point is that it is obvious to you. It's not obvious to your users. That's what the privacy policy helps with. An app of any kind can be doing more than you may think. There are many things to complain about with Google. This isn't one of them.
Oh, and the part about location data is blatantly untrue, because one of the options on mapscroller is "Current City".
> For a screen saver. A privacy policy. For a screen saver. The point is that it is obvious to you. It's not obvious to your users. That's what the privacy policy helps with. An app of any kind can be doing more than you may think. There are many things to complain about with Google. This isn't one of them.
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. Making your good intentions explicit can only help!
I 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
For example, getting paid to receive and forward data, or to send it directly to a third party may be something a developer could do and thing they are complying with "we don't store your data". Technically correct, probably not legally correct, but unlikely to matter legally unless noticed and they are sued.
Much better to be explicit about things as long as it's still easily readable.