-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Add clear rewards data and clear payment data #926
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
Comments
Marking this as p3 and privacy related because currently there is no way to delete browsing history associated with rewards unless the user deletes the files on disk. if rewards is enabled, browsing history is logged to |
I think the right solution would be to extend brave://settings/clearBrowserData to include controls for Brave Rewards. For the simply view, we should add a "Brave Rewards data" item which removes all attention info created from the indicated time period. On the advanced tab, we should add a couple of items.
@mandar-brave @NejcZdovc Could someone on the Rewards team indicate whether there are any other ways that information equivalent to browsing-history might be stored? |
What is defined as "applicable time period"? Currently we store auto-contribute information based on month and year. The options available when clearing data are "last hour", "last 24 hours", "last 7 days", and "last 4 weeks". How should we handle clearing data based on what is chosen? |
@jasonrsadler Are you saying that we have no way of knowing what auto-contribute info was added in the last hour, the last 24 hours, or last 7 days? |
Correct. @NejcZdovc to confirm but I believe we are only storing the month and the year. |
@tomlowenthal that is correct we accumulate time per month and not per visit |
Sounds like we'll need to change that in order to be able to support deletion. |
Personally I would be happy if someone just added an option for "Clear Brave rewards and payment data since the beginning of time". Having time intervals can be a follow-up but I don't think it's strictly necessary (we didn't have this in b-l) |
I think we shouldn't change it. We should adjust place where we have clear like @diracdeltas said |
I think we should do both, but I'm okay with only having "from the beginning of time" as a first pass. Brave Rewards is basically another browser history repository separate from the regular browser history. People should have at least the same degree of transparency and control that they have over their regular browser history. Those time intervals are really useful tools. Let's say I open a regular tab instead of a private one, and browse for a minute before realizing my mistake. That's what "from the last hour" is for, and it's a valuable feature. I shouldn't have to blow away my entire auto-contribute list to do this. |
@tomlowenthal let's discuss the time based ask on the product meeting - worth a debate. Considering the data, unlike browsing or bookmarks, is not very usable as such it's not clear to me that a time-based approach is needed but let's open it to @rebron as well. @jasonrsadler for now, the options you have presented
are fine. However, the wallet and the wallet balance remain intact. cc @NejcZdovc |
@mkarolin @jasonrsadler @bradleyrichter @mandar-brave making sure this one is on your radar as well. #492 |
If you're going to clear auto-contribute on exit, you'd be better-off just not enabling that feature. |
Per slack convo, I think #492 uses a different tab and shouldn't have rewards included. Either let the user explicitly clear rewards, or if they want it cleared on exit, just disable. |
Per convo with @bridiver, updating requirements defined so far:
|
cc @davidtemkin and @mandar-brave |
closing as this will be implemented in #10064 |
Verified passed with
Verification passed on
Encountered #11235 Verification passed on
-Encountered #11235 |
User should be able to remove rewards data (auto contribute, donation, tipping) and remove payment data (previous payments). This should delete the data on disk.
From browser laptop

The text was updated successfully, but these errors were encountered: