New User Verification Flow

Our commitment to security and privacy, ensuring that user verification is handled with the utmost care and their data is encrypted and securely stored in a decentralized manner.

1. Submit data for KYC: The user begins by submitting their personal data required for KYC. This is a standard compliance process to verify the identity of the users. - We can process documents from 190 countries.

2. Perform KYC: Togggle takes the submitted data and performs the necessary checks to verify the user’s identity.

3. Send KYC data + results: Once the verification is complete, the KYC data and results are sent to Togggle's backend.

   3.1 Encrypt and upload user data: Togggle's backend then encrypts the user's data for security. 3.2 Encryption: The encrypted data is processed, likely adding additional layers of encryption or security measures.

4. Issue an interoperable VC: After the data is securely encrypted, a Verifiable Credential (VC) is issued. VCs are digital certificates that use cryptography to provide a secure and tamper-evident way for a claim to be represented and verified. In our case, the VC is a hash that can be minted in every chain if needed.

5. Return VC: The VC is then returned, possibly to the user or to another system within Togggle, ensuring that the user's verified identity is securely stored and ready for use.

POD: The user's encrypted data, along with their VC, is stored in their Personal Online Datastore (POD), where it can be managed and accessed securely.