AeroNyx Privacy Policy
Explains what AeroNyx-operated services collect, what they do not collect, and why AeroNyx cannot decrypt E2E messages, node-blind MemChain plaintext, user-held keys, or packet payloads.
AeroNyx Privacy Policy
Effective date: July 6, 2026
AeroNyx is a Wyoming, United States-based company building an open privacy protocol and product ecosystem for private network routing, encrypted communication, node-blind memory, and autonomous-agent coordination. This Privacy Policy explains what information AeroNyx collects, how we use it, and the privacy boundaries we design into AeroNyx products.
This policy applies to AeroNyx websites, documentation, applications, APIs, Nodeboard, AeroNyx Privacy Network, encrypted messaging features, MemChain, developer tools, support channels, and related services that link to this policy.
1. Scope and Layer Model
AeroNyx has four distinct layers:
- AeroNyx-operated services: websites, apps, APIs, Nodeboard, documentation, support channels, discovery services, bootstrap lists, public statistics, and other services operated by AeroNyx.
- 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: external model providers, RPC providers, payment processors, app stores, hosting providers, independent node operators, and other services selected by users or node operators.
This Privacy Policy describes AeroNyx-operated services and the data AeroNyx processes through those services. It also explains the privacy design of the AeroNyx protocol, but independent node operators and third-party services may have their own legal obligations, security practices, and privacy policies.
2. Our Privacy Position
AeroNyx is designed around a simple rule: infrastructure should move, store, and coordinate encrypted data without needing AeroNyx-operated services to read the user's private content. We separate encrypted user content from the limited metadata required to operate a networked service.
Where AeroNyx uses end-to-end encryption, node-blind storage, or user-held keys, AeroNyx-operated infrastructure cannot decrypt or access plaintext content protected by those keys, including:
- message plaintext
- encrypted message attachments
- MemChain memory plaintext and private memory objects
- private keys, seed phrases, wallet secrets, or user-held decryption keys
- private conversation history and private AI memory contents
- application-layer payloads protected by end-to-end encryption
- browsing contents protected by HTTPS or other end-to-end encrypted protocols
Encrypted user content remains unreadable to AeroNyx, but some metadata is still necessary to operate a networked service. For example, AeroNyx may process account identifiers, public wallet addresses that you choose to connect, node registration data, aggregate network statistics, device diagnostics, timestamps, bandwidth counters, and abuse-prevention signals.
3. AeroNyx Cannot Decrypt User Content
For AeroNyx Privacy Network, encrypted messaging, relay, and MemChain features, AeroNyx-operated infrastructure is designed not to decrypt, inspect, read, monitor, or recover user-held encrypted content.
This means AeroNyx-operated services do not have the technical ability to access the plaintext of user-key-protected encrypted packets, encrypted messages, encrypted attachments, MemChain memory plaintext, private memory objects, private keys, seed phrases, or user-held decryption keys.
Because AeroNyx-operated services cannot decrypt this encrypted content, AeroNyx also cannot review encrypted payloads for meaning, recover lost encrypted content, or determine what a user transmitted inside an encrypted payload.
Privacy Network routing note: when traffic is routed through network nodes, a node may process limited routing data required to transmit packets, such as endpoint, destination IP/port, protocol, timing, and byte counts. AeroNyx's control plane is designed around aggregate operational reporting and does not require nodes to report packet contents, full URLs, browsing history, message plaintext, MemChain plaintext, or user-held decryption material.
Users should still use end-to-end encrypted application protocols, such as HTTPS, for content confidentiality on the wider internet. AeroNyx's privacy protocol does not turn third-party websites, external services, independent node operators, or destination services into AeroNyx-operated services.
This boundary does not apply to information you intentionally send to AeroNyx in plaintext, such as support emails, public community posts, bug reports, legal notices, or other direct communications with AeroNyx.
4. Information We Collect
Information you provide
We may collect information you choose to provide, including:
- email address or contact details when you request support, join a waitlist, or communicate with us
- account profile information, if you create an AeroNyx account
- public wallet addresses or public identifiers you choose to connect
- node operator registration details, such as node name, region, public endpoint, service capability, and administrative contact information
- feedback, bug reports, support messages, and other content you intentionally send to AeroNyx
Application and device information
We may collect limited technical information needed to operate, secure, debug, and improve AeroNyx, including:
- app version, build version, operating system, device type, language, and region
- crash logs, performance diagnostics, and error reports
- security and abuse-prevention events
- connection state needed to provide services, such as session start and end time, encrypted byte counters, and service health status
Privacy Network and protocol statistics
AeroNyx may publish or process aggregate protocol statistics, such as:
- total encrypted traffic
- encrypted packet or relay counts
- node health and uptime summaries
- peer discovery summaries
- route proof acceptance or rejection counts
- capacity and availability metrics
These statistics are intended to describe protocol health. They are not intended to expose individual user browsing contents, message plaintext, wallet-level activity, DNS contents, or individual private destinations.
Nodeboard and node operator data
If you operate an AeroNyx node or use Nodeboard, we may process:
- node registration records
- public endpoint and region data
- node service capability and capacity metadata
- heartbeat, health, lifecycle, and restart recovery events
- command audit logs for administrative actions
- incident and maintenance records
Nodeboard is an operations product designed to display protocol and node health without exposing user content.
Because AeroNyx is an open protocol, independent people and organizations may run compatible protocol nodes. When a node operator chooses to register, report, or manage a node through AeroNyx-operated services, AeroNyx may process the operational node metadata described above to support discovery, health monitoring, compatibility, abuse prevention, and network transparency.
Node operators should also review the AeroNyx Node Operator Policy: https://docs.aeronyx.network/articles/aeronyx-node-operator-policy.
MemChain and encrypted storage
MemChain is designed as node-blind memory. AeroNyx nodes are designed to store encrypted memory objects, blind indexes, and versioned metadata without receiving plaintext memory content or user-held decryption keys.
If you choose an external AI model provider to distill or answer over your memories, relevant plaintext may be sent to that provider according to your configuration and that provider's terms. If you use a local model, memory processing can remain local to your device.
Cookies and similar technologies
Our websites may use cookies, local storage, and similar technologies for security, preferences, analytics, and product improvement. You can control cookies through your browser settings, but some features may not function correctly if cookies are disabled.
For more detail, see the AeroNyx Cookie Policy: https://docs.aeronyx.network/articles/aeronyx-cookie-policy.
5. How We Use Information
We use information to:
- provide, maintain, and improve AeroNyx products
- route encrypted traffic and messages
- operate node discovery, health checks, and capacity reporting
- synchronize encrypted, node-blind state where enabled
- authenticate users and node operators
- provide support and respond to requests
- detect abuse, spam, malware, attacks, and service misuse
- debug crashes, improve reliability, and monitor performance
- publish aggregate protocol transparency metrics
- comply with legal obligations and enforce our terms
6. How We Share Information
We do not sell your private message content, private memory content, wallet secrets, or packet payloads.
We may share limited information with:
- service providers that help us host, secure, operate, analyze, or support AeroNyx
- payment processors, if paid features are offered
- infrastructure providers used to deliver websites, APIs, and application services
- professional advisers, such as lawyers, accountants, auditors, or security consultants
- law enforcement, regulators, or courts when required by applicable law
- parties involved in a merger, financing, acquisition, restructuring, or similar corporate transaction
For legal request handling and transparency reporting, see the AeroNyx Law Enforcement and Transparency Policy: https://docs.aeronyx.network/articles/aeronyx-law-enforcement-and-transparency-policy.
When third-party services are used, their own terms and privacy policies may apply.
7. Legal Bases and Compliance
Depending on where you live, we process personal information based on one or more legal bases, including:
- your consent
- performance of a contract
- legitimate interests in operating, securing, and improving AeroNyx
- compliance with legal obligations
- protection of users, AeroNyx, and the public from abuse or security threats
If a privacy law grants you specific rights, we will honor those rights where they apply.
8. Your Choices and Rights
Depending on your location, you may have the right to:
- access personal information we hold about you
- request correction of inaccurate information
- request deletion of certain information
- object to or restrict certain processing
- withdraw consent where processing is based on consent
- opt out of marketing communications
- request a portable copy of certain information
To make a privacy request, contact us at hi@aeronyx.network. We may need to verify your request before acting on it.
9. California Privacy Notice
If California privacy law applies to your use of AeroNyx, California residents may have rights to know, access, correct, delete, and opt out of certain uses of personal information.
AeroNyx does not sell personal information or share personal information for cross-context behavioral advertising as those terms are commonly used under applicable privacy law, unless we provide the notice and choice required by that law. AeroNyx does not use private message plaintext, private memory plaintext, packet payloads, seed phrases, private keys, wallet secrets, or user-held decryption material for cross-context behavioral advertising.
10. Data Retention
We keep information only for as long as reasonably necessary for the purposes described in this policy, including service operation, security, fraud prevention, dispute resolution, legal compliance, and legitimate business needs.
For more detail, see the AeroNyx Data Retention Policy: https://docs.aeronyx.network/articles/aeronyx-data-retention-policy.
Retention periods vary by data type. For example:
- support messages may be retained while needed to resolve requests
- crash logs and diagnostics may be retained for debugging and reliability
- node health and command audit logs may be retained for operational security and accountability
- aggregate protocol statistics may be retained to show long-term network health
- encrypted user-controlled data may remain available until you delete it, your retention settings expire, or the service removes it under applicable policy
11. Security
We use technical, organizational, and administrative safeguards designed to protect information. No system is perfectly secure. You are responsible for protecting your own devices, credentials, wallets, recovery phrases, and private keys.
To report a vulnerability, see the AeroNyx Security and Vulnerability Disclosure Policy: https://docs.aeronyx.network/articles/aeronyx-security-and-vulnerability-disclosure-policy.
Where AeroNyx uses end-to-end encryption, node-blind storage, or user-held keys, loss of your keys may make data unrecoverable. AeroNyx cannot decrypt data that it was not designed to read or recover user-held decryption material that it never received.
12. International Users
AeroNyx is operated from the United States and may process information in the United States and other countries. By using AeroNyx, you understand that information may be transferred to jurisdictions with privacy laws different from those in your country.
13. Children
AeroNyx is not intended for children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact us at hi@aeronyx.network.
14. Changes to This Policy
We may update this Privacy Policy from time to time. If we make material changes, we will update the effective date and may provide additional notice through the website, app, or other reasonable channels.
15. Contact
For questions or privacy requests, contact:
AeroNyx
Email: hi@aeronyx.network