Privacy
we recognize that the protection of your personal information is a very important principle in building trust and maintaining a good relationship between us. We take the protection of your personal information very seriously.
We value your privacy and seek to protect the information we handle regarding its criticality, sensitivity and privacy importance in order to fulfil our customers’ and business partners
We value your privacy and seek to protect the information we handle regarding its criticality, sensitivity and privacy importance in order to fulfil our customers’ and business partners
ESMIN’S COMPLIANCE WITH GDPR
GDPR is set to take effect on May 25, 2018. On and after that date, Esmin will comply with GDPR to the extent applicable.
Under GDPR, Esmin may be designated as (i) a “controller” subject to GDPR with respect to certain data sets; (ii) a “processor” subject to GDPR with respect to certain data sets; or (iii) not subject to GDPR for certain data sets.
Under GDPR, Esmin may be designated as (i) a “controller” subject to GDPR with respect to certain data sets; (ii) a “processor” subject to GDPR with respect to certain data sets; or (iii) not subject to GDPR for certain data sets.
GDPR DOES NOT APPLY
For other relationships, GDPR will not apply, either because the data does not constitute protected data, or because the customer is not subject to GDPR.
EXAMPLE: A US-based customer purchases managed hosting services for marketing data concerning US citizens.
EXAMPLE: A US-based customer purchases managed hosting services for marketing data concerning US citizens.
GDPR does not apply.
EXAMPLE: An EU-based customer purchases colocation services from Esmin. Esmin does not have logical access to any customer data. Esmin does not have a login, passwords, or any other data, and cannot access the server. Esmin provides only physical security of the actual machine storing the data. Esmin is not a data processor because Esmin does not perform any operation on the customer’s data. It is not necessary to execute a processor agreement with Esmin under GDPR.
EXAMPLE: An EU-based customer purchases network services from Esmin. Esmin does not have logical access to any customer data in connection with network services. It is not necessary to execute a processor agreement with Joriole under GDPR, because Joriole is acting as a “mere conduit” of the data and is not considered a processor of the data (See GDPR Article 2[4]).
EXAMPLE: An EU-based customer purchases network services from Esmin. Esmin does not have logical access to any customer data in connection with network services. It is not necessary to execute a processor agreement with Joriole under GDPR, because Joriole is acting as a “mere conduit” of the data and is not considered a processor of the data (See GDPR Article 2[4]).