This Hosting and Servers Terms of Service (“Terms of Service”) is by and between Code For Host, Inc and the customer who orders Code For Host’s cloud services (“you” or “Customer”).  These Terms of Service form part of an agreement (this/the “Agreement”) between Code For Host, Inc, and Customer.  The Agreement (as defined below) governs the provision of Code For Host, Inc’s Hosting services and the use of Code For Host, Inc’s service constitutes acceptance and agreement to Code For Host, Inc’s Terms of Service. By accepting the Agreement via electronic click-through authorization, Customer acknowledges that it has read and fully understands all of the terms and conditions set forth in the Agreement and hereby agrees to abide by the terms and conditions hereof.

The initial term for each Order begins on the date we make the Services available for your use and continues for the period stated in the Order.  If no period is stated in the Order, then the initial term shall be one month.  Upon expiration of the initial term, the Order will automatically renew for successive renewal terms of one month each, unless and until one of us gives the other a written notice of termination for convenience prior to the expiration of the initial term, or then-current renewal term, as applicable. If the services purchased are offered on an hourly basis your term will start when we make the Services available for your use and will continue until you delete them. You must follow Code For Host, Inc’s non-renewal process accessible from the Code For Host, Inc Cloud control panel to give an effective notice of non-renewal.

Suspension.  We may suspend your Services without liability if: (i) we reasonably believe that the Services are being used (or have been or will be used) in violation of the Agreement, (ii) we discover that you are, or are affiliated in any manner with, a person who has used similar services abusively in the past; (iii) you don’t cooperate with our reasonable investigation of any suspected violation of the Agreement; (iv) we reasonably believe that your Services have been accessed or manipulated by a third party without your consent, (v) we reasonably believe that suspension of the Services is necessary to protect our network or our other customers, (vi) a payment for the Services is overdue, or (vii) suspension is required by law.  We will give you reasonable advance notice of a suspension under this paragraph and a chance to cure the grounds on which the suspension is based, unless we determine, in our reasonable commercial judgment, that a suspension on shorter or contemporaneous notice is necessary to protect Code For Host, Inc or its other customers from imminent and significant operational or security risk.

No High-Risk Use.  You may not use the Services in any situation where failure or fault of the Services could lead to death or serious bodily injury of any person, or to physical or environmental damage.  For example, you may not use or permit any other person to use, the Services in connection with aircraft or other modes of human mass transportation, nuclear or chemical facilities, or Class III medical devices under the Federal Food, Drug and Cosmetic Act.

Data Backup: CodeforHost Inc offer daily backups (up to previous 7 days) with Advance packs only. The backup is captured once per day.
Notable that for any physical damage, or unexpected hardware failure, or for any other accidental case, CodeforHost Inc do not ensure full data protection security with services. For such cases, we recommended to use your own remote backup management.

Inode or File uses Limitation: Currently, there are no file limits for advance Shared Hosting packs, VPS and Dedicated servers. This means you can use full of your allocated storage with limitless files without any interruptions.
But there are some limits for budget/basic pack users. As we explained that budget pack’s servers have come with bit low resources, so there are some limitations.

For example, when an account has hundreds of thousands of files, it significantly degrades overall disk performance, as each file on the disk must be tracked/indexed. An easy analogy would be a table of contents or glossary for a book. If the book only has a few hundred pages, the index or glossary is likely to be small, and easy to search. If the book has 5,000 pages, finding what you want might take significantly longer. The file system on a server works in a similar way, just on a larger scale. The size of the file does not matter, only the size. For example, a DVD image (say, 4.5gb) only counts as one inode or file.
So, there are some file limits to keep the server performance well and to prevent abuse. The limit is given below: