Abuse Policy

1.1. Abuse reports are accepted at abuse@averisca.cloud. For efficient review, please include the VPS or IP, category, date and time with time zone, event description, URL or domain, log excerpts, email headers or other technical evidence, and a reply contact where available. Not every field is required.

1.2. This policy applies to VPS and other Averisca services where security and abuse matters are involved.

2.1. Receiving a report does not itself establish a violation, trigger an automatic block, or constitute an admission of user responsibility.

2.2. The service may review the report, request more information, identify the related VPS or IP, review available technical logs, and reject an obviously incomplete, inaccurate, fraudulent, or unrelated report.

3.1. If a report appears substantiated after an initial review, the service sends a notice to the account email with the VPS or IP, category, issue description, required action, and response deadline.

3.2. The standard response period is up to 24 hours from the time the notice is sent.

3.3. The user may resolve the issue, contact support, explain the situation, report a compromised VPS, or provide information showing that no violation occurred.

3.4. If the issue is resolved, the case is closed. If the user does not respond, abuse continues, or required steps are not taken, the service may restrict network access, temporarily suspend the VPS, or apply another minimally necessary technical restriction.

4.1. Where there is an ongoing immediate threat, the service may immediately and temporarily restrict the VPS or network without waiting 24 hours. Examples include an active DDoS attack, botnet/C2, malware propagation, phishing, mass spam, intensive brute force, mass scanning, a compromised VPS continuing to attack, or a threat to Averisca infrastructure stability.

4.2. Immediate restriction is a temporary protective measure, not an automatic permanent termination. Once the threat is stopped, the service will notify the user, explain the reason, and, where reasonable, allow remediation and consider restoration or further measures.

5.1. A first compromise incident is not automatically treated as intentional user misconduct. The service may temporarily disconnect the network or VPS to stop an attack.

5.2. The user may be asked to rotate passwords and SSH keys, reinstall the operating system, fix the vulnerability, remove malware, update software, or restore data from a backup. The VPS may be restored after the issue is resolved.

6.1. For repeated violations, deliberate attacks, phishing, botnet operation, deliberate malware distribution, intentional circumvention of restrictions, systematic disregard of notices, or predominant use of a VPS for prohibited activity, the service may terminate the VPS, refuse restoration, refuse new orders or future renewals, and reasonably limit new orders to prevent repeated abuse.

7.1. The decision to restrict a service and the question of a refund are separate. Restriction does not itself mean automatic forfeiture of all funds.

7.2. Voluntary refunds may be limited in cases of confirmed fraud, deliberate abuse, or gross violation to the extent permitted by applicable law. General refund rules are set out in Section 7 of the Public Offer.