Acceptable Use and Abuse Measures at SolumeCore
What is not allowed on SolumeCore, how abuse is monitored, which measures come before a suspension, what happens to your data and how to appeal.
SolumeCore hosts game servers, apps, websites and virtual servers on shared infrastructure, so a few rules keep every customer's service healthy. This document summarises what is not allowed, how abuse is detected in general terms, the order in which measures are applied, what happens to your data during a case and how to appeal. The binding text is always the Terms of Service and the Acceptable Use Policy, which SolumeCore publishes on its website; this page is an explanation, not a replacement.
The short version: we aim to isolate before suspending. A notice with evidence comes first, the smallest effective measure second, time to fix it third, and suspension only as a last resort.
What is not allowed
Across the Terms of Service and the Acceptable Use Policy, the main prohibited uses are:
- Cryptocurrency mining on shared plans (game servers, apps and web hosting). The Terms also prohibit undeclared mining that degrades other customers on shared infrastructure.
- Attacks of any kind: DDoS, scanning third-party ports, brute force, or attempts to access other people's systems from our network.
- Spam and abusive relays: sending unsolicited email, phishing, or running open relays and open proxies.
- Malware and content that is illegal where we operate, or that infringes someone's intellectual property.
- Deliberately degrading other customers on the same node.
- Reselling the service, or offering it as a public VPN, open proxy or tunnel service for third parties, unless your plan expressly allows it.
- Hiding abuse: using VPNs, proxies or tunnels to conceal the real origin or destination of activity that would otherwise break the rules. Using them for your own legitimate purposes (remote access, privacy, development) is not prohibited.
- Testing our platform (vulnerability scans, brute force, exploiting the panel, API or infrastructure) without prior written authorization. If you find a real vulnerability, report it to [email protected] instead of exploiting it.
If you are unsure whether a use case is allowed, ask in a ticket before you deploy it. That is much easier than resolving a case afterwards.
How abuse is monitored
SolumeCore uses automated monitoring of resource usage and network behaviour, depending on the product, and staff review what the systems flag. Monitoring focuses on abuse indicators, such as unusual sustained load, outgoing traffic patterns and markers of known malicious software. It is not a human review of your private content, and the Terms state that we do not access or monitor the content of your server except when strictly necessary to support you, to investigate a reported violation, or when the law requires it.
We do not publish detection signals or thresholds, because that would only help people who want to evade them. Detections can be wrong, which is why every measure is reversible and can be appealed.
What happens when something is detected
The Acceptable Use Policy describes a ladder, from lightest to heaviest:
- Notice with evidence. A notice in your panel tells you what was detected, when and on which server, with the minimum evidence needed. Reports from third parties are anonymised.
- The smallest possible measure. Limiting or isolating only the abusive process or traffic (for example, outgoing connections) instead of switching everything off. Players and visitors keep connecting whenever possible.
- Time to fix it. The notice tells you what to do. Most cases end here.
- Suspension as a last resort, for severe or repeated abuse, or when the risk to other customers or the network cannot be contained any other way.
Internally, measures include recording the event, alerting staff, limiting CPU, isolating outgoing connections, stopping the server and suspending it. Which of them are applied automatically versus manually is a configuration decision and can change over time. The Terms also reserve the right to suspend immediately, without prior notice, any service that is harming our network or third parties, and to tell you the reason as soon as possible afterwards.
Important: suspension for abuse is not the same as suspension for non-payment. Paying an invoice does not lift an abuse measure. For billing suspensions, see service suspension for non-payment.
What you should do if you receive a notice
- Read the evidence in the notice: the listed processes, files or connections.
- Remove anything you do not recognise. A server can be abused by someone else if it was compromised, for example through a weak password or an outdated plugin.
- Change your passwords and review who has access to the server (see delegated access and account security).
- If you think it is a mistake, appeal.
Appeals
Where case details and appeals are enabled, each case in your panel shows its evidence and an Appeal button. It opens a support ticket already linked to the case, and a person reviews it; the public policy page states the response commitment it is configured with. While a case or an appeal is open, the policy states that your data is not deleted and that you can export it.
These features belong to SolumeCore's "Trust" module and are configurable, so what you see may differ. If you do not see a case or an Appeal button, open a ticket yourself and mention the notice you received. If your account has been suspended, the panel can still let you open tickets and, where enabled, view and appeal your cases. If you cannot sign in at all, contact support through the contact page.
Data during and after a case
- Evidence kept for a case is limited to what is needed to describe it, and is purged after a retention period once the case is closed.
- A service with an open abuse case or appeal is not purged by the automatic cleanup that follows cancellations.
- Whether a final downloadable backup is offered when cancelling a service that was suspended for abuse is a policy setting that is off by default, especially because of illegal content. Do not count on one; keep your own backups (see backups and retention).
Reporting abuse
If you believe a SolumeCore customer is attacking you or hosting abusive content, send the details (addresses, timestamps, logs) to support through the contact page or by email to [email protected]. Reports from third parties are handled with anonymisation when they are shown to the customer concerned.
Related documents
- Service suspension for non-payment
- DDoS protection and firewall
- Backups and retention
- Account security
FAQ
Is cryptocurrency mining allowed?
Not on shared plans such as game servers, apps and web hosting. The Terms also forbid undeclared mining that degrades other customers on shared infrastructure. If you need dedicated compute for that kind of workload, ask support before ordering rather than assuming.
Will my server be suspended without warning?
The policy aims for a notice first and the smallest effective measure. However, the Terms reserve the right to suspend immediately, without prior notice, a service that is harming our network or third parties, and to notify you as soon as possible with the reason.
Can I still reach my files during an abuse suspension?
That depends on the measure and the product. A limit or isolation keeps the server running; a suspension blocks console, file and SFTP access. Open a ticket to discuss what is possible.
How do I contest a decision?
Use the Appeal button on the case if it is shown, or open a ticket explaining why you believe the detection is wrong. A person reviews each appeal.
Are my files being read?
The Terms say we do not access or monitor the content of your server except when strictly necessary to support you, to investigate a reported violation, or when the law requires it. Automated monitoring looks for abuse indicators rather than reading your private content.