Skip to content
This repository has been archived by the owner on May 10, 2019. It is now read-only.

Need to present and have user agree to TOS & privacy policy #37

Closed
vthunder opened this issue Jun 27, 2011 · 8 comments
Closed

Need to present and have user agree to TOS & privacy policy #37

vthunder opened this issue Jun 27, 2011 · 8 comments

Comments

@vthunder
Copy link

Sad, but true.

@lloyd
Copy link
Contributor

lloyd commented Jun 27, 2011

need specifics. are links at the bottom of the dialog and a default unchecked box sufficient? are links the same as on all other moz sites?

@ghost ghost assigned benadida Sep 30, 2011
@jbonacci
Copy link
Contributor

Would this be considered "fixed" now that we have the updated TOS and Privacy pages in the new UI?

@jbonacci
Copy link
Contributor

At this point, we have two pages that the user can read, but there is nothing to check off or sign.
Is that still required?

@benadida
Copy link
Contributor

Yes, this is required. We should add this at least at the time that users set a password.

@skinny97214 ? I know this is going to make you sad, but we don't have a choice.

@skinny97214
Copy link

Proposal: sites can choose between three options.

  1. no checkbox
  2. checkbox prechecked
  3. checkbox unchecked

@benadida
Copy link
Contributor

@skinny97214 sorry I'm talking about something else. This is our TOS & privacy policy, not the site's. So when we prompt for a user password to set up their BrowserID account, we need them to affirmatively opt into our ToS and Privacy Policy. Sadly, we don't have the choice of (1) or (2). It has to be (3).

@lloyd
Copy link
Contributor

lloyd commented Feb 28, 2012

dup of issue #841

@lloyd lloyd closed this as completed Feb 28, 2012
@jbonacci
Copy link
Contributor

Yep. Verifying as a dupe.

rfk added a commit that referenced this issue May 9, 2016
bump awsbox to compensate for npm mess and relative-dates module
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants