shameless plug for my app true weather:
https://play.google.com/store/apps/details?id=net.conceptual...
Privacy policies don't need to be complicated:
"TrueWeather does not collect any personal information."
https://play.google.com/store/apps/details?id=net.conceptual...
Privacy policies don't need to be complicated:
"TrueWeather does not collect any personal information."
I view my dedicated home IP as personal, if not all that private, information. Does minimal logging actually require storing personal information? Is there a common, or legal definition of what personal information is?
I'm all for simple policies, but I would also rather they be accurate, and I would hate to see people who are trying to do good by having a simple policy like that end up in trouble because the law doesn't quite agree.
and yes, there is a legal definition of personal information. since im based in canada, that would be as defined by PIPEDA (the Personal Information Protection and Electronic Documents Act)
!!! You're the best. Thank you! Unfortunately not US/Can, otherwise I'd immediately switch to your app just because of that (I'd buy it anyway if it was paid, just to show support).
I wish more devs would have this approach. You don't need telemetry to create good software. You don't need to monitor what the user does with your application, when and how. You don't need to log everything, or listen in on conversations with third-party APIs. You don't have to outsource testing and QA onto your users.
Sentry does a really nice job of restricting the data which is stored, for how long, and scrubbing things which might have been included by mistake. I was just setting up an on-premise server yesterday and it’s pretty easy to configure it server-wide in a privacy-preserving manner.
edit: just realized this comes across like bikeshedding. I do applaud and like your approach to privacy and its simplicity. It wouldn't decrease the appeal of your app at all to mention that you query the environment canada data, which is probably a public service and will not missue the data itself).
I wasn't trying to insinuate your policy was wrong (I actually assumed it was likely correct, a weather app doesn't generally require much in the way of server support from anything except the weather service), but that "Privacy policies don't need to be complicated" might be a bit optimistic for a lot of apps.