Thank you for your enthusiasm -- we think Cryptomove is cool too!<p>There are no special provisions right now to have storage in the cloud or on any special servers. This alpha version has servers making TCP&#x2F;IP connections. The data is stored in directories that have to reside on mounted disks. So, as long as TCP&#x2F;IP connection works and directories are available, the servers may reside anywhere; as long as disks are mounted, they can also reside anywhere (say, NFS).<p>Obviously, versions beyond alpha might choose to have a hierarchy of storage devices -- from memory disks to mounted disks to cloud storages.<p>Cryptomove does not use any TOR interface.<p>The current version randomly sends data parts from one server to another via a TCP&#x2F;IP connection, or moves the part within the local store. Therefore, the path traveled is not known in advance. However, the movement is star-like -- after the part hops randomly N steps, it retracts back to the point of origin retracting the same path.<p>On the forward path, each data part is encrypted (AES) on each server with that server&#x27;s password, so at the end of the path of N steps it is encrypted N times. When retracting, on each server it gets decrypted, and then re-encrypted again.<p>When it comes back to the base server, it immediately starts another random path forward, again being encrypted moving away at the base over and over, while being decrypted&#x2F;re-encrypted on the way back.<p>By default, the movement is not frequent -- each part moves once a day. If there are many parts, then one would see constant movement of random parts in random directions. However, data user may accelerate default movement frequency. Similarly, system owners (Admins) can slow down or accelerate the frequency of any part that travels through a particular server.