Mind Lake SDK
  • Overview
  • Get started
    • Tutorial step-by-step
    • TypeScript Quick-Start
    • Python Quick-Start
  • Use Cases
    • 1-Single User with Structured Data
    • 2-Single User with UnStructured Data
    • 3-Multi Users with Permission Sharing
  • Glossary
  • TYPESCRIPT API REFERENCE
    • MindLake
    • MindLake.DataLake
    • MindLake.Cryptor
    • MindLake.Permission
    • Return Code
  • PYTHON API REFERENCE
    • MindLake
    • MindLake.DataLake
    • MindLake.Cryptor
    • MindLake.Permission
    • Return Code
Powered by GitBook
On this page
  • Encryption & Permission
  • Secure Key Storage

Glossary

Previous3-Multi Users with Permission SharingNextTYPESCRIPT API REFERENCE

Last updated 1 year ago

Encryption & Permission

Contrary to conventional centralized databases that utilize role-based access control, Mind Lake does not directly manage user access control. Instead, permission management is accomplished through client-side encryption. Users with the capability to decrypt the data possess the necessary permissions while everyone else, including Mind Lake itself, is unable to access the encrypted information. All unencrypted data within Mind Lake is accessible to any user.

When a user in Mind Lake wishes to share encrypted data with another user, they must grant decryption permissions to the recipient. With these permissions, the recipient can then decrypt the shared data using a specific key associated with their account.

If you choose not to encrypt the data while inserting to Mind Lake, it will be accessible to any user.

Secure Key Storage

Diagram of Key Storage Process