System and method for secure transitory data storage and management

Abstract

A system and method for secure storage and management of transitory data, comprising at least a profile manager, a callback manager, a context analysis engine, and a vault manager, which allows a user to create a data container to store data preferences, which encrypts the data stored within a data container, which creates a password for accessing the data container, which temporarily stores the data container, which manages data container interactions between the system user and a second user, such as a business enterprise, and which establishes default preferences and creates a default container based upon context content data.

What is claimed is: 
     
         1 . A system for secure storage and management of transitory data containers, comprising:
 a computing device comprising a memory and a processor;   a context analysis engine 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 a plurality of session attributes associated with a callback request from a callback requester; 
 generate, in response to the plurality of session attributes, context content pertaining to at least one of the callback requester, the callback recipient, and a session attribute; 
 forward the context content to a vault manager; 
 the 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 the context content; 
 receive profile data; 
 receive a data container comprising callback requester preferences; 
 encrypt the data container; 
 store the encrypted data container in the memory of the computing device; 
 retrieve the encrypted data container from the memory when the callback requester and the callback recipient have an initial conversation; 
 create a hash password to access the encrypted data container; and 
 delete the encrypted data container at the callback requester's request or when a callback requester-defined timeline of existence preference has been surpassed. 
 
   
     
     
         2 . The system of  claim 1  wherein if a data container is not received, a default container is created with a set of default preferences established using the context content and the profile data. 
     
     
         3 . The system of  claim 2  wherein the default preferences are encrypted, and the encrypted default data container is stored in the memory of the computing device. 
     
     
         4 . The system of  claim 2  wherein a hash password is created for the default data container. 
     
     
         5 . The system of  claim 1  wherein the hash password is generated by combining the phone numbers of the callback recipient and the callback requester. 
     
     
         6 . The system of  claim 1  further comprising an audit logger 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 create a blockchain to keep a detailed record of data container access and interaction. 
     
     
         7 . A method for secure storage and management of transitory data containers, comprising the steps of:
 initiating a session when first contact is made with a callback requester;   generating, at a context analysis engine and in response to a plurality of session attributes, context content pertaining to at least one of the callback requester, a callback recipient, and the session attributes;   forwarding the context content to a vault manager;   receiving the context content;   receiving profile data;   receiving a data container comprising a plurality of callback recipient-defined preferences;   encrypting the data container;   storing the encrypted data container in the memory of the computing device;   retrieving the encrypted data container from the memory when the callback recipient and the callback requester have an initial conversation;   creating a hash password to access the encrypted data container; and   deleting the encrypted data container at the container creator's request or when the callback recipient-defined timeline of existence preference has been surpassed.   
     
     
         8 . The method of  claim 7 , wherein if a data container is not received, a default container is created with a set of default preferences established using the context content and the profile data. 
     
     
         9 . The method of  claim 8 , wherein the default preferences are encrypted, and the encrypted default data container is stored in the memory of the computing device. 
     
     
         10 . The method of  claim 8 , wherein a hash password is created for the default data container. 
     
     
         11 . The method of  claim 7 , wherein the hash password is generated by combining the phone numbers of the callback requester and the call recipient. 
     
     
         12 . The method of  claim 7 , further comprising the steps of creating a blockchain to keep a detailed record of data container access and interaction.