-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewards opt in needs a ToS link as part of opt in #3124
Labels
feature/rewards
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
release-notes/include
Milestone
Comments
mandar-brave
added
feature/rewards
priority/P2
A bad problem. We might uplift this to the next planned release.
labels
Jan 28, 2019
@mandar-brave what is the use case for the first screen? |
NejcZdovc
added
priority/P3
The next thing for us to work on. It'll ride the trains.
and removed
priority/P2
A bad problem. We might uplift this to the next planned release.
labels
Mar 7, 2019
9 tasks
19 tasks
ryanml
added a commit
to brave/brave-core
that referenced
this issue
Apr 2, 2019
ryanml
added a commit
to brave/brave-core
that referenced
this issue
Apr 8, 2019
3 tasks
pilgrim-brave
pushed a commit
to brave/brave-core
that referenced
this issue
Apr 16, 2019
This was referenced May 10, 2019
Verified passed with:
Verification passed on
Verification passed on
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature/rewards
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
release-notes/include
When a new user opts in to Brave Rewards, the ToS should be made available as part of the opt in process.
@jenn-rhim please add mock for how the ToS and needed text should be place at opt in.
@NejcZdovc - part of the Brave Rewards spec review flow.
The text was updated successfully, but these errors were encountered: