This is more general compliance, less product req. Going to descope this from prod MVP for now, John H will work with legal on this. 

The 14Mar discussion with Product noted potential requirements/flow:

• Display agree/disagree only on the first login in community galaxy with social auth, before being allowed to proceed with account creation
• Display this as a new screen with TBD text
• Require the user to click accept in order to proceed with account creation, if they do not click accept, do not create account
• If user already has an account, this screen will not be displayed

Given this current set of requirements, if we can have this check before account is created, we may not need a backend flag stored in the database.

Need to see how this could interact with user creation outside community.