Because it will be used by other services. Like google requiring one for you to use their services. That's the problem.

It seems to me as if it would get used by the same services that already require an id, except they would now not require a physical check of the id anymore.

▲

9dev 3 days ago | parent | prev [-]

I don’t see that happening in Belgium, though?

▲

duskdozer 3 days ago | parent [-]

You don't? Google already requires ID for developers in Belgium [0], and it's complying with regional laws for age verification [1]. The EU is also starting to look at age verification [2]. I don't see how it's such a stretch that Google may want to expand this further even in the absence of government demands, considering the huge ad/data incentive for them to directly link accounts to IRL identities.

[0]https://support.google.com/googleplay/android-developer/answ...

[1]https://www.digitaltrends.com/phones/google-play-store-wants...

[2]https://digital-strategy.ec.europa.eu/en/factpages/blueprint...

	▲	seszett 3 days ago \| parent [-]
		> Google already requires ID for developers in Belgium But it also requires id in France, even for people who don't have an eid. Or in the US, and most likely just about everywhere in the world. I don't see how this is related in any way to having a chip on an id document.