Data Privacy
The Monadata Protocol is committed to ensuring that personal data remains private and is shared only with trusted entities.
Personal Data Encryption
Monadata employs a patented non-custodial encryption method to safeguard personal data. Data is always encrypted before it leaves the user’s browser. Each user’s file is encrypted using their own encryption key. When this key needs to be shared with a DQNode, it is further encrypted with the DQNode's encryption key.
Process Overview:
File Upload: The user uploads a file (F) that is currently unencrypted to the Monadata Protocol.
Signature Creation: The dApp prompts the user to sign a message with their wallet. This process generates a unique signature that can only be replicated by signing the same message with the same wallet.
Encryption Key (EK) Generation: The generated signature serves as the encryption key (EK), which is then used to encrypt the file F via a symmetric encryption method.
Encryption of EK: The encryption key (EK) is subsequently encrypted using the DQNode's public key, resulting in an encrypted encryption key (EEK).
DQNode Decryption: The validator receives the EEK and decrypts it using their private key to retrieve the original EK.
File Decryption: Finally, the EK is used by the DQNode to decrypt and access the file F.
This encryption process ensures that only authorized DQNode Operators can access the encrypted files provided by users.
DQNode's Encryption Key
To function as a DQNode within the Monadata Protocol, DQNode Operators must purchase a DQNode's encryption key. This key is essential for decrypting the encryption keys (EK) provided by users, enabling secure access to the necessary data.
Last updated