KDE PIM Privacy Policy

[Ianseeks]

On Thursday, 7 March 2019 11:51:23 GMT Daniel Vrátil wrote:
> Hi all,
> 
> Google has effectively blocked new user logins for the API keys that we use to 
> authenticate again their services. This can be worked around on SMTP/IMAP by 
> using regular authentication methods, but cannot be worked around for services 
> that use the REST API like Google Calendar. Right now all new users just see 
> "App is blocked" instead of login page [0] (see BKO#404990)
> 
> In order to get the keys unblocked we need to have the application* "verified" 
> by Google which among other things requires us providing a link to a privacy 
> policy. Since the official KDE Privacy Policy is still being worked on, I've 
> thrown together a super-simple privacy policy:
> 
> 	https://community.kde.org/KDE_PIM/Privacy_Policy

Why copy Google's Privacy_Policy as a temporary measure and see if they pass their own policy?   :)

> It's short, but then again, we are not doing anything shady, so just saying 
> "we good" should be enough for now.
> 
> First, I'm hereby letting you know we now actually have a privacy policy :-) 
> Second, feel free to (and please do) improve it. I've taken inspiration from 
> privacy policies of other projects around the internet, but I'm not overly 
> creative in this regard and my lawyer-speak sucks.
> 
> Cheers,
> Dan
> 
> * not "application" as in our software, but application as in the account in 
> Google Cloud that the API keys are part of
> 
> [0] https://bugsfiles.kde.org/attachment.cgi?id=118581
> 


-- 
opensuse:tumbleweed:20190305
Qt: 5.12.0 KDE Frameworks: 5.55.0 - KDE Plasma:  5.15.2 - kwin 5.15.2
kmail2 5.10.2 - akonadiserver 5.10.2 - Kernel:  4.20.13-1-default  - xf86-video-nouveau:  1.0.15