Open Brave browser and return to duckduckgo to confirm that the settings have been shredded.
DEFECT SUMMARY: After a Global Clear History takes place it seems that it’s no longer possible to preserve the Never Shred setting at the site level. The duckduckgo site is used as an example but the site will continue to be shredded regardless of specifying Never Shred at the site level.
So, to be clear,
you expect Clear Data Now (or basically Manually Wiping Everything) SHOULD preserve the data because of the setting of Never Auto Shred per site (or otherwise)?
If I’m understanding you correctly, I don’t think that’s a bug, I think manually wiping everything with Clear Data Now is meant to Clear ALL Data PERIOD.
& I think this would be a Feedback/Feature Request instead… though for me personally I wouldn’t want that feature, if I want to Clear all my data, I don’t want to have to then make changes per site or otherwise.
But please correct me if I’m wrong in my interpretation and I don’t mean to be rude, disagreeable or argumentative.
Also, I am NOT a Brave employee, I’m just a fellow user wanting to help
…and clarify in this instance.
And Thank you for editing your original Topic here and deleting your duplicate Topic here.
Hi, thanks for your question I’ve reworded my defect slightly to hopefully make it clearer.
Essentially, if i perform a Global Clear History i would expect the site level Never Shred to be removed. That’s working fine.
I have the global setting Auto Shred: App Close and have specified a site to Never Shred. When i close the app the cache is cleared except for my Never Shred site. This is working fine too.
The problem is that once you perform a Global Clear History (perhaps for the first time) the browser will never let you save Never Shred at the site level.
It seems impossible to save or preserve the Never Shred at site level after you have performed a Global Clear History. It seems like a defect because it worked perfectly before the Global Clear History but changes behaviour after the Global Clear History.
I’m pretty sure Clear Data Now is working as it’s supposed to…
or as I put it: “Manually Wiping Everything”
or as YOU put it: “Global Clear History”
It’s meant to wipe everything, that’s what that function is there for.
And as I said:
If I want to Clear all my data, I don’t want to have to then make changes per site or otherwise.
And I think THAT is why it is not a defect.
If you don’t want to have all your data wiped, don’t use Clear Data Now, you’ve already got things setup manually to do so when you close the app anyway, so there’s no real reason to.
OR
If you do use Clear Data Now just do NOT include Cookies and Site Data when doing so.
I don’t use Clear History regularly. I only used it once. But since using it that once it’s now impossible to preserve Site: Never Shred.
Site: Never Shred settings worked and were preserved on App Close before i used Clear History for the first time. Since then App Close clears Site: Never Shred.
Initiating Clear History appears to break the ability to preserve Site: Never Shred.
To be clear, when you say “Clear History” or “Global Clear History” you ARE referring to:
Brave All Settings > Shields & Privacy > Clear Private Data (subheading) > Clear Data Now
correct?
And that you used that feature ONCE, and you believe that now the previous setup settings of:
Brave All Settings > Shields & Privacy > Auto Shred > App Close
ALONG WITH & MORE TO THE POINT… Any Website > Brave Shields (Lion Icon in top right) > Shred Site Data > Auto Shred > CHOICE Never
Does NOT work anymore (since you last used that Clear Data Now function)?
I assume THAT is what you are saying?
That ALL your data is regularly being WIPED at Close? AND OBVIOUSLY You WANT to keep SOME DATA per website but that’s just not happening?
(Slightly) SEPERATELY…
If that’s the case, that is NOT what I am experiencing, and actually since your last comment I went and looked in:
Brave All Settings > Shields & Privacy > Manage Website Data
And I’m actually seeing a bunch of stuff I do NOT want saved, so I’m a bit confused by that, but that’s unrelated to you and I might create my own Topic about it.
Kind of the opposite of you,
You want to keep things and it’s being wiped.
I want things wiped but they’re being kept.
(Assuming we’re on the same page now with what I wrote above the Break / Slightly Seperately).
Because of that I’m going to wipe everything (again using Clear Data Now) and start fresh and see if it starts happening as it has with you…
I’m thinking it was the upgrade to iOS 26 though.
I went from iOS 18.7.1 to iOS 26.1 and I think THAT fudged some stuff.
EDIT: Clear Data Now didn’t wipe stuff just now so I instead went into Manage Website Data and Removed All
Correct the Site: Never Shred is forgotten after App Close (with Auto-Shred set to App Close). Initially it worked correctly and was preserved on App Close. But after performing a Global Clear History THEN reinstated Site: Never Shred it is subsequently wiped on App Close.
Thanks for testing I’m on iOS26.1
Interestingly, my App Close and Clear History do wipe everything. There’s no residual data for me.
I think what happened for me because I DID notice since updating from 18.7.1 to 26.1 on Monday in brave://settings/braveSync/setup that there were TWO iPhones in Sync, and I ONLY HAVE ONE iPhone, So I THINK what happened to me, was there was a problem in transitioning Brave Sync on my phone between the Operating System upgrade, thus instead of continuing to Sync with my phone, instead CREATED another phone in the Sync Chain… and even though I’d removed the no longer syncing iPhone on I guess maybe Tuesday… my actual phone still had risidual left overs from the previous Sync… so then from when we were talking I finally figured I should actually look in Manage Website Data and sites were there but they were blank (no words saying e.g. Cache, Cookies and Local storage - just site and nothing underneath). So I manually removed the outdated syncing iPhone as I said and then as I said in previous post, clicked Removal All - even more Manually removing everything to start fresh.
I know this is somewhat unrelated to what you’ve shared but you DO also have an iPhone with your bug so I’m curious if upgrading recently is maybe more the culprit than the “Global Clear History” a.k.a. Clear Data Now …maybe check YOUR Brave Sync for more than one iPhone if you are using Brave Sync.
Also, I’d like to tag in @Mattches for comment on this (for my issue as I’ve discussed in this comment and hopefully if you don’t figure it out from my suggestion @boxer yours too of course):
I feel like I solved why sometimes people get MORE THAN ONE iPhone in their Sync Chain (when only having one device), something gets corrupted in Brave Sync during the upgrade processes from one OS (18.7.1) to another OS (26.1).
I don’t use Sync. Would really like a response to the Site: Never Shred issue though. Using DDG with default settings is annoying when i have perfectly configured DDG settings saved…
Bah, I wish I had a spare device to test this on. But I absolutely don’t want to shred my own data as a test!
@boxer let me just confirm something here. When you go back to the part of returning to DuckDuckGo and setting to Never Shred, have you ever exited out completely right away and then returned to configure the search settings? Or do you immediately change the settings and then exit out?
While one would think it shouldn’t be an issue, I’m wondering if there’s just some issue occurring with that. If I’m right, then exiting and returning should show the change to Never Shred as still existing and then any settings on DDG or whichever site would maintain.
Of course, other question is to confirm that when you return and see the site data has been shredded, is the Shields setting still the same or did it change?
@boxer I’m trying to look through issues. At first was wondering if it might be tied in with this Github issue but that speaks more about subdomains and all.
Then another one is the opposite of your issue, where things persisted. Plus it is talking about it being set for tabs being closed rather than app.
I know @User.1.000.000.000 pinged Mattches earlier. I’m also going to tag in @StephenHeaps to see if he might know anything and if perhaps they can replicate it.
Do keep in mind that it’s currently the weekend and most staff are active on the weekdays. So may need to give it some time before we hear back, especially as they may try to catch up with everything that’s been going on.
Oh shoot, I missed one that seems to fit this issue exactly. So it’s a known issue, but I’m not quite sure of the status. Seems like they tried pushing the fix but it never went though completely if I’m seeing things right. Either way, hopefully tagging Stephen Heaps and my +1 on the Github will help figure out the status.
Also, @boxer sorry, but noticed you don’t have the version of Brave you’re using. What version is yours on? I see you mentioned iOS version, but wanting to make sure you are using most recent of Brave, which should be 1.83 (118). I kinda ran with the idea that you’re using something up-to-date but I should’ve verified before everything else
Sorry I wasn’t more helpful with this guys (and confused about the issue for a bit … at least it kept the conversation going and got to the right peoples attention ) but I’ve been watching and glad to see it’s gotten to the people who can fix
I’ve reworded my defect slightly to hopefully make it clearer.
is why it is not a defect.
Just wanted to get it ackowledged and logged 
) but I’ve been watching and glad to see it’s gotten to the people who can fix