Terms of Service
Shooting Star Hosting • Integrated Operational Guidelines
01. Account Provisions & Node Resource Scope
By establishing a node deployment profile on Shooting Star Hosting, you are granted a dedicated share of NVMe infrastructure resources bound to your selected plan (Milky Way or Andromeda). These allocations are provided solely for standard web operations, sales funnels, and application handling. Runaway script executions or unmanaged system loops that intentionally compromise shared backend server neighbors will result in localized account containment limitations.
02. Account Setup & Resource Allocation Rules
All new hosting profiles are provisioned upon validated authentication clear tokens. Accounts are explicitly restricted from employing custom deployment scripts, backend tasks, or heavy background processes that intentionally degrade mutual network speed parameters. Any user profile exceeding targeted system boundaries may face automated resource mitigation steps to maintain performance stability.
03. Third-Party Software Scope & Limits of Liability
You are granted complete dashboard control to configure custom content structures and execute independent third-party software applications inside your file space. However, Shooting Star Hosting explicitly disclaims any operational liability or direct technical support for third-party functionalities, application-level exploits, or custom code failures. Users must contact the original authors of external software packages for specialized support.
04. Core Server Restrictions & Gated Tool Protocol
To preserve global network integrity and secure neighbor data rings against cross-contamination vulnerabilities, specific development actions are permanently locked down on our shared architectural layer. Root shell execution commands, open SSH terminal connections, and command-line automation protocols (including WP-CLI and native Drush tools) are strictly unavailable. All file operations must run cleanly through secure FTP pathways or the native cPanel File Manager interface.
05. Infrastructure Uptime Guarantee & Prohibited Configurations
We target an optimal cluster up-time standard across all web instances. Customers are strictly barred from deploying malicious network toolsets, unauthorized proxy loops, or utilizing platform assets to broadcast anti-spam threshold alerts. Violations of server environment isolation properties will result in immediate service suspension cycles without account evaluation delays.
06. Billing Adjustments & Manual NVMe Overages
Services are rendered on transparent, contract-free monthly or annual billing tracks. If your system scale outpaces your default physical NVMe storage capacity, limits must be adjusted manually by an system operator. Mid-cycle storage tier upgrades require a manual service ticket submission from the client portal; all subsequent parameter adjustments will apply a clean, pro-rated resource update balance straight to your running invoice.
07. Data Backups & System Maintenance Transitions
While manual snapshot routines are recommended for your production systems, we process automated storage backups strictly for platform infrastructure recovery operations. Shooting Star Hosting does not assume legal responsibility for file corruption or database parameter state losses resulting from user-end scripts, custom file injections, or unmanaged update mismatches.
08. Termination Parameters & Data Loss
You remain the sole owner of all uploaded assets and traffic frameworks. You maintain complete agency to cancel your service profile or migrate assets outward at any point. Unsettled invoice arrears or intentional, malicious service exploits can result in temporary service restriction or full system termination, which will permanently dump all unarchived site files and database metrics from the server hardware.
09. Termination Protocols & Content Purges
Either organization may execute contract cancellation processes inside our client billing portal framework. Upon service termination, all web data pools, isolated node profiles, and tracking metrics are marked for decommissioning. Active content assets are entirely destroyed within our system clusters within a hard 30-day lifecycle window following termination.
Order payment confirms acceptance of our operational guidelines.