When you first log in to Supercluster Airlock, the only thing required is a MetaMask wallet. This is required in order for our system to be able to retrieve the user’s on-chain assets, including tokens, NFTs, POAPs, Otterspace Badges, and Snapshot Proposals.
Depending on the group requirements, the user may also be required to authenticate with specific web2 platforms. For instance, if a group requirement is defined as a Discord role, then the community member requesting access will be required to also log in with their Discord in order for Airlock to know which roles the user has obtained.
Another factor that may require additional authentication from the user is the tools that the user will need access to. For instance, Notion requires users to have an email for authentication in their system. Initially, users will be required to provide an email to Airlock to be used for user generation within Notion. All of this will be self-serviced for the community member.
<aside> 💡 Note: We are planning to build a credential (e.g email) generation feature into our product. This will allow members to not have to even supply an email to the Airlock system. This feature is high on our priority list.
</aside>
Currently, Supercluster will store the wallet address along with any additional authentication methods that the user has performed. This currently includes email and Discord username.
None of the user’s attributes, such as assets (tokens, NFTs, etc) or any engagement parameters are stored in our database. Once the initial request has been processed, Airlock no longer has any idea on what the user has in their wallet.
We are integrating various third party platforms. Here are a list of existing providers:
[Link to Privacy Policy]
[Link to Terms of Service]