Absolutely - Here’s all that info for you.
1 -
2-
3 -
4 - I do not use brave sync so N/A
1 Like
Thanks, let me tag in @shivan as I know he was the one asking for information.
Awesome! Thanks so much for organizing all this. Just to add an A/B test angle — once I noticed the issue, I set up my laptop to retain all browsing data on exit, while my desktop continued clearing browsing history. Despite the difference, both still log me out of Google daily, so it doesn’t seem tied to data-clearing settings in my case.
Thanks a lot, we’re really struggling repro’ing this.
- What extensions do you have installed?
- Can you take a screenshot of brave://settings/content/siteData?
- Can you take a screen recording of the issue on a brand new profile?
@FaintNet out of curiosity, do you have yours set as a trusted device? Such as spoken about at https://support.google.com/accounts/answer/2544838
I’m also wondering if people are using a particular form of 2FA or passkey that might be triggering a quicker expiration than others.
At least some random thoughts. It’s weird that only some people are being impacted while majority aren’t.
1 - I am currently running these extensions:
2 - Here is that info:
3 - I can take a screen recording if it’s truly helpful, but honestly, I’m not sure it would show anything new — it just drops me straight to the Google sign-in page, as if I were launching the browser for the first time. No accounts are saved, and I’m effectively starting from scratch every time. It feels like the session is getting wiped or invalidated behind the scenes.
@Saoiray - To answer your question: every time I log back into my Google account, it registers a new trusted device. As shown in the screenshot, I end up with a new “device” roughly once per day, which aligns with the frequency of the forced logouts.
On days where I use both my desktop and laptop, I see two new sessions — one for each login. On days like today, when I’ve only used the desktop, it only adds a single new device as expected.
I used inspect element to remove my location for privacy, but the rest of the page is unchanged.
1 Like
I’d be curious to see if you’d have the same issue if you did a new browser profile. Try without any of the extensions and see if there’s an issue. There could be any number of strange interactions. But especially depending on the filters you’re using on uBlock Origin in conjunction with Shields.
Anyway, keep in mind I’m just the normal user who chimes in with random ideas. Not sure of exact percentages but know my random thoughts or questions have guided people to the answers on a lot of issues. Perhaps not the “nail on the head” but got attention focused in the right direction. At the very least it serves to help rule things out.
Just got logged out again - I actually went ahead and did a full clean reinstall on my laptop to rule out any possible profile corruption or extension conflicts. No extensions, no sync, stock settings, and same result.
So it’s definitely not a profile or config issue at this point.
1 Like
Interestingly enough I’m having the same issue and also have Sponsorblock installed.
Brave Version:
Extensions:
Site Data:
I’ve tested this with a completely clean profile and no extensions installed, and the issue still happens. SponsorBlock (or any other extension) isn’t touching session persistence, so I don’t think extensions are the culprit here.
This seems more like an issue with session storage, fingerprinting, or site isolation that’s affecting how Brave maintains persistent logins.
1 Like
To be fair I don’t experience this on my Windows installation (yet).
I’m on Hyprland Wayland, so not sure if that’d affect anything. But happens on Hyprland (wayland), Plasma Wayland, and Plasma X11 for me.
Not going to lie, it’s getting old having to sign into all my sites every single time I open my browser, especially since I use 2FA on most of them. It’s not just Google/YT, it’s Matrix, even the Brave Community site, everything. It’s not registering to keep me logged in on stuff.
Just wanted to give you a quick update on how I’ve fixed it (so far). I went to brave://settings/content/siteData, and set the option to Delete Data
then I closed Brave entirely, rebooted my machine, set it BACK to Allow sites to save data on your device
Restarted Brave again, then logged into YouTube, Google, and various other sites, then rebooted my machine several more times to test, and so far it’s kept me logged in all of the time.
Another facet is that I’m on Linux, and had both gnome-keyring and kwallet (KDE’s version of keyring) installed. I removed gnome-keyring prior to doing any of this so that kwallet would take priority. Had to uninstall Github Desktop (gnome-keyring was a dependency) to do it which sucks since I use it every day, but I may just have to find another git client unless Brave can figure out why it’s not allowing sites to save data even though it’s set to.
1 Like
Hi,
I had the same problem with the mobile version of Brave — after closing it, been logged out of YouTube. Allowing the app to remember passwords solved the problem for me.
I’m having this same issue on Arch Linux, tried both flatpak and aur, clear .config, .cache, .local/share, nothing works
I’m also having this issue on OpenSUSE Tumbleweed on Brave version: 1.77.95-1
I had the same problem. The only solution was to manually add the account and pass to brave in brave://password-manager/passwords
It’s been nearly two months now. I see this has been marked as a P2 on GitHub, which at least confirms it’s being tracked. But from a user perspective, there’s been no meaningful communication or update, and the issue has persisted.
This is not a misconfiguration on my end (or anyone’s for that matter) - it’s a persistent session bug on Brave’s side. Every time I close and reopen Brave, I get logged out of Google. More concerning: Google logs each of these as a new device login, and I now have 20+ new “devices” associated with my Google account this month alone.
That’s clearly not expected behavior from a Chromium-based browser. Session and cookie persistence are basic functionality, and this kind of repeated identity cycling could easily cause confusion or make google suspicious of the affected accounts.
I’ve tested all the usual troubleshooting steps:
- Clean profile with no extensions
- Cookies and site data explicitly allowed
- Shields off
- No sync, no flags
- Whitelisted all relevant Google domains
This still happens consistently, even with fresh setups. It’s likely an issue in how Brave is handling session storage or partitioning - but either way, it needs attention from engineering.
Can someone from Brave please confirm this is being actively worked on? It’s not just inconvenient - it’s a break in basic browser functionality, and I’m sure others are running into this silently too.
I am on build 1.78.102 Chromium: 136.0.7103.113 (Official Build) (64-bit)
Yes, this is being actively worked on. There are also devs in that thread discussing the issue as of the last hour.
Thanks for the follow-up. Just to clarify what I meant earlier - when I mentioned there hasn’t been a “meaningful update,” I was referring to the fact that while discussion and ongoing investigation are important, it’s still unclear from the outside how close this is to being resolved. I completely understand that some issues take time to fully diagnose, but a bit more clarity around where things stand would really help manage expectations.
As for the recent questions in the GitHub thread - here’s everything I can confirm:
- brave://flags - I’m not running with any non-default flags enabled. I’ve also reproduced the issue using a clean, untouched profile with all flags set to default.
- brave://version - 1.78.102 Chromium: 136.0.7103.113 (Official Build) (64-bit)
- Fresh install - I’ve reproduced the issue on both my desktop and laptop, each running a fresh install of Brave with clean user profiles. No extensions, no sync, no carryover data - the behavior persists consistently across both systems.
- Origin Trials - I checked via DevTools (Application → Top → Origin Trials), and there are no trial tokens present in my browser. Screenshot attached for reference.
Appreciate the continued work.