Acceptable Use Policy
Effective date: November 6, 2026
Soulixer provides hosting for websites, game communities, bots, and server workloads. This Acceptable Use Policy (AUP) sets out how those services may be used while protecting other customers, third parties, and the hosting environment. It forms part of our Terms of Service.
1. Scope and responsibility
1.1. This policy applies to your Soulixer account and every service you purchase or operate through it. It also covers activity carried out through access you give to developers, administrators, players, end users, or other third parties.
1.2. Use each service for the purposes and within the permissions described in its plan. Administrative access, an available port, or an unused resource allocation does not authorize activity that harms others or breaches these rules.
1.3. You must have the permissions needed for the content, applications, and data you host. A service may be used only in accordance with applicable law and the terms of any third-party platforms it connects to.
2. Content, rights, and personal safety
2.1. Do not use Soulixer to commit fraud, steal credentials or identities, distribute harmful software, or operate deceptive pages, services, or payment schemes.
2.2. Content involving child sexual abuse or exploitation, criminal threats, or unlawful promotion of violence is prohibited. We may restrict access immediately and handle relevant evidence or reports as required by law.
2.3. Do not host or distribute material that infringes another party's rights, including unlicensed commercial software or assets you have no right to share. Legitimate open-source software, permitted modifications, and properly licensed content remain subject to their own licence terms.
2.4. Do not publish private personal information without a lawful basis, facilitate stalking or targeted harassment, or use hosted services to threaten people. Reports must identify the relevant conduct; a complaint alone does not establish that a policy violation occurred.
3. Network and security boundaries
3.1. Do not attack, disrupt, intercept, or access systems without authorization. This includes operating attack-for-hire services, coordinating traffic floods, stealing access tokens, or attempting to compromise another customer's service.
3.2. Security testing must be lawfully authorized by the owner of every target and remain within a defined scope. Obtain Soulixer's written approval before testing activity that could affect shared infrastructure, other customers, or the stability of our network.
3.3. Do not bypass service isolation, evade resource controls, tamper with the hosting platform, impersonate network identities, or use a service to conceal or relay abuse. Report a suspected Soulixer vulnerability privately to support instead of testing it against unrelated accounts.
4. Email, bots, and automation
4.1. Mail and automated messages must follow the permissions included in your service and the rules of the receiving platform. Recipients must have an appropriate basis for receiving the messages. Do not use purchased or harvested contact lists for unsolicited bulk messaging.
4.2. Bots must operate with valid permissions and credentials. Do not use them for account takeovers, credential collection, spam, harassment, deceptive engagement, or evasion of platform restrictions.
4.3. Do not run an unrestricted mail relay or forward traffic that you cannot reasonably control. If your application becomes compromised or begins sending unwanted traffic, stop the affected process, secure the credentials, and cooperate with the investigation.
5. Rules for hosted workloads
5.1. Game hosting may run the game servers and permitted plugins or mods supported by the plan. Do not deliberately crash shared hosts, exploit management interfaces, attack other communities, or distribute game assets without the necessary rights.
5.2. Shared web hosting is intended for the websites and related applications described in the plan. Public file-distribution platforms, unrelated bulk storage, high-volume relays, or persistent compute jobs require a plan that expressly supports those workloads.
5.3. For customer-managed VPS or other services with administrative access, you are responsible for the operating system, installed applications, access controls, and security updates unless your order includes those management tasks. A compromised service must be secured even where the initial compromise was unintentional.
5.4. Cryptocurrency mining, public proxy or VPN resale, and sustained benchmarking require a plan that expressly permits the workload. Do not run these workloads on game, bot, or shared web hosting plans.
6. Resource use and fair sharing
6.1. Follow the CPU, memory, storage, bandwidth, process, and other limits stated for your plan. Do not circumvent those limits or move abusive processes between services to avoid intervention.
6.2. Dedicated allocations may be used within the purchased plan's stated limits. Shared allocations must also be used in a way that preserves reasonable access for other customers. Resource use is assessed against the plan and its effect on the hosting environment, rather than a universal unpublished CPU percentage.
6.3. If a workload exceeds its limits or materially affects other services, we may ask you to optimize it, reduce its impact, or move to an appropriate plan. Immediate rate limits or isolation may be necessary while an active disruption is contained.
6.4. Keep storage relevant to the service you purchased and remove unwanted processes or files. A reference to unmetered usage does not remove the technical capacity, workload restrictions, or other limits expressly stated for the plan.
7. Accounts, access, and payment integrity
7.1. Keep account and billing information accurate. Do not use stolen payment details, fabricated identities, or additional accounts to evade a suspension, a required verification, promotion limits, or refund restrictions.
7.2. Protect passwords, API keys, and access tokens, and grant access only to people you authorize. Notify support promptly if you suspect that your account or service has been taken over.
7.3. Reselling or transferring service access as a business requires the permission set out in your plan or Soulixer's written authorization. You remain responsible for the activity of people to whom you provide access.
8. Abuse notices and urgent containment
8.1. Monitor your registered email and client account for service notices. Respond to an abuse notice within 24 hours, or within a shorter deadline clearly stated for an urgent security incident, and explain the steps taken to stop the activity.
8.2. When feasible, a notice will identify the affected service, the rule involved, and the action needed. We may request relevant logs or other information needed to distinguish a configuration problem, compromised service, or deliberate misuse.
8.3. Active attacks, serious threats, unlawful exploitation material, or an ongoing compromise may require immediate containment without waiting for a response. Measures may include stopping a process, restricting network access, or temporarily suspending the affected service.
9. Enforcement and review
9.1. Enforcement depends on the seriousness, impact, evidence, and history of the incident. A warning, corrective action, temporary restriction, or termination may be appropriate. Repeated evasion or refusal to resolve an established violation may lead to wider account restrictions under the Terms of Service.
9.2. To request a review, reply to the notice or open a support ticket with the service ID, your explanation, and any remediation evidence. We will consider relevant information, including evidence that an allegation is mistaken. Restoration may depend on the service being safe to operate and any applicable legal restrictions.
9.3. Suspension, termination, and refund eligibility are governed by the Terms of Service and Refund Policy. Availability assessments are governed separately by the Service Level Agreement. This policy does not remove rights or remedies that cannot lawfully be excluded.
10. Data protection and backups
10.1. Information used to investigate abuse is handled in accordance with our Privacy Policy. Reports should contain only the information reasonably needed to identify and assess the issue.
10.2. Maintain independent backups of your hosted content. Suspension or termination may restrict access, and this policy does not create a backup, retention, or restoration guarantee. Data handling remains subject to the applicable service terms and legal requirements.
11. Reporting a concern
11.1. Send abuse reports to abuse@soulixer.in. Include the relevant domain, IP address or service reference, incident times with their time zone, a clear explanation, and suitable supporting evidence. Do not send passwords, access tokens, or unnecessary personal data.
11.2. For suspected child exploitation or other illegal material, provide its location or identifying reference without downloading, uploading, or forwarding the material itself. If someone is in immediate danger, contact the appropriate emergency authority.
11.3. For help with your own service, open a support ticket or email support@soulixer.in from your registered address. Knowingly fabricated reports or threats made to obtain a benefit may themselves be investigated as abuse.
12. Policy updates
12.1. The effective date above identifies this version. Soulixer may publish updates to address changes in its services, security needs, or legal obligations. Review the current policy alongside the terms supplied with your plan.
12.2. Updated rules apply prospectively, subject to applicable law and written service commitments. An update does not itself make previously permitted conduct a past violation; existing prohibitions and urgent security measures continue to apply.