Legal center

AeroNexus Fair Use Policy

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

This Fair Use Policy (the "FUP") explains how AeroNexus protects the availability, performance, and security of the Service while keeping shared resources fair for everyone. It forms part of the AeroNexus Terms of Service (the "Terms"). Capitalized words not defined here have the meanings given in the Terms.

How rate limits are counted. AeroNexus does not publish exact technical rate limits, counting methods, time windows, or the specific identifiers used for a request. To operate and protect the Service, usage may be counted or grouped using factors such as an IP address or network, User or account, Customer or community, group, bot, application or integration, credential or session, feature or resource, or a combination of these. This list is illustrative; it does not reveal which factors apply to a particular request. Technical controls may differ by feature and may change as traffic, capacity, security risks, and the Service evolve.

The AeroNexus Privacy Policy explains how AeroNexus handles the related operational, security, and personal data.

The AeroNexus Acceptable Use Policy separately governs prohibited, unsafe, unlawful, and abusive conduct.

1. Who and what this Policy covers

This FUP applies to every Customer, User, Authorized User, account, application, integration, bot, automated client, and connected resource that accesses or uses the Service. It covers all AeroNexus features and infrastructure, including websites, dashboards, APIs, bots, modmail, real-time services, webhooks, exports, surveys, automation, storage, and background processing.

A separately signed Negotiated Agreement or Order Form may provide different capacity or usage terms. It overrides this FUP only where it expressly addresses the same issue. The order of precedence in the Terms governs any other conflict.

2. What fair use means

Fair use means using the Service for its intended purpose without placing unreasonable or avoidable strain on shared systems or reducing the Service's reliability for others.

When AeroNexus reviews usage, it may consider:

  • the feature's intended purpose and documented use;
  • the amount, frequency, duration, and pattern of activity;
  • whether activity is occasional or sustained;
  • whether requests are valid, efficient, and responsive to errors or technical controls;
  • the effect on other Users, shared capacity, queues, latency, data stores, security, or stability;
  • whether the activity resulted from a defect, retry loop, compromised credential, or deliberate evasion; and
  • whether the Customer or User cooperates with a reasonable request to investigate or correct the issue.

High usage is not automatically unfair. A short, legitimate spike will not be treated the same as sustained or harmful activity. Use may still be restricted when reasonably necessary to address an Acceptable Use Policy violation, security incident, active attack, legal requirement, product defect, or immediate risk to the Service or others.

3. Technical limits and service responses

AeroNexus may use dynamic rate limits, concurrency controls, queues, capacity controls, payload restrictions, or other safeguards. These controls are protective operating measures, not guaranteed usage allowances. They may vary between features, change without revealing their exact configuration, and respond to current capacity, traffic patterns, abuse risk, or security conditions.

The Service may slow, delay, queue, reject, or temporarily restrict activity when a control is reached. A technical control or rejected request does not by itself mean that a User violated this FUP.

Clients and automations must respond reasonably to Service instructions. This includes reducing activity after a limit or capacity response, waiting before trying again, using bounded backoff, and stopping unintended retry loops. Where the supported interface and use case allow it, clients should avoid unnecessary requests by caching, batching, filtering, paginating, or removing duplicates.

4. No evasion

You must not split, rotate, disguise, or distribute activity across related or alternate access methods, identities, or resources primarily to avoid a limit, restriction, throttle, plan requirement, suspension, or enforcement measure.

Legitimate separation for security, testing, distinct communities, or supported product use is allowed. AeroNexus may consider the purpose, ownership or control, activity pattern, technical relationship, and documented configuration when deciding whether related activity is an attempt to evade a control.

5. How AeroNexus may respond

When usage is excessive, inefficient, unintended, or destabilizing, AeroNexus may take a proportionate step such as:

  • explaining the observed issue and asking the Customer or User to investigate;
  • asking for activity to be corrected, optimized, scheduled, or reduced;
  • temporarily slowing, queueing, rejecting, or restricting affected activity;
  • temporarily limiting an affected feature, automation, integration, export, or background process; or
  • suspending or terminating access for severe, repeated, intentional, evasive, or harmful conduct as permitted by the Terms and Acceptable Use Policy.

For a less serious issue, AeroNexus will ordinarily provide notice and a reasonable opportunity to correct it when doing so is appropriate and safe. AeroNexus may act immediately when reasonably necessary to protect security, service stability, data, Users, third parties, or shared infrastructure. An emergency restriction is a protective measure and is not automatically a final finding that the Terms were breached. AeroNexus will review the circumstances and provide notice where reasonably possible.

6. Plans, allowances, and charges

AeroNexus currently offers no paid plans, purchased capacity, or overage billing. Technical controls do not create a promise that any amount of usage will always be available.

If AeroNexus later offers a paid plan or purchased allowance, the applicable Pricing Page, Product Documentation, Order Form, or Negotiated Agreement will describe the included commercial allowance and any charges before purchase. AeroNexus will not impose a surprise or retroactive overage charge.

Unless a Negotiated Agreement expressly says otherwise, describing a feature as "unlimited" would mean only that the plan has no preset commercial allowance for the stated feature. It would not mean infinite capacity or exemption from this FUP, the Terms, the Acceptable Use Policy, security controls, or service-stability measures.

7. Questions and review

If you believe a restriction was applied in error, or if you need help with an accidental spike, malfunctioning automation, or compromised credential, contact info@aero.nexus. Include the affected account or resource, feature, approximate time, and a short description of what happened. Do not send passwords, tokens, secret credentials, or other authentication material.

You may ask AeroNexus to review a restriction or discuss whether additional capacity is available. A review request does not automatically pause an urgent security or stability measure, and AeroNexus does not guarantee that additional capacity can be provided. An unresolved enforcement appeal may be sent to legal@aero.nexus.

8. Changes to this Policy

AeroNexus may update this FUP for a valid Service, capacity, security, platform, business, or legal 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 any 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. A temporary technical control does not silently create a new fee or retroactively reduce a purchased or expressly agreed allowance. The Terms govern acceptance, re-acceptance, continued use, and conflicts. Mandatory consumer, contract, and privacy rights remain unaffected.

9. Contact

Jump toBrowse this policy