Data Retention Policy

This policy distinguishes record retention from closing a ticket, canceling a subscription, or deleting a game server. There is currently no single enforced automatic purge schedule for all GameVerse data. Records without an implemented expiry can remain for an indefinite period unless staff removes them or a system's own lifecycle removes them. We do not promise a fixed deletion deadline that the current systems do not implement.

1. Accounts and credentials

Account/profile records remain while an account exists; inactivity does not trigger a website account purge. Staff can process account-deletion requests. The local deletion operation removes the user and certain related ticket/subscription records, but does not by itself cancel Stripe billing, remove a hosting-panel account/server, or delete Discord or mailbox copies. These systems need separate review.

Login tokens expire after approximately one hour. This is a session expiry, not account-data deletion. Revoking an API key stops its use but retains the revoked-key record; audit records can remain independently of a key or account.

2. Billing and subscriptions

Local subscription records link billing and hosting identifiers. When a subscription-ended event is processed, the application attempts server deletion and removes its local subscription row. Stripe billing records, payment notifications, invoices, disputes, and operational logs are separate. We have not adopted one universal deletion deadline for those records, and deleting a local row does not erase Stripe's records.

To stop recurring charges, cancel the subscription through billing management or request cancellation from support. Account deletion is not cancellation.

3. Server files and backups

Server files remain on hosting storage until removed by you, an administrator, or the service lifecycle. Subscription termination can lead to server deletion without a guaranteed export or recovery period. Export important data before the termination date.

Customer-managed backups, infrastructure backups/snapshots, and recovery archives are separate copies. This policy does not promise a universal backup frequency, retention window, secure-erasure deadline, or ability to restore a particular server. Removing live data does not establish that every recovery copy has been erased. A deletion request must identify these copies for operational review; third-party copies may be subject to the provider's own lifecycle.

4. Support, Discord, and email

Closing or archiving a ticket changes its status; it does not erase its transcript. Website ticket messages and events have no automatic age-based purge. A closed Discord ticket channel can be deleted while its recovered transcript and attachment links remain on the website. External message copies, notifications, attachment hosting, and Discord role/message history are separate from that transcript.

Email correspondence can remain in mailboxes. Where automated ticket email is enabled, marking a processed email as read is not deleting it; failed-message handling can also retain copies. No uniform mailbox purge period is specified by the website.

5. Logs, queues, and browser storage

Security/API audit records, operational logs, announcement-delivery records, and Discord reconciliation history may remain after the underlying action completes. The website does not implement a common age-based purge for them. Host-specific log rotation or provider lifecycles are not an all-systems deletion guarantee.

The dismissed-announcement value in local storage remains until replaced or cleared in your browser; it has no built-in expiry. Discord authorization-state cookies expire after ten minutes. These browser/session lifetimes do not set retention periods for server-side records.

6. Requests and exceptions

Request access, correction, or deletion through support or the email below. Identify the account and requested scope: hosting data, support history, billing, or all relevant records. We may verify identity and distinguish live records from backups and provider copies. Necessary billing, dispute, security, and legally required records may need to remain. Applicable statutory deadlines and rights take precedence over this description of current technical behavior.

A completed request should explain what was removed, what remains and why, and any unresolved provider/backup limitations. It must not be described as complete erasure based only on deleting an account row. This policy does not create a new right to keep records longer than applicable law permits.

Resource-configurator test records

Canceling a resource-configurator test order requests immediate cancellation of its sandbox subscription and deletion of its mapped real server. The order, immutable resource/price snapshot, provider mapping, event/job records, panel-user mapping and invitation hash/use records remain for operational review; cancellation does not erase them. Quote and invitation expiry prevents new use, not record retention. No uniform automatic age-based purge is implemented for these test records, and deleting a real test server does not establish removal of backup or provider copies.

For reviewed variants, profile/version and settings snapshots, acknowledgement records, capacity reservations/waits and operator-notification delivery records also support provisioning and reconciliation. Canceling a queued order does not erase these records or mailbox copies, and no new automatic purge deadline is introduced. Secret inputs are cleared from the test review page when leaving it; this is not deletion of the protected server-side configuration used for the quote or order. Non-secret selections in browser history and copied URLs remain under the browser or recipient’s control.

TEST capacity-refund records retain the original verified payment identity, amount/currency, payment time/deadline and refund/reconciliation history even after subscription cancellation. They support recovery, duplicate-refund prevention and billing review. The seven-day rule is a refund-initiation deadline, not a data-deletion schedule. A refund does not erase orders, provider records, mailbox copies or backups; no new automatic purge period is introduced.