I stand by my point it is undocumented in the sense that how do I know it is not ‘phoning’ home in the back ground or other wise doing other and I dont necessarily mean ‘bad’ things in the back ground.
As DIM is not a TSR it doesn’t do anything in the background—if you monitor your web traffic you can see that even if you leave it running, DIM doesn’t connect to DAZ 3D unless you hit the refresh or download buttons.
I admit the info about exactly what DIM does is not in the documentation, but here’s the information I posted a while back:
1) when you tell DIM to check (either when first signing on or when pressing the refresh button), it sends the DAZ 3D server your login credentials. No information about anything on your computer, whether installed by DIM or not, is sent.
2) the DAZ 3D server sends back a file with information about everything in your purchase history, indicating what the current versions are.
3) DIM takes that file and compares it with the local records of what it has installed, as well as any products still waiting to be installed, and populates the “Ready to Download” tab with the list of new or updated products. All the processing of that data is done locally.
4) If you then press a download button (either for an individual item or for the queue of selected items), DIM sends DAZ 3D your login credentials and a list of the requested files. Again, no information other than the files you’ve requested is sent—for example, if you didn’t select some files, that information is only known locally.