System and method for secure storage and management of transitory data using a blockchain

Abstract

A system and method for secure storage and management of transitory data using a blockchain, comprising at least a callback manager, a context analysis engine, a vault manager, and a blockchain manager, which allows a user to create a data container to store data preferences, which encrypts the data stored within a data container, and which stores the encrypted data container in a blockchain. For each block, block reference data may is generated comprising the location of the block and its associated decryption key, and the block reference data is then encrypted with a second encryption key and stored off the blockchain in a separate database. The second key is distributed to involved parties to permit access to and reading of the block reference data. The block reference data is deleted based on self-destruct event triggers or when the involved parties are finished accessing the block reference data.

What is claimed is: 
     
       1. A system for secure storage and management of transitory data using a blockchain, comprising:
 a computing device comprising a memory and a processor; 
 a blockchain manager comprising a first plurality of programming instructions stored in the memory and operating on the processor, wherein the first plurality of programming instructions, cause the computing device to:
 receive an encrypted data object, the encrypted data object comprising transitory data; 
 store the encrypted data object in a block on a blockchain; 
 generate block reference data, the block reference data comprising at least a location of the block and its decryption key; 
 encrypt the reference block data; 
 generate a second encryption key that decrypts the encrypted block reference data; 
 store the encrypted reference block data in a database; 
 distribute the encryption key to involved parties, wherein the second encryption key allows the involved parties to decrypt and read the block reference data; and 
 delete the transitory data by destroying the encrypted block reference data. 
 
 
     
     
       2. The system of  claim 1 , wherein the blockchain manager is further configured to monitor for one or more self-destruct event triggers. 
     
     
       3. The system of  claim 2 , wherein the one or more self-destruct event triggers comprise at least one of a timer-based trigger, a trigger packet, and a device-based trigger. 
     
     
       4. The system of  claim 2 , wherein the blockchain manager destroys the encrypted block reference data responsive to a detected self-destruct event trigger. 
     
     
       5. The system of  claim 1 , wherein the data object is a data container. 
     
     
       6. The system of  claim 1 , further comprising a vault manager comprising a second plurality of programming instructions stored in the memory and operating on the processor, wherein the second plurality of programming instructions, cause the computing device to:
 receive context content; 
 receive profile data; 
 receive a caller created data object, wherein the data object comprises caller defined preferences; 
 encrypt the preferences stored within the caller created data object; and 
 send the encrypted data object to the blockchain manager. 
 
     
     
       7. The system of  claim 1 , further comprising a callback manager comprising a third plurality of programming instructions stored in the memory and operating on the processor, wherein the third plurality of programming instructions, cause the computing device to:
 initiate a session when first contact is made with a caller; and 
 send session attributes to at least one of a context analysis engine and a data message aggregator. 
 
     
     
       8. The system of  claim 7 , further comprising the context analysis engine comprising a fourth plurality of programming instructions stored in the memory and operating on the processor, wherein the fourth plurality of programming instructions, cause the computing device to:
 receive the session attributes; 
 generate, in response to the session attributes, context content pertaining to at least one of the callback requester, the callback recipient, and the session attributes; and 
 forward the context content to a vault manager. 
 
     
     
       9. A method for secure storage and management of transitory data using a blockchain, comprising the steps of:
 receiving an encrypted data object, the encrypted data object comprising transitory data; 
 storing the encrypted data object in a block on a blockchain; 
 generating block reference data, the block reference data comprising at least a location of the block and its decryption key; 
 encrypting the reference block data; 
 generating a second encryption key that decrypts the encrypted block reference data; 
 storing the encrypted reference block data in a database; 
 distributing the encryption key to involved parties, wherein the second encryption key allows the involved parties to decrypt and read the block reference data; and 
 deleting the transitory data by destroying the encrypted block reference data. 
 
     
     
       10. The method of  claim 9 , further comprising the step of monitoring for one or more self-destruct event triggers. 
     
     
       11. The method of  claim 10 , wherein the one or more self-destruct event triggers comprise at least one of a timer-based trigger, a trigger packet, and a device-based trigger. 
     
     
       12. The method of  claim 10 , further comprising the step of destroying the encrypted block reference data responsive to a detected self-destruct event trigger. 
     
     
       13. The method of  claim 9 , wherein the data object is a data container. 
     
     
       14. The method of  claim 9 , further comprising the steps of:
 receiving context content; 
 receiving profile data; 
 receiving a caller created data object, wherein the data object comprises caller defined preferences; 
 encrypting the preferences stored within the caller created data object; and 
 sending the encrypted data object to the blockchain manager. 
 
     
     
       15. The method of  claim 9 , further comprising the steps of:
 initiating a session when first contact is made with a caller; and 
 sending session attributes to at least one of a context analysis engine and a data message aggregator. 
 
     
     
       16. The method of  claim 15 , further comprising the steps of:
 receiving the session attributes; 
 generating, in response to the session attributes, context content pertaining to at least one of the callback requester, the callback recipient, and the session attributes; and 
 forwarding the context content to a vault manager.