Learn how Radian secures your models, files, entities, simulations and results.
We use TLS (successor of SSL) to protect communications between our users and the server, preventing spoofing of the data being transferred. We use HSTS to enforce users interact with Radian only over TLS.
Passwords are stored in the database via salting and hashing. Salting implies inputting random data into your plain-text password, and hashing means irreversibly encrypting the result, thus generating a unique encrypted entry.
Every data file is encrypted at rest and in transit by default. We use security credentials for every file request, securing the petition and retrieval of data files.
Our cloud provider facilities are certified in ISO/IEC 27001:2013, and AICPA SOC 3, ensuring high levels of reliability, privacy and security.
Our databases get backed up every 24 hours
Radian is monitored by New Relic and Sentry
Current application uptime for a period of 12 months
Files and entities are truly erased at your will
Each customer has a sandbox for database and files
We can keep your data even after your license expires
Each version update takes into account every user's data
Each parameter and file is checked before being stored