Closed Bug 887370 Opened 11 years ago Closed 10 years ago

Add privacy policy generator text/links to submission privacy policy section

Categories

(Marketplace Graveyard :: Developer Pages, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1055790

People

(Reporter: dbuchner, Unassigned)

Details

(Whiteboard: [repoman][contribute])

Attachments

(2 files)

Attached image Mock for implementation
Please modify the text to reflect what is show in the mock, and add the links to the following privacy policy generators: Iubenda - https://www.iubenda.com/en/mobile, PrivacyChoice - http://privacychoice.org/policymaker
It looks like those sites have a narrow set of languages they offer.  Are you only wanting to show those links in English?
Talked to dbuc.  He is designing a new landing page with legal and will update this bug when he has a place for us to link to.
Assignee: nobody → dbuchner
Priority: -- → P3
(In reply to Wil Clouser [:clouserw] from comment #2)
> Talked to dbuc.  He is designing a new landing page with legal and will
> update this bug when he has a place for us to link to.

Here's the content legal would like us to go with: https://docs.google.com/file/d/1AmZNEuU9Zxuhg0aO3wxffW6oE-UGBRCdZGQ9cUS6sJHXmCd0FuTIImfHnzXZ/edit?usp=sharing

They've decide we can just show this as a modal that is shown in the context of the privacy policy section in the submission flow.
(In reply to Daniel Buchner [:dbuc] from comment #3)
> They've decide we can just show this as a modal that is shown in the context
> of the privacy policy section in the submission flow.

What does this mean?
(In reply to Wil Clouser [:clouserw] from comment #4)
> (In reply to Daniel Buchner [:dbuc] from comment #3)
> > They've decide we can just show this as a modal that is shown in the context
> > of the privacy policy section in the submission flow.
> 
> What does this mean?

When the user clicks the links, as show in the mockup, show the content provided in a modal. The content will live in the Marketplace, not on Mozilla.org (the legal team couldn't get that larger page ready in time)
Thanks.  Is there a time constraint on this bug I don't know about?

Squeezing this into a modal is more work for everyone (engineering, QA, L10n [twice], etc.).  The content you have here is documentation so it seems like it should go with all our other documentation on the devhub and we should just link to that and avoid the modal altogether.  Is the landing page you're talking about something you're trying to get in the devhub w/ Fred and is that blocked on something?
(In reply to Wil Clouser [:clouserw] from comment #6)
> Thanks.  Is there a time constraint on this bug I don't know about?
> 
> Squeezing this into a modal is more work for everyone (engineering, QA, L10n
> [twice], etc.).  The content you have here is documentation so it seems like
> it should go with all our other documentation on the devhub and we should
> just link to that and avoid the modal altogether.  Is the landing page
> you're talking about something you're trying to get in the devhub w/ Fred
> and is that blocked on something?

Legal is working on a larger privacy policy solution - but for now, they gave us this content to help developers in the submission flow who need privacy policy info/generators. I guess we can put this on DevHub, but I was thinking a modal would be a easier/better temporary solution (if the page gets index on Dev Hub, we have to maintain a link/redirect - removing a modal that sits behind an auth flow presents no such issues)
Temporary things tend to be pretty permanent around here and it's a pretty big engineering difference.  Fred - do you have a place on the devhub where this content would go?
Attached image privacyTooltip.jpg
I agree with Wil that temporary things tend to stick around a long time, and I also agree with Dan that we don't want to rip people out of the flow to read documentation. I'd like to suggest the following "solution" for this pending all the other projects that are in flux around the submission flow and devhub, including another usability test we're prepping to run. If this solution needs to be tweaked in the future, we'll get more direction from the future usability tests because the Privacy Policy stuff tends to steal the show even when we're not testing for it.

I'll take the content legal has provided in the PDF linked above and add it as a page to MDN under the apps section. This is going to further our efforts of migrating dev hub content to MDN. In the flow we can provide a tooltip (see attached sketch) that gives users a summary of the info included in Dan's initial mock, but we'll also include a link to the MDN page that opens in a new tab, if they want to read more. That way we give them a chunk of useful data in the flow, that's out of the way and will continue to be useful, even if we come up with a better documentation solution down the line. 

Thoughts? I can work on what the box will actually say if this is the direction we want to move in.
Sounds good to me.  I'm not sure those hover boxes support links right now, but I assume it'll work.
Assignee: dbuchner → asantos
I've added the document to MDN at: https://developer.mozilla.org/en-US/docs/Web/Apps/Publishing/Privacy_Policies_for_Open_Web_Apps

I'm not sure that there's any more work on my end for this one...
This seems to be pretty easy to link to the MDN page, could be a popup or just a bit of text under the privacy policy.
Assignee: asantos → nobody
Whiteboard: [repoman][contribute]
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: