That's not how the industry works.

Also, here, fixed your statement for you: Privacy laws generally don't let you evade a restriction simply by changing the technical mechanism used to achieve the same tracking or identification. Whether something is a cookie, fingerprint, local-storage identifier, or another technique is often less important than what the technique does and what legal rule applies to that activity. However, the mechanism can still matter because different laws and provisions regulate different technical activities, and lawful tracking is not necessarily prohibited merely because its purpose is to track.

First of all, you're the one to choose what you're fingerprinting for, and if you include the battery or such changing factors maybe you should rethink your career as an engineer.

My web apps lack any telemetry, the only cookies that get set are for sessions, users settings and various redux like storage on client side which can be opted out. It's more than proper. :)

I am not against cookie banners, I own a few web apps and each of them have proper configurable cookie settings (including the banner).

All I am saying is that most companies (especially one's that do not reside in EU) do not care and will track you across websites by fingerprinting your hardware when visiting their website. Some do not even use cookies at all.

For the past 10 years or so tracking is done with hardware fingerprinting anyways. Cookies are of the past.

Haven't you guys used a kite before?

I am reading through lines and I seem to be stuck confused. Why isn't the whole clipboard partitioned?

Example: Youtube - separate array(whatever) holding its clipboard Facebook - separate array(whatever) holding its clipboard

When trying to copy-paste between apps, simply link its containers and provide cross-access for said apps. This way you keep it modular and as secure as possible while not allowing other services to access a specific container.

I have yet to use GrapheneOS, sadly past phones I had did not support it.