I don't trust any browser based on Chrome. Here's why:
Some years ago I wrote a tool that would (supposedly) let me focus on what I was doing by replacing DNS entries in my local machine's /etc/hosts file with pointers to localhost. Since time immemorial, linux systems and their ilk have had rules for DNS where the hosts file is checked *before* any DNS lookups are done. I used it for quite some time with a cron entry that turned it on at a certain time and turned it off at a certain time. Since Macs are based on Unix, it worked like a charm! My daughter, who was then in high school, asked to install it for her and I did, happy that someone would use my cool tool.
Only it didn't work for her. Why? Because she uses Chrome.
After troubleshooting, I discovered that Chrome completely bypasses any local DNS configuration and uses its own. As someone who's been using Unix for decades this REALLY bothers me. What other non-standard things is it doing? What's it using for DNS? I'm sure Google did these things to make Chrome "work better" or make it "more secure" or some other such thing, but bypassing a fundamental system behavior left a bad taste in my mouth.