At Encoding.com, user passwords are stored in a secure location separately from the primary application data, and all user passwords are protected with cryptographic hash algorithms.
At Encoding.com, data at rest is stored using 256-bit AES encryption. In addition, all customer files are stored within file systems on dedicated systems called FTFs (short for “File Transfer Fabric”). File names are replaced with random strings so that no file is identifiable by name.
Encoding.com stores customer account information in a secure, redundant, highly available database system with access restricted to authorized members of the Operations Group.
At Encoding.com, job requests (API or UI) transferred between client and server over the untrusted internet is 128-bit SSL/TLS encrypted (at minimum). If supported by the client browser, data is then encrypted via 256-bit SSL/TLS.
Encoding.com supports encrypted file transfer protocols such as Aspera FASP, SFTP, and HTTPS.
Encoding.com supports various ACL functions of Amazon Web Services including key/secret pairs and limited duration credentials. Additionally, read access can be granted to the Encoding.com AWS user. Encoding.com also supports the use of directly-encrypted source assets.
If media is transferred to Encoding.com, source assets by default are stored for up to 15 days to allow for customers to generate additional output profiles without the need to re-transfer assets. Customers have the option of deleting the source assets immediately after processing is complete by using the DeleteMedia API call, or clicking Delete in the Encoding.com UI.
Encoding.com does not allow the storage of any customer data on removable storage media at any time.
No customer data is ever stored on desktops, laptops, or mobile devices.
Updated about 16 hours ago