Usage and Billing Schedule

This Schedule forms part of the Eytak Consumer Terms of Service. It explains plan fees, metered usage, included credit, overage, optional execution freeze thresholds and payment enforcement.

1. Currency, billing unit and taxes

1.1 We bill in pounds sterling (GBP) and Turkish lira (TRY). The currency that applies to you is the one shown on the checkout page before you place your order. The merchant of record selects it from your location at that point, and it is then fixed for the life of that subscription: it does not change if you move, and we do not convert an existing subscription from one currency to the other. Clause 2 and clause 3 state the fees and rates for each currency, and the figures for your currency are the ones that apply to you.

1.1.1 A subscription's currency is also the currency of everything derived from it: included credit, metered usage, any overage, any refund and any proportionate amount payable under clause 13.

1.2 Resource rates are expressed as a price per unit for a standard 30-day equivalent of 2,592,000 seconds. Metered charges accrue per second as follows:

charge = measured units x elapsed billable seconds x 30-day unit rate / 2,592,000

1.3 Usage is calculated with greater precision than the smallest unit of your billing currency. The dashboard and invoice may round aggregated totals to that smallest unit. We do not intentionally round every individual second up to a whole unit.

1.4 Polar calculates and adds any applicable VAT, sales tax or similar transaction tax at checkout or invoicing. Polar shows the tax-inclusive initial charge before purchase and the tax-inclusive total of later overage on the relevant invoice.

2. Plans and Packages

If your billing currency is GBP:

If your billing currency is TRY:

2.0 The two currencies are separate published price lists, not a conversion of one another. The lira fees are lower in real terms than the sterling fees, deliberately, and neither is derived from the other by an exchange rate. The lira resource rates in clause 3 are derived from the sterling ones at the rate stated in clause 11.4, which is what makes the included credit in each currency buy the same proportion of that currency's fee.

2.1 The base fee pays for access to the plan and includes the stated infrastructure credit. It is not a refundable deposit and is not determined solely by actual resource use.

2.2 Unused included credit expires at the end of the applicable trial or billing period. It does not roll over, transfer to another account or have cash value.

2.3 Promotional credit may have additional expiry or eligibility conditions disclosed when it is granted.

2A. Fixed-price Packages

2A.1 A Package is an alternative to the plans in clause 2 and is bought for one server. It fixes the resources that server is permitted to use, it runs for a fixed period of 30 days from activation, and its price is paid once, when you place the order. A Package is not metered: it includes no infrastructure credit, consumes none, accrues no usage charge and cannot accrue overage, whether the server is running, sleeping or stopped. Clauses 3 to 7 of this Schedule — resource rates, what is measured, measurement source and intervals, application of credit and overage, and the optional execution freeze threshold — do not apply to a Package or to a server running on one. The currency of a Package order is the one shown at checkout before you place that order, as described in clause 1.1, and is fixed for that order.

If your billing currency is GBP:

If your billing currency is TRY:

The price stated is the whole price of the 30-day period and is payable once, before the server is activated. Polar calculates and adds any applicable tax as described in clause 1.4. The two currencies are separate published price lists in the same sense as clause 2.0: the lira figures are not the sterling ones converted, and the rate in clause 11.4 has no part in producing them.

2A.2 A Package does not renew automatically. We do not keep a payment method on file for it, and nothing is charged when its period ends. To continue, you place a new order, which is an ordinary order under clauses 4.3 and 10 of the Consumer Terms with its own pre-contract information, its own express early-performance request and its own 14-day statutory cancellation right. A renewal order may be for a different Package from the one it renews. The 30 days it buys run from the later of the time the order is placed and the end of the period being renewed, so renewing before your current period ends adds 30 days to that period and loses you nothing.

2A.3 Reminder. We will send one reminder to the email address on your account within 3 days before the end of the period, stating when the period ends and what happens if you do not renew. External email delivery may be delayed or fail for reasons outside our reasonable control, so the end of the period is also shown in the panel throughout, and the panel is the primary place to check it.

2A.4 When the period ends. If no renewal order has been placed by the end of the period, the server stops. Nothing further is charged: there is no payment method on file and no amount becomes due for the Package or for anything after its period ends. Your server and its data are then kept, stopped, for 7 days at no charge, so that you can renew and continue with the data you had; a renewal order placed within those 7 days makes the server available again. If none has been placed when they expire, the Service for that server ends and the recovery period in section 8 of the Backup and Data Lifecycle Schedule applies, so your Service Data remains recoverable for a further 168 hours and is deleted after that.

2A.5 Sleep. A Package server sleeps when no player is connected and may be woken when a player connects, as described in section 7 of the Minecraft Service Schedule. Sleeping neither shortens nor extends the 30-day period and does not change the price. The period runs in calendar time from activation, and the price is the same whether the server is played on every day of it or none.

2A.6 The figures in 2A.1 are a ceiling, not an allocation. They are the maximum CPU, memory and disk the server is permitted to use. Nothing is reserved for you on the node, nothing is refunded for what you do not use, and the server does not scale beyond the ceiling automatically. Exceeding a ceiling never becomes an extra charge: nothing on a Package is metered, so there is nothing to charge for. The CPU and memory figures are applied to the server as hard limits, and the disk figure is the storage we undertake to keep for the server for the period. To run beyond a ceiling you order a larger Package (clause 2A.2) or a metered plan under clause 2.

2A.7 Moving a Trial server to a Package. While a server is on the Trial, you may place a Package order for that server instead of an order for a new one. A server is on the Trial while the Trial runs and, once it has ended, for as long as the server is being kept, stopped, under section 8 (including under clauses 8.4 and 8.5 for a Trial begun before 14 September 2026), until the Service for it ends. The order is an ordinary Package order under clauses 2A.1 and 2A.2, with its own pre-contract information, its own express early-performance request and its own 14-day statutory cancellation right. When the Package is activated:

• the server keeps its Service Data — its world, configuration, mods, plugins and other content — and its address label;
• the resources stated for that Package in clause 2A.1 become the server's ceilings under clause 2A.6;
• the Package's 30-day period runs from activation; and
• from then on the server is a Package server. The Trial ends for that server only: it no longer draws on the trial credit, the end of the Trial does not stop it or end its Service, and clauses 6.5 and 8.1 to 8.5 of this Schedule and clause 8.6 of the Backup and Data Lifecycle Schedule no longer apply to it. What happens when its period ends is governed by clause 2A.4.

Any other server linked to the same billing account stays on the Trial, and the Trial's credit, its end and what happens to a server after it ends continue to apply to that server exactly as before. Only a server on the Trial can be moved in this way. A server on Starter or Pro cannot: it stays metered under clauses 3 to 7 for as long as that plan runs, and a Package ordered on such an account is for a new server. If you exercise the statutory cancellation right for an order under this clause, the Package period ends at the time of cancellation and clause 2A.4 applies from then, as it would at the end of any period: the server stops, is kept, stopped, for the time stated there, and the recovery period in section 8 of the Backup and Data Lifecycle Schedule follows. The server does not return to the Trial. Any amount due for the time the Package ran is calculated under clause 13.6.

3. Resource rates

If your billing currency is GBP:

If your billing currency is TRY:

The per-second figures in this table are rounded for display. Charges are calculated from the 30-day equivalent rates using the formula in clause 1.2, without replacing those rates with the rounded display figures.

3.1 For billing under this Schedule, one GB means 1,073,741,824 bytes (2^30 bytes). The dashboard and invoice will use the same convention.

3.2 Warm-sleep swap is charged at the persistent-disk rate rather than the RAM rate.

3.3 We do not charge for a failed backup object that was not successfully stored. Each successfully retained copy that you can restore from consumes storage and counts toward backup storage usage. The isolated cold-vault copy described in clause 4.1 of the Backup and Data Lifecycle Schedule does not: it is kept for our own resilience, is not available to you for restoration, and its bytes are not counted or charged to you.

4. What is measured

4.1 CPU: the average CPU cores actually measured for the Minecraft container during the billable interval while it is executing.

4.2 RAM: the average memory bytes actually measured for the Minecraft container during the billable interval while it is executing.

4.3 Persistent disk: the measured bytes occupied by persistent server storage. Persistent disk remains chargeable while a server is running, sleeping, hibernating, manually stopped or billing-frozen because the data continues to be stored.

4.4 Warm-sleep swap: measured memory pages moved to swap or equivalent persistent storage while the server is in warm sleep.

4.5 Backup storage: the measured bytes of successful backup objects retained for the account that you can restore from, including separately retained restorable copies, and excluding the isolated cold-vault copy as explained in clause 3.3.

4.6 A stopped server normally stops generating CPU and RAM charges, but persistent disk and retained backups continue to accrue charges until deleted. A warm-sleep server normally has little or no CPU or RAM charge, while persistent disk and measured swap remain chargeable.

4.7 Usage caused by a restart, update, backup, restore or customer-requested support operation may be metered where the resources are actually consumed.

5. Measurement source and intervals

5.1 Eytak's internal metering ledger, based on measurements reported by the hosting node and storage systems, is the primary record of resource usage. It is not conclusive if you provide credible evidence of an error.

5.2 Under normal operation, usage is aggregated in billing windows of no more than 60 seconds. Charges within each window use the actual elapsed billable seconds and average measured units; they are not rounded up to a full minute. A dashboard figure may lag behind live use.

5.3 If a valid sample is unavailable, we will not estimate CPU or RAM usage from the configured maximum merely to increase a charge. We may use reliable storage-system records to measure persistent disk and backup bytes while a process is stopped.

5.4 We may correct an obvious metering, calculation or display error. A correction will not impose a retroactive charge where doing so would be unfair or contrary to applicable law. We will explain a material correction.

5.5 Meter records are kept for the period stated in the Privacy Notice and for as long as reasonably needed to resolve billing disputes and meet legal obligations.

6. Application of credit and overage

6.1 Eligible metered usage is first deducted from available infrastructure credit.

6.2 On a paid plan, when credit reaches zero, subsequent eligible usage becomes overage. Polar invoices and collects overage on the following monthly subscription invoice. The applicable timing will be displayed before purchase and in the billing area.

6.3 Overage is unlimited by default on a paid plan. Once you are on a paid plan, merely exhausting included credit does not stop a server. You must enable an execution freeze threshold, stop or delete resources, or cancel the plan if you do not want further eligible usage to accrue. The Trial works the other way round: it cannot accrue overage, and clause 6.5 applies instead.

6.4 We will send usage-alert emails when measured eligible usage reaches 80% and 100% of the included credit granted for the current billing period. Delivery may be delayed or fail for reasons outside our reasonable control. The dashboard is the primary place to review current usage.

6.5 The Trial cannot accrue overage. There is no payment method on file during a Trial, so there is nothing an overage could be charged to. When the trial credit is exhausted, or when the Trial's 24 hours are up, whichever comes first, the Trial ends and every server linked to the billing account stops, as set out in clause 8. Nothing further is metered or charged, including for persistent disk or retained backups, from that point. Ordering a paid plan grants that plan's included credit and makes the servers available again.

7. Optional execution freeze threshold

7.1 You may set an account-level monthly overage execution freeze threshold in the billing panel. The threshold is measured against aggregate overage from all resource types and servers linked to the billing account. It has no effect during the Trial, which cannot accrue overage and is governed by clauses 6.5 and 8 instead.

7.2 We will send an email when measured overage reaches 80% and 100% of the selected threshold. External email delivery may still be delayed or fail as explained in the Consumer Terms.

7.3 At 100%, we will freeze all servers linked to the billing account. CPU and RAM execution charges then stop, but persistent disk and retained backup storage continue. Because those storage charges continue, this threshold is not a maximum bill cap. We will retain sufficient panel access for you to view and delete chargeable storage or change the threshold.

7.4 The threshold is enforced at metering intervals. Under normal operation, chargeable CPU and RAM execution above the threshold is limited to no more than 120 seconds of use caused by measurement and enforcement delay. If a telemetry incident would cause a larger execution overshoot, we will not charge the execution portion above that allowance. Continuing disk and backup storage, tax and valid corrections are not part of that execution allowance and can increase the final amount.

7.5 You may raise or remove the threshold in the panel. An affected server may then be unfrozen, unless it is also stopped, suspended or frozen for another reason.

7.6 At the start of a new billing period, the overage counter resets. Servers frozen solely because of the cap may be made available again, subject to account and payment status.

8. End of the Trial

8.1 The Trial ends when its credit is used or 24 hours after it began, whichever comes first. When it ends, every server linked to the billing account stops. Nothing is charged: the Trial has no payment method, no plan begins, and no amount becomes due for the Trial itself or for anything after it. The time at which the Trial will end is shown in the billing area from the moment it begins.

8.2 A Trial does not convert into a paid plan and we do not select one for you. Your servers are kept, stopped, so that you can decide. To continue, you order Starter or Pro. That is an ordinary order under clauses 4.3 and 10 of the Consumer Terms: the plan's recurring base fee for your billing currency (clause 2) plus applicable taxes is charged when the order is placed, the plan's included credit is granted, and your servers are made available again with their data. The pre-contract information in clause 7.3 of the Consumer Terms is shown before you place that order, and the statutory cancellation right and the proportionate charge in clause 13 apply to it as they do to any other order. Instead of a plan, you may move an individual server to a Package under clause 2A.7.

8.3 If no paid plan has started within 168 hours after the Trial ends, the Service ends. The recovery period in section 8 of the Backup and Data Lifecycle Schedule then applies to the Service Data, so it remains recoverable for a further 168 hours after the Service ends and is deleted after that. No persistent-disk or backup-storage charge accrues at any point after a Trial ends. Ordering Starter or Pro during the recovery period is the restoration route described in clause 8.3 of that Schedule.

8.4 Trials begun before 14 September 2026. A Trial that began before 14 September 2026 keeps the terms it began on, which were as follows and which apply to that Trial in place of clauses 2, 6.5 and 8.1 to 8.3. The Trial ran in two stages. The first stage needed no payment method, included GBP 0.50 (or TRY 39 for an account billed in lira) of infrastructure credit once, and ended when that credit was used or after 14 days, whichever came first. Putting a payment method on file began the second stage, which added a further GBP 0.50 (or a further TRY 39) of credit once, together with a further 14 days. On starting the Trial the customer selected the paid plan it would continue on, Starter by default or Pro. A Trial with no payment method on file could not convert and simply stopped, with clause 6.5 as then in force applying to the stopped servers. A Trial with a payment method on file converted automatically, unless cancelled before the trial expiry time shown in the billing area, into the selected plan at that plan's recurring base fee for the account's billing currency plus applicable taxes, with no trial usage to settle because the Trial could not exceed its credit. The expiry time and conversion price were displayed before the order was placed, in the order confirmation and in the billing area. Clause 8.3 does not apply to a Trial under this clause: its servers, if stopped, remain subject to the terms it began on, and the Service does not end merely because of the passage of time after it stopped. Clause 8.5 sets out the only way in which the Service for such a Trial may end.

8.5 Ending a Trial under clause 8.4. We may end the Service for a Trial under clause 8.4 whose servers are stopped and on which no paid plan has started, but only after individual notice to you. We will send that notice to the email address on your account and it will state the date on which the Service will end, which will be at least 30 days after the notice is sent. Nothing is charged before, on or after that date. If you order Starter or Pro before that date, or put a payment method on file and your Trial continues under clause 8.4, the Service is not ended and your servers are made available again with their data. If neither has happened by the date stated, the Service ends and the recovery period in section 8 of the Backup and Data Lifecycle Schedule applies, so your Service Data remains recoverable for a further 168 hours and is deleted after that. We will not end a Service under this clause without having sent you that notice.

9. Renewal and cancellation

9.1 Starter and Pro renew for successive monthly billing periods until cancelled.

9.2 An ordinary subscription cancellation request prevents the next renewal and takes effect at the current period end. The plan fee is not charged for a later period, but usage and storage continue through the effective end and while chargeable data remains stored under this Schedule. Statutory cancellation under clause 10 of the Consumer Terms is immediate.

9.3 If you permanently delete all servers and backups before the period ends, metered resource charges for those resources stop at the timestamp of the confirmed deletion request, but the current period's base fee is not automatically refunded.

9.4 Rights to cancel during a statutory cooling-off period or because of a non-conforming Service are not restricted by this clause.

9.5 Clauses 9.1 to 9.3 are about Starter and Pro. A Package is not a subscription: it does not renew, there is nothing to cancel to prevent a renewal, and clause 2A governs what happens when its period ends. Permanently deleting a Package server before its period ends stops nothing being metered, because nothing was, and does not refund the Package price. Your statutory cancellation right is unaffected and is priced by clause 13.6.

10. Failed payment process

10.1 If a payment fails, Polar or Eytak may retry it and send notices. We will not state a fixed retry count unless the checkout and Polar configuration support it.

10.2 At 72 hours overdue, affected servers will be billing-frozen unless payment has completed or enforcement is on hold for a genuine payment dispute. Persistent storage charges continue until the seven-day termination point or earlier deletion.

10.3 At seven days overdue, the affected Service will be terminated unless payment has completed or enforcement remains on hold for a genuine dispute. Ordinary usage and storage charges stop at that point, and the Service enters the no-additional-charge seven-day recovery period in the Backup and Data Lifecycle Schedule. Amounts validly incurred before termination remain due.

10.4 A recoverable copy remains available during the recovery period subject to the conditions in the Backup and Data Lifecycle Schedule. Recovery is not available after the period expires.

11. Price changes

11.1 We will give at least one complete billing period's advance notice of a material increase to a base fee or resource rate, or to a Package price, except where a faster change is required by law or tax rules outside our control.

11.2 A new rate applies only prospectively from the date stated in the notice. You may cancel renewal before it takes effect.

11.3 Tax changes made by Polar may take effect when required by the relevant tax rule.

11.4 The lira resource rates in clause 3 are derived from the sterling ones at a stated rate of TRY 65 per GBP 1. That rate is a published figure in this Schedule, not a live exchange rate: it does not move on its own, and no charge of yours changes because a market rate changed during your billing period.

11.5 We may revise the rate in clause 11.4, and will not do so more often than once per calendar quarter. A revision that increases a lira resource rate is a resource-rate increase and receives the notice required by clause 11.1 before it takes effect. A revision that decreases one may take effect immediately. Revising it does not change the lira plan fees in clause 2, which are a separate published price list (clause 2.0).

12. Billing questions and meter disputes

12.1 Contact support@eytak.com promptly if you believe a measurement or invoice is wrong. Include the invoice or order reference, server, period, disputed resource and reason.

12.2 We will review relevant ledger entries, node or storage measurements, account actions and known incidents. Polar may need to decide or process the transaction outcome as merchant of record.

12.3 Raising a genuine dispute does not waive your legal rights. You should continue paying undisputed amounts where possible.

12.4 Nothing in this Schedule limits a statutory remedy for an incorrect charge, unauthorised payment or non-conforming Service.

13. Proportionate charge on statutory cancellation

13.1 This section applies only where you validly requested early performance and then exercise a statutory cancellation right during the 14-day period.

13.2 For Starter or Pro:

• the proportionate base fee is the monthly base fee multiplied by the elapsed service seconds and divided by the total seconds in that billing period;
• the proportionate included credit is the plan's monthly included credit multiplied by the same elapsed fraction; and
• the resource component is eligible metered usage supplied up to cancellation, less that proportionate included credit, with a minimum of zero.

The amount due is the proportionate base fee plus the resource component and applicable tax. This prevents the same included usage from being charged once through the plan component and again as resource use.

13.3 During the Trial, the base-fee component is zero and the trial credit remains available. Because the Trial cannot accrue overage (clause 6.5) and never converts into a paid plan (clause 8.2), no amount is due for the Trial itself under this section. A Starter or Pro plan ordered after a Trial is a separate order, and the calculation in clause 13.2 applies to it from its activation to cancellation. For a Trial governed by clause 8.4 that converted into a paid plan, clause 13.2 applies to that plan from the conversion timestamp.

13.4 Example, for a subscription billed in GBP: if a Pro billing period contains 30 days and statutory cancellation occurs exactly three days after Pro activation, the elapsed fraction is 10%. The plan component is GBP 1 and the included credit for that period is GBP 1. If eligible measured usage during those three days is GBP 1.40, the resource component is GBP 0.40 and the total before tax is GBP 1.40.

13.4.1 The same arithmetic applies to a subscription billed in TRY, using that currency's figures throughout: on the same facts the plan component is TRY 39.90, the included credit for that period is TRY 39.90, and measured usage of TRY 55.86 gives a resource component of TRY 15.96 and a total before tax of TRY 55.86.

13.5 No amount is charged under this section if we started the Service during the cancellation period without the express early-performance request required by law.

13.6 Packages. A Package is not metered and includes no credit, so the calculation in clause 13.2 reduces to one term. If you validly requested early performance and then exercise the statutory cancellation right for a Package order, the amount due is the Package price multiplied by the seconds of service elapsed and divided by the 2,592,000 seconds of the 30-day period:

charge = Package price x elapsed seconds / 2,592,000

There is no resource component and no credit apportionment, because a Package meters nothing and includes nothing to apportion. Elapsed seconds run from activation of the period being cancelled. For a renewal ordered before the previous period had ended, they run from the end of that previous period, so a renewal you paid for early and then cancelled before it began carries no charge at all. Nothing is due under this clause if we started the Service without the express early-performance request required by law (clause 13.5), and nothing is due for an order that was paid for but never provisioned. The balance of the price is reimbursed as described in clause 10.6 of the Consumer Terms.

13.6.1 Example, for an Iron Package billed in GBP: the price is GBP 8.99 for the 30-day period, and statutory cancellation exactly three days after activation makes the elapsed fraction 10%, giving an amount due of GBP 0.90 before tax, with the rest of the price reimbursed.

13.6.2 The same arithmetic applies to a Package billed in TRY, using that currency's figures throughout: on the same facts, an Iron Package at TRY 269 gives an amount due of TRY 26.90 before tax.