search

Piwigo / Piwigo-Android

Piwigo Native Android App
GNU General Public License v3.0
140 stars 43 forks source link

Add privacy policy #62

Closed ramack closed 6 years ago

ramack commented 6 years ago

As we are handling sensitive user information - photos and user account data, we need to have a privacy policy for the app. IANAL but it seems we need to have a public web page, with the policy. It should include

How does the iOS app handle that?

Edit: Open:

Philio commented 6 years ago

You also need to include things like app permissions, 3rd party processors (e.g. if you include a library and they use user data etc) with corresponding links to their own privacy policies, etc.

If you stick with the default crash reporting for app published on Google Play then this is already in terms/policies user has already accepted to download and install your app (as previously mentioned this also provides superior user experience as doesn't require them to send an email from a private account), then you could use the 3rd party library for FOSS version.

I suspect much of GDPR (EU regulations you referred to) does not apply as no user data is actually stored by Piwigo as the user is connecting to their own server.

Might want to consider using something like https://www.iubenda.com/ for Google Play, it is reasonably priced and will save a lot of time and hassle (you'd have a privacy policy done quicker than writing your original issue here!), provides various versions (API, HTML) so you can show on web/in app.

On Sun, 21 Oct 2018 at 00:00, Raphael Mack notifications@github.com wrote:

As we are handling sensitive user information - photos and user account data, we need to have a privacy policy for the app. IANAL but it seems we need to have a public web page, with the policy. It should include

  • Who is the site/app owner?
  • what kind of data we store and record (user account data, all documents and data entered) and for which purpose
  • that we pass this data to the site the user has entered, and therefore the privacy policy of the operator of the accessed galleries need to be referred (is there one for piwigo.org/demo for example?)
  • the app itself need to show the privacy policy
  • What third parties will have access to the information? Will any third party collect data through widgets (e.g. social buttons) and integrations (e.g. facebook connect)?
  • do not forget crash reporting emails
  • What rights do users have? Can they request to see the data you have on them, can they request to rectify, erase or block their data (under European regulations most of this is mandatory)?
  • Description of process for notifying users and visitors of material changes to the privacy policy
  • Effective date of the privacy policy
  • included in the about section of the app

How does the iOS app handle that?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Piwigo/Piwigo-Android/issues/62, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOhGsOkIiKJ6TkrSEApkMRrMVRHHV5jks5um6sLgaJpZM4XyLST .

ramack commented 6 years ago

while searching I also stumbled over iubenda, but I personally am not willing to pay money to get something I finally cannot judge. Going the easy way anyhow doesn't seem the best choice here, so I tried to understand and do what is necessary.

If you or @plegall is willing to pay that or has any lawyer at hand, feel free to propose improvements - up to a complete rewrite.

Philio commented 6 years ago

Yep it's down to Piwigo team to decide if they want to pay someone or for a service.

I use Iubenda with 2 of my businesses and a handful of apps now. It's cheap and quick. You can't publish without a privacy policy and I think any other method is going to certainly cost time if not also money.

On Sun, 21 Oct 2018, 9:45 pm Raphael Mack, notifications@github.com wrote:

while searching I also stumbled over iubenda, but I personally am not willing to pay money to get something I finally cannot judge. Going the easy way anyhow doesn't seem the best choice here, so I tried to understand and do what is necessary.

If you or @plegall https://github.com/plegall is willing to pay that or has any lawyer at hand, feel free to propose improvements - up to a complete rewrite.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Piwigo/Piwigo-Android/issues/62#issuecomment-431702538, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOhGprCgbn4yi8EZmpKSqK_1SPTZuMDks5unNz5gaJpZM4XyLST .

ramack commented 6 years ago

@EddyLB @plegall what do you think: does it make sense to also have a copy of the Privacy-Policy.md in the Android repository? This would then beside (piwigo.org website, the Mobile git repo, the resources of the iOS app and the resources of the Android app) be the 5th storage location... Is that worth anything?

EddyLB commented 6 years ago

Hi @ramack , I agree with you. We should not multiply the copies but share one. We can leave the Privacy-Policy.md file where it is but could also put it in a git submodule and share it (including translations — German, French and Swedish are now available). That way, we would be informed of updates and implement them independently whenever possible. This submodule could eventually be used for sharing other things in the future. @plegall , what are your thoughts?

ramack commented 6 years ago

for translations I think we cannot really share it, because the format is different. We could do that only if we'd have the complete file and the translations also as files as resources. But I will do the same split and crowdin will simply suggest the exact match from the translation memory :-)

Having a submodule for this file doesn't seem too helpful. If we don't see a strong argument I would just link the Privacy_Policy.md in the Piwigo-Mobile repository where I need it (and this is basically the README.md)