Unsupported scripts and control panel web app for a hosting company
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

tac.txt 5.4KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384
  1. 0004
  2. <h3>1. Billing</h3>
  3. <h4>1.1 General billing information</h4>
  4. <p>Payment for UTD-Hosting services must be made in advance. All services last for one year (365 days) unless otherwise stated. At the end of the one year period, if payment has not been made to continue services, all services provided for the user will cease.
  5. </p>
  6. <h4>1.2 Payment handling</h4>
  7. <p>All payments made to UTD-Hosting are handled by <a href="http://www.paypal.com/" class="external">Paypal</a>, and are therefore subject to their <a href="https://www.paypal.com/uk/cgi-bin/webscr?cmd=p/gen/ua/ua-outside" class="external">user agreement</a>. Payments made to UTD-Hosting will only be accepted once they have been fully cleared by Paypal.
  8. </p>
  9. <h4>1.3 Refunds</h4>
  10. <p>All payments to UTD-Hosting are final. In the case of account termination, either initiated by the user or initiated by UTD-Hosting, any prepaid service will be forfeited.
  11. </p>
  12. <h4>1.4 Account ownership</h4>
  13. <p>
  14. All accounts are owned soley by the user who registered the account, or the user who made contact with UTD-Hosting staff in order to have the account created. Accounts may not be transferred to any other party. UTD-Hosting services may not be resold to any third party or any other user.
  15. </p>
  16. <h3>2. Disclosure of information</h3>
  17. <h4>2.1 General</h4>
  18. <p>While UTD-Hosting strives to maintain the privacy and integrity of all data stored by the user, we cannot guarantee either. Users should avoid transferring or storing sensitive or private information using the services provided by UTD-Hosting. Users should make regular backups of any data hosted for them on UTD-Hosting services to avoid loss of data in case of a hardware or software error.
  19. </p>
  20. <h4>2.2 Disclosure to law enforcement agencies</h4>
  21. <p>UTD-Hosting may disclose any information pertaining to any services used by any user to any law enforcement agent who formally requests such information in writing. In such a circumstance, the user will not be notified of such a request, or UTD-Hosting's response.
  22. </p>
  23. <h4>2.3 Monitoring of user actions and data</h4>
  24. <p>UTD-Hosting may monitor any and all actions performed by the user, including but not limited to files uploaded via FTP, e-mails sent and received via UTD-Hosting servers, commands and programs executed by users with SSH access, and files requested via HTTP. In addition, UTD-Hosting may inspect any file, database or e-mail stored on UTD-Hosting servers, if there is suspicion that the user may be in violation of this agreement.</p>
  25. <h3>3. Use of UTD-Hosting services</h3>
  26. <h4>3.1 Unacceptable uses</h4>
  27. <p>UTD-Hosting services may <span class="bold">not</span> be used for:
  28. </p>
  29. <ul><li> Organising or participating in illegal activity</li>
  30. <li> Distributing copyrighted material without the correct permission</li>
  31. <li> Distributing viruses, trojans or other malware</li>
  32. <li> Sending unsolicited or excessive commercial e-mail</li>
  33. <li> Attempting to gain illegal access to any service, server or computer, whether related to UTD-Hosting or not</li>
  34. </ul>
  35. <p>In addition, the following are forbidden:
  36. </p>
  37. <ul><li> Any script, program or other file that causes disruption to UTD-Hosting systems</li>
  38. <li> Attempting to gain illict access to any UTD-Hosting services</li>
  39. <li> Attempting to gain access to any files or data hosted on UTD-Hosting systems that has not been directly uploaded or created by the user.</li>
  40. </ul>
  41. <h3>4. Account cancellation</h3>
  42. <h4>4.1 Cancellation and notification</h4>
  43. <p>UTD-Hosting reserves the right to terminate any account at any time, for any of the reasons outlined in section 4.2, or, in exceptional circumstances, for any reason deemed appropriate by UTD-Hosting staff. Any payment made in advance for services from UTD-Hosting will be forfeited if an account is cancelled. Upon account cancellation, an e-mail will be sent to the account holder's address.
  44. </p>
  45. <h4>4.2 Reasons for cancellation</h4>
  46. <p>Accounts may be cancelled by UTD-Hosting without prior warning, as per condition 4.1, for the following reasons:
  47. </p>
  48. <ul><li> Lack of payment</li>
  49. <li> Any unacceptable use (as defined in section 3.1) of any service(s) provided by UTD-Hosting</li>
  50. </ul>
  51. <h4>4.3 Data availability following cancellation</h4>
  52. <p>If an account is cancelled due to lack of payment, or following a request for cancellation by the account holder, the following data will be made available for download by the account holder for seven days after the cancellation of the account:
  53. </p>
  54. <ul><li> Contents of any MySQL databases associated with the account</li>
  55. <li> Any unread e-mail messages</li>
  56. <li> All files stored within the account's 'home' directory</li>
  57. </ul>
  58. <p>Accounts cancelled by UTD-Hosting without consultation with the account holder, excluding accounts cancelled as a result of non-payment, are excempt from this clause. Data held for these accounts will be removed from UTD-Hosting systems within fourty-eight hours of account cancellation.
  59. </p>
  60. <h3>5. Future updates</h3>
  61. <p>These terms and conditions may be updated at any time. Users will be notified via their registered e-mail address when the terms and conditions have been updated. There will then be a two week period during which users should contact UTD-Hosting support at support@utd-hosting.com if they do not agree with the revised conditions. If, after two weeks, UTD-Hosting has not been contacted with objections, it will be assumed that the user agrees to the new conditions and they will become binding.
  62. </p>