In this document, we discuss on a high level what safety measures are in place on our end as a data processor as well as what features are offered by Cryptolens platform that you can enable as a data controller.
If you require more details about what safety measures are taken on our side as data processor, you can find them in this document.
When developing Cryptolens, we apply an assume breach policy. This means that we develop components in such a way as to ensure that if a breach occurs, we can minimize its damage.
Access to your information is restricted to specific employees. All employees that need to access your information have signed a non disclosure agreement.By default, none of our employees access your data unless you ask us for help with troubleshooting. In such cases, sensitive data is masked and we always strive to minimize access to the information to what is needed to help you with a certain query.
Our database firewall is restricted so that only authorized services can access it. Moreover, we restrict the permission each service has and mask sensitive fields.
In order to safeguard customer data and ensure compliance, both you as a software vendor and us as the data processor have to cooperate. In this section, we have outlined several tips of how to increase safety when using Cryptolens.
Methods such as Activate and GetKey allow you to mask certain fields to boost privacy. Masking is especially important if you are developing an SDK. We recommend that you mask:
Notes, Data objects - if you are storing data related to your customer, since it will be visible by all the end users.
Activated Machines - should always be masked since it reveals personal identifiable information about the customers.
