Backup and Data Lifecycle Schedule

This Schedule forms part of the Eytak Consumer Terms of Service. It explains backup targets, storage charges, restores, suspension, recovery and deletion.

1. Important backup warning

1.1 Eytak backup features reduce the risk of data loss but do not eliminate it. A backup may fail, be incomplete, contain already-corrupted data, or be incompatible with a later server version.

1.2 You should keep an independent, current copy of important worlds and configuration outside Eytak. An Eytak backup is not an archive, legal record, or guaranteed disaster-recovery service.

1.3 We do not exclude responsibility that cannot lawfully be excluded. If data loss results from our failure to use reasonable care and skill, your statutory rights remain available.

2. Automatic backup targets

2.1 Where backups are enabled, we target one automatic backup per day. This is an operational target, not a guarantee that a backup will complete every day.

2.2 Subject to successful creation and available storage, the target retention is:

2.3 Older snapshots may be pruned when the target count is exceeded. Failed or incomplete attempts do not count as successful retained snapshots and do not themselves generate backup-storage charges.

2.4 We may stagger backup times, pause jobs during incidents, or reschedule a backup to protect node stability.

3. Manual backups

3.1 The panel may allow an authorised user to request a manual backup. A request is not confirmation that the backup completed.

3.2 Completion status should be checked in the panel before relying on the backup or making a destructive change.

3.3 Manual backups count toward storage usage and may count toward or be subject to the plan's retention limit as stated in the panel.

4. Storage architecture and charging

4.1 Backup objects may be stored with a specialist storage provider in one or more geographic locations. We may retain a separate cold-vault copy to reduce the risk that a node compromise destroys both live data and the latest backup.

4.2 Only successfully stored bytes are charged. Every separately retained copy that you can restore from consumes storage and is measured at the backup rate in the Usage and Billing Schedule. The isolated disaster-recovery copy described in clause 4.1 is kept for our own resilience, is not available to you for restoration, and is not charged to you — consistent with clauses 5.3 and 10.2.

4.3 Checksums or similar integrity checks reduce transfer-error risk but do not guarantee that application-level data is complete or usable.

4.4 Backup storage continues to accrue charges while backup objects are retained, including while the Minecraft process is stopped or frozen.

5. Turning backups off

5.1 You may turn backups off for a server where the panel permits.

5.2 Turning backups off stops new scheduled backups and stops customer backup-storage charges at the confirmation timestamp. So that switching backups off by mistake is recoverable, the retained Eytak backup objects for that server are then held, unbilled, for up to 72 hours before deletion begins; turning backups back on within that period keeps them. Permanently deleting a server is different and no such period applies — see clause 9.2.

5.3 The panel must warn you that this action removes restore points. Residual disaster-recovery copies may remain temporarily as described in clause 10, but they are not available for ordinary restoration and are not billed to you.

6. Restores

6.1 A restore replaces or modifies live server data and may cause permanent loss of newer changes. You must review the selected snapshot and confirmation warning before proceeding.

6.2 We may create a precautionary copy before a restore where technically feasible, but we do not guarantee one unless the panel confirms its successful creation.

6.3 Restore time depends on backup size, node and storage availability, network conditions and Minecraft content. Any estimate is non-binding unless expressly agreed otherwise.

6.4 A restore may fail because an object is unavailable, corrupt, incomplete, too large or incompatible. We will use reasonable care and skill in operating the restore function and will investigate a reported failure.

7. Operational states are not deletion

7.1 Stopping, sleeping, hibernating or billing-freezing a server does not delete its persistent world or retained backups.

7.2 A server frozen at an execution freeze threshold or for failed payment remains stored and continues to generate persistent disk and backup-storage charges until termination, deletion or the start of the free recovery period.

7.3 A temporary Acceptable Use Policy or security investigation does not by itself authorise permanent deletion, except where deletion is required by law or reasonably necessary to prevent serious continuing harm and less intrusive measures are insufficient.

8. End-of-service recovery period

8.1 When a plan ends at the close of its billing period, or is terminated after seven days of non-payment, we retain a recoverable copy of the affected Service Data for 168 hours unless you previously confirmed immediate permanent deletion. The termination confirmation will state the start and expiry timestamps in UTC.

8.2 During the recovery period:

• the Minecraft server does not run;
• no new CPU or RAM usage is charged;
• we do not charge additional persistent-disk or backup-storage fees solely for the recovery copy;
• ordinary panel access may be restricted; and
• you may request one standard export or restoration through support.

8.3 Restoration requires an active paid plan and may require resolution of outstanding undisputed charges. An outstanding amount does not by itself prevent one standard export of recoverable Service Data, although we may require identity verification and may restrict an export that would be unlawful, unsafe or disclose another person's protected data.

8.4 Recoverability during the 168-hour period is subject only to pre-existing corruption, a legal prohibition or a serious security condition that makes restoration or export unsafe. No recovery is available after the stated UTC expiry timestamp.

8.5 The recovery period is a last-resort convenience and not a replacement for your own export or backup before cancellation.

9. User-requested permanent deletion

9.1 The panel may offer Delete server permanently or equivalent wording. This is different from stopping a server or cancelling renewal.

9.2 If you complete a clear, authenticated and irreversible-deletion confirmation, we will immediately make the server unavailable, stop customer billing for that server's resources, and initiate deletion from chargeable active systems of the container, world volume, configuration, routes, Minecraft console and game logs, and associated available backups. The 72-hour period in clause 5.2 does not apply: deletion of those backup objects begins at the same time, because a deleted server cannot be restored and the period would protect nothing. There is no seven-day recovery period for that server.

9.3 We may require re-authentication or other verification before carrying out a high-risk deletion request.

9.4 Resource charges stop at the timestamp of the confirmed permanent-deletion request. Deletion does not cancel or refund the current plan base fee and does not erase valid charges already incurred.

10. Residual copies and legal retention

10.1 Deletion first removes data from active use and makes it unavailable through ordinary product and support functions.

10.2 Encrypted or access-restricted residual copies may remain in system-level backups until overwritten under our backup rotation, for no longer than 30 days unless clause 10.3 applies. They are isolated, are not used to provide the Service and are not restored except where necessary for disaster recovery, security investigation or legal compliance.

10.3 We may retain particular data longer where reasonably necessary to comply with law, preserve evidence, establish or defend legal claims, prevent fraud or respond to a binding order. Access will be limited and the data deleted when the reason ends.

10.4 Billing, consent, security and transaction records have separate retention periods described in the Privacy Notice and are not Minecraft Service Data available for restoration.

11. Exports

11.1 Where an export function is available, you should export important data before deleting a server or allowing a plan to end.

11.2 Export availability, format and maximum size may depend on technical limits. We will not claim that SFTP or a complete filesystem export is available unless the product actually provides it.

11.3 Contact support before the plan ends if the panel does not provide an export you reasonably need. We will use reasonable efforts to assist, but a custom export is not guaranteed where it is technically impossible, unlawful or would compromise another user or the Service.

12. Security incidents

12.1 If we reasonably suspect corruption, malware, unauthorised access or destructive activity, we may preserve a relevant snapshot or restrict restoration while investigating.

12.2 We may refuse to restore a backup that would reintroduce malware, illegal material or a serious security vulnerability. Where possible, we will explain safer available options.