AeroNyx

AeroNyx Acceptable Use Policy

AeroNyx6 tháng 7, 20267 phút đọc12 lượt xem

Defines prohibited conduct, user content responsibility, decentralized node abuse boundaries, privacy-respecting enforcement, and no-backdoor acceptable-use handling.

AeroNyx Acceptable Use Policy

Effective date: July 6, 2026

AeroNyx is a Wyoming, United States-based company building an open privacy protocol and product ecosystem. This Acceptable Use Policy explains the conduct that is not allowed when using AeroNyx-operated services, publishing or registering compatible protocol nodes through AeroNyx-operated surfaces, interacting with Nodeboard, using AeroNyx Privacy Network, sending encrypted messages, storing encrypted memory through MemChain, or using AeroNyx developer tools.

This policy is part of the AeroNyx Terms of Service. It is designed to protect users, node operators, developers, independent infrastructure participants, and AeroNyx-operated services while preserving a core privacy boundary: AeroNyx does not read end-to-end encrypted payload plaintext, node-blind memory plaintext, private keys, seed phrases, or user-held decryption material.

1. Scope

This policy applies to:

  • AeroNyx-operated websites, applications, APIs, documentation, support channels, and developer tools
  • AeroNyx Privacy Network and encrypted messaging features provided through AeroNyx-operated services
  • Nodeboard and other AeroNyx-operated node management, discovery, telemetry, or transparency services
  • node registration, heartbeat reporting, lifecycle events, capacity reporting, route proofs, and protocol statistics submitted to AeroNyx-operated services
  • MemChain and other encrypted storage features provided through AeroNyx-operated services

AeroNyx is an open protocol. Anyone may run compatible protocol nodes, subject to applicable law, technical compatibility, security requirements, hosting rules, and their own infrastructure responsibilities. Running a node does not mean AeroNyx has approved, certified, endorsed, supervised, or taken responsibility for that node.

AeroNyx-operated apps, Nodeboard, bootstrap lists, discovery services, public statistics, and routing surfaces may apply health, compatibility, security, abuse-prevention, capacity, or quality filters before displaying, ranking, selecting, or routing to a node.

2. User Content and Legal Responsibility

You are responsible for content, traffic, messages, files, memories, prompts, requests, commands, metadata, node advertisements, and other activity that you create, send, store, route, relay, publish, or cause to be processed through AeroNyx.

AeroNyx cannot decrypt or access user content protected by end-to-end encryption, node-blind storage, user-held keys, private keys, seed phrases, or other user-controlled decryption material that AeroNyx never receives. This technical boundary does not transfer legal responsibility for your activity to AeroNyx.

You must comply with laws, regulations, sanctions, export controls, telecommunications rules, data protection rules, hosting rules, and third-party rights that apply to your activity and jurisdiction.

3. Prohibited Conduct

You may not use AeroNyx-operated services or AeroNyx-compatible protocol participation to:

  • violate applicable law, regulation, sanctions, export controls, or court orders
  • create, upload, store, route, relay, request, or distribute child sexual abuse material or content that exploits or harms minors
  • threaten, harass, stalk, dox, intimidate, or promote violence against individuals or groups
  • distribute malware, ransomware, spyware, credential stealers, phishing kits, botnets, exploit kits, or harmful code
  • conduct phishing, fraud, scams, spam, fake support, impersonation, or deceptive activity
  • attack, overload, disrupt, scan, probe, scrape, or interfere with AeroNyx infrastructure, independent nodes, third-party systems, or user devices without authorization
  • attempt to deanonymize users, correlate private traffic, defeat privacy protections, or build unauthorized surveillance datasets
  • bypass rate limits, access controls, abuse-prevention systems, payment controls, node eligibility filters, or security measures
  • forge, manipulate, replay, or falsify node heartbeats, route proofs, capacity data, lifecycle events, traffic statistics, peer discovery data, restart recovery state, or protocol health reports
  • use Sybil behavior, fake nodes, false capabilities, manipulated availability, or misleading endpoints to degrade route quality or deceive users
  • violate intellectual property, privacy, publicity, contractual, or other third-party rights
  • publish or transmit non-consensual intimate content, private personal information, or other unlawful private material
  • use AeroNyx for unauthorized gambling, regulated financial activity, weapons sales, controlled substances, or other activity requiring permissions you do not have
  • use AeroNyx to evade legally valid restrictions in a way that creates legal, security, or operational risk for AeroNyx-operated services
  • misrepresent affiliation with AeroNyx, claim official certification without permission, or use AeroNyx marks in a misleading way

4. Node Operator Requirements

Node operators must not use compatible nodes to inspect, decrypt, inject, tamper with, log, sell, correlate, or intentionally expose user content or private routing activity.

Node operators are responsible for their own nodes, including security, uptime, lawful operation, hosting rules, disclosures, taxes, licenses, abuse handling, local logging or retention obligations, and compliance with laws that apply to their operation.

When using AeroNyx-operated node surfaces, node operators must provide accurate node configuration, endpoint, capability, region, capacity, route proof, heartbeat, and lifecycle information. False reporting may result in removal from AeroNyx-operated discovery, Nodeboard, routing, transparency, or public statistic surfaces.

For more detail, see the AeroNyx Node Operator Policy: https://docs.aeronyx.network/articles/aeronyx-node-operator-policy.

5. Security Research

Good-faith security research must follow the AeroNyx Security and Vulnerability Disclosure Policy: https://docs.aeronyx.network/articles/aeronyx-security-and-vulnerability-disclosure-policy.

Security testing must avoid user harm, service disruption, privacy invasion, data exfiltration, persistence, malware deployment, destructive testing, social engineering, and testing independent nodes or third-party systems without authorization.

6. Privacy-Respecting Enforcement

AeroNyx does not weaken encryption, require secret backdoors, or inspect encrypted payload plaintext to enforce this policy.

AeroNyx may enforce this policy using information it can lawfully access, such as:

  • account, support, billing, website, app, or API records from AeroNyx-operated services
  • user reports, abuse reports, vulnerability reports, and public information
  • node registration, heartbeat, lifecycle, capacity, route proof, and protocol health metadata
  • aggregate protocol statistics and security events
  • legal requests, emergency requests, or preservation requests handled under the Law Enforcement and Transparency Policy

AeroNyx cannot provide, inspect, or moderate data it does not collect, control, or have the technical ability to decrypt.

7. Enforcement Actions

If AeroNyx believes this policy has been violated, or that activity creates legal, security, abuse, privacy, trust, or operational risk, AeroNyx may take action including:

  • warning the user or node operator
  • limiting, suspending, or terminating access to AeroNyx-operated services
  • removing or reducing visibility of a node from AeroNyx-operated discovery, bootstrap, ranking, routing, Nodeboard, or public statistic surfaces
  • rejecting node heartbeats, route proofs, command requests, telemetry, or registration attempts
  • rate limiting, blocking, or filtering traffic to AeroNyx-operated services
  • preserving records where legally required or reasonably necessary
  • reporting activity to law enforcement, regulators, hosting providers, app stores, payment processors, or other third parties where legally required or appropriate

Independent protocol nodes and third-party services may have their own rules, logs, retention practices, enforcement choices, and legal obligations. AeroNyx is not responsible for independent nodes or third-party services it does not operate.

8. Appeals and Reports

If you believe AeroNyx took action in error, or if you want to report abuse, contact:

AeroNyx
Email: hi@aeronyx.network

Please include enough context for AeroNyx to review the issue without sending private keys, seed phrases, user-held decryption material, or unnecessary sensitive content.

9. Relationship to Other Policies

This policy should be read together with:

If there is a conflict between this policy and the Terms of Service, the Terms of Service control unless the Terms say otherwise.

10. Changes

AeroNyx may update this policy from time to time. If changes are material, AeroNyx may provide notice through the website, app, documentation, Nodeboard, or other reasonable channels.