Private infrastructure. Responsible use.
Build your own services, protect your communications and keep control of your software. These usage rules set the boundaries for workloads hosted through SilentVPS.
Workloads within the catalogue
Self-hosted applications, private clouds, mailboxes, lawful seedboxes, personal VPNs, encrypted tunnels and onion services fit the privacy-focused catalogue. A technology such as Tor or WireGuard does not make a project prohibited by itself.
Tor middle relays and bridges are within the intended workloads. Tor exit nodes are excluded from this catalogue. Check with the operator if your workload requires a special network policy, public proxy, intensive scanning or sustained resource use beyond the selected plan.
Prohibited activity
- Malware distribution, phishing, credential theft, botnet control and fraudulent impersonation.
- Denial-of-service attacks, unauthorized access, exploitation or scanning of systems without permission.
- Unsolicited bulk messaging, abusive mail relaying and deliberate evasion of abuse controls.
- Illegal content, including child sexual abuse material, and unlawful distribution of content for which you do not have the necessary rights.
- Interference with other customers, attempts to escape server isolation or deliberate disruption of the host network.
Your responsibility for the server
Keep the operating system and applications patched, protect credentials and SSH keys, and restrict exposed ports to what your project needs. Maintain independent backups of important data. Root access also gives you responsibility for your configuration.
Use CPU, memory, storage and transfer within your selected allocation. Do not treat a listed traffic allowance as permission to attack another network or degrade a shared service.
Reporting abuse
Use the contact page with the affected address or domain, relevant timestamps and time zone, a concise description, and evidence you are entitled to share. Provide enough context to distinguish legitimate research or a relay from an actual attack.
Do not send passwords, wallet recovery phrases, private keys or unrelated personal information. The contact form returns a reference for the saved report; that acknowledgement is not a promise of a response time.
Assessment and protective measures
Reports should be assessed on their evidence, the applicable rules and the effect on others. An allegation alone does not establish that an account acted unlawfully. Where a security incident or harmful activity requires intervention, protective measures can include restricting a workload or suspending access.
This page does not set a guaranteed investigation timeline, an appeal deadline or an automatic refund outcome. Order and refund questions are covered separately so that usage restrictions are not confused with payment status.