As of version 4.2, SilverSHielD implements a server-side technology to protect uploads and downloads when the client doesn't.
Some clients (like WinSCP for instance) upload large files using a temporary name; the file is then renamed to the supposed destination file name only upon successful upload. By doing so, should the upload break for some reason, the original file on the server remains untouched.
So it's important to understand that if your client already does so, you do not have to use SafeUp™.
But when your client doesn't apply any upload/download protection technique, SafeUp™ can be very useful, because it basically does the same (upload with fake name and rename after successful
upload) but on the server-side.
SafeUp™ can be enabled/disabled per every single user.