Terms of service

ExtraHosting provides managed hosting for Discord.js projects, with GitHub deployments, project controls, logs, and resource monitoring. These terms describe the conditions for using the service. If you use ExtraHosting on behalf of a team or organisation, you must have permission to act for it.

You must be eligible to use Discord and GitHub under their own terms and comply with the laws that apply to you. ExtraHosting is an independent service and is not affiliated with or endorsed by Discord or GitHub.

Sign in with your own Discord account. You are responsible for protecting your account, bot tokens, GitHub permissions, and project credentials. Review active sessions and collaborator access, and tell your hosting administrator if you suspect unauthorised use.

Give collaborators only the access they need. You are responsible for the projects and activity you authorise through your account.

Hosting access is granted by an administrator. Your active plan determines the available project slots, resources, features, and access period. Any price, payment arrangement, renewal, or refund conditions must be agreed with the administrator when hosting is arranged.

Activating a project uses a hosting slot and requires available worker capacity. An unused slot does not guarantee immediate activation. New allocations and resource increases may be temporarily unavailable when safe capacity is full.

Capacity protection does not by itself stop existing projects. Separate access rules still apply: expired or suspended hosting access can stop projects and disable automatic deployments. Renew access before it expires if you need the project to continue running.

Use ExtraHosting for projects you are authorised to host. Do not use the service to:

• Host unlawful content, malware, phishing, or credential theft.
• Send spam, attack other services, or violate Discord or GitHub policies.
• Access another account, project, or system without permission.
• Bypass security controls, isolation, plan limits, or resource restrictions.
• Deliberately exhaust shared resources or interfere with other customers.

Administrators may restrict access or suspend an offending project to address abuse, security incidents, or violations of these terms. These actions are separate from admission controls for new capacity.

You retain your rights to the code and data you upload. You authorise ExtraHosting to access, copy, build, run, and store that material as needed to provide hosting and the features you enable.

You must have the rights to your repositories, dependencies, and content. You are responsible for your bot’s behaviour and for any personal data it collects, including providing appropriate notices and permissions to its users.

Account and hosting data are described in the Privacy policy. Keep secrets in project environment variables and avoid writing credentials or unnecessary personal data to logs.

Store persistent project data in the documented data directory. Other files inside the runtime container are temporary and can be replaced during deployment. Resource and storage limits continue to apply.

Backup availability and the number of snapshots retained depend on your plan and configuration. Restoring a snapshot replaces the project data covered by that snapshot. Keep your own copies of important code and data; hosted snapshots are not a substitute for an independent backup.

Deleting a project removes its hosting workload and can permanently remove its stored files and snapshots. Export anything you need before deleting. See the documentation for deployment and restore requirements.

Deployments and runtime availability depend on your code, dependencies, plan limits, available infrastructure, and external services. Maintenance, network failures, or incidents may interrupt hosting. No specific uptime or recovery commitment applies unless separately agreed in writing.

You are responsible for testing your bot, monitoring its behaviour, and choosing resources suitable for its workload. Nothing in these terms excludes liability or consumer rights that cannot lawfully be excluded.

You can stop or delete projects and release hosting access using the available dashboard controls. Releasing access or deleting a project does not automatically delete your account or every operational record.

For account closure, data requests, or questions about an existing hosting arrangement, contact your hosting administrator. Export required data and disconnect integrations before ending access.

These terms may be updated as the service changes. The date at the top identifies the current version. Any change remains subject to applicable law and any separate agreement governing your hosting.

Contact the ExtraHosting administrator who arranged your hosting access through the channel you used to arrange it. Include your account or project name, but never send passwords, bot tokens, or other secrets.