I've just submitted a new Android release (3.12.5) including the necessary link to the privacy policy.

The App was delisted by Google because…

Issue: Violation of Usage of Android Advertising ID policy and section 4.8 of the Developer Distribution Agreement

Google Play requires developers to provide a valid privacy policy when the app requests or handles sensitive user or device information. We’ve identified that your app collects and transmits the Android advertising identifier, which is subject to a privacy policy requirement. If your app collects the Android advertising ID, you must provide a valid privacy policy in both the designated field in the Play Console, and from within the app.


We do not collect or use the Android advertising ID, but the App uses Google Play services for maps and push messaging, which in turn seem to silently use the unique advertising ID to identify and track the user. So we now cover Google's hidden privacy violations with our public privacy policy, which doesn't feel right. But it's either that or remove Google maps & push messaging from the App.

Regards,
Michael


Am 28.09.18 um 08:34 schrieb Mark Webb-Johnson:
Yep. That is comforting. I’ve made that change.

Regards, Mark.

On 28 Sep 2018, at 2:31 PM, Michael Balzer <dexter@expeedo.de> wrote:

Mark,

seems to be covering more than we actually need, but better that way.

To make it less scaring, how about beginning with…

Open Vehicles is a community project, with smartphone apps, vehicle modules, websites and vehicle communication services provided as public services to our users.

Using these public services is completely optional. The Open Vehicles software is available as Open Source, allowing any user to review and modify the source code and build, host, use and provide private or customized versions.

Your privacy is important to us. […]

Regards,
Michael


Am 26.09.18 um 03:52 schrieb Mark Webb-Johnson:

We are way overdue from having a privacy policy. Given what we do, it is tough. We are a community project not charging for services, and need to protect both our user’s data and ourselves.

I’ve created a draft policy, based on an open source template. It is available here:


Reading those policy documents is always scary. If anyone has any suggestions to make it less so, while still providing the necessary protections, please help!

Regards, Mark.


_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev


-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev


_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev


-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26