Acceptable Use Policy

This Acceptable Use Policy applies to services provided by Reonr Limited, trading as Reonr. Reonr Limited is based in Port Harcourt, Rivers, Nigeria.

This Policy exists to protect Reonr customers, networks, infrastructure, domain services, payment systems, upstream providers, public users, and the wider internet from unlawful, abusive, harmful, or irresponsible activity.

Use of Reonr services means you agree to comply with this Policy, the Terms of Service, applicable product rules, third-party provider rules, domain authority rules, and applicable law.

This Policy applies to Web Hosting, cPanel Hosting, WordPress Hosting, VPS Hosting, Dedicated Servers, Cloud Hosting, Reseller Hosting, Plesk and DirectAdmin control panel licenses, Domain Registration, Domain Transfer, DNS Management, Email services, SSL, Backups, Website migration, Support services, and related products.

It applies to your account, websites, applications, servers, databases, files, emails, scripts, domains, DNS records, IP addresses, users, customers, resold services, support activity, and any activity using Reonr infrastructure or services.

You are responsible for all activity under your account, whether performed by you, staff, developers, contractors, customers, resold users, compromised scripts, compromised mailboxes, malware, exposed credentials, or unauthorized users who gained access through your systems.

You must maintain secure software, strong credentials, patched applications, clean mailing practices, lawful content, accurate domain information, proper DNS records, and appropriate backups.

You must not knowingly allow abuse to continue after you become aware of it. Failure to respond to abuse notices or security incidents may be treated as a violation of this Policy.

You must not use Reonr services to store, publish, transmit, promote, link to, facilitate, or profit from unlawful content or activity.

Prohibited content and activity includes child sexual abuse material, terrorism-related content, credible threats of violence, human trafficking, illegal weapons trafficking, unlawful controlled substances, stolen credentials, stolen payment data, identity theft material, revenge abuse material, extortion, blackmail, illegal gambling, scams, counterfeit goods, and other content or conduct prohibited by law.

Reonr may take immediate action where content or activity presents serious legal, safety, security, child protection, or public harm risk.

You must not use Reonr domain, DNS, hosting, email, or server services for DNS abuse, domain abuse, or domain-enabled harm.

Prohibited DNS and domain abuse includes malware distribution, botnet command and control, phishing, pharming, domain hijacking, DNS hijacking, deceptive redirects, malicious subdomains, domain generation abuse, fast-flux style abuse, and spam where spam is used to deliver or enable other abuse.

Domain abuse may be handled under this Policy, the Domain Abuse Policy, registry rules, registrar rules, ICANN requirements, NiRA rules, country-code registry rules, law enforcement requests, and provider abuse requirements.

You must not host, distribute, redirect to, link to, command, control, advertise, or facilitate malware, ransomware, spyware, trojans, droppers, exploit kits, botnets, loaders, credential harvesters, fake login pages, phishing pages, pharming systems, malicious browser extensions, or malicious downloads.

You must not collect, trade, verify, test, sell, publish, or use stolen credentials, session tokens, API keys, payment data, identity documents, or personal data obtained without proper authority.

Compromised customer websites used for phishing or malware remain the customer's responsibility. Reonr may disable, quarantine, suspend, or remove affected content to protect users and infrastructure.

You must not send spam, unsolicited bulk email, deceptive messages, purchased-list campaigns, harvested-list campaigns, snowshoe spam, phishing messages, malware messages, fraudulent outreach, or messages that violate applicable anti-spam, consumer protection, or electronic communications laws.

You must not use Reonr services to host landing pages, redirectors, images, tracking links, unsubscribe pages, DNS records, mailboxes, or infrastructure that supports spam or abusive messaging sent from another network.

High-volume mailing, newsletters, transactional mail, and marketing email must be permission-based, properly authenticated, honest, traceable, and compliant with applicable law and provider rules.

You must use accurate sender identity, valid reply handling, lawful consent, working unsubscribe methods where required, clean lists, proper bounce handling, and reasonable sending rates.

You should configure SPF, DKIM, DMARC, reverse DNS, and other sender authentication where applicable. Failure to maintain sender reputation may result in mail throttling, outbound mail limits, suspension, or refusal of mail service.

You must not forge headers, hide sender identity, evade reputation systems, rotate domains or IPs to bypass blocks, use open relays, operate spam traps, or continue sending to users who opted out.

You must not use Reonr services for denial-of-service attacks, distributed denial-of-service attacks, reflection attacks, amplification attacks, packet floods, port scanning, vulnerability scanning without authorization, brute-force attacks, credential stuffing, scraping attacks, spam relays, open proxies, command and control, or unauthorized access attempts.

You must not interfere with Reonr infrastructure, other customers, upstream providers, data centers, domain providers, payment providers, security systems, mail systems, DNS systems, or third-party networks.

You may only perform vulnerability scanning, penetration testing, load testing, stress testing, exploit testing, or security research against systems you own or are expressly authorized to test.

Security testing must not target Reonr infrastructure, other customers, shared systems, upstream providers, payment gateways, registrars, registries, or third-party networks without written authorization from the responsible owner.

Testing that causes instability, excessive load, alerts, security risk, reputation damage, or third-party complaints may be blocked or suspended even if you intended it as research.

You must use resources in a manner consistent with the service purchased. You must not consume excessive CPU, memory, disk I/O, network, process, database, mail, inode, storage, or backup resources in a way that harms service stability or other customers.

Reonr may apply limits, throttle usage, request optimization, move workloads, require an upgrade, disable scripts, suspend accounts, or terminate services where resource use is abusive, unsafe, or incompatible with the product type.

Shared and reseller hosting are designed for normal websites, email, databases, and business hosting use. They are not intended for sustained high-load workloads, file archives, public mirrors, video streaming hubs, mass mailing, crypto mining, bot systems, scraping farms, proxy networks, or abusive automation.

Unlimited or unmetered language is subject to fair use, technical limits, abuse controls, backup limits, inode limits, mail limits, and service stability requirements.

Server and cloud customers are responsible for securing, patching, monitoring, and managing their operating systems, applications, firewall rules, credentials, services, and users unless the service is expressly sold as managed.

You must not use server resources for abusive scanning, DDoS activity, malware hosting, botnet control, spam, public proxy abuse, credential attacks, mining abuse, illegal content, or activity that harms Reonr, upstream providers, or third-party networks.

Public proxies, VPN exit nodes, Tor exit nodes, open relays, traffic tunnels, anonymization services, and traffic relay services are prohibited unless Reonr expressly approves them in writing for the specific service and use case.

Even where a private proxy or VPN is approved, it must not be used for spam, scraping abuse, credential attacks, account creation abuse, payment abuse, evasion, unlawful access, or activity that generates abuse complaints.

Automation must be lawful, rate-limited, and respectful of target systems. You must not use Reonr services for abusive scraping, account creation abuse, ticket abuse, credential testing, inventory hoarding, ad fraud, fake engagement, spam comments, form abuse, or other automation that harms third parties.

High-volume automation may be restricted where it causes network complaints, provider complaints, excessive load, IP reputation damage, or legal risk.

Cryptocurrency mining, proof-of-work mining, mining pools, hidden mining scripts, resource monetization scripts, and similar sustained resource workloads are prohibited on shared, reseller, and managed hosting unless expressly approved in writing.

On VPS, cloud, or dedicated services, Reonr may prohibit or restrict mining where it violates provider rules, creates excessive load, harms hardware, causes network complaints, triggers abuse reports, or affects infrastructure stability.

Hosting storage must be used for active website, email, application, and service data related to the purchased hosting plan. You must not use hosting storage primarily for remote backups, file dumping, media archives, public file mirrors, pirated content, seedboxes, or unrelated storage services unless the plan expressly allows it.

You must not store malware, stolen data, leaked credentials, phishing kits, exploit kits, illegal content, or files that infringe intellectual property rights.

You must not use Reonr services for scams, impersonation, fake shops, counterfeit sales, investment fraud, romance fraud, payment fraud, chargeback abuse, identity fraud, false business information, stolen payment methods, or deceptive commercial activity.

Orders, renewals, or services linked to payment abuse, fraud indicators, false identity, stolen cards, mule accounts, sanctions risk, or chargeback abuse may be rejected, suspended, reversed, or terminated.

You must not use Reonr services to infringe copyright, trademarks, trade secrets, software licenses, database rights, design rights, publicity rights, or other intellectual property rights.

Examples include pirated software, cracked licenses, unauthorized streaming, counterfeit goods, unauthorized use of brands, fake login pages, illegal IPTV, unauthorized downloads, and other infringing materials.

Copyright and takedown complaints may also be handled under the Copyright / Takedown Policy.

You are responsible for ensuring that regulated activities are lawful in the jurisdictions where you operate and where your users are located. Reonr may restrict or refuse services involving high legal, payment, fraud, safety, or provider risk.

High-risk activities may include financial services, lending, investment offers, gambling, adult content, pharmaceuticals, weapons, health claims, money services, political campaigning, regulated data processing, and other activities requiring licenses or heightened compliance.

Reonr may require additional verification, refuse support, suspend services, or terminate accounts where regulated or high-risk activity creates unacceptable risk.

You must not use Reonr services to unlawfully collect, process, sell, publish, scrape, trade, leak, or misuse personal data, credentials, payment data, identity documents, private communications, location data, or sensitive information.

You are responsible for privacy notices, lawful basis, consent, security safeguards, data subject rights, and compliance obligations for data you collect or process using Reonr services.

You must not use Reonr services to generate, host, distribute, or automate deceptive content, impersonation, phishing, fraud, deepfake abuse, harassment, spam, illegal content, malware, credential theft, or other harmful activity.

AI-assisted or automated systems must comply with this Policy in the same way as human-created content and manual activity.

Resellers are responsible for their customers, sub-accounts, users, hosted domains, support processes, billing practices, abuse response, and policy enforcement.

You must ensure your customers comply with this Policy. Abuse by your customer, sub-account, developer, contractor, user, or compromised service may result in action against your reseller account or affected services.

Abuse reports should be sent to [email protected]. Reports should include the affected domain, IP address, URL, email headers, timestamps, screenshots, logs, evidence, and a clear explanation of the issue where available.

Legal notices should be sent to [email protected]. General support issues should be sent to [email protected]. Privacy requests should be sent to [email protected].

Incomplete reports may take longer to review. Reonr may request additional details before taking action unless urgent harm requires immediate action.

You must respond promptly to Reonr abuse notices, security notices, provider complaints, registrar notices, registry notices, and legal notices. The required response time may depend on severity.

You may be required to remove content, patch software, reset credentials, clean malware, disable scripts, stop sending mail, correct DNS records, suspend a customer, provide evidence, or explain remediation steps.

Failure to respond, repeated incomplete responses, or failure to fix the issue may lead to suspension or termination.

Reonr may investigate suspected abuse using account records, server logs, mail logs, DNS records, domain records, support history, payment records, security alerts, third-party reports, provider notices, malware scans, screenshots, and other available evidence.

Reonr may access affected services where reasonably necessary to identify, contain, investigate, remediate, preserve, or verify abuse, security incidents, legal requests, or policy violations.

Reonr may take enforcement action based on severity, evidence, customer history, risk, provider requirements, legal obligations, and impact on infrastructure or third parties.

Enforcement may include warning, support ticket request, throttling, outbound mail restriction, file quarantine, malware removal, DNS disablement, URL disablement, domain lock, nameserver change, IP null-route, firewall block, service suspension, account suspension, termination, refusal of renewal, provider escalation, or report to authorities.

Reonr may act without prior notice where necessary to protect users, infrastructure, customers, third-party networks, payment systems, domain systems, legal compliance, public safety, or service availability.

Urgent action may be used for phishing, malware, child safety issues, active attacks, spam outbreaks, exposed credentials, DDoS activity, law enforcement requests, registrar or registry requirements, severe resource abuse, or repeated policy violations.

Reonr may preserve account data, logs, files, domains, DNS records, payment records, support records, or other evidence where reasonably necessary for abuse handling, security, legal compliance, provider requirements, dispute handling, or enforcement.

Reonr may disclose relevant information to registrars, registries, data centers, payment gateways, security vendors, law enforcement, regulators, complainants, affected parties, or professional advisers where required or permitted by law, provider rules, policy enforcement, or protection of rights and safety.

Repeated abuse, repeated compromise, repeated spam complaints, repeated malware infections, repeated ignored notices, or repeated provider complaints may result in stronger enforcement, including permanent termination or refusal of future service.

Reonr may treat related accounts, reseller sub-accounts, repeated domain patterns, repeated payment patterns, or accounts under common control as connected where needed to prevent abuse evasion.

You may be responsible for costs caused by abuse or policy violations, including restore fees, cleanup fees, chargeback fees, provider fees, domain recovery fees, manual support fees, emergency work, incident response, and third-party charges.

Payment of fees does not guarantee reinstatement where the risk remains unacceptable or the violation is serious.

If you believe enforcement was applied in error, you may contact [email protected] or [email protected] with evidence, explanation, remediation steps, and account details.

Reonr may require cleanup, verification, password resets, software updates, customer removal, configuration changes, payment correction, abuse history review, or written assurances before reinstatement.

Reinstatement is not guaranteed, especially for serious abuse, unlawful content, repeated violations, chargeback abuse, fraud, or provider-imposed restrictions.

This Policy should be read with the Terms of Service, Hosting Abuse Policy, Domain Abuse Policy, Copyright / Takedown Policy, Privacy Policy, Cookie Policy, Refund Policy, and any service-specific rules.

Where a specific policy provides more detailed rules for a specific issue, that policy applies together with this Acceptable Use Policy.

Reonr may update this Acceptable Use Policy from time to time to reflect legal, technical, security, provider, operational, or business changes. The updated version will be posted with a revised Last Updated date.

Continued use of services after changes take effect means you accept the updated Policy.

Business address: Port Harcourt, Rivers, Nigeria.

Abuse reports should be sent to [email protected]. Legal notices and policy questions should be sent to [email protected]. Support requests and general account issues should be sent to [email protected]. Privacy requests should be sent to [email protected].

Contact should be made by email through the channels listed in this section unless Reonr provides a different channel for a specific service, dispute, or legal process.