Transition of Services Policy

Dated version: 21 Jan 2023

1. Transition of Services

The Client may migrate services in-house or to another service provider at any time following the completion of the Minimum Service Period. Because all subscription fees are non-refundable, we strongly recommend timing the migration to occur near the end of the current subscription term.

2. Provision of Migration Instructions

To facilitate a smooth transition, Yunolabs provides detailed instructions regarding the preparation steps and the technical specifications of the project. These instructions cover the backup of the database, media storage, and website code. The new provider is responsible for using these instructions to download the latest data snapshot and restore it to their own hosting infrastructure.

3. Infrastructure and Security Limitations

Because the setup of infrastructure, data restoration, and security protocols vary significantly between providers, Yunolabs does not provide setup or restoration services on external servers. We do not oversee third-party infrastructure and, therefore, cannot guarantee the security, stability, or quality of service once the data leaves our environment.

4. Domain Migrations

Domains must be registered for a minimum of 60 days to be eligible for migration. Upon request, Yunolabs will provide a transfer authorization (EPP) code. The Client is responsible for initiating the transfer process and bearing all associated costs.

5. Assistance and Support

Yunolabs provides the necessary migration instructions as part of the standard transition process. Should the Client require Yunolabs to perform additional migration tasks, these services may be engaged separately and will be quoted on an ad-hoc basis. Please note that Support Units may not be used to offset migration costs.

6. Security Responsibilities

Upon migrating in-house or to a new provider, the Client assumes full and sole responsibility for the security, maintenance, and updates of all migrated services and third-party integrations.

7. Retention of Assets, Data, and Files

Yunolabs will not maintain the project’s code, assets, and files after the transfer is completed. It is the Client’s responsibility to ensure all data is safely stored and backed up elsewhere before this window closes.

8. Third-Party Assets and Exclusions

The migration of third-party assets and integrations must be handled by the new service provider. Additionally, certain elements of the Website may include integrations whose ownership cannot be transferred. This includes proprietary third-party code or services owned by Yunolabs, such as UX tools (e.g., HotJar), cloud hosting accounts, content management services, or specific automation systems.

9. Right to Amend

Yunolabs reserves the right to amend or modify this Transition of Services Policy at any time. Such amendments may be necessary due to changes in our technical infrastructure, security requirements, or shifts in industry standards. Any updates to this policy will be reflected on the Yunolabs website.