Cdc according to this using Brave mobile shouldn't have any impact in terms of privacy as far as my knowledge goes.
The links I've shared in my post don't mention Brave mobile browser, so I can't arrive to the same conclusion.
Also, it's good to remember that you can have security without privacy, but you can't have privacy without security. Here's a quote from the link above:
Chromium has decent exploit mitigations, unlike the available alternatives. This is improved upon in Vanadium by enabling further mitigations, including those developed upstream but not yet fully enabled due to code size, memory usage or performance. For example, it enables type-based CFI like Chromium on the desktop, uses a stronger SSP configuration, zero initializes variables by default, etc. Some of the mitigations are inherited from the OS itself, which also applies to other browsers, at least if they don't do things to break them.
So, Vanadium has further mitigations, which I think Brave mobile may not have. I don't know if Brave mobile team goes an extra mile to fork Vanadium's mitigations on top of what they do. Also, there's the WebView part that's very much important. Brave won't provide WebView for your phone, so if you using Brave, you're actually using Vanadium WebView, too. At least for your apps. Maybe 'don't put all your eggs in one basket' approach can be mentioned here and is relevant for your threat model.
Cdc Please share your opinions.
I use Brave browser on desktop only, because I don't know of better alternatives from security and privacy (combined) points of view. Tor browser will give you anonymity if you use it right, at least to some extent, but no security since it's unfortunately, Gecko based. As for mobile, Vanadium is my best friend.
With that said, I recall some regular community members mentioned in GrapheneOS chat rooms that Brave is fine as long as your threat model agrees with it.
Hope this helps.