This Schedule forms part of the Eytak Consumer Terms of Service. Capitalised terms have the meanings given in the Consumer Terms.
1. Scope of the managed Service
1.1 Eytak provides a managed platform for creating and operating Minecraft server instances. Depending on the features shown in your plan and panel, the Service may include:
- automated server provisioning;
- a web control panel;
- start, stop, restart, sleep and wake controls;
- server metrics, logs and console access;
- configuration controls for supported files and settings;
- supported software, loader and Minecraft version selection;
- installation of supported content from Modrinth or CurseForge;
- an Eytak subdomain and optional custom-domain routing;
- backups and restores under the Backup and Data Lifecycle Schedule;
- workspace collaboration and role-based access; and
- customer support.
1.2 The Service supports Minecraft Java Edition server software unless the order summary expressly states otherwise. References elsewhere on the Website to another game or edition do not add it to your order.
1.3 General SFTP access, unrestricted filesystem access, a complete file manager, a particular mod or plugin, migration assistance, or any other feature is included only if it is expressly shown as available in your plan or authenticated panel.
2. Server creation and provisioning
2.1 When creating a server, you may be asked to choose a server name, Minecraft version, software or loader, region, address label, content and settings.
2.2 Provisioning is subject to available capacity, compatible software and a valid billing account. Provisioning times shown on the Website are estimates unless expressly stated to be guaranteed.
2.3 We may select or move the underlying node, host port, container, network route or storage location where reasonably necessary for capacity, maintenance, resilience, security or legal compliance. We will use reasonable care to minimise avoidable disruption and data loss.
2.4 A displayed resource figure may represent a configurable ceiling rather than continuously reserved or consumed capacity. Charges are determined under the Usage and Billing Schedule, not solely by the displayed ceiling.
3. Supported software and versions
3.1 Supported server software may include Vanilla, Paper, Purpur, Spigot, Fabric, Forge, NeoForge or other software displayed in the creation flow. Availability can vary by Minecraft version and region.
3.2 Minecraft, Java, loaders, mods and plugins change independently of Eytak. A version or combination that worked previously may become incompatible, unsupported, insecure or unavailable.
3.3 We may withdraw an unsafe or end-of-life version, require an update, or temporarily block a known harmful component. Where reasonably possible, we will give notice and offer a supported alternative.
3.4 You are responsible for reviewing compatibility warnings and testing material changes. We recommend creating a current backup before changing a Minecraft version, server software, loader, modpack, mod, plugin or raw configuration file.
4. Minecraft terms and account authentication
4.1 You must obtain and maintain all Minecraft accounts and licences required for your use and your players' use. You must comply with the current Minecraft End User Licence Agreement, Usage Guidelines and other applicable Microsoft or Mojang rules.
4.2 Server creation requires affirmative acceptance of the Minecraft EULA. We may record the account, date, wording, linked EULA version or URL, and technical evidence of acceptance.
4.3 The panel may expose Minecraft's online-mode setting for legitimate technical uses, such as operation behind a properly configured authenticated proxy or in another setup permitted by Microsoft or Mojang. Disabling account authentication does not authorise unlicensed, pirated or otherwise unlawful access to Minecraft. You remain responsible for ensuring that every use is lawful and permitted by the applicable Minecraft terms.
4.4 Eytak is an independent hosting provider. It is not affiliated with, authorised by, sponsored by or endorsed by Microsoft Corporation or Mojang Studios. Minecraft is a trademark of the Microsoft group of companies.
5. Mods, plugins, modpacks and third-party content
5.1 Catalog results and content metadata may be supplied by Modrinth, CurseForge or another third party. Availability in the panel does not mean that Eytak owns, endorses, audits or guarantees that content.
5.2 You must comply with the author, platform and distribution licences applying to each item. You must not use the Service to obtain or distribute content where you do not have the necessary rights.
5.3 We may filter or refuse content that is identified as non-distributable, malicious, unlawful, incompatible or contrary to the Acceptable Use Policy. Automated checks are not comprehensive and do not transfer responsibility for your selection to Eytak.
5.4 Third-party content may cause crashes, corruption, security issues, excessive resource use or incompatibility. We will use reasonable care and skill in operating the installation feature, but we do not guarantee third-party content itself.
5.5 Changing installed content may require container recreation, file changes or a restart. Persistent world storage is intended to be retained during a supported content update, but you should maintain a current backup before proceeding.
6. Configuration and console access
6.1 The panel may expose supported configuration fields, selected raw configuration files and console commands. It does not necessarily expose every file or server function.
6.2 You are responsible for commands and configuration changes submitted by you or an authorised workspace member. We may validate, reject or limit a command or change where reasonably necessary for security, service stability or compliance.
6.3 Some changes require a restart and may not take effect until one occurs. A restart can disconnect players and may interrupt unsaved game activity.
6.4 Where supported, we may create a precautionary copy before overwriting a configuration file. Such a copy is not a substitute for the backup feature or your independent backup.
7. Sleep, stop and wake behaviour
7.1 A server may have the following operational states:
- running, when the Minecraft process is active;
- warm sleep, when execution is frozen and memory may be moved to swap storage;
- hibernating or stopped, when the Minecraft process is not running but persistent data remains;
- billing frozen, when access is restricted because an execution freeze threshold or payment rule has been triggered; or
- pending deletion or deleted.
7.2 Automatic sleep may be enabled by default. You may be able to change it in the panel. Warm sleep is intended to reduce CPU and RAM use, but swap and persistent disk remain chargeable under the Usage and Billing Schedule.
7.3 Wake-on-connect may attempt to start a sleeping server when a player connects. Startup time depends on the Minecraft version, world and installed content. A Minecraft client may time out before a large or heavily modded server becomes ready.
7.4 Manually stopped, billing-frozen, suspended or terminated servers do not necessarily wake automatically.
8. Server addresses and domains
8.1 An Eytak address label is licensed for use with the Service and is not sold to you. It must satisfy technical and Acceptable Use Policy requirements and remain unique.
8.2 We may reclaim an address when the related server is deleted or the Service ends. We may rename, suspend or remove an address that infringes rights, impersonates another person, misleads users, or creates a legal or security risk.
8.3 To use a custom domain, you must control it and complete the requested DNS verification. You are responsible for registration, renewal, DNS correctness and third-party registrar charges.
8.4 We do not guarantee continuing ownership or availability of a third-party domain name or the global timing of DNS changes.
9. Workspaces and team members
9.1 The account owner may invite other people aged 18 or over and assign roles. Permissions displayed in the panel determine the actions available to each role.
9.2 The owner is responsible for choosing appropriate roles, removing access when no longer needed, and ensuring authorised users comply with the agreement.
9.3 A workspace is a collaboration and access-control feature. Unless the panel expressly states otherwise, billing responsibility remains with the account that purchased the plan.
9.4 Deleting a workspace does not itself cancel a plan or delete a server unless the confirmation screen expressly says that it will.
10. Metrics, logs and player information
10.1 We may collect server metrics, player counts, actions, console output and logs to operate, meter, secure and support the Service.
10.2 Minecraft logs and worlds may contain player names, identifiers, IP addresses, chat or other personal data. You must provide any information required by law to your players and must have a lawful basis for your own processing of that information.
10.3 You must not use console, logs, webhooks or API access to unlawfully monitor, profile, harass or discriminate against players.
10.4 Retention periods for operational logs and metrics are described in the Privacy Notice or panel and may differ from the Service Data recovery period.
11. APIs and webhooks
11.1 API tokens and signed webhooks are optional technical features. You must protect token and webhook secrets, use only the scopes needed, and promptly revoke compromised credentials.
11.2 You are responsible for the security and lawfulness of the destination to which you direct a webhook. Delivery attempts may disclose event and server metadata to that destination.
11.3 We may apply reasonable rate limits, rotate signing methods on notice, or suspend an integration that threatens security or stability.
12. Support boundaries
12.1 We support the Eytak platform and will use reasonable efforts to diagnose supported Minecraft configurations. We do not guarantee that we can repair every world, mod, plugin or third-party configuration.
12.2 We may ask you to reproduce an issue using supported software, disable incompatible third-party content, provide relevant logs, restore a backup or approve a restart.
12.3 With your request or where otherwise permitted by the Consumer Terms, authorised support personnel or support systems may access relevant server details, logs and configuration to investigate an issue. Access will be limited to what is reasonably necessary.
13. Security and abuse response
13.1 We may isolate a container, block traffic, revoke credentials, disable a mod or plugin, or suspend a server where reasonably necessary to address malware, active exploitation, unauthorised access, attacks or material network harm.
13.2 We will distinguish temporary containment from permanent deletion and, where lawful and safe, explain the action and available remedy.
13.3 Reports about unlawful or infringing server content should be sent to abuse@eytak.com with enough information to identify the server, content, legal right or risk, and the reporter's contact details.