/e/OS is not fully degoogled, as DNS connectivity checks, hardware attestation provisioning, and eSIM activation all go through Google.
It is often many weeks or months behind on security updates, especially in the WebView, which makes it easy to exploit.
It doesn't support bootloader locking on many devices, and if you lock the bootloader on a phone that does support it, it could brick if /e/OS is on an older security patch than the stock ROM was.
It doesn't use a lot of the hardening in GrapheneOS such as hardened_malloc which prevents memory corruption exploits, even if the hardware supports it.
And finally, /e/OS's text-to-speech sends what you say to OpenAI, despite local options being available.
If you want a properly secure Android phone, the best option is GrapheneOS, however it only supports Pixel phones and future Motarola phones due to its high security requirements.
If you can't get a Pixel then iOS in lockdown mode is the next best option, however if you can't replace your phone, LineageOS is much worse than Graphene although it is still much better than /e/.
I think you might not understand the meanings of privacy and security.
These are two different things, you can have privacy without security and the other way around. Having both is the best case.
As @ExLisper@lemmy.curiana.net said, some people care more about all those app trackers rather than have a full secure phone.
If there would be the one solution 100% privacy and security and available for most phones I would instantly use it. But it is not available yet.
If you are happy with Graphene OS good for you, but keep in mind it might not be what everyone is looking for.
I think you replied to the wrong comment but you said the right thing :)
To me it shows me that I replied to the right comment. I just tagged you, as I agreed with what you said in your comment below.
Ok, I guess no one tagged me before. TIL.