Billing, Suspension & Retention Policy

Price disclosure

Before checkout, show product, package, BDT price, billing unit, prepaid

period, renewal price/cycle, resource limits, taxes, add-ons and

separate storage/IP/licence fees.

Hourly VPS

Display rate, billing start event, rounding/minimum charge, stop event,

auto-renew behaviour and charges that continue while stopped. Configure:

`[ADMIN: hourly start]`, `[ADMIN: rounding/minimum]`,

`[ADMIN: compute stop rule]`, `[ADMIN: storage/IP/snapshot charges]`,

`[ADMIN: auto-renew/termination]`. Provide timestamped usage history

where supported. New rates must not be retroactively applied to accrued

usage.

Daily VPS

Display daily rate, billable-day definition, partial-day rule, start

event, expiry timezone, renewal behaviour and stopped-resource charges.

Configure: `[ADMIN: daily unit]`, `[ADMIN: partial-day rule]`,

`[ADMIN: expiry timezone]`, `[ADMIN: stopped-resource fees]`.

Monthly and longer VPS

Show total prepaid amount in BDT, covered period, renewal amount/cycle,

auto-renew/auto-debit status, failed-payment outcome and

upgrade/downgrade prorating rules. Discounts apply only as shown at

checkout.

Stopped service

Stopping a VPS does not necessarily release disk, IP, snapshots or other

allocations. Clearly label charges that continue. Use confirmed

cancellation/termination to stop future service billing. Terminated data

may not be recoverable.

Non-payment lifecycle

Configure and publish the exact reminder, grace period, suspension,

final notice, retention and deletion sequence. Suggested safe

workflow: 1. Send due/renewal reminders. 2. Apply the disclosed grace

period `[ADMIN: duration]`. 3. Suspend/restrict after grace and notify

the customer. 4. Send final notice before termination

`[ADMIN: duration]`. 5. Recheck gateway status, pending transactions,

disputes, manual holds and legal retention before deletion. 6. Record

every action and notification in audit logs. 7. Delete data/release IP

only after final checks and the published retention period.

A three-hour post-suspension deletion window is very short and creates

serious accidental data-loss risk. Do not use it unless specifically

approved, prominently disclosed and protected by tested payment rechecks

and warnings. A longer retention window is preferable.

Paid, stopped and pending-payment services

Do not delete a paid VM just because it is stopped. Preserve it through

the paid term unless the customer terminates it or a valid

security/legal exception applies. A pending payment is not automatically

a failed payment; hold deletion while it is reasonably capable of

confirmation. Staff must not mark an invoice paid without verification.

Backups, notices and records

Publish backup schedule, location, retention, restore limits and fees

per product. Never advertise daily backups unless enabled and monitored.

Customers should keep independent backups. Configure

`[ADMIN: backup retention]` and `[ADMIN: terminated-service retention]`.

Send notices to configured account channels and log payments,

suspensions, holds, restores and deletions.