936682 - Deal with ToS and Privacy Policy going away from the Persona API

Status: RESOLVED WONTFIX

(Marketplace Graveyard :: General, defect, P3)

Description

[Matt Basta [:basta]]

Persona is removing ToS and PP from their API, meaning we can't have links to them in there. This bug is to make sure we have a plan for when that happens so we don't have another fire drill scrambling to get it to work. This must be approved by product, UX, and legal.

Some suggested fixes:

- Put links to those docs elsewhere
- Add popups
- Send emails instead

Comment 1

[Wil Clouser [:clouserw]]

marking productwanted.  David - I think this is on you.  If you haven't worked with legal you should CC urmika and get her input as well on what needs to be done here.

/CC lloyd for what kind of a timeline we're looking at.

Comment 2

[David Bialer [:dbialer]]

Is there any degree of control that Marketplace will have in login/signup screens for new Firefox Accounts?    This is the most appropriate time to present any terms of service and PP if a user needs an opportunity to review these documents before they register. The best option I see is a popup, though this is distinctly a pretty sad method.  I am copying Urmika and am going to request this feature for Firefox Accounts.

Comment 3

[Lloyd Hilaiel [:lloyd]]

Note: this removal would not happen before we've got firefox accounts in place.  We are not going to rip a feature out from under you.

David, the intention of ToS work for FxA right now is to develop a modular ToS so that a user can opt into a core bundle of services accessible via FxA with a single acceptance of ToS.  Conversations with Urmika are ongoing right now to figure out how to accomplish this, and at the same time have a set of ToS documents that are transparent, accurate, honest, and even (gasp) readable.

CCing Dan and Francois from persona to re-inforce.  ToS and PP are inappropriate in persona, but we're not going to rip a feature out from under you until it's no longer relevant to you.

Comment 4

[David Bialer [:dbialer]]

I can see a master Firefox Account set of agreements, and then a set of modular rider agreement so that when a particular service is activated, those agreements would be available.  These rider agreements may be included and combined with the core agreements if the Signup originates from one of the non-core services.

If the non-core service is added later, then there might be an additional agreement when that service is used for the first time - but I think we would need to figure out the way of checking or keeping track of these, updating, etc.

However as you note - I am all for the principles that you outline of transparency, honesty and readability.

Thanks.  No need for us to panic.  Sounds like this is being thought through and we'll await your direction.

Comment 5

[Lloyd Hilaiel [:lloyd]]

David: Yeah, this is exactly the way I'm thinking about this - new services can be released at any point during the B2G train cycles, such that we cannot know at train freeze time what set of ToS should be included in our core (FTU) call to action.  Rather than trying to guess and including broad language in our ToS(es), we'll simply state our terms as precisely as we can, and then have a mechanism for one-click user confirmation at first time use of new services.  We know we'll need such a mechanism anyway.

I have not yet figured out how exactly we'll track the set of services that are agreed to all at once as a logical part of FxA, but I'll include ckarlof on this thread who is taking the lead on reviewing the FxA ToS.  I'll update as we figure out more.

Comment 6

[Matt Basta [:basta]]

(In reply to Lloyd Hilaiel [:lloyd] from comment #3)
> Note: this removal would not happen before we've got firefox accounts in
> place.  We are not going to rip a feature out from under you.

Understood. This bug is to make sure we have a plan that lines up with your timeline.

Comment 7

[David Bialer [:dbialer]]

This will go away with Firefox Accounts

Comment 8

[Wil Clouser [:clouserw]]

wontfixing based on comment 7