A method for managing a data item , comprising: receiving, by a hub comprising a processor and a memory, a first access request for the data item from a first engine executing on a computing device operated by a first host ; sending, by the hub, the first access request for the data item to a second engine executing on a first computing device of a second host , wherein the second host owns the data item; receiving, by the hub and from the second engine in response to sending the first access request to the second engine, the data item and an access rule set by the second host for the first host; sending, by the hub, the access rule and the data item to the first engine for storage, wherein the first engine grants the first host access to the data item according to the access rule; receiving, by the hub, a recall request from the second engine for the data item, wherein the second host is able to issue the recall request in response to the second host owning the data item; and sending, by the hub, the recall request to the first engine, wherein the first engine deletes the data item stored on the computing device operated by the first host in response to the recall request; receiving, by the hub, a state of an engine associated with a ghosting mode, wherein the engine associated with the ghosting mode is disconnected from the hub after the state is received; establishing, on the hub, a proxy engine based on the state, the proxy engine being a quasi-mirror of the engine associated with the ghosting mode; and executing, by the hub, a data synchronization operation between the proxy engine on the hub and the engine associated with the ghosting mode after the engine associated with the ghosting mode is reconnected to the hub, the data synchronization operation synchronizing an access entry created by the proxy engine. receiving, by a hub comprising a processor and a memory, a first access request for the data item from a first engine executing on a computing device operated by a first host ; sending, by the hub, the first access request for the data item to a second engine executing on a first computing device of a second host , wherein the second host owns the data item; receiving, by the hub and from the second engine in response to sending the first access request to the second engine, the data item and an access rule set by the second host for the first host; sending, by the hub, the access rule and the data item to the first engine for storage, wherein the first engine grants the first host access to the data item according to the access rule; receiving, by the hub, a recall request from the second engine for the data item, wherein the second host is able to issue the recall request in response to the second host owning the data item; and sending, by the hub, the recall request to the first engine, wherein the first engine deletes the data item stored on the computing device operated by the first host in response to the recall request; receiving, by the hub, a state of an engine associated with a ghosting mode, wherein the engine associated with the ghosting mode is disconnected from the hub after the state is received; establishing, on the hub, a proxy engine based on the state, the proxy engine being a quasi-mirror of the engine associated with the ghosting mode; and executing, by the hub, a data synchronization operation between the proxy engine on the hub and the engine associated with the ghosting mode after the engine associated with the ghosting mode is reconnected to the hub, the data synchronization operation synchronizing an access entry created by the proxy engine. <EOS>