Brave 1.77.101 with Chrome 135.0.7049.115
Windows 10 Home x64 22H2
I normally would configure Brave to purge all its locally cached data on its exit. However, I had to omit purging all site data on exit to get one site to work (Google Voice). The AutoPlay permission is configured to Block by default, because I don’t want sites blaring their audio at max volume just because I visit their site. When at Google Voice, I had to undo the AutoPlay block permission (i.e., to allow AutoPlay although nothing auto-plays there); else, clicking on their Play button does nothing (actually the element is disabled in their web page when AutoPlay is disabled). This change of permission is stored as site data.
I still want Brave to purge all locally cached data on exit, including any site permissions I might’ve changed during a web session. However, to get some sites to work means having to undo the default permissions applied to them. Okay, but on exit then those exceptions for site permissions are lost, because ALL site data gets purged on exit.
I changed a site permission for voice.google.com for AutoPlay, but to keep it requires I not purge ALL site data on exit of Brave. I’d like to purge all site data on exit except for those I granted a change of permission and added as an exception to the purge. I did not find an exclusion or whitelist list to the purge-on-exit option which would let me keep the site permissions that I granted. I should not have to keep all site permissions just to keep one.
The same for cookies. On exit, and if cookies are selected to purge-on-exit, ALL cookies get purged. There is no whitelist of which cookies to keep on a purge-on-exit. I want to purge all cookies on exit except some whitelisted ones.
Purge-on-exit (delete browsing history on exit) only lets me delete everything within a category, or delete nothing in a category. No middle ground to delete everything EXCEPT what is whitelisted. Any cure for this bipolar disorder?
This gets regularly asked - and rightly so as not clear. @Matches or somebody should be able to give you the specifics but it is along the lines of you need to set the Shields settings for that specific site to not forget you when you close the site.
When I look in Settings-Privacy and Security-Site and Shields settings-View permissions and data stored across sites I have a number of sites where my settings are maintained.
Hope this helps but if I am barking up the wrong tree then apologies.
The “Forget me when I close this site” option is not described nor documented, and it is a clumsy and non-intuitive method to add exceptions to the purge-on-exit operation. I’m not sure Brave even prompts you when you close a site (nor just what “close” means) to alert you to choose to add an exception, or not, or even make you aware that you are adding an exception to the purge-on-exit operation.
I went to Brave issues, and searched on “Forget me” to find:
That asks why users cannot see the list of exceptions they created when the “Forget me” option is enabled, and they chose to not be forgotten for a particular site. Geez, create hidden exceptions. Just stupid.
With “Forget me” off, enabling per-site is clutzy. You click the Shields toolbar icon, and elect to add the site to an override list (which you cannot view). With “Forget me” on, disabling is a per-site operation by clicking on the Shields toolbar icon, but you can’t see the exceptions list for what choices you’ve made. With “Forget me” on, the only way to remove a site that you previously excepted is to revisit that same site to then click on the Shields toolbar button to unforget that site.
These override and exception lists are stored somewhere for Brave to track them across web browser sessions, but the Brave devs decided not to expose them when they added the “Forget me” option. This just sucks. “Forget” needs to get replaced with a different “F” word.
opened a week ago which addresses the “Forget me” setting by exposing or showing an editable exception list instead of hiding it might be a duplicate of:
opened 5 years ago that suggests adding an exception list (and hopefully showing it, and it is editable) to the purge-on-exit option. Maybe the same suggested editable displayable exception list could be used for both.