Creation of the Personal Decentralized Storage

Register: This is the initial step where the user signs up for services with Togggle, initiating their journey into a decentralized identity ecosystem.
Create User POD¹: Once registered, Togggle's backend system creates a Personal Online Datastore (POD) for the user. A POD is a secure storage space where personal data is kept.
Permission Request: In alignment with privacy-by-design principles, the user is then prompted to grant Togggle permission to store personal data. This is a crucial step emphasizing user control and consent in the data management process.
Grant Permission: After the user grants permission, the process of safeguarding their data can proceed. This permission ensures that Togggle acts within the legal and ethical boundaries set by data protection regulations.
Data Sharding: Togggle then takes the user's WebID, a unique identifier for the user in the decentralized web, and shards it using Threshold + Polynomial Encryption (TH + P³ Encryption). Sharding is the process of breaking the data into pieces and distributing it across multiple nodes (servers), and this specific encryption method adds layers of security and redundancy.
Store User WebID⁴ and Create UUID⁵: The final step is storing the encrypted and sharded WebID in the decentralized storage. Alongside this, a Universal Unique Identifier (UUID) is created for the user, likely to further ensure the uniqueness of the user's identity within the system.

This dataflow represents a user-centric model of identity management where privacy and security are paramount. By decentralizing storage and employing advanced encryption methods, Togggle ensures that the user's identity and data are protected against centralized points of failure and unauthorized access.

Send Data for Encryption: Our story begins with data embarking from the Togggle backend. This is where the raw user data, perhaps provided during registration or subsequent activities, is prepared to be sent for encryption.
Perform TH + P Encryption: The next chapter sees the data undergoing our robust Threshold Homomorphic + Polynomial encryption. This sophisticated encryption technique ensures that data, while still usable for computations, is securely encrypted and can be split into multiple pieces.
Send Encrypted Data: Once encrypted, the data is then dispatched to the user's Personal Online Datastore (POD). This secure transmission ensures that the encryption integrity remains intact.
Fragmentation: Within the safe confines of the POD, the data undergoes fragmentation. This step is akin to dividing a secret into several parts, with each part being meaningless on its own. It’s a measure that significantly enhances data security.
Upload and Distributed into the Decentralized Storage: In the final leg of its journey, the data fragments are uploaded and distributed across the decentralized storage infrastructure. This not only adds another layer of security but also ensures that data retrieval requires assembling the distributed fragments, making unauthorized access practically impossible.

By now, the data has transformed from its original state into a secure, encrypted, and fragmented form, residing within a decentralized framework. This guarantees the highest level of privacy and security, allowing users to engage with digital services with peace of mind, knowing their data is secure within Togggle’s system.

PreviousTypes of Storages NextNew User Verification Flow

Last updated 1 year ago

Register: This is the initial step where the user signs up for services with Togggle, initiating their journey into a decentralized identity ecosystem.
Create User POD¹: Once registered, Togggle's backend system creates a Personal Online Datastore (POD) for the user. A POD is a secure storage space where personal data is kept.
Permission Request: In alignment with privacy-by-design principles, the user is then prompted to grant Togggle permission to store personal data. This is a crucial step emphasizing user control and consent in the data management process.
Grant Permission: After the user grants permission, the process of safeguarding their data can proceed. This permission ensures that Togggle acts within the legal and ethical boundaries set by data protection regulations.
Data Sharding: Togggle then takes the user's WebID, a unique identifier for the user in the decentralized web, and shards it using Threshold + Polynomial Encryption (TH + P³ Encryption). Sharding is the process of breaking the data into pieces and distributing it across multiple nodes (servers), and this specific encryption method adds layers of security and redundancy.
Store User WebID⁴ and Create UUID⁵: The final step is storing the encrypted and sharded WebID in the decentralized storage. Alongside this, a Universal Unique Identifier (UUID) is created for the user, likely to further ensure the uniqueness of the user's identity within the system.

Send Data for Encryption: Our story begins with data embarking from the Togggle backend. This is where the raw user data, perhaps provided during registration or subsequent activities, is prepared to be sent for encryption.
Perform TH + P Encryption: The next chapter sees the data undergoing our robust Threshold Homomorphic + Polynomial encryption. This sophisticated encryption technique ensures that data, while still usable for computations, is securely encrypted and can be split into multiple pieces.
Send Encrypted Data: Once encrypted, the data is then dispatched to the user's Personal Online Datastore (POD). This secure transmission ensures that the encryption integrity remains intact.
Fragmentation: Within the safe confines of the POD, the data undergoes fragmentation. This step is akin to dividing a secret into several parts, with each part being meaningless on its own. It’s a measure that significantly enhances data security.
Upload and Distributed into the Decentralized Storage: In the final leg of its journey, the data fragments are uploaded and distributed across the decentralized storage infrastructure. This not only adds another layer of security but also ensures that data retrieval requires assembling the distributed fragments, making unauthorized access practically impossible.