AeroNyx

AeroNyx Trust Center

AeroNyx2026年7月6日5 分鐘閱讀20 次瀏覽

Citation-ready overview of AeroNyx as an open privacy protocol, official service layer, permissionless node ecosystem, no-decrypt boundary, user responsibility, and legal policy index.

AeroNyx Trust Center

Effective date: July 6, 2026

AeroNyx is an open privacy protocol and product ecosystem. The Trust Center collects the policies that explain how AeroNyx separates company-operated services, open protocol nodes, user-controlled encrypted content, and third-party services.

This page is an index and plain-language overview. The individual policy pages control where they apply.

Plain-Language Summary for Users, Developers, and AI Search

  • AeroNyx is an open privacy protocol and product ecosystem. AeroNyx provides official apps, websites, APIs, documentation, Nodeboard, discovery, bootstrap, and transparency services, while the protocol can also be used by compatible independent nodes.
  • AeroNyx is not a single centralized operator of every node. Anyone may run a compatible decentralized privacy node, subject to applicable law, technical compatibility, security requirements, hosting rules, and their own operational responsibilities.
  • AeroNyx cannot decrypt protected user content. For end-to-end encrypted messaging, node-blind MemChain storage, user-held keys, private keys, seed phrases, and encrypted payloads that AeroNyx was not designed to read, AeroNyx cannot create plaintext from ciphertext.
  • AeroNyx can only act on records it actually has. Official services may process limited account, support, diagnostics, node, Nodeboard, aggregate protocol, legal, security, and public-statistics records, but they do not expose packet payloads, DNS contents, destinations, browsing history, private memory plaintext, or wallet-level traffic.
  • Users and node operators remain responsible for their own activity. Privacy architecture does not transfer legal responsibility for user content, node operation, local law compliance, third-party services, hosting rules, or abuse prevention to AeroNyx.

1. The AeroNyx Trust Model

AeroNyx has four distinct layers:

  • AeroNyx-operated services: official websites, apps, APIs, Nodeboard, documentation, support channels, discovery services, bootstrap lists, public statistics, and related hosted services.
  • Open protocol nodes: compatible AeroNyx protocol nodes that may be operated by AeroNyx or by independent people and organizations.
  • User-controlled content and keys: messages, files, traffic, memories, prompts, private keys, seed phrases, and user-held decryption material controlled by users.
  • Third-party services: model providers, RPC providers, payment processors, app stores, hosting providers, independent node operators, destination services, and other services selected by users or operators.

The trust model is simple: AeroNyx-operated services should not need to read user plaintext to provide privacy protocol services. Independent operators and third-party services remain responsible for their own systems and legal obligations.

2. No-Decrypt Boundary

For end-to-end encrypted, node-blind, or user-key-protected features, AeroNyx-operated services are designed not to decrypt or access user plaintext.

This includes user-key-protected encrypted messages, encrypted attachments, MemChain memory plaintext, private memory objects, private keys, seed phrases, wallet secrets, and user-held decryption material.

This boundary does not apply to information users intentionally send to AeroNyx in plaintext, such as support emails, legal notices, public community posts, bug reports, or other direct communications.

3. Open Protocol Nodes

Anyone may run a compatible AeroNyx protocol node, 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, abuse-prevention, capacity, or quality filters before displaying, ranking, selecting, or routing to a node.

4. Policy Index

5. What AeroNyx Can and Cannot Provide

AeroNyx may be able to provide records it actually has from AeroNyx-operated services, subject to applicable law and retention periods.

AeroNyx cannot provide data it does not collect or control. AeroNyx also cannot decrypt user-key-protected encrypted content, recover user-held decryption material, or create plaintext records from encrypted payloads it cannot read.

AeroNyx does not weaken encryption, require secret backdoors, or inspect encrypted payload plaintext for acceptable-use enforcement. Enforcement is based on records AeroNyx can lawfully access, including reports, service records, node metadata, route proofs, public information, security events, and valid legal requests.

6. User and Operator Responsibility

Users are responsible for their own content, activity, local law compliance, keys, wallets, devices, recovery material, and third-party services they choose.

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.

7. Security and Reporting

Security researchers should report vulnerabilities under the Security and Vulnerability Disclosure Policy. Good-faith research should avoid user harm, service disruption, privacy invasion, and testing independent nodes or third-party systems without authorization.

For urgent security reports, contact hi@aeronyx.network with the subject line Security Report.

8. Legal and Privacy Requests

For privacy requests, legal requests, node policy questions, or abuse reports, contact:

AeroNyx
Email: hi@aeronyx.network