Acceptable Use Policy

1 Purpose

This Acceptable Use Policy ("AUP") defines what you may and may not do when using the Viirless Discord bot hosting platform ("Service"). It applies to all users regardless of plan and is incorporated by reference into the Terms of Service.

The goal of this policy is to protect the integrity and availability of the platform, the safety of other users, and compliance with applicable law. Viirless is a shared-infrastructure hosting service — abuse by one user impacts everyone.

2 Permitted Uses

The Service is designed exclusively for hosting Discord bots. The following are examples of permitted use:

• Hosting Discord bots that interact with the Discord API in compliance with Discord's Terms of Service and Developer Policy
• Running utility bots (moderation, music, games, economy, logging, etc.) for Discord servers you own or manage
• Running scheduled tasks or background jobs directly related to your Discord bot's functionality
• Using environment variables to store your Discord bot token and other credentials needed by your bot
• Uploading bot source code via ZIP archive or a GitHub repository you own or have permission to use
• Using the dashboard API to automate management of your own bots
• Using the collaboration feature to invite trusted team members to help view, manage, or operate a bot you own, within the permission levels you configure

3 Prohibited Activities

The following activities are strictly prohibited. This list is not exhaustive — Viirless reserves the right to take action against any use we determine to be harmful, abusive, or contrary to the spirit of this policy.

3.1 Illegal & Harmful Content

• Hosting, distributing, or linking to child sexual abuse material (CSAM) or any content that sexually exploits minors
• Distributing malware, ransomware, spyware, trojans, or any malicious code
• Storing, processing, or transmitting stolen personal data, login credentials, or financial information obtained without authorisation
• Facilitating illegal gambling, drug trafficking, weapons sales, or other criminal activity

3.2 Platform Abuse & Resource Misuse

• Cryptocurrency mining or any proof-of-work computation unrelated to a Discord bot
• Running processes that are not part of your Discord bot's functionality (e.g. web scrapers, proxy servers, VPNs, general-purpose compute)
• Deliberately consuming excess CPU, RAM, disk, or bandwidth to degrade the experience for other users ("noisy neighbour" abuse)
• Circumventing container resource limits through technical means
• Storing large media files, datasets, or archives unrelated to your bot's operation

3.3 Discord & Third-Party Abuse

• Operating selfbots or user account automation in violation of Discord's Terms of Service
• Mass spamming, raiding, nuking, or coordinating harassment against Discord servers or their members
• Running token loggers, phishing bots, or credential-harvesting scripts targeting Discord users
• Scraping Discord user data (messages, profiles, IDs) at scale without explicit consent
• Impersonating Discord staff, other services, or known public figures
• Launching or facilitating DDoS attacks, IP stressers, or any network disruption against Discord or any third party
• Discord API rate-limit abuse: deliberately or negligently causing 100 or more HTTP 429 (rate limit) responses within a 15-minute window. This includes — but is not limited to — sending commands or messages in tight loops, flooding interactions, or otherwise making requests at a rate that exceeds Discord's published limits
• Gateway reconnect flooding: causing your bot to repeatedly reconnect to Discord's WebSocket gateway without a genuine reason (e.g. in a tight retry loop after an error), resulting in 100 or more reconnect events within 15 minutes
• Message, presence, or interaction spam: sending bulk messages, spamming presence/status updates, or flooding interaction replies/edits at rates that violate Discord's rate limits or constitute harassment of servers, channels, or users

3.4 Platform Security & Integrity

• Attempting to escape Docker container isolation or access the host filesystem, network, or other users' containers
• Probing, scanning, or attempting to exploit vulnerabilities in the Viirless platform or its infrastructure
• Reverse-engineering, decompiling, or otherwise attempting to derive the source code of the Viirless platform
• Using the Service to attack, probe, or scan third-party systems or networks
• Circumventing rate limits, authentication, or other security controls

3.5 Account & Billing Abuse

• Creating multiple accounts to circumvent free-plan limits or abuse trial resources
• Sharing, selling, or transferring your account or login credentials to third parties
• Reselling access to the Service or subletting container resources without written permission from Viirless
• Filing fraudulent chargebacks or payment disputes for services that were delivered
• Using stolen payment methods or fraudulent billing information to purchase tokens, bot slots, plan subscriptions, or any other platform feature
• Initiating a chargeback on a monthly recurring plan payment and continuing to use the service during the disputed period
• Purchasing extra bot slots through legitimate means and then using those slots in combination with banned or suspended accounts, or otherwise using purchased slots to circumvent enforcement action
• Registering or using a third-party account to regain access to the Service following a suspension or ban ("ban evasion by proxy") — both the evading account and any associated accounts will be permanently terminated
• Using collaboration invitations to grant access to suspended or banned users, or to circumvent plan-level bot limits
• Accepting a collaboration invitation for the purpose of extracting, copying, or misusing the bot owner's source code, environment variables, secrets, or credentials
• As a collaborator, using your granted access for any purpose beyond the legitimate management of the shared bot — including modifying files, environment variables, or bot behaviour in ways not authorised by the bot owner
• Unban review system abuse: submitting false, fabricated, or materially misleading information in an unban review request for the purpose of circumventing a legitimate ban
• Filing a chargeback or payment dispute with your bank or card issuer for an unban review fee after the review has been completed — whether the outcome was an approval or a denial — constitutes a fraudulent chargeback and will result in permanent termination with no further right of review
• Using the unban review process as a delay tactic while continuing to operate ban-evading accounts or violate platform policies during a pending review period
• Harassing, threatening, or attempting to coerce Viirless staff members in connection with an unban review request or its outcome

4 Collaboration Feature

The Viirless collaboration feature allows bot owners to invite other registered users to help manage a specific bot. The following rules apply to all parties involved in a collaboration.

4.1 Bot Owner Responsibilities

• You are fully responsible for all actions taken by collaborators you invite.
• You must not invite users who have been suspended or banned from the platform.
• Think carefully before granting "View Env" permission — it exposes sensitive secrets such as your Discord bot token to the collaborator.
• You must not use collaboration as a mechanism to share a single bot subscription across multiple unrelated parties in a commercial or semi-commercial arrangement without written permission from Viirless.

4.2 Collaborator Responsibilities

• Your access is limited to the specific bot you have been invited to, within the permissions the owner has configured.
• You must not attempt to access resources, files, or configuration beyond what your permission level allows.
• You must not exfiltrate, copy, share, or misuse the bot owner's source code or environment variable secrets.
• All actions you take on a shared bot are subject to this AUP and the Terms of Service — violations may result in enforcement action against your own account.

5 AI Coding Assistant

Viirless provides an optional AI Coding Assistant that lets you interact with Google Gemini directly within the file editor of your bot. The following rules apply to all users of this feature.

5.1 Permitted uses

• Using the AI to write, edit, refactor, or debug your Discord bot's source code
• Using the AI to manage your bot's environment variables (set, update, delete)
• Using the AI to explore and understand your own bot's file structure
• Any other use that is lawful, within the spirit of the platform, and compliant with Google's AI usage policies

5.2 Prohibited uses

You must not use the AI Coding Assistant to:

• Access other users' bots or files — the AI operates only within your own bot's directory; any attempt to use prompt injection or other techniques to break out of this sandbox is strictly prohibited
• Generate malicious code — including bots that perform DDoS attacks, spam, phishing, credential harvesting, self-replication, or any other harmful activity
• Circumvent platform restrictions — do not use the AI to create code that attempts to escape container isolation, access other users' data, or bypass rate limits or resource quotas
• Submit prompts that violate Google's usage policies — including requests for illegal content, content that sexualises minors, or content that violates Google's Generative AI Prohibited Use Policy
• Use the API key of another person without permission — only use API keys that you own or are authorised to use
• Automate abuse — do not write scripts or bots that interact with the AI Coding Assistant in an automated fashion to bypass quotas, generate spam, or scrape the service

5.3 Your responsibility for AI output

You are solely responsible for reviewing, testing, and taking responsibility for any code generated by the AI Coding Assistant before running it. Viirless does not warrant the safety, correctness, or security of AI-generated code. If the AI generates code that causes harm — to your bot, your users, or third parties — you bear full responsibility.

6 Discord Policy Compliance

All bots hosted on Viirless must comply with Discord's current policies at all times, including:

• Discord Terms of Service
• Discord Community Guidelines
• Discord Developer Policy

This includes bots that are generated in whole or in part by the AI Coding Assistant. The fact that code was AI-generated does not exempt it from compliance with Discord's policies or these Terms.

7 Egress IP Responsibility

Each bot hosted on Viirless is assigned a dedicated outbound IP address from our IP pool. This IP is permanent and is used for all of that bot's outbound internet traffic, including all connections to Discord's HTTP API and Gateway.

7.1 Your Responsibilities

• You are responsible for ensuring your bot does not behave in a way that causes its assigned IP to be rate-limited, flagged, or blocked by Discord or any third-party service.
• Your assigned IP is not shared with other users' bots. If your IP becomes blocked by Discord, it affects only your bot — but it also means only you are responsible for the behaviour that caused it.
• You must not deliberately attempt to trigger platform-wide rate limits or cause Viirless's IP pool to be degraded as a form of sabotage or protest.

7.2 Prohibited IP-Related Behaviour

• Deliberately writing bot code that generates abusive request patterns for the purpose of getting the assigned IP rate-limited or blocked by Discord
• Attempting to circumvent or disable the platform's automatic abuse detection (e.g. by suppressing log output that would otherwise trigger detection)
• Using multiple bots across different IPs in a coordinated manner to distribute abusive load and evade per-IP thresholds

8 Enforcement

Viirless monitors platform resource usage and log output and may investigate reported or suspected violations. Enforcement actions may include, depending on the severity and nature of the violation:

• Automatic warning flag — set by the platform's automated abuse detector when a bot exceeds a warning threshold; visible to administrators but does not stop the bot
• Automatic bot suspension — triggered immediately and without prior notice when a bot exceeds a critical abuse threshold (see Section 7 and Terms of Service Section 5.2); the bot is stopped and locked until the issue is resolved
• A manual warning issued to the account holder by staff
• Manual temporary or permanent suspension of the offending bot by staff
• Suspension or termination of the account (with or without notice)
• Reporting the activity to Discord Trust & Safety, law enforcement, or other relevant authorities

Viirless reserves the right to act immediately and without notice when we believe continued operation poses an imminent risk to the platform, other users, or third parties. Automatic suspensions do not require human review prior to taking effect.

9 Reporting Violations

If you become aware of a bot hosted on Viirless that is violating this policy or applicable law, please report it to us:

• Support ticket — open a ticket from your dashboard
• Email — abuse@viirless.net
• Discord — via our support server

We take all abuse reports seriously and aim to respond within 24 hours for urgent matters.

10 Bot Template Marketplace

The Viirless Marketplace allows users to publish and acquire Discord bot templates. The following rules apply to all Marketplace participants in addition to all other sections of this AUP.

10.1 Template Uploads — Permitted

• Submitting templates built from your own original code or code you hold valid distribution rights to
• Publishing free templates for the community at no token cost to buyers
• Publishing paid templates at a token price you set
• Including placeholder descriptions for required environment variable keys to help buyers understand what values to supply
• Updating or withdrawing your pending template submissions prior to admin approval
• Requesting review and reinstatement of a denied template after addressing the stated reason for denial

10.2 Template Uploads — Prohibited

• Uploading templates that contain malicious code — including token grabbers, webhook exfiltration, credential harvesters, backdoors, ransomware components, obfuscated harmful scripts, or any code designed to harm users who import or run the template
• Uploading templates that contain CSAM, illegal content, or code that violates Discord's Terms of Service or Developer Policy
• Embedding your own Discord bot token, API keys, database credentials, or any other sensitive secret values inside template source files — env values must never be included in templates
• Uploading code you do not own or have permission to distribute (copyright infringement)
• Creating misleading or fraudulent template listings that misrepresent the template's functionality, language, category, or origin
• Deliberately obfuscating code to make security review more difficult
• Using template uploads as a vector to attempt path traversal, zip-slip, or other file extraction attacks against platform infrastructure

10.3 Acquiring & Using Templates — Prohibited

• Purchasing or claiming templates using stolen, fraudulently obtained, or manipulated token balances
• Attempting to duplicate-claim free templates in an automated or coordinated manner to abuse storage limits
• Using the "import into existing bot" feature to maliciously overwrite another user's bot files without their consent (applicable to collaborators)
• Reverse-engineering or redistributing paid template source code outside of the platform's permitted personal deployment use
• Manipulating download or purchase counts through automated bots, coordinated actions, or fraudulent means

11 Changes to This Policy

We may update this AUP at any time. Changes will be posted to this page with an updated date. Continued use of the Service after changes are posted constitutes acceptance of the revised policy. For material changes we will provide notice via the dashboard or our Discord server.

Questions about this policy? Contact us at support@viirless.net or open a support ticket from the dashboard.