AeroNexus Terms of Service

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

These Terms of Service (the “Terms”) govern access to and use of AeroNexus websites, applications, dashboards, APIs, bots, community tools, and other related products, features, and services that AeroNexus makes available (together, the “Service”).

For these Terms, “AeroNexus,” “we,” “us,” and “our” mean the provider of the Service. “You” means any individual or entity that accesses or uses the Service (a “User”), including anyone acting on behalf of an organization, Discord server, Roblox group, or other community. A “Customer” is an organization or community operator that uses or authorizes use of the Service. A “Dashboard Administrator” is a User who signs in to configure or manage a Customer or connected resource, and a “Modmail User” is a User who contacts a community or its staff through an AeroNexus modmail bot. An “Authorized User” is a User whom a Customer permits to access or operate its account, community, connected resource, application, integration, bot, or API client. An “Order Form” is a written ordering document accepted by both sides. A “Negotiated Agreement” is a separately signed agreement between AeroNexus and a Customer. “Product Documentation” means AeroNexus’s published technical or product documentation, and a “Pricing Page” means an AeroNexus page that expressly describes plan pricing, allowances, or commercial conditions.

The AeroNexus Acceptable Use Policy (the “AUP”) and AeroNexus Fair Use Policy (the “FUP”) are incorporated into and form part of these Terms. Together, the AUP and FUP are the “Policies.” The AUP governs prohibited, unsafe, unlawful, and abusive conduct. The FUP governs shared-resource use, published limits, metering, and responses to excessive or destabilizing usage.

By accessing or using any part of the Service—including by creating or signing into an account, connecting or managing a resource, opening or participating in a modmail ticket, sending a modmail message, or selecting an acceptance control—you confirm that you have read, understood, and agree to these Terms and the incorporated Policies. Where AeroNexus presents an acceptance control, it may require you to affirmatively accept before continuing. AeroNexus may record the applicable document version, User identifier, acceptance or use event, choice, and timestamp to document acceptance.

The Privacy Policy is a notice explaining personal-data processing. Accepting these Terms also confirms that you received or could access that notice, but it is not blanket consent to every data-processing activity. Optional processing that legally requires consent, including optional measurement, is subject to a separate choice.

If you do not agree to these Terms, do not access or use the Service.

1. Eligibility and authority

You may use the Service—including by creating or controlling a dashboard account, opening or participating in a modmail ticket, or sending a modmail message—only if you:

• are at least 18 years old and, if the law where you live sets a higher age of legal majority, have reached that higher age;
• have legal capacity to enter into these Terms;
• have a valid Discord account that you are permitted to use;
• comply with the minimum-age and other rules of Discord, Roblox, and any other connected platform; and
• are not prohibited from using the Service by applicable law or a binding platform restriction.

If you use AeroNexus for a company, organization, Discord server, Roblox group, or community, you represent that you have authority to accept these Terms for it and to configure AeroNexus to access and process its information.

This age requirement applies to every User, including every Dashboard Administrator and Modmail User. A parent or legal guardian may not accept these Terms to authorize someone who does not meet it. Community administrators must not invite or knowingly permit anyone who does not satisfy this Section to use AeroNexus.

2. The Service

AeroNexus is a free dashboard, API, bot-orchestration, modmail, and real-time platform for managing Discord bot services and Discord- and Roblox-focused communities, including guild and group configuration, tickets and transcripts, partnerships, surveys, and aviation-style flight, fleet, aircraft, airport, and related community information.

Every modmail message successfully processed through AeroNexus is written to AeroNexus’s database to operate the ticket, provide the authorized community staff with its history, and generate a transcript. Modmail messages are not ephemeral and do not disappear merely because the author closes or deletes an account.

Features can vary by deployment, account, bot, group, server, role, and development stage. Some features may be identified as beta, preview, experimental, or early access. The Service depends on third-party platforms and internet infrastructure and may change without corresponding changes by those third parties.

3. Accounts, credentials, and API use

3.1 Discord sign-in

AeroNexus uses Discord authentication for Dashboard Administrators. You authorize AeroNexus to receive the account information and permissions shown during the Discord authorization flow and to use them as described in the Privacy Policy. A Modmail User may interact through Discord without creating a dashboard account, but AeroNexus still processes the User’s Discord identifier, message content, and related ticket information.

3.2 Account and credential security

You must:

• keep your Discord account, devices, active sessions, bot tokens, OAuth credentials, API credentials, and recovery methods secure;
• use only credentials you are authorized to use;
• promptly revoke and replace a credential that may have been exposed;
• do not share, publish, expose, sell, sublicense, or transfer access or credentials to an unauthorized person;
• use supported roles, separate credentials, and least-privilege access where reasonably available; and
• notify [email protected] promptly if you suspect unauthorized AeroNexus access.

You are responsible for activity carried out through your account or credentials to the extent permitted by law and reasonably within your control. If a credential may be compromised, you must promptly stop affected activity and revoke or rotate the credential where possible. AeroNexus may revoke sessions or credentials, require a new security challenge, restrict access, or suspend an integration when reasonably necessary to protect the Service or Users.

3.3 Accurate information

Information you submit to AeroNexus must be accurate, current, and not misleading. Platform-derived names, identifiers, permissions, or counts can become stale; you must review important configurations before relying on them.

3.4 Published limits and fair use

AeroNexus may apply limits to groups, bots, requests, concurrency, real-time connections, messages, storage, bandwidth, automation, compute, database work, files, or features. A contractual plan limit or allowance must be published in the dashboard, Product Documentation, a Pricing Page, an Order Form, or a Negotiated Agreement. The FUP explains how limits are measured, how occasional spikes differ from sustained excessive usage, and how AeroNexus may respond.

No high usage is automatically a violation merely because it is high. You must remain within any purchased or agreed limit, comply with the AUP and FUP, and respond appropriately to technical controls. AeroNexus currently offers no paid plans, purchased capacity, or overage billing.

3.5 APIs and automated clients

An “API Credential” includes an API key, token, signing secret, OAuth credential, bot credential, session credential, or other secret used by an application, integration, bot, script, webhook, or automated client to access the Service.

When using an API or automated interface, you must:

• use only documented or expressly authorized endpoints, methods, scopes, and credentials;
• protect API Credentials and issue each client only the access it reasonably needs;
• comply with published request-rate, concurrency, payload, storage, execution, and usage limits;
• read and honor rate-limit responses, retry periods, Retry-After instructions, and documented backoff requirements;
• reduce request frequency and use reasonable backoff after throttling, capacity, or transient errors;
• avoid malformed, repetitive, duplicate, unnecessary, or abusive requests and unbounded retry loops; and
• promptly disable, isolate, revoke, or rotate a compromised or malfunctioning client or credential.

You must not use an undocumented, private, internal, administrative, or otherwise unauthorized API; use automation to bypass a product restriction; or split usage across accounts, credentials, integrations, identities, IP addresses, proxies, or connected resources primarily to avoid a limit, charge, throttle, restriction, suspension, or enforcement measure. Temporary rate limiting or rejected requests do not by themselves establish a breach, but deliberately evading or repeatedly ignoring those controls may do so.

A Customer must take reasonable steps to ensure compliance with these Terms and the Policies by its Authorized Users, staff, applications, integrations, bots, API clients, and connected resources. This includes appropriate instructions, permissions, credential controls, technical safeguards, and oversight.

4. Permission to connect communities and platforms

You may connect a Discord server, bot, Roblox group, or other resource only if you have all permissions required by the relevant owner, platform, community rules, and applicable law. You authorize AeroNexus to perform the API calls, bot actions, storage, display, transmission, and configuration reasonably necessary to provide the features you enable.

You must comply with all applicable third-party terms and policies, including the Discord Terms of Service, Discord Developer Terms and policies, Roblox Terms of Use, and relevant API, community, intellectual-property, and data-use rules.

AeroNexus is not affiliated with, endorsed by, or responsible for Discord or Roblox unless expressly stated otherwise. Third-party platforms may change, limit, revoke, or discontinue access at any time. AeroNexus is not liable for a third-party platform decision, outage, policy change, content-delivery failure, account action, or API limitation except where applicable law requires otherwise.

5. Customer Content

5.1 Definition

“Customer Content” means information or material submitted, configured, generated, imported, or processed through the Service by or for you, including bot and group configuration, Discord or Roblox platform data, every successfully processed modmail message and its metadata, tickets, transcripts, snippets, blacklists, surveys, group names and descriptions, flight and fleet records, aircraft and airport information, images, attachments, and links.

5.2 Your ownership

As between you and AeroNexus, you retain any rights you have in Customer Content. These Terms do not transfer ownership of Customer Content to AeroNexus.

5.3 Limited license to operate the Service

You grant AeroNexus a non-exclusive, worldwide, royalty-free license to host, cache, store, reproduce, format, transmit, display, and otherwise process Customer Content only as reasonably necessary to:

• provide, secure, maintain, troubleshoot, and improve the Service;
• carry out your settings and instructions;
• make content available to the users and administrators you authorize;
• comply with law and enforce these Terms; and
• prevent or address security, abuse, or technical issues.

This license lasts while the Customer Content is processed through the Service and for the limited retention periods described in the Privacy Policy. It does not authorize AeroNexus to sell Customer Content or use private ticket content for targeted advertising.

5.4 Your responsibilities for Customer Content

You represent and warrant that:

• you have the rights, permissions, and lawful basis needed to submit and process Customer Content;
• your instructions and use of Customer Content comply with law, platform rules, and your own notices and community policies;
• you will not instruct AeroNexus to process content in a way that infringes another person’s rights; and
• you will provide legally required information and choices to members, staff, ticket participants, and other affected people.

You are responsible for reviewing access roles and permissions. Do not use public or broadly accessible transcript links for private or sensitive information.

5.5 Content from Discord’s CDN and external locations

Some images, attachments, avatars, or other content may be hosted by Discord or another third party rather than AeroNexus. AeroNexus does not control the continued availability, security, deletion, or terms of an external copy. An exported transcript or file downloaded or shared by you is also outside AeroNexus’s control.

5.6 Modmail logging, transcripts, and account removal

When a Modmail User or authorized staff member sends a message through an AeroNexus modmail flow, AeroNexus stores every message it successfully processes in the ticket database. Stored information may include message text, edits, timestamps, Discord identifiers, display information, staff replies, attachment or media links, delivery metadata, and related ticket events. AeroNexus uses those records to operate the ticket, preserve the conversation’s context, allow authorized staff review, and generate or export a transcript.

By opening or participating in a modmail ticket, you instruct and authorize AeroNexus and the relevant community administrator to record and process those messages for these purposes. Do not use modmail for information that you do not want recorded or disclosed to the authorized staff of the relevant community.

Closing or deleting a User account does not automatically delete the text of messages already included in a ticket or transcript. AeroNexus will de-link, replace, or anonymize direct account and author identifiers where appropriate, while message bodies ordinarily remain for the community’s documented ticket-retention period so the transcript remains intelligible and complete.

Message text can itself identify a person and therefore can remain personal data even after the author field is anonymized. Nothing in these Terms eliminates a mandatory privacy right. If applicable law requires a message to be erased or redacted and no continuing lawful basis or exception applies, AeroNexus or the relevant community administrator will do so. Copies already exported or retained independently by an authorized User, Discord, a CDN, or another third party may be outside AeroNexus’s control.

5.7 Feedback

If you voluntarily provide suggestions or feedback about AeroNexus, you grant us a perpetual, irrevocable, worldwide, royalty-free right to use that feedback to develop and improve the Service without identifying you publicly or owing compensation. This does not give us ownership of other Customer Content.

6. Acceptable use and service restrictions

You, each Customer, and each Authorized User must comply with the AUP and FUP. Without limiting those Policies, you must not use the Service to:

• violate law, a binding request or order, applicable sanctions or export controls, platform rules, or another person’s rights;
• conduct or facilitate fraud, deception, spam, phishing, scams, impersonation, malware, exploitation, harassment, threats, or other unlawful harmful activity;
• collect, use, or disclose personal data without an appropriate purpose, notice, permission, security, and legal basis;
• process special-category, biometric, health, financial-account, government-identifier, or similarly sensitive data unless strictly necessary, lawful, appropriately secured, and expressly supported by the Service;
• infringe intellectual-property, privacy, publicity, confidentiality, database, contractual, or other rights;
• gain or attempt unauthorized access to an account, credential, bot, API, database, endpoint, system, network, data, or infrastructure;
• scan, test, attack, disrupt, overload, or interfere with the Service without written permission;
• bypass or evade authentication, authorization, access controls, account controls, security measures, billing controls, product restrictions, rate limits, quotas, usage limits, throttles, suspension, or enforcement;
• create or use multiple accounts, credentials, workspaces, integrations, IP addresses, proxies, identities, or connected resources primarily to avoid fees, limits, restrictions, or enforcement;
• share, sell, sublicense, publish, or expose an account credential or API Credential to an unauthorized person;
• use an undocumented, private, internal, administrative, or unauthorized API or interface;
• use credentials, bots, automation, or platform data contrary to Discord’s, Roblox’s, AeroNexus’s, or another provider’s applicable rules;
• falsely imply affiliation with AeroNexus or another person;
• resell, sublicense, or provide the Service as a bureau service without written permission; or
• help another person do any of the above.

Good-faith security research must be coordinated in advance through [email protected] or another security contact AeroNexus publishes. Written permission may limit the systems, methods, timing, data handling, and reporting allowed. Do not access, retain, or disclose another person’s data beyond what is legally authorized and necessary to report a vulnerability safely.

7. Enforcement, suspension, and cooperation

Community administrators are primarily responsible for their own community rules, staff conduct, content review, and user-facing appeals. AeroNexus does not undertake to monitor every ticket, message, transcript, configuration, request, or integration.

AeroNexus may investigate suspected violations of these Terms, the Policies, platform rules, or law. You must reasonably cooperate with an abuse, fraud, reliability, or security investigation, including by stopping affected activity, rotating credentials, identifying a responsible integration, preserving relevant records, or implementing a reasonable corrective measure. Any request for information will be limited to what is reasonably relevant and remains subject to applicable law and third-party rights.

Depending on severity, duration, repetition, intent, risk, impact, and cooperation, AeroNexus may:

• issue a warning or request for information;
• request correction, remediation, optimization, or reduced usage;
• throttle, queue, reject, or limit traffic, requests, concurrency, or executions;
• restrict a feature, integration, bot, group, export, automation, credential, or connected resource;
• revoke a session, token, API key, credential, or authorization;
• remove, disable, quarantine, or restrict Customer Content where legally and technically appropriate;
• suspend some or all access to the Service; or
• terminate access under Section 13.

7.1 Ordinary enforcement

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. A notice may identify the affected conduct, requested corrective action, relevant deadline or condition, and consequence of failing to correct it. The appropriate cure period depends on the circumstances; these Terms do not promise a fixed period.

7.2 Emergency protective action

AeroNexus may act immediately and without advance notice when it reasonably believes action is necessary to protect security, service stability, Users, third parties, data, or infrastructure; contain fraud, malware, exploitation, credential compromise, an active attack, or significant service disruption; prevent circumvention; preserve evidence; or comply with law, a binding request, or an urgent platform requirement.

An emergency throttle, restriction, credential revocation, or suspension is a protective measure and is not automatically a final determination that you breached these Terms. AeroNexus will review the circumstances and give notice where reasonably possible.

7.3 Reports and review

Suspected violations or compromised accounts may be reported to [email protected]. You may ask for review of an enforcement decision at [email protected]. A request for review does not automatically pause an urgent protective measure. AeroNexus may withhold information where disclosure would compromise security, privacy, another person’s rights, an investigation, or a legal obligation.

8. Privacy and community responsibilities

The AeroNexus Privacy Policy explains AeroNexus’s processing. Dashboard Administrators and Modmail Users must be given access to that Policy before using the relevant Service. Users acknowledge receiving the Policy; they do not provide blanket privacy consent merely by accepting these Terms. When you administer a community using AeroNexus, you are responsible for the personal data you direct AeroNexus to process.

You must, as applicable:

• publish an accurate privacy notice and any required bot or ticket notice;
• identify yourself as the responsible community operator or controller;
• explain the purposes, legal bases, recipients, retention, and user rights for community processing;
• configure staff, roles, channels, transcripts, and exports according to least privilege;
• respond to access, correction, deletion, restriction, objection, and portability requests;
• obtain consent where required and maintain evidence of it;
• avoid collecting more information than reasonably necessary;
• establish and follow an appropriate retention and deletion schedule;
• notify AeroNexus promptly of a personal-data breach or unlawful instruction affecting the Service; and
• prevent community members who do not meet Section 1’s age requirement from using AeroNexus and comply with protections applicable to children and teenagers in your community.

Dashboard Administrators and Modmail Users must satisfy Section 1’s age requirement. If your broader community includes people who do not meet that requirement, you must ensure they cannot access or use AeroNexus through your community, bots, or modmail flows. You must not use AeroNexus to target or profile children for advertising.

9. Data Processing Terms

This Section applies when AeroNexus processes personal data contained in Customer Content on behalf of a Customer that is a controller under the GDPR or similar law. It forms a data-processing agreement between that Customer (the “Controller”) and AeroNexus (the “Processor”). For AeroNexus’s own account, security, analytics, and platform-administration purposes, AeroNexus may act as a separate controller as described in the Privacy Policy.

9.1 Documented instructions

AeroNexus will process Customer Personal Data only on the Controller’s documented instructions, including these Terms, the Controller’s feature configurations, support requests, and use of the Service, unless EU or Member State law requires other processing. If legally permitted, AeroNexus will inform the Controller before processing required by law. AeroNexus will promptly inform the Controller if, in its opinion, an instruction infringes applicable data-protection law and may suspend the affected processing while the issue is resolved.

9.2 Confidentiality

AeroNexus will ensure that people authorized to process Customer Personal Data are subject to an appropriate duty of confidentiality and access it only as needed for their duties.

9.3 Security

Taking into account the state of the art, implementation costs, and the nature, scope, context, and purposes of processing, AeroNexus will maintain measures designed to provide a level of security appropriate to the risk. Measures may include authentication, role- and resource-based access controls, rate limiting, security headers, origin validation, bot protection, bounded messages, connection monitoring, restricted operational endpoints, credential controls, backup and recovery measures, and procedures for addressing incidents.

The Controller is responsible for secure account administration, bot-token and credential handling, endpoint and device security, staff authorization, transcript distribution, and configuring the Service appropriately for its risk.

9.4 Subprocessors

The Controller gives AeroNexus general authorization to use subprocessors necessary to host, store, transmit, secure, support, and maintain Customer Personal Data. This may include production hosting, deployment, database, cache, networking, and infrastructure providers. AeroNexus will impose data-protection obligations on a subprocessor that are no less protective in substance for the relevant processing than the obligations in this Section, as required by Article 28 GDPR. AeroNexus remains responsible for the subprocessor’s performance to the extent required by applicable law.

AeroNexus will make its current subprocessor information available through the Privacy Policy, a published list, or on request. For a material new subprocessor that will process Customer Personal Data, AeroNexus will provide reasonable notice where required. The Controller may object on reasonable data-protection grounds. The parties will work in good faith on a solution; if none is reasonably available, either party may terminate the affected feature.

Discord, Roblox, Cloudflare, Microsoft, and other third-party platforms may act as independent controllers for some processing under their own terms and are not subprocessors merely because the Controller independently chooses to use or connect them.

9.5 Assistance with individual rights

Taking into account the nature of the processing, AeroNexus will provide reasonable assistance through available technical and organizational measures so that the Controller can respond to requests to exercise data-subject rights. If AeroNexus receives a request relating primarily to Customer Personal Data, it may refer the requester to the Controller and will not respond on the Controller’s behalf unless instructed or legally required.

9.6 Breach notification

AeroNexus will notify the Controller without undue delay after becoming aware of a personal-data breach affecting Customer Personal Data. As information becomes available, the notice will describe the nature of the breach, affected data and people, likely consequences, measures taken or proposed, and an appropriate contact. The Controller remains responsible for notifications to authorities and affected people unless law assigns that duty to AeroNexus.

9.7 Compliance assistance

Considering the nature of processing and information available to AeroNexus, AeroNexus will provide reasonable assistance with the Controller’s obligations concerning security, breach assessment, data-protection impact assessments, and prior consultation. Assistance that requires material custom work may be subject to a mutually agreed fee, unless the need results from AeroNexus’s breach of these Terms.

9.8 International transfers

If AeroNexus transfers Customer Personal Data from the EEA to a country that does not benefit from an applicable adequacy decision, AeroNexus will use a lawful transfer mechanism, such as the European Commission’s Standard Contractual Clauses, together with supplementary measures where required. The Controller authorizes transfers reasonably necessary to provide the Service under those safeguards.

9.9 Return and deletion

At the end of the relevant processing, AeroNexus will, at the Controller’s choice where technically available, delete or return Customer Personal Data and delete remaining copies, unless law requires retention. Data in backups may remain until overwritten through the normal rotation cycle and will remain protected and unavailable for ordinary use.

Deletion by AeroNexus cannot recall transcripts, files, or messages already exported or shared by the Controller or another authorized user, or data retained independently by Discord, Roblox, a CDN, or another third party.

9.10 Information and audits

AeroNexus will make available information reasonably necessary to demonstrate compliance with this Section. Where that information is insufficient, the Controller may request a reasonable audit no more than once in a twelve-month period, unless a breach, regulator, or law reasonably requires more. Audits must protect other customers, security, confidentiality, and system integrity; use existing reports and remote review where reasonable; occur during normal business hours on reasonable notice; and be at the Controller’s cost unless the audit identifies a material AeroNexus breach.

9.11 Processing details

10. AeroNexus intellectual property

The Service, including its software, interface, design, branding, documentation, and non-Customer content, is owned by AeroNexus or its licensors and protected by intellectual-property law. Subject to these Terms, AeroNexus grants you a limited, non-exclusive, non-transferable, revocable right to access and use the Service for your internal or community-management purposes.

Except to the extent expressly permitted by these Terms, an applicable open-source license, AeroNexus’s written authorization, or mandatory law, you may 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 retains 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 an exception may be used or disclosed only as applicable law permits.

You may not use AeroNexus names, logos, or branding in a way that suggests endorsement or causes confusion. Open-source components remain governed by their applicable licenses, which control if they conflict with this Section for that component.

11. Free Service; no paid plans

AeroNexus currently offers no paid plans and does not process payments through the Service. There are no subscription renewals, trial charges, cancellation fees, or refunds.

Because there are currently no AeroNexus Service fees, no AeroNexus fee continues to accrue during a suspension. If AeroNexus later introduces a paid plan, the applicable Pricing Page, Product Documentation, Order Form, or Negotiated Agreement must state before purchase whether fixed or usage-based fees remain payable during a suspension, how any credits or refunds work, and whether minimum commitments apply. AeroNexus will not impose an undisclosed or retroactive suspension charge.

If AeroNexus introduces a paid feature, it will disclose the price, billing interval, taxes, renewal and cancellation rules, refund terms, and any additional conditions before charging you. You will not be charged merely because these Terms change.

You remain responsible for third-party costs you choose to incur, such as Discord, Roblox, hosting, internet, mobile-data, or related platform charges.

12. Service changes, beta features, and availability

AeroNexus may add, change, limit, suspend, or discontinue a feature to improve the Service, respond to platform or legal changes, protect security, manage resources, or end an experiment. Where practical, we will give reasonable notice of a material discontinuation that affects stored Customer Content.

AeroNexus strives for 100% Service availability, but the Service remains provided “as is” and “as available.” This is an operational objective only, not a guarantee, commitment, service-level agreement, or basis for service credits.

The Service may experience interruptions, delays, data-sync issues, platform outages, or errors. Beta and experimental features may be incomplete, change frequently, or be withdrawn. AeroNexus does not guarantee uninterrupted availability, error-free operation, permanent storage, or compatibility with every platform change.

Maintain independent copies of Customer Content you must preserve. Do not rely on AeroNexus as the sole archive for legal, safety-critical, or business-critical records.

13. Term and termination

These Terms begin when you first accept them or use the Service and continue until terminated.

You may stop using the Service at any time, revoke AeroNexus through Discord where available, disconnect your bots and groups, and request account deletion at [email protected] or [email protected]. Modmail Users may also stop using a ticket, subject to any community rules and the transcript-retention provisions below.

AeroNexus may restrict, suspend, or terminate access for a violation of these Terms, the AUP, or the FUP, or for another reason described in Section 7. Ordinary and emergency enforcement are distinguished in Sections 7.1 and 7.2.

13.1 Effect of suspension

During a suspension, AeroNexus may disable some or all dashboard access, API access, credentials, bots, integrations, real-time connections, automations, exports, or other connected features. Requests may be rejected or throttled, and affected features may stop operating immediately. A suspension does not itself delete Customer Content or terminate these Terms. Customer Content remains subject to the Privacy Policy, Section 5.6, and the Data Processing Terms.

Emergency security, legal, platform, stability, or abuse circumstances may make access to or export of Customer Content temporarily unavailable. For a non-urgent suspension, AeroNexus will, where reasonably possible and appropriate, explain the condition for restoration and allow access needed to correct the issue or retrieve Customer Content. No access or export is promised where it would increase risk, violate law or platform rules, expose another person’s data, undermine an investigation, or be technically unavailable.

Fees during suspension are addressed in Section 11 and any applicable Order Form or Negotiated Agreement. AeroNexus currently charges no Service fees.

13.2 Termination and data

Where reasonably possible, AeroNexus will allow an opportunity to export Customer Content before a non-urgent termination, but security, legal, platform, stability, or abuse circumstances may make that impossible.

After termination:

• your right to use the Service ends;
• connected features may stop operating immediately;
• AeroNexus may delete or de-identify account and author-linkage information according to the Privacy Policy and Section 9;
• ticket message bodies are not automatically erased by account termination and ordinarily remain for the applicable ticket-retention period under Section 5.6, subject to mandatory privacy rights and lawful exceptions;
• externally exported transcripts and third-party copies remain outside AeroNexus’s control; and
• provisions that by nature should survive will remain effective, including ownership, licenses needed for retained copies, privacy and data-processing duties, disclaimers, liability, indemnity, and general terms.

14. Disclaimers and statutory rights

Nothing in these Terms excludes, restricts, or waives a right or remedy that cannot lawfully be excluded, including mandatory consumer rights, data-protection rights, liability for fraud or intentional misconduct, gross negligence where it cannot be limited, or death or personal injury caused by negligence where applicable.

Subject to those protections, the Service is provided “as is” and “as available.” To the maximum extent permitted by law, AeroNexus disclaims implied warranties and conditions, including merchantability, satisfactory quality, fitness for a particular purpose, non-infringement, availability, accuracy, and uninterrupted or error-free operation.

AeroNexus does not warrant that community content is accurate, lawful, complete, or safe; that a transcript will be accepted as an official record; that Discord, Roblox, or another provider will preserve access or content; or that every security threat will be detected.

If you are a consumer in the EEA or another jurisdiction with mandatory digital-service rights, those rights continue to apply. Contact [email protected] if you believe the Service does not conform to a mandatory requirement.

15. Limitation of liability

To the maximum extent permitted by law, AeroNexus and its owners, operators, personnel, affiliates, licensors, suppliers, service providers, and agents will not be liable for any loss, damage, claim, cost, or liability arising out of or relating to the Service or these Terms, including any loss or damage resulting from:

• access to, use of, inability to use, or reliance on the Service;
• any act, omission, output, response, decision, delay, failure, interruption, error, defect, inaccuracy, or unavailability of the Service or any bot, automation, API, integration, real-time feature, or other Service function;
• loss, corruption, deletion, alteration, disclosure, or unavailability of data, messages, tickets, transcripts, configurations, credentials, or other content;
• Customer Content, community administrators, Users, integrations, exported content, unauthorized access, security incidents, or credential compromise; or
• Discord, Roblox, a CDN, hosting or infrastructure providers, or any other third-party platform, product, service, content, action, omission, outage, restriction, or policy change.

This exclusion applies, to the maximum extent permitted by law, to direct, indirect, incidental, special, consequential, exemplary, and punitive damages; loss of profit, revenue, goodwill, anticipated savings, business opportunity, use, or data; and the cost of a substitute service, regardless of the legal theory and even if AeroNexus was advised that the loss was possible or a remedy fails of its essential purpose.

Where liability cannot lawfully be excluded but may lawfully be limited, AeroNexus’s total aggregate liability arising from or relating to the Service or these Terms will not exceed the greater of EUR 100 and the amount you paid directly to AeroNexus for the Service during the twelve months before the event giving rise to liability.

Nothing in this Section excludes or limits liability to the extent that applicable law does not permit it to be excluded or limited.

16. Business-user indemnity

This Section applies only if you use AeroNexus for a trade, business, profession, organization, or community operation, and only to the extent permitted by law.

You will defend and indemnify AeroNexus against a third-party claim, damage, judgment, fine, cost, and reasonable legal fee arising from:

• Customer Content or an instruction you provide;
• your violation of Sections 3.5, 4, 5, 6, 8, or 9, the AUP, or the FUP;
• your infringement of another person’s rights; or
• your community’s unlawful processing, moderation, publication, or distribution of data or content.

AeroNexus will give reasonable notice of a covered claim and allow you to control the defense, provided you may not settle in a way that admits AeroNexus wrongdoing, imposes an obligation on AeroNexus, or fails to release AeroNexus without our written consent. AeroNexus may participate with counsel at its own cost.

17. Changes to these Terms and Policies

We may update these Terms, the AUP, or the FUP for a valid reason, including a Service, security, safety, capacity, provider, platform, business, or legal change. Each revised document will show a new “Last updated” date. The AUP and FUP also describe changes specific to their subject matter, consistently with this Section.

For a routine, clarifying, or administrative change that does not materially reduce a User’s rights or materially expand a User’s obligations, we will ordinarily give at least three days’ advance notice. Dashboard Administrators may receive that notice in the dashboard. Modmail Users will receive it through the modmail flow, a bot notice, or another reasonably available channel because they may never access the dashboard.

For a material change, including a material reduction to a contractual allowance, we 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, we will ordinarily give at least 30 days’ notice and preserve any mandatory right to terminate. We may ask a Dashboard Administrator to re-accept the changed document before continuing and a Modmail User to accept the new version before opening a new ticket or sending another message.

Continued use after the effective date constitutes acceptance only where applicable law permits that method and the notice clearly says so. Silence, inactivity, or continued use will not be treated as consent to personal-data processing that legally requires a separate affirmative choice. If law or the nature of a material contractual change requires express acceptance, the changed term will not bind the User until the User affirmatively accepts it.

If you do not agree to a revised version, you must stop using the affected Service before it takes effect. 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. A temporary emergency technical control does not silently create a new fee or retroactively reduce a purchased or expressly agreed allowance. Mandatory consumer, contract, and privacy rights remain unaffected.

18. General terms

• Entire agreement. These Terms, the AUP, the FUP, any applicable Order Form, and any feature-specific or separately written terms you accept form the agreement concerning the Service. The Privacy Policy is the applicable transparency notice and does not create blanket contractual consent to personal-data processing.
• Order of precedence. If documents directly conflict on the same issue, the following order applies: (1) a Negotiated Agreement; (2) an applicable Order Form; (3) these Terms; (4) the AUP; (5) the FUP; (6) Product Documentation; and (7) a Pricing Page. A higher-ranking document controls only to the extent of the conflict. A Negotiated Agreement or Order Form overrides a public policy only where it expressly addresses the same issue; otherwise the documents supplement one another. Within these Terms, Section 9 controls for processor obligations concerning Customer Personal Data. Mandatory law prevails over every document.
• Assignment. You may not assign these Terms without AeroNexus’s written consent. AeroNexus may assign them in connection with a reorganization, transfer, merger, acquisition, or sale of the Service, subject to applicable law and continued protection of personal data.
• No waiver. Failure to enforce a provision is not a waiver.
• Severability. If a provision is unenforceable, it will be limited to the minimum extent necessary, and the remainder will continue in effect.
• No partnership. These Terms do not create employment, agency, partnership, franchise, fiduciary, or joint-venture relationship.
• Electronic communications. You agree to receive Service and legal notices electronically through the Service, Discord, or an available account contact, subject to applicable law.
• Language. The English version governs to the extent permitted by law. A mandatory local-language rule or consumer interpretation right remains unaffected.
• Headings. Headings are for convenience and do not change meaning.

19. Contact

• Legal: [email protected]
• Privacy: [email protected], [email protected]
• General support: [email protected]