Metrly Non-Payment Policy

This policy explains what happens when Metrly cannot collect an automatic payment for a paid Service. It is part of the Metrly Terms of Service, but it is written in plain language so you can understand the operational timeline and recovery steps.

The timeline at a glance

If an automatic payment fails, Metrly will notify you and begin the non-payment timeline at the first failed attempt. Approximately 72 hours after that attempt, affected servers will be powered off and suspended. Seven calendar days after the first failed attempt, unpaid servers and their data will be permanently deleted. Later retries do not restart these deadlines. Paying after deletion restores account billing eligibility but does not recreate deleted servers or data. Exact deadlines are displayed in the Metrly Console.

• First failed attempt: Metrly opens a non-payment case, emails your primary account address, and displays the exact UTC deadlines in the Console.
• About 48 hours after the first failure: Metrly sends a 24-hour power-off warning.
• Approximately 72 hours after the first failure: affected servers are powered off and billing-suspended. They cannot be restarted while the required balance remains unresolved.
• About six calendar days after the first failure: Metrly sends a final 24-hour deletion warning.
• Seven calendar days after the first failure: unpaid affected servers and their data are permanently deleted.

Retries do not restart the clock. If Stripe or Metrly retries the payment later, the original first-failure timestamp still controls. A later failed payment starts a new timeline only after the earlier balance has been fully resolved and the earlier non-payment case has been closed.

What is affected

“Affected servers” are the servers that the Metrly Console identifies as subject to the unpaid balance. The Console is the authoritative place to see which servers are included.

“Server data” includes server files, world and save data, databases, configuration files, logs, mods, plugins, scheduled tasks, and other data maintained for an affected server. All Metrly-hosted backups and snapshots associated with an affected server are also permanently deleted. A copy you exported and stored independently is not affected.

Deletion of affected servers does not delete your Metrly account. Metrly retains account records, invoice and payment history, policy-acceptance records, and security and audit history in accordance with its Privacy Policy, record-retention schedule, and applicable law.

How to stop pending deletion

Pay all required past-due amounts before the deletion timestamp displayed in the Console. A successful full payment cancels the pending billing deletion, removes the billing suspension, and restores access to an otherwise eligible server. You may need to power the server back on manually.

Pending, partial, disputed, reversed, or subsequently failed payments do not stop the timeline unless the Console explicitly shows that the required balance has been resolved. A bank or card dispute is not a cancellation request and does not pause enforcement.

Automatic renewal and your payment method

Metrly Services automatically renew until canceled. Metrly automatically charges the payment method on file for accrued usage and any other recurring fees disclosed before enrollment. Usage-based amounts can vary from one billing period to another. Estimates are not spending caps unless Metrly explicitly labels them as caps.

You are responsible for maintaining a valid payment method and sufficient funds. You can review payment methods, current usage, estimates, invoices, and deadlines in the Metrly Console.

Notices and controlling timestamps

Metrly sends non-payment notices to your primary account email address and displays them in the Console. We may use other channels when available. You are responsible for keeping a valid, monitored email address on your account. Failure to receive or read a notice does not change the deadlines displayed in the Console except where required by law.

All enforcement timestamps are calculated and stored in Coordinated Universal Time (UTC). The Console may additionally display your local time. The timestamp and time-zone designation shown for the deadline in the Console control.

Administrative holds

Metrly may grant an administrative hold, but holds are discretionary. A hold is valid only when the Metrly Console displays the hold and revised deadlines. A support ticket, email, chat, or verbal statement alone does not create a hold. If the Console does not show a revised deadline, plan around the original deadline.

Cancellation is separate

Voluntary cancellation and non-payment enforcement are different processes. A failed payment is not a cancellation request. To stop future usage, use the cancellation control for the affected server in the Metrly Console. Cancellation does not erase usage or another balance already incurred, and it does not restart an active non-payment deadline.

If payment happens after deletion

Paying all required amounts after deletion restores account billing eligibility once the payment is final, but it does not recreate deleted servers, files, databases, backups, snapshots, or other data. You must create a new server and restore from your own independently stored copy, if you have one.

Getting help

Open the Support Portal in the Metrly Console if a payment is shown as complete but the balance remains unresolved, if the listed affected servers appear incorrect, or if you need accessibility assistance. Do not assume a support request pauses the timeline; only the deadlines actually displayed in the Console control.