You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »


"3Delight Cloud – unquestionably t
he most secure 
cloud rendering service on the market." 

 

Here is a brief on how 3Delight Cloud securely handles your data. Some of the strategies employed, unique to 3Delight Cloud, makes it the most secure cloud rendering service on the market.

Data Communication

3Delight Cloud uses TLS/SSL (256 bits encryption) when uploading your scene data to the cloud and when downloading the rendered images back to your computer. TLS/SSL is the most secured internet communication available – the same standard used by banks and other organization in need of high security.

Scene Data Storage

Once your scene data reached the cloud, it is fragmented into inaccessible smaller parts and stored using AES-256 encryption. The fragmentation is done using a proprietary process that makes it virtually impossible to rebuilt your scene without the original data on your hard drive (even if one broke the encryption to access the stored data, which in itself is impossible using current technology).

Image Data Storage

Unique to 3Delight Cloud, your images are never stored in the cloud. Not even momentarily. Here is how it works: during rendering, pixels (in buckets of 16x16) are streamed directly to your computer. It is the program that we run on your computer during rendering that assembles these to form the image and save it to your hard drive (or display it to your screen).

*And remember, these small buckets of pixels are transferred using TLS/SSL (256 encryption).

A few notes are in order here:

  • When using 3Delight Cloud, it is important to make sure your internet connection is not severed. If it is, rendering will abort as it will not know where to send the pixels. This is also why it is futile to ask us if you could download your images after such an interruption if it occurs. No images are ever saved on 3Delight Cloud.
  • As the rendering streams the pixels, a tiny fraction is retained to form a thumbnail (120x66 pixels) which is saved (encrypted) in your Transaction History. Here is a sample:


What if someone breaks into your account?

The consequences are limited:

1) Your scene data won't be accessible as log as the person does not have access to your scene data on your own drive (see comments in the Scene Data Storage section above).
2) Your rendered images wont be accessible as they are not stored in the cloud (see Image Storage Data section above).

3) The person login in to your account will be able to see your account balance and spending as well as the thumbnails of your rendering.


  • No labels