System and method for secure transitory data storage and management
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.
1. A system for secure storage and management of transitory data containers, comprising:
a computing device comprising a memory and a processor; and
a domain-specific database stored on the memory of the computing device, wherein the domain specific data comprises pre-defined enterprise specific rules and preferences; and
a callback 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:
initiate a session when first contact is made with a caller;
send session attributes to at least one of a context analysis engine and a data message aggregator; and
a context analysis engine 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 session attributes;
generate, in response to the session attributes, context content pertaining to at least one of the callback requestor, the callback recipient, and the session attributes;
forward the context content to a vault manager; and
the vault 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:
receive the context content;
receive profile data;
retrieve enterprise specific rules and preferences from the domain-specific database;
receive a caller created data container, wherein the data container comprises caller defined preferences;
encrypt the preferences stored within the caller created data container;
store the encrypted data container in the memory of the computing device;
retrieve the data container from the memory when the caller and the call recipient have an initial conversation;
create a hash password that both the caller and call recipient can use to access the data container; and
delete the data container at the container creator's request or when the caller defined timeline of existence preference has been surpassed.
2. The system of claim 1 wherein if a caller created data container is not received, a default container is created with a set of default preferences established using the context content, the profile data, and the enterprise specific rules and preferences.
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 two phone numbers of the caller and a call recipient.
6. The system of claim 1 further comprising an audit logger 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:
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 requestor;
sending session attributes to a context analysis engine;
receiving the session attributes;
generating, in response to the session attributes, context content pertaining to at least one of the callback requestor, the callback recipient, and the session attributes;
forwarding the context content to a vault manager;
receiving the context content;
receiving profile data;
retrieving enterprise specific rules and preferences from the domain-specific database;
receiving a caller created data container, wherein the data container comprises caller defined preferences;
encrypting the preferences stored within the caller created data container;
storing the encrypted data container in the memory of the computing device;
retrieving the data container from the memory when the caller and the call recipient have an initial conversation;
creating a hash password that both the caller and call recipient can use to access the data container; and
deleting the data container at the container creator's request or when the caller defined timeline of existence preference has been surpassed.
8. The method of claim 7 wherein if a caller created data container is not received, a default container is created with a set of default preferences established using the context content, the profile data, and the enterprise specific rules and preferences.
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 two phone numbers of the caller and a call recipient.
12. The method of claim 1 further comprising the steps of:
creating a blockchain to keep a detailed record of data container access and interaction.