MYRTLELABS S.A.S.

content/contact-us/_index.md

@@ -26,13 +26,13 @@ If you have any issues with the product or any ideas about how it can be improve
 
 ## Company name and address
 
-We are the MYRTLE GROUP S.A.
+We are the MYRTLELABS S.A.S.
 
 Address: <br/>
 Ecuador, Quito <br/>
-La Armenia, Juan Montalvo <br/> 
-Conjunto Prados de la Armenia, casa 73 <br/>
-RUC 1792537754001 <br/>
+La Armenia, Juan Leon Mera y Numa Pompillo <br/> 
+Conjunto Prados de la Armenia N9-960 <br/>
+RUC 1793212306001 <br/>
 Postal code 170803 <br/>
 Email: [email protected] <br/>
 Website: [cloudback.it](https://cloudback.it)

content/privacy/_index.md

@@ -11,7 +11,7 @@ keywords: cloudback, privacy policy, gdpr, gdpr compliant, gdpr compliant backup
 
 ## Introduction
 
-We, the MYRTLE GROUP S.A., have built the Cloudback application as a Commercial service. This service is provided by us and is intended for use as is. We fully comply with the European General Data Protection Regulation (GDPR) laws, requirements and regulations.
+We, the MYRTLELABS S.A.S. (previosly [MYRTLE GROUP S.A.](https://docs.cloudback.it/posts/myrtlelabs/)), have built the Cloudback application as a Commercial service. This service is provided by us and is intended for use as is. We fully comply with the European General Data Protection Regulation (GDPR) laws, requirements and regulations.
 
 This Policy is used to inform visitors and users regarding our policies about the collection, use, and disclosure of Personal Information of anyone using the Service.
 
@@ -85,15 +85,15 @@ We value your data subject rights under GDPR and therefore appointed Prighter.co
   Prighter.com <br/>
   Maetzler Rechtsanwalts GmbH & Co KG <br/>
   Attorneys at Law <br/>
-  c/o MYRTLE GROUP S.A. <br/>
+  c/o MYRTLELABS S.A.S. <br/>
   Schellinggasse 3/10, 1010 Vienna, Austria <br/>
 
   Please add the following subject to all correspondence:
   GDPR-REP ID: 15719145
 
 **Information according to Art 27 EU GDPR**
 
-MYRTLE GROUP S.A. is a company located outside of the European Union. In order to comply with Art 27 EU GDPR, Prighter.com has been nominated as our representative in the European Union. If you want to
+MYRTLELABS S.A.S. is a company located outside of the European Union. In order to comply with Art 27 EU GDPR, Prighter.com has been nominated as our representative in the European Union. If you want to
 make use of your data privacy rights, please visit [our Compliance Landing Page](https://prighter.com/q/15719145)
 
 <a href="https://prighter.com/q/15719145"><img style="max-width: 301px; max-height: 148px;" src="https://prighter.com/certificateofrepresentation/15719145/getwebcertificate.png"
@@ -105,9 +105,9 @@ Controller for the purposes of the General Data Protection Regulation (GDPR), ot
 
 Address: <br/>
 Ecuador, Quito <br/>
-La Armenia, Juan Montalvo <br/> 
-Conjunto Prados de la Armenia, casa 73 <br/>
-RUC 1792537754001 <br/>
+La Armenia, Juan Leon Mera y Numa Pompillo <br/> 
+Conjunto Prados de la Armenia N9-960 <br/>
+RUC 1793212306001 <br/>
 Postal code 170803 <br/>
 Email: [email protected] <br/>
 Website: [cloudback.it](https://cloudback.it)

content/security/data-breach-response-policy.md

@@ -11,7 +11,7 @@ keywords: github backup, cloudback, security, data security, data protection, da
 
 ## Purpose 
 
-The purpose of the policy is to establish the goals and the vision for the breach response process in the MYRTLE GROUP S.A. ("we" or "Cloudback"). This policy will clearly define to whom it applies and under what circumstances, and it will include the definition of a breach, staff roles and responsibilities, standards and metrics (e.g., to enable prioritization of the incidents), as well as reporting, remediation, and feedback mechanisms. The policy shall be well publicized and made easily available to all personnel whose duties involve data privacy and security protection.
+The purpose of the policy is to establish the goals and the vision for the breach response process in the MYRTLELABS S.A.S. ("we" or "Cloudback"). This policy will clearly define to whom it applies and under what circumstances, and it will include the definition of a breach, staff roles and responsibilities, standards and metrics (e.g., to enable prioritization of the incidents), as well as reporting, remediation, and feedback mechanisms. The policy shall be well publicized and made easily available to all personnel whose duties involve data privacy and security protection.
 
 Cloudback Information Security's intentions for publishing a Data Breach Response Policy are to focus significant attention on data security and data security breaches and how Cloudback’s established culture of openness, trust and integrity should respond to such activity. Cloudback Information Security is committed to protecting Cloudback's employees, partners and the company from illegal or damaging actions by individuals, either knowingly or unknowingly.
 

content/security/disaster-recovery-plan-policy.md

@@ -11,7 +11,7 @@ keywords: github backup, cloudback, security, data security, data protection, da
 
 ## Overview
 
-The purpose of the policy is to establish the goals and the vision for the disaster recovery process in the MYRTLE GROUP S.A. ("we" or "Cloudback"). It is important to understand that having a contingency plan in the event of a disaster gives Cloudback a competitive advantage. This policy requires management to financially support and diligently attend to disaster contingency planning efforts. Disasters are not limited to adverse weather conditions. Any event that could likely cause an extended delay of service is considered.
+The purpose of the policy is to establish the goals and the vision for the disaster recovery process in the MYRTLELABS S.A.S. ("we" or "Cloudback"). It is important to understand that having a contingency plan in the event of a disaster gives Cloudback a competitive advantage. This policy requires management to financially support and diligently attend to disaster contingency planning efforts. Disasters are not limited to adverse weather conditions. Any event that could likely cause an extended delay of service is considered.
 
 ## Purpose
 

content/security/incident-response-plan.md

@@ -11,7 +11,7 @@ keywords: github backup, cloudback, security, data security, data protection, da
 
 ## Introduction
 
-The purpose of the document is to establish the goals and the vision for the incident management process in the MYRTLE GROUP S.A. (“we” or “Cloudback”).
+The purpose of the document is to establish the goals and the vision for the incident management process in the MYRTLELABS S.A.S. (“we” or “Cloudback”).
 This document discusses the steps taken during an incident response plan.
 
 ## Incident Response Process

content/security/vulnerability-management-workflow.md

@@ -11,7 +11,7 @@ keyword: github backup, cloudback, vulnerability management workflow, vulnerabil
 
 ## Introduction
 
-The purpose of the document is to describe the established vulnerability management workflow in the MYRTLE GROUP S.A. (“we” or “Cloudback”).
+The purpose of the document is to describe the established vulnerability management workflow in the MYRTLELABS S.A.S. (“we” or “Cloudback”).
 
 ## Overview
 

content/terms/_index.md

@@ -11,7 +11,7 @@ keywords: github backup, cloudback, github repository backup, github backup as a
 
 ## Introduction
 
-The Cloudback Terms of Service are between MYRTLE GROUP S.A. ("we" or "Cloudback") and the customer who orders the Cloudback services ("you" or "Customer"). By using the cloudback.it website or any services described on the cloudback.it website (collectively, "Service"), you are agreeing to be bound by the following terms and conditions ("Terms of Service").
+The Cloudback Terms of Service are between MYRTLELABS S.A.S. ("we" or "Cloudback") and the customer who orders the Cloudback services ("you" or "Customer"). By using the cloudback.it website or any services described on the cloudback.it website (collectively, "Service"), you are agreeing to be bound by the following terms and conditions ("Terms of Service").
 
 Violation of any of the terms below will result in the termination of your Account.  Cloudback prohibits certain conduct on the Service as described below. You understand and agree that Cloudback cannot be responsible for conduct or activity on the Service or for "Content" transmitted, posted, or stored  using the Service. You agree to use the Service at your own risk. For the purposes of this agreement "Content" means information, data files, written text, computer software, music, audio files or other sounds, photographs, videos or other images to which you may have access as part of, or through your use of, the Service.