Page MenuHomePhabricator

Add warning for user on /authorize about privacy policy
Open, HighPublic

Description

Our privacy policy allows us to share a user's information when they have given consent.

Give the user explicit notice when they authorize the connected app that we may send information to the connected app about the user, and that the data collected is governed by the connected app's privacy policy, not our's.

Michelle suggested, "Allowing Hello World to do these actions means that some of your information may be sent to Hello World and will be used according to their privacy policy."

There is already a message for this iirc, text just needs to be added.


Version: unspecified
Severity: normal

Details

Reference
bz62687

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 2:53 AM
bzimport set Reference to bz62687.
bzimport added a subscriber: Unknown Object (MLST).
csteipp created this task.Mar 15 2014, 1:39 AM

@csteipp my solution to T59457 actually means we can't add this to an existing message, because I'm using the message(s) in core. In that case, is this just a duplicate of T64686?

@csteipp my solution to T59457 actually means we can't add this to an existing message, because I'm using the message(s) in core. In that case, is this just a duplicate of T64686?

@MarkTraceur, not quite. Michelle's request was that we add another message into the dialog. We already add mwoauth-form-legal to the authorize form, it's just a blank message right now. Adding the app's name as a parameter and defining the message to Michelle's suggested wording would be the minimum implementation. It would be great to get UX input.

Defining the message as is gives,

UX input appreciated.

MarkTraceur set Security to None.

Change 303328 had a related patch set uploaded (by Dpatrick):
Note coverage under consumer privacy policy

https://gerrit.wikimedia.org/r/303328

dpatrick added a comment.EditedAug 6 2016, 12:43 AM

So, now the problem is that we don't specifically collect a link to the consumer's privacy policy. And so, the link that appears just below this new message is confusing, and we don't have data to reconcile that (re. T64686).

Tgr added a subscriber: Tgr.Aug 8 2016, 9:25 PM

Adding policy links would be a simple change, the problematic part is, what to do with existing consumers? That's T59631: OAuth developers should be able to change some of the parameters they registered an application with instead of having to submit a new application and that does not seem simple.

Tgr added a comment.Aug 17 2016, 3:38 AM
In T64687#2535018, @Tgr wrote:

Adding policy links would be a simple change, the problematic part is, what to do with existing consumers? That's T59631: OAuth developers should be able to change some of the parameters they registered an application with instead of having to submit a new application and that does not seem simple.

I guess we could just special-case adding a privacy policy where one did not exist before.

Aklapper removed dpatrick as the assignee of this task.Feb 19 2018, 11:20 AM