These terms provide a complete commercial framework for a dedicated hosting and infrastructure business. Final versions should still be reviewed by qualified counsel and aligned with the operating entity, jurisdiction, and whether the website is acting as a lead-generation or direct service platform.
1. Scope of service
Safe Cloud Online may provide dedicated infrastructure planning, quoting support, market evaluation, server configuration discussions, and related hosting or consulting services. The services are intended to help customers assess workload fit, infrastructure design, and market availability before a confirmed commercial commitment. These terms apply to website enquiries, proposal discussions, and any final written service order accepted by both parties.
2. Quotes, availability, and order acceptance
Any quote, estimate, or presentation made on the website is informational and does not constitute a final offer or guaranteed availability. Service availability, hardware suitability, installation timing, lead time, network configuration, and pricing remain subject to written confirmation. A final order becomes binding only when an authorised representative of the business accepts the proposal or a signed service agreement is executed.
3. Customer responsibilities
The customer is responsible for providing accurate workload information, business requirements, contact information, and any operational constraints relevant to the proposed service. The customer remains responsible for the lawful use of software, data, credentials, applications, and traffic sent to the infrastructure. A customer must also inform the business of any legal, regulatory, or sensitive-data requirements that may affect deployment.
4. Fees, taxes, and payment terms
Unless otherwise stated in a written proposal, all prices, billing terms, taxes, setup charges, support scope, and renewal schedules must be confirmed in the final customer agreement. Payment terms, due dates, currency, invoicing method, and any late-payment interest or suspension rights should be stated in the same final agreement. Website examples are not final offers and should not be treated as binding pricing.
5. Service location and deployment
Location examples on the website are market examples for planning and comparison only and do not confirm the ongoing availability of a specific facility, server, or service in any city, region, or country. Any deployment timeline, market, installation plan, network route, or data-location requirement must be confirmed in writing before a commitment is made.
6. Support and service levels
Support scope, service windows, escalation procedures, and response obligations must be specified in the final agreement or service schedule. If a service-level commitment is offered, the specific metrics, exclusions, service credits, and conditions must be clearly stated. The website does not create an automatic support promise or service-level commitment without a written agreement.
7. Security and lawful use
Customers must comply with all applicable laws, data-protection obligations, and contractual restrictions when using the services. The customer must maintain appropriate access control, backup routines, and application security for its own systems and data. Unlawful, abusive, fraudulent, disruptive, or harmful activity is not permitted and may result in investigation, suspension, or termination under applicable policies and final service terms.
8. Suspension, termination, and remedies
Either party may have rights to suspend or terminate service under a final written agreement when there is a material breach, legal requirement, security risk, non-payment, or other valid reason identified in that agreement. The final contractual wording should explain notice periods, cure rights, suspension conditions, data return or deletion, and any remediation steps. The website itself does not replace the final formal agreement for these matters.
9. Intellectual property and confidentiality
Each party retains ownership of its own intellectual property and confidential information. Any information shared in service discussions should be treated as confidential to the extent required by the written agreement and applicable law. Customer data and content remain the customer’s responsibility unless the final agreement states otherwise.
10. Warranties and liability
The business should state any express warranties, service guarantees, and limitations of liability in the final written agreement. The website does not create an implied warranty of fitness, merchantability, or unqualified availability for infrastructure services unless explicitly set out in a signed or accepted document. Liability caps, exclusions, and indemnity terms should be tailored by legal counsel for the service model and jurisdiction.
11. Privacy and data handling
Personal data processing is governed by the Privacy Notice. The final service agreement should also define data-processing obligations, security responsibilities, retention routes, and required notification procedures where personal data or service records are involved.
12. Governing law and dispute resolution
These terms are intended to be governed by the laws of the jurisdiction where the business operates, unless a different governing law is agreed in writing. Any dispute should be resolved through the method stated in the final agreement, which may include negotiation, mediation, arbitration, or court proceedings. The final contract should state the specific jurisdiction, venue, and process before use.
13. Contact details
For legal notices, support issues, billing disputes, and customer service questions, use the contact details published by the company on the live website and in the final agreement. The operational business should maintain a monitored contact address and ensure the published details are accurate before launch.
← Back to legal information