EULA (Hosting)
Software licence conditions vary by the exact product. This section summarises your responsibilities; the applicable Microsoft, cPanel, WHMCS or other vendor licence remains relevant.
20 sections · Click a heading to read its content.
Contents of this document
01. Definitions.
“Software” means the licensed operating system, control panel, billing system or other product included in your order. “Vendor” is its rights holder or authorised licensor. “EULA” is the applicable end-user licence agreement. The actual version, permitted use and licence quantity must be identified for your service.
02. Ownership of products.
A software licence grants permitted use; it does not transfer the vendor’s copyright or ownership. Your own content remains yours subject to third-party rights. Bespoke code ownership must be addressed in the separate development agreement.
03. Use of software.
Use software only within its authorised server, account, user, location and hosting scope. Additional licences may be needed when cloning, migrating or expanding a service. Ask us to identify the licence before relying on a particular deployment right.
04. Copies and backups.
Make copies only where the licence or law permits, including permitted backup copies. Do not distribute activation keys, licence files or installer packages outside the authorised scope. A licence restriction does not remove a right that legislation expressly protects.
05. Reverse engineering, decompilation and disassembly.
Follow the actual vendor restrictions and any applicable statutory exceptions. These general terms do not create a broader prohibition than the licence or law permits. Seek advice where interoperability, research or other legally protected activity is involved.
06. Rental of products.
Do not rent, lend or sublicense licensed software unless the applicable licence expressly allows it. A hosting-reseller account is not itself a software rental licence.
07. Not for resale software.
Software marked not for resale, trial, evaluation, educational or internal use must not be sold or used outside its permitted purpose. Commercial hosting rights require the appropriate licence.
08. Usage in accordance with policies.
Comply with the applicable licence, acceptable-use requirements and law. We must identify a material restriction before you order a service that depends on it.
09. Responsibility for website/server content.
You must have rights to the files, databases, images, fonts and software you upload. Keep customer-managed software licensed and supported. Do not upload malware or use an unlicensed copy merely because it can run technically.
10. Termination.
If a licence or hosting service ends, continued software use may no longer be authorised. Arrange permitted exports and removal of licensed copies. TIN must respect the contractual and statutory notice rules applicable to its own service.
11. Vendor warranties and remedies.
Any vendor warranty or support entitlement depends on the actual licence. Request the licence and warranty information for the specific product before relying on a vendor remedy. Mandatory rights against the relevant supplier remain unaffected.
12. TIN warranties and remedies.
TIN is responsible for its agreed licensing and service obligations. The general liability terms apply. A third-party EULA does not automatically remove a consumer remedy against TIN.
13. Product support.
Support scope, updates and escalation depend on the purchased package and vendor entitlement. Development, customisation, data repair and third-party compatibility work are not assumed to be included.
14. Fault tolerance and critical uses.
Do not rely on ordinary shared hosting or standard business software as the sole control for life-critical or safety-critical systems. Any specialised use requires an expressly suitable design and agreement.
15. Export restrictions.
Comply with applicable export, sanctions and use restrictions of the actual licence and law. Check the particular product and proposed location before deployment.
16. Liability for breach.
A licence breach may require correction, suspension or removal of unauthorised software, subject to law. Claims and recovery must be connected to the facts and the applicable agreement; no automatic unlimited indemnity is imposed here.
17. Information disclosure.
Vendors may need licence identifiers, server details or account quantities to activate and verify authorised use. Personal information must be handled on a lawful basis and limited to the purpose. See the Privacy Policy.
18. Governing law.
South African mandatory protections apply to TIN’s customer relationship. A vendor’s own licence may identify a different governing law for its own rights, but cannot remove rights that cannot lawfully be excluded.
19. Amendments.
Licence changes must be handled under the applicable agreement. We will communicate material changes affecting your service where required, rather than treating an unnoticed website change as sufficient consent.
20. Entire agreement.
The accepted order, identified vendor licence and applicable TIN terms define the licensed service. Request a copy of the relevant licence if it was not supplied. Marketing descriptions cannot authorise rights that the actual licensor has not granted.