> The OpenID spec specifies that an id_token needs to contain the following, based on scope: - email: email, email_verified - profile: name, family_name, given_

> The OpenID spec specifies that an id_token needs to contain the following, based on scope: - email: email, email_verified - profile: name, family_name, given_name, middle_name, nickname, preferred_username, profile, picture, website, gender, birthdate, zoneinfo, locale, updated_at I understand the need of an email and other data, and that they can work as PKs in the Web/Mob apps' databases. But also those data are a medium to communicate with the actual user. So again I am curious about why ProtonMail doesn't provide a mechanism like this. They have all the data, the brand and the credibility to run a service with the following business model.