AeroNyx Law Enforcement and Transparency Policy

Effective date: July 6, 2026

AeroNyx is a Wyoming, United States-based company building an open privacy protocol and product ecosystem. This policy explains how AeroNyx handles law enforcement, government, regulatory, emergency, preservation, and legal requests involving AeroNyx-operated services.

This policy is intended to make one boundary clear: AeroNyx may be able to provide records it actually has from AeroNyx-operated services, but AeroNyx cannot decrypt user-key-protected encrypted content, recover user-held keys, or provide data it does not collect or control.

1. Scope

This policy applies to AeroNyx-operated services, including official websites, apps, APIs, Nodeboard, documentation, support channels, discovery services, bootstrap lists, public statistics, and related hosted services operated by AeroNyx.

This policy does not make independent protocol nodes, external model providers, RPC providers, payment processors, app stores, hosting providers, destination services, or other third parties AeroNyx-operated services. Those parties may have their own legal obligations and response procedures.

2. Our Principles

AeroNyx evaluates legal requests according to these principles:

• comply with valid legal obligations that apply to AeroNyx
• protect user privacy and security
• require requests to be specific, lawful, and properly issued
• narrow or challenge overbroad, vague, unlawful, or technically impossible requests where appropriate
• notify affected users when legally permitted and appropriate
• provide only records AeroNyx has and can lawfully disclose
• preserve the no-decrypt boundary for user-key-protected encrypted content

3. Information AeroNyx Cannot Provide

For end-to-end encrypted, node-blind, or user-key-protected features, AeroNyx-operated services are designed not to have plaintext access. AeroNyx cannot provide what it does not possess or cannot technically access.

Depending on the feature and configuration, AeroNyx generally cannot provide:

• private keys, seed phrases, wallet secrets, or user-held decryption material
• message plaintext protected by end-to-end encryption
• encrypted attachment plaintext
• MemChain memory plaintext or private memory objects
• decrypted packet payloads protected by user-held encryption
• passwords or recovery secrets that AeroNyx does not store
• browsing history, full URLs, DNS contents, or destination contents that AeroNyx-operated services do not collect
• a decrypted copy of encrypted payloads routed through the privacy protocol

AeroNyx also cannot guarantee that independent node operators or third-party services have the same records or follow the same practices.

4. Information AeroNyx May Have

Depending on the user's choices, service configuration, and retention periods, AeroNyx-operated services may have limited records such as:

• account identifiers, email addresses, or profile information provided by the user
• public wallet addresses or public identifiers the user chose to connect
• support emails, bug reports, legal notices, or other plaintext communications sent to AeroNyx
• app version, device type, region, language, crash logs, diagnostics, or security events
• node operator registration records, public endpoint, region, capability, and administrative contact information
• Nodeboard command audit logs, lifecycle events, health events, maintenance records, and incident records
• aggregate protocol statistics, such as encrypted traffic totals, packet counts, relay counts, node health, and uptime summaries
• payment or subscription records processed by AeroNyx or payment providers
• server logs or abuse-prevention signals retained by AeroNyx-operated services

Available records vary. AeroNyx does not create new records, decrypt content, or redesign systems to satisfy a request.

For general retention targets, see the AeroNyx Data Retention Policy: https://docs.aeronyx.network/articles/aeronyx-data-retention-policy.

5. Legal Process Requirements

Legal requests should be sent to hi@aeronyx.network with the subject line Legal Request.

Requests should include:

• the requesting agency or party
• the name, title, and contact information of the requester
• the legal authority for the request
• the signature or authorization required by law
• the specific account, public identifier, node ID, endpoint, transaction, time range, or records requested
• a clear explanation of the legal basis and relevance
• any non-disclosure order, sealing order, emergency certification, or preservation demand

Email is provided for routing and review. It does not waive any legal requirement for formal service of process.

6. Emergency Requests

AeroNyx may review emergency requests involving imminent risk of death, serious physical injury, child safety, or comparable emergency harm.

Emergency requests should clearly state:

• the nature of the emergency
• the specific harm and why it is imminent
• the records requested
• how the requested records may address the emergency
• the requester's authority and contact information

AeroNyx may require follow-up legal process after responding to an emergency request.

7. Preservation Requests

Where required by applicable law, AeroNyx may preserve available records for a limited period. Preservation does not mean AeroNyx has reviewed, produced, or agreed to produce the records.

AeroNyx cannot preserve content or keys it does not possess, cannot decrypt, or cannot access.

8. User Notice

When legally permitted and appropriate, AeroNyx may notify affected users or node operators before producing records.

AeroNyx may delay or withhold notice if prohibited by law, court order, risk of harm, risk to security, risk to an investigation, or other legally valid reason.

9. Narrowing, Challenging, and Refusing Requests

AeroNyx may seek clarification, narrow, challenge, or refuse requests that are:

• overbroad
• vague
• technically impossible
• not properly authorized
• inconsistent with applicable law
• seeking data AeroNyx does not have
• seeking decryption or user-held keys AeroNyx cannot provide
• targeting independent nodes or third parties outside AeroNyx's control

10. Independent Nodes and Third Parties

AeroNyx is an open protocol. Independent people and organizations may operate compatible nodes. AeroNyx does not control every compatible protocol node, independent node operator, destination service, model provider, RPC provider, payment processor, app store, hosting provider, or other third-party service.

If a request concerns an independent node or third-party service outside AeroNyx's control, the requester may need to contact that operator or service directly.

AeroNyx-operated services may have node metadata if a node operator chose to register, report, or manage a node through those services, but AeroNyx does not automatically possess all logs or records held by independent operators.

11. Transparency Reporting

AeroNyx may publish aggregate transparency information about legal requests, preservation requests, emergency requests, or account/node requests, unless prohibited by law or operationally unsafe.

Transparency reports may include totals, request types, jurisdictions, challenged requests, complied-with requests, and categories of records disclosed. They will not include user plaintext, private keys, or other confidential details.

12. Changes

AeroNyx may update this policy as our services, protocol design, legal obligations, or operational practices evolve.

13. Contact

For legal requests or questions about this policy:

AeroNyx
Email: hi@aeronyx.network
Subject: Legal Request