Implement Detailed Explanation for "Encryption" with Gnosis Safe, ENS, BrightID and Other Stamps

[erichfi]

User Story:

As a Gitcoin Passport user, I want a detailed explanation for how my data from Gnosis Safe, ENS, BrightID, and other stamps is represented and stored, So that I understand the privacy and security measures in place, knowing that my specific account addresses from these platforms are not directly stored but rather represented in a privacy-preserving manner.

Acceptance Criteria

GIVEN a user is reviewing or adding stamps from Gnosis Safe, ENS, BrightID, LinkedIn, Discord, and Proof of Humanity to their Gitcoin Passport, WHEN they interact with the information related to the credential, THEN they should be presented with an intentional, functional, and aesthetically pleasing description that explains:

Account Name Provider Name (e.g., "Google")

Product & Design Links:

See example:

Tech Details:

Open Questions:

• [ ] Should we include information about user privacy here in the credential description?

Notes/Assumptions:

[lebraat]

To start, I'll provide some recommended headers and credential names to replace "Account Name" and "Encrypted. Might come back through with some more specific recommendations for the descriptions

Stamp - Header - Credential name

Gnosis Safe - Safe - Owns account (Should we remove 'Gnosis'?) ENS - ENS - Owns domain BrightID - BrightID - Verified identity LinkedIn - LinkedIn - Owns account Discord - Discord - Owns account Proof of Humanity - Proof of Humanity - Verified identity