Service policy
Abuse Policy
How Cheap Clouding receives, reviews, prioritizes, and responds to abuse reports involving hosted content, domains, accounts, and platform activity.
Effective date: July 23, 2026
Customer clarity
Plain-language terms for hosting, domains, billing, support, and WordPress services.
Portal coverage
Maps to hosting, domains, billing, support, and WordPress workflows.
Support path
Questions can move into support with service and billing context attached.
Policy guidance
These pages help customers understand service expectations before ordering or opening a support request.
Review service details, billing dates, cancellation terms, and renewal timing before ordering.
Use support tickets for account-specific policy, billing, domain, or service questions.
Keep hosting usage, quota, and service details easy to review inside the customer portal.
Support path
Policy questions should flow through support so your account can link tickets, services, invoices, domains, plugin licenses, and support history together.
Reporting abuse
Abuse reports should be sent through the support channel or to support@cheapclouding.com with enough detail for review. Reports should include the domain, URL, IP address if available, timestamps with timezone, screenshots, message headers, logs, affected accounts, and a clear explanation of the issue.
- For phishing, malware, or scams, include the exact URL and any redirect chain.
- For spam, include full message headers and the recipient address affected.
- For copyright, trademark, or legal complaints, include the rights owner, authorization to act, the exact material at issue, and the requested action.
Review process
Cheap Clouding triages reports based on severity, evidence quality, active harm, customer history, provider requirements, and legal risk. We may link the report to affected services, domains, invoices, tickets, audit logs, and security events.
- High-risk reports such as phishing, malware, credential theft, child safety issues, active attacks, and payment fraud receive priority review.
- We may ask the reporter or customer for additional evidence when the report is incomplete or disputed.
- We may preserve relevant logs or records where needed for incident response, dispute handling, provider escalation, or legal compliance.
Customer response
Customers may be asked to remove content, patch software, clean malware, disable scripts, rotate credentials, update DNS, verify ownership, stop abusive traffic, or provide context. Restoration may depend on successful remediation and risk review.
- Compromised sites may remain restricted until malware, vulnerable code, unauthorized users, and persistence mechanisms are removed.
- Domain, DNS, or service actions may be delayed or blocked where abuse, fraud, or ownership disputes are unresolved.
- Repeated incidents may require a managed security plan, migration to a higher plan, or account closure.
Actions we may take
Depending on the facts, Cheap Clouding may warn, suspend, restrict, remove, disable, quarantine, redirect, rate-limit, block, terminate, report, or escalate an affected account, site, service, domain, plugin assignment, or order.
- We may act without advance notice when active harm or provider escalation requires it.
- We may share necessary information with registrars, payment processors, infrastructure providers, security partners, law enforcement, or affected third parties where appropriate.
- False, abusive, or bad-faith reports may be rejected and may lead to account restrictions.