Draft policy for operator review. This theme is connected to WHMCS: a configured installation can create customer accounts, orders, invoices and support records, and use enabled payment and service modules. Before adopting this policy, the operator must complete its verified identity, contacts, service terms and actual data practices. Installing the theme does not configure those business settings.
- Applies to
- All services
- Commercial detail
- Your accepted order
- Edition
- Model policy
Scope and agreement
These model terms cover domains, Web Hosting, Cloud Hosting, Reseller Hosting, VPS Hosting, Dedicated Servers, Game Servers, Professional Email, SSL Certificates, VPN, Web Design, Backup & Recovery, Website Migration and Managed Services. “Provider” means the legal entity identified in the accepted service order; “customer” means the account holder or the organisation they are authorised to represent.
A live service agreement must identify that entity, its contact details and the applicable jurisdiction before an order is accepted. The Weeby theme supplies the interface; the configured WHMCS installation manages account and order workflows. The operator is responsible for service delivery and the terms under which it accepts an order.
The accepted order defines the service, resources, term, fees and agreed scope. A separately signed agreement or statement of work takes priority where it expressly changes these terms. Mandatory law takes priority over conflicting contractual wording. Product-specific policies apply to the service they address.
Orders and service activation
An enquiry, quotation or configuration preview is not confirmation that resources, a domain name or a delivery date have been reserved. A live order becomes effective only after the provider confirms acceptance and any stated payment or verification requirements are met.
- Review the configuration, renewal price, billing period, taxes, optional extras and any minimum term before approving an order.
- Supply accurate account and billing information, and keep an account contact available for operational notices.
- Do not submit an order on behalf of another person or organisation without authority.
- Activation and project dates depend on the accepted order, available resources, necessary access and third-party approvals. Installing the theme does not configure provisioning or establish an instant-activation promise.
Fees, renewals and cancellation
The accepted order must show the currency, recurring price, renewal interval, applicable taxes, chargeable usage and any setup or third-party fees. Promotional prices, if offered, must state their duration and renewal basis. Optional extras require an affirmative selection or separate approval.
A recurring service renews according to the selected term unless it is cancelled using the provider’s published process before the stated cutoff. Turning off auto-renewal for a domain and cancelling a hosting subscription are separate actions. Cancelling a payment instruction does not itself cancel a service agreement.
Price changes, overdue-payment handling and any suspension process must be communicated through the account contact and applied consistently with the accepted order and applicable law. Refund requests follow the Refund & cancellation policy.
Accounts, content and security
You control the content and applications you place on the service, unless a managed scope expressly assigns a task to the provider. Maintain lawful rights to that material, protect your credentials, limit account access and keep software under your control appropriately maintained.
- Keep an independent, usable copy of important data. Included or optional backups have the scope and retention described in the order.
- Protect private keys, authorisation codes, recovery codes and administrative credentials; do not include them in ordinary enquiry forms.
- Notify the provider promptly if you suspect unauthorised account access or a compromised application.
- Use resources within the purchased allocation and follow the Acceptable Use Policy.
Hosting, servers and reseller services
Hosting and server allocations are defined by the purchased plan, including storage, CPU, memory, transfer, websites, accounts and any permitted use limits. “Cloud,” “managed” or “dedicated” does not by itself specify an availability commitment, a dedicated CPU entitlement or a particular management task.
For VPS, Dedicated Servers and Game Servers, the order must identify the operating system, access model, software licences and the boundary between infrastructure support and application administration. Customer-installed plugins, mods and applications remain the customer’s responsibility unless included in writing.
A reseller is responsible for its own customer relationship, first-line support, lawful processing and downstream terms. Resellers must pass through applicable resource and acceptable-use restrictions. Third-party control panels, billing licences and other software are included only when the order expressly lists them.
Domains, email, certificates and VPN
Domain services are subject to the sponsoring registrar, registry and applicable domain rules. Registration is not guaranteed until confirmed by the registry. Keep registration details current and monitor renewal notices. See the Domain registration policy.
Professional Email is subject to mailbox, storage and sending limits in the order. Delivery to every recipient cannot be guaranteed; recipient systems and reputation controls can affect acceptance. Permission to send marketing messages and correct DNS authentication are customer responsibilities unless a managed task covers configuration.
SSL certificate issuance and continued validity depend on the certificate authority’s validation and subscriber rules. A certificate does not certify that website content is trustworthy or free of vulnerabilities. Protect the private key and request revocation promptly after a suspected compromise.
VPN access does not remove legal obligations or guarantee anonymity. The actual provider, technical scope, permitted devices, logging practices and location options must be disclosed before a live VPN service is ordered.
Design, migration, backups and management
A statement of work should define Web Design deliverables, milestones, revisions, content responsibilities, acceptance, licences and the ownership or transfer of completed work. Any third-party theme, font, stock asset, plugin or subscription retains its own licence conditions.
Migration work requires authorised source access, a recent backup, an agreed transfer scope and a cutover plan. Compatibility, DNS changes and third-party restrictions can affect timing. Do not cancel the source service until the agreed checks are complete.
Backup & Recovery and Managed Services are limited to the systems, schedules, retention, tasks and access permissions specified in the order. Recovery time and recovery point objectives apply only if agreed. A backup is not a substitute for security controls or tested restoration.
Support and service commitments
Support channels, coverage hours, priorities, response targets and any excluded tasks must be identified in the service order or published support schedule. A response target is different from a guaranteed resolution time.
Availability commitments and credits apply only where a service-specific schedule has been accepted. The Service level policy explains the measurement framework; it does not add an unstated uptime guarantee to every service.
Suspension, termination and data export
The provider may restrict an affected service where reasonably necessary to address material abuse, unauthorised use, an immediate security threat, a lawful direction or a material payment breach. The reason, scope and next step should be communicated where lawful and practicable. Urgent protection may require action before notice.
Where a breach can be remedied, the applicable notice or cure process must be identified. Access should be restored when the relevant issue is resolved, subject to the agreed conditions and any continuing legal restriction.
Before cancellation or termination, arrange a data export and confirm the retention and deletion schedule. A paid service is not an indefinite archive. The order must identify any post-termination access period and chargeable migration or recovery work.
Rights, liability and disputes
Each party retains rights in its pre-existing materials. You authorise the provider to process customer content only as needed to deliver the agreed service and comply with lawful obligations. Any wider use requires a separate lawful basis or agreement.
Any contractual limitation, exclusion or liability cap must be set out in the accepted agreement and assessed for the parties and jurisdiction concerned. These model terms do not insert a blanket cap. Nothing in them removes a right or liability that applicable law does not permit the parties to exclude.
Raise a service or billing dispute through the provider’s published contact route and include the order reference and relevant evidence. The accepted agreement must identify the governing law, dispute process and competent forum; this template does not choose them.
Changes and contact
A live provider should retain the version accepted with each order and explain material policy changes, their effective date and any available customer options. Changes should not retrospectively alter accrued rights or an agreed fixed-term commitment without a valid contractual basis.
Use the WHMCS contact form for a general service or policy question, or the appropriate support department for an account matter. The operator must separately identify the channel and delivery requirements for contractual or legal notices.
Explore the services and review the terms relevant to your project.
