Legal center

AeroNexus Acceptable Use Policy

Effective date: 10 July 2026
Last updated: 15 July 2026

This Acceptable Use Policy (the “AUP”) establishes rules for lawful, secure, and responsible use of the AeroNexus Service. It forms part of the AeroNexus Terms of Service (the “Terms”). Capitalized words not defined here have the meanings given in the Terms.

This AUP applies to every User, including Dashboard Administrators and Modmail Users, and to each Customer, Authorized User, application, integration, bot, script, API client, credential, and connected resource using or interacting with the Service. A Customer is responsible, to the extent permitted by law and reasonably within its control, for compliance by the people and technical clients it authorizes.

The AeroNexus Fair Use Policy separately governs shared-resource consumption, limits, and responses to excessive usage.

1. Purpose and interpretation

The purpose of this AUP is to protect the legality, safety, security, availability, and proper operation of AeroNexus, its Users, connected communities, third-party platforms, and infrastructure. You must comply with this AUP whenever you access or use the Service, direct another person to use it, or allow a technical client to act through your account or credentials.

The examples below are not exhaustive. AeroNexus will connect enforcement under this AUP to a reasonable concern involving applicable law, user or third-party safety, security, service stability, platform integrity, fair access, or the proper intended operation of the Service. This AUP does not create a general right for AeroNexus to restrict lawful use for an unrelated reason.

2. Illegal, deceptive, or harmful activity

You must not use the Service to engage in, facilitate, promote, or knowingly assist:

  • activity that violates applicable law, regulation, court order, sanctions, export-control requirements, or a binding platform rule;
  • illegal, fraudulent, deceptive, misleading, or harmful conduct;
  • spam, unsolicited bulk messaging, unauthorized commercial messages, phishing, scams, fraudulent solicitations, or deceptive links;
  • impersonation, identity deception, account takeovers, false claims of affiliation, or credential theft;
  • malware, ransomware, spyware, malicious code, destructive payloads, botnets, cryptojacking, or tools designed primarily to compromise accounts, devices, data, or systems;
  • harassment, threats, stalking, doxing, unlawful discrimination, exploitation, grooming, sexual abuse, trafficking, or content that unlawfully endangers or harms another person;
  • creation, storage, solicitation, or distribution of child sexual abuse material or other unlawful exploitative content;
  • unlawful surveillance, tracking, collection, sale, disclosure, or processing of personal data; or
  • infringement or misappropriation of copyright, trademark, patent, trade secret, database, privacy, publicity, confidentiality, contractual, or other third-party rights.

Community moderation decisions remain primarily the responsibility of the relevant Customer or community administrator. Nothing in this Section requires AeroNexus to monitor every ticket, message, transcript, configuration, or connected community.

3. Security, access, and circumvention

You must not:

  • access or attempt to access an account, credential, bot, system, network, server, database, data set, API, endpoint, administrative function, or infrastructure without authorization;
  • probe, scan, enumerate, test, exploit, or assess the vulnerability or security of the Service or related infrastructure without AeroNexus’s prior written permission;
  • conduct penetration testing, red-team activity, load testing, or coordinated vulnerability testing against the Service without prior written scope and authorization;
  • launch or assist a denial-of-service attack, distributed denial-of-service attack, traffic flood, resource-exhaustion attack, or other deliberate service disruption;
  • bypass, disable, defeat, tamper with, or evade authentication, access controls, account controls, bot protection, security challenges, authorization checks, technical safeguards, billing controls, rate limits, quotas, concurrency limits, feature restrictions, or enforcement measures;
  • create or use multiple accounts, workspaces, groups, credentials, API keys, integrations, IP addresses, devices, proxies, VPN endpoints, identities, or other methods primarily to avoid a limit, charge, throttle, restriction, suspension, or enforcement action; or
  • help another person obtain or retain unauthorized access or conceal a violation.

Good-faith security research must be coordinated in advance through [email protected] or another security contact AeroNexus publishes. Written permission may define scope, timing, systems, methods, data handling, and reporting requirements. Permission for one test does not authorize another.

4. APIs, automation, and service integrity

When using an AeroNexus API, webhook, bot, automation feature, or other machine interface, you must:

  • use only documented or expressly authorized interfaces and methods;
  • comply with the applicable Product Documentation, the Fair Use Policy, and any limit shown in the dashboard, documentation, response headers, error response, Order Form, or Negotiated Agreement;
  • respect request-rate, concurrency, storage, message, payload, execution, and other applicable limits;
  • honor rate-limit responses, retry periods, Retry-After instructions, and documented backoff requirements;
  • reduce request frequency after errors or throttling and use reasonable backoff rather than immediate or repetitive retries;
  • validate requests and avoid excessive, malformed, repetitive, duplicate, unnecessary, or abusive calls;
  • secure webhooks, callbacks, applications, bots, and client environments against unauthorized use; and
  • stop or reduce automated activity when AeroNexus reasonably asks you to address a security, stability, or abuse concern.

You must not:

  • scrape, crawl, spider, index, harvest, or automate access in a way that overloads the Service, bypasses product restrictions, evades a technical control, or collects data without authorization;
  • use an undocumented, private, internal, administrative, deprecated, or otherwise unauthorized API or endpoint;
  • send deliberately malformed traffic or construct requests intended to cause errors, excessive database work, repeated cache misses, resource contention, or degraded performance;
  • use the Service for cryptocurrency mining, proof-of-work computation, unrelated hosting, proxying, relaying, general-purpose batch computation, or another infrastructure workload unless AeroNexus expressly permits it in writing; or
  • consume shared compute, storage, bandwidth, database, email, messaging, automation, AI, API, or operational resources in a manner prohibited by the Fair Use Policy.

Temporary rate limiting, rejection of a request, or a capacity error does not by itself establish that you violated this AUP. AeroNexus will consider the surrounding circumstances, including your response to the control and whether activity was accidental, occasional, sustained, evasive, or harmful.

5. Credentials and account protection

You must use only accounts and credentials you are authorized to use. You must keep Discord credentials, AeroNexus sessions, bot tokens, OAuth credentials, API keys, signing secrets, recovery methods, and other access material confidential and appropriately secured.

You must not share, publish, expose, sell, transfer, sublicense, lease, or make an account or credential available to an unauthorized person. Customer-approved access should use supported roles, separate credentials, and least-privilege permissions where available rather than shared secrets.

If you know or reasonably suspect that an account or credential has been lost, disclosed, compromised, or misused, promptly revoke or rotate it where possible, stop affected activity, and notify [email protected]. Do not send a live password, token, API key, or other secret in the report.

6. Intellectual property and technical restrictions

Except to the extent expressly permitted by the Terms, an applicable open-source license, AeroNexus’s written authorization, or mandatory law, you must not:

  • copy, reproduce, extract, mirror, frame, republish, or systematically collect protected elements of the Service;
  • reverse engineer, decompile, disassemble, decode, translate, adapt, or attempt to derive or discover source code, object-code structure, algorithms, architecture, models, model weights, prompts, non-public APIs, schemas, security mechanisms, or proprietary methods;
  • use extraction, observation, testing, benchmarking, or automated collection primarily to create, train, reproduce, substitute for, or materially improve a competing product or service;
  • circumvent a technical protection applied to software, content, interfaces, credentials, or data; or
  • remove, obscure, alter, or falsify a copyright, trademark, attribution, ownership, confidentiality, or other proprietary notice.

These restrictions do not prohibit independent development, lawful use of public information, or an act that applicable law does not allow the parties to restrict. Where mandatory software law applies, a lawful user may retain any non-waivable right to observe, study, or test a program while carrying out an authorized act, and to perform acts indispensable to obtain information needed for interoperability of an independently created program, subject to the conditions and limits imposed by that law. Information obtained under such an exception may be used or disclosed only as the applicable law permits.

7. Customer responsibility and cooperation

A Customer must take reasonable steps to ensure that its Dashboard Administrators, staff, Authorized Users, applications, integrations, bots, API clients, and connected resources comply with the Terms, this AUP, and the Fair Use Policy. This includes maintaining appropriate permissions, credential controls, technical safeguards, user instructions, and oversight for automated clients.

You must reasonably cooperate with an AeroNexus abuse, fraud, reliability, or security investigation. Cooperation may include stopping or reducing affected activity, rotating credentials, preserving relevant records, identifying the responsible integration, explaining an apparent anomaly, or implementing a reasonable corrective measure. AeroNexus will limit a request for information to what is reasonably relevant and expects cooperation to remain subject to applicable law, confidentiality duties, and the rights of other people.

You must not retaliate against a person who reports a suspected violation in good faith.

8. Reporting suspected violations

Report a suspected violation or compromised account to [email protected]. Legal or formal abuse notices may be sent to [email protected].

Where available, include the affected account, community, group, bot, ticket, message, integration, API client, date or time, and a concise description of the concern. Do not obtain unauthorized access, collect unnecessary personal data, or publish secrets or harmful content in order to make a report.

AeroNexus may acknowledge, investigate, preserve, refer, or close a report as appropriate. AeroNexus cannot promise to disclose confidential investigation details, another User’s data, or every enforcement outcome.

9. Enforcement

When AeroNexus reasonably believes this AUP may have been violated, it may investigate and take a proportionate measure connected to the severity, duration, repetition, intent, risk, and impact of the conduct. Measures may include:

  • a warning or request for information;
  • a request to stop, correct, secure, or remediate activity;
  • temporary throttling, request rejection, or reduced concurrency;
  • temporary or permanent feature, integration, bot, group, or content restrictions;
  • session, token, API-key, credential, or authorization revocation;
  • removal, disabling, quarantine, or restriction of Customer Content where legally and technically appropriate;
  • account or Service suspension; or
  • termination under the Terms.

For a less serious violation, AeroNexus will ordinarily provide notice and a reasonable opportunity to correct the issue where doing so is appropriate, lawful, and unlikely to increase harm. AeroNexus may act immediately and without advance notice when reasonably necessary to protect security, service stability, Users, third parties, data, or infrastructure; contain fraud, malware, exploitation, or an active attack; preserve evidence; comply with law or a binding request; or prevent circumvention of an existing restriction.

The effect of suspension or termination on Service access, connected features, Customer Content, and retained ticket records is described in the Terms. You may request review of an enforcement decision at [email protected]. A request for review does not automatically pause an urgent protective measure.

10. Changes to this AUP

AeroNexus may update this AUP for a valid legal, security, safety, platform, Service, or operational reason. A revised version will show a new “Last updated” date.

For a routine, clarifying, or administrative change that does not materially reduce a User’s rights or materially expand a User’s obligations, AeroNexus will ordinarily give at least three days’ advance notice through the channels described in the Terms. For a material change, AeroNexus will provide reasonable advance notice through a durable or directly addressed channel. Where a change materially and negatively affects a consumer’s access to or use of the Service, AeroNexus will ordinarily give at least 30 days’ notice and preserve mandatory termination or objection rights.

A change required immediately for law, urgent security, active abuse, service stability, or a third-party platform requirement may take effect sooner, with notice where reasonably possible. The Terms govern acceptance, re-acceptance, and the effect of continued use, and mandatory consumer and privacy rights remain unaffected.

11. Contact

Jump toBrowse this policy