Terms of Service
All services provided by Premento.com may only be used for lawful purposes. The customer agrees to indemnify and hold harmless Premento.com from any claims resulting from the use of our services. Premento.com is dedicated to providing an all-round top quality service. The terms and conditions which follow are necessary to ensure that we may continue to provide the best possible service to all of our customers whilst at the same time fulfilling our legal and ethical responsibilities. Failure to follow any term or condition will be grounds for immediate account deactivation without notice. Premento.com will be the sole arbiter as to what constitutes a violation of any of these provisions. Activity which results in the suspension or deactivation of an account will result in a forfeiture of all fees paid. Complaints made regarding abuses of an account will be investigated and if found guilty will be grounds for immediate suspension. Although we try to maintain a very high service availability, the services provided by Premento.com are not designed for mission critical use, and should not be used for such purposes unless there is a written confirmation from us. To report suspected abuses or any violations of these policies, please contact us by sending a mail to [email protected].
The client is responsible for all activity originating from the account unless proven to be a victim of outside hacking or address forgery. The client is responsible for securing their username/password. The client assumes responsibility for all material on their site that may be put on by a third party (such as the usage of Free For All links pages). The client agrees that he or she has the necessary knowledge to create and maintain their web space. Client agrees that it is not the responsibility of Premento to provide this knowledge or support outside matter specific to Premento servers.
UCE (Unsolicited Commerce Email) Spamming
UCE (Unsolicited Commerce Email) or Spamming, or the sending of mass unsolicited email, from or through a Premento server or using an email address that is maintained on a Premento machine is STRICTLY prohibited. Click Here to find the limits and guidelines of mail usage. Premento will be the sole arbiter as to what constitutes a violation of this provision. If you engage in any of the foregoing activities using the service of another ISP or IPP, but channeling activities through a Premento server as a maildrop for responses, you are in violation. Violators accounts will be terminated without notice.
Maintenance of Information The information provided to Premento is saved indefinitely and may be stored on one or more databases directly or indirectly maintained by Premento. Premento employs industry standard security measures to protect the confidentiality of the information.
While we cannot guarantee that loss, misuse or alteration to data will not occur; we make every effort to prevent such occurrences. Any other particularly sensitive information, such as credit card numbers collected for commercial transactions, is encrypted prior to transmission by you to Premento.
Server Usage Limitations
User may not:
- Use 25% or more of system resources for longer then 90 seconds. There are numerous activities that could cause such problems; these include: CGI scripts, FTP, PHP, HTTP, etc.
- Run stand-alone, unattended server-side processes at any point in time on the server. This includes any and all daemons, such as IRCD.
- Run any type of web spider or indexer (including Google Cash / AdSpy) on shared servers.
- Run any software that interfaces with an IRC (Internet Relay Chat) network.
- Run any bit torrent application, tracker, or client. You may link to legal torrents off-site, but may not host or store them on our shared servers.
- Participate in any file-sharing/peer-to-peer activities.
- Run any gaming servers such as counter-strike, half-life, battlefield1942, etc
- Run cron entries with intervals of less than 15 minutes.
- Run any MySQL queries longer than 15 seconds. MySQL tables should be indexed appropriately.
- When using PHP include functions for including a local file, include the local file rather than the URL.
- To help reduce usage, do not force html to handle server-side code (like php and shtml).
Only use https protocol when necessary; encrypting and decrypting communications is noticeably more CPU-intensive than unencrypted communications.