Backup and Data Retention Policy

1. Hosting backup schedule

This period applies to customer hosting backups. The restore points available on a given date may vary depending on the backup set and the service. A continuous 7-day history, hourly restore points or indefinite archiving are not promised. Before requesting a restore, the customer may ask support to confirm the available dates and scope.

Taking backups daily is the intended operating procedure; any technical failure or missing backup is investigated, and the provider's liability in respect of its commitment is reserved. Backups do not constitute an absolute guarantee against data loss.

2. Scope and server products

Which files, databases, e-mail or configuration in a hosting account can be restored depends on the scope of the available backup set; the scope is verified before a restore. Content that was excluded or never backed up is not assumed to exist. The customer should separately confirm the scope it needs for critical applications.

VDS/VPS snapshots, server backups and operating system reinstallation are different operations. If a server package explicitly includes daily/weekly snapshots, its own description applies. The hosting backup frequency and the 2–7 day period do not automatically extend to all servers. Reinstallation may erase the data on the disk; the operation and its effect on data must be explained before approval.

3. Restore requests

The support ticket must state the service number, the requested date and the part you want restored. The available restore point and the effect of the operation are confirmed. A restore may overwrite changes made after the selected date; it is recommended that existing data be preserved separately before the operation. Backups are not provided to another customer or to any unauthorized person.

If paid work outside the package is required, the scope and fee are disclosed in advance. No promise that data “will definitely be restored” is made before it has been verified that a backup exists. Application consistency, the presence of malicious files in an old backup and database compatibility may require checks.

4. Additional protective measures by the customer

For its critical content, the customer should keep up-to-date backups and any necessary archives independently of the HOSTIMOR infrastructure. It is advisable to check the accessibility and restorability of these backups periodically. These recommendations do not remove the backup work undertaken by HOSTIMOR or its liability for its own fault.

If long-term retention, special disaster recovery or a copy in a different location is required, its scope and fee must be agreed as a separate service. This text does not claim that such an additional service is included in all packages.

5. Cancellation, expiry and deletion

Content should be exported before cancellation or termination of the service. When an active service ends, online access and access to backups may also end; standard backups are not a separate long-term archive. It is not guaranteed that a copy that has been deleted, or whose retention period has passed, can be recovered. Where appropriate, the customer is informed of the effects of the service ending and any migration/export request is considered.

Customer account, invoice, support and statutory traffic records are different from hosting file backups. These records are kept according to their purpose and the relevant legal retention obligations. When the conditions for retention no longer apply, appropriate deletion, destruction or anonymization is carried out; it is not envisaged that all records will be deleted on the same date as the technical hosting backup or kept indefinitely.

6. Contact and data rights

Backup and restore requests: destek@hostimor.com or the support system in the client area. Separate applications concerning personal data rights are governed by the KVKK Application Procedure and the Privacy Notice (KVKK).