Bytegrounds policy

Service & Backup Policy

This policy sets practical expectations for service limits, backups, billing recovery, and customer responsibilities.

Effective July 11, 2026 · Version 2026-07-11

Package limits

Storage, transfer, inode, domain, database, mailbox, FTP, cron, SSH, runtime, and other limits are controlled by the DirectAdmin package attached to the order. Features not displayed or confirmed are not promised.

Backups

Unless the order explicitly states a schedule and retention window, server backups are an operational recovery aid rather than a customer backup guarantee. Keep independent, current copies of files, databases, email, and configuration.

A successful backup job does not guarantee that every changing application file or third-party dependency can be restored to a specific moment.

Payment recovery

A failed renewal produces a customer notice and a grace period of 5 days while Stripe retries, unless fraud or abuse requires faster action. Service may be suspended when a subscription becomes unpaid, canceled, or paused and restored after a later confirmed payment.

Support scope

Support covers storefront account state, billing routing, DirectAdmin access, and reasonable hosting compatibility guidance. Application development, debugging, security remediation, content changes, and migrations are separate work unless the order includes them.

Maintenance and security

Bytegrounds may perform maintenance or urgent security work and may require customers to update vulnerable software. Customers are responsible for application code, plugins, themes, credentials, and access granted to collaborators.

Questions about this policy?support@bytegrounds.com