Find what matters
- Limits belong to the purchased plan, not hidden rules.
- Disk space does not measure all application consumption.
- Diagnosis and proportionate containment before changing plans.
This summary helps navigation. Full conditions are set out in the clauses below.
1.Purpose and transparency
This policy governs hosting and public-tool resources while protecting other users and the purchased service. It does not create secret quotas or retrospective reductions. The order, offer and product terms identify applicable limits.
Commercial expressions without a numeric cap need clear technical conditions; they do not mean infinite CPU, memory, processes, email or storage. Relevant limits must be clarified before purchase, not only after consumption.
2.What is measured
CPU measures processing; RAM working memory; I/O and IOPS disk volume and operations; processes and connections simultaneous tasks; inodes files and directories. Disk, databases, execution time, messages and traffic may also have limits. These are not equivalent metrics.
A small website may use considerable CPU. Limits state units, time windows or bursts, account or application scope and behavior at the cap. Reserved and shared resources must not be conflated.
3.Legitimate growth and diagnosis
Campaigns, sales and traffic peaks are not automatically abuse. Slow queries, plugins, tasks, bots, attacks and genuine growth need different solutions. Guidance identifies the affected resource without exposing sensitive safeguards.
Upgrading is not the only answer. Caching, bug fixes, database or task optimization may resolve usage. Upgrade recommendations explain need and cost without promising application-dependent results.
4.Storage and compatible purposes
Hosting storage is for the website, databases and covered data, not unrestricted device backups, anonymous repositories or unrelated mass distribution. Temporary own-site copies respect the quota and are removed safely.
Disk capacity does not replace inode limits or database integrity. Quota guidance distinguishes necessary files, regenerable cache, duplicates and copies without arbitrary customer-data deletion. Exceptions and costs require accepted scope.
5.Automation and incompatible processing
Bots and integrations control frequency, concurrency and duration. Shared hosting is not for mining, intensive model training, abusive scans or incompatible persistent load. Lawful APIs are assessed by consumption rather than prohibited merely for using AI.
Multiple accounts and meter exploitation must not evade limits. Free tools have disclosed quotas; free access does not authorize unlimited automation.
6.Limit behavior and containment
Caps may queue, temporarily reject or terminate work, slow responses or prevent new writes depending on the resource. Behavior must match the plan and be disclosed. Concrete risks may require immediate component containment with reasons communicated.
Limited containment and proportionate correction are preferred. Misconfigured caps and infrastructure faults must be corrected and are not excluded from the SLA merely by labeling them excessive use.
7.Plan changes and review
Capacity, cycle or product changes require disclosed resources, price, start date and data effects. There is no blanket authorization to charge an upgrade. Check compatibility and protect data before downgrading.
To challenge a limit, provide service, time, behavior and evidence. The response explains the criterion and review route. Changes do not retrospectively reduce purchased resources or statutory rights.
Zovvi Cloud · Rocketz Digital Ltda · CNPJ 37.843.555/0001-05 · Av. Paulista, 2073