Privacy & Data Use

1. Overview & scope

This privacy note describes how the Electrum NEO Wallet project approaches data and privacy. It covers:

• the Electrum NEO Wallet desktop application for Neo and Neo X; and
• this marketing website where you learn about the wallet and download releases.

It does not cover external services such as Neo/Neo X RPC providers, explorers, bridges, DeFi protocols, or social / community platforms. Those services have their own privacy policies and terms.

2. What we don’t collect

By design, the wallet and this website aim to minimise how much personal data is collected or processed. In particular:

• No custody of your funds.
• No access to your seed phrase or private keys.
• No in-wallet user accounts or passwords on our servers.
• No KYC / identity verification flows inside the wallet.
• No on-chain transaction history profiling for marketing.

The wallet operates as a client that speaks to Neo and Neo X infrastructure you select or trust. Network operators, explorers, bridges and dApps may observe and log activity according to their own policies.

3. Wallet app: what stays on your device

The desktop app stores sensitive wallet material locally on the device where you run it. In particular:

• Your recovery phrase and private keys are generated on your machine and are not sent to project maintainers or to a central server.
• Your wallet file (containing encrypted key material and metadata) is stored locally by the app, under your user account on the operating system.
• Configuration and preferences such as selected RPC endpoints, network (MainNet or TestNet), language and UI settings are also stored locally.

The wallet may show technical information such as balances, addresses and transaction history in the interface, but this information is derived from public blockchain data and from your local wallet file.

Logs and diagnostic information

The wallet may keep temporary logs on your device to help troubleshoot connection issues, RPC errors or application crashes. These logs typically contain:

• timestamps of events and error messages;
• your wallet and application version;
• basic operating system information.

When you report an issue (for example on GitHub or in a community channel), you choose whether to share any logs or diagnostics. Review logs before sharing them publicly and redact anything you are not comfortable disclosing.

4. Network connections and RPC nodes

Electrum NEO Wallet uses a thin-client / SPV-style architecture. Instead of downloading the full blockchain, the wallet connects to Neo and Neo X RPC nodes to query balances and broadcast transactions.

When you use the wallet:

• the app connects to RPC endpoints you select or that are recommended in the configuration;
• those RPC operators may log your IP address, request patterns and other technical metadata as part of their infrastructure operations;
• your transactions and interactions with smart contracts become part of the public Neo / Neo X blockchains and can be observed by anyone using an explorer.

Custom endpoints and self-hosted nodes

Advanced users may configure the wallet to connect to their own Neo / Neo X nodes. In that setup, any logging or retention of IP addresses and request data is fully under the control of the infrastructure you operate.

5. Website, cookies and usage analytics

This website is primarily informational: it explains how the wallet works and provides links to downloads and source code. To keep the site secure and to understand aggregate usage, we may use:

• strictly necessary cookies or local storage for basic functionality such as remembering your cookie preferences; and
• privacy-respecting analytics to understand which pages are visited and which platforms (desktop / mobile, browser families) are used.

Any analytics we use are intended to work with aggregated, non-identifying data. We do not use this website to:

• build marketing profiles from your on-chain activity; or
• sell your personal data to advertising networks.

You can typically control or block cookies and trackers in your browser settings. Using content blockers or “Do Not Track” preferences may further reduce the amount of data shared with third parties when browsing the site.

6. Error reports, issues and community channels

The project uses public channels such as GitHub, community chats and social platforms to coordinate development and support users. When you interact through these channels, you decide which information to disclose.

• On GitHub, issues and comments are public by default. Avoid posting recovery phrases, private keys or raw wallet files. If you share logs, review them first.
• In community chats (such as Discord or Telegram), administrators and platform providers may see your messages and metadata in line with their own terms of service.
• Screenshots may expose wallet balances, addresses and parts of your transaction history. Consider masking sensitive details before sharing.

Each platform you use to contact the project (GitHub, Discord, Telegram, Twitter/X, etc.) is itself operated by a third party with its own privacy policy and data practices.

7. Third-party services

The Electrum NEO Wallet project is part of a broader Neo ecosystem. Depending on how you use the wallet and this website, you may interact with:

• Neo / Neo X RPC and node providers that expose blockchain data and accept transaction broadcasts;
• explorers for inspecting blocks, transactions and addresses;
• bridges and DeFi protocols for moving assets or participating in on-chain strategies;
• social platforms used for announcements and community support;
• source code hosting platforms where releases, checksums and issues are published.

These services are independently operated. Their operators decide which data they collect, how long they keep it, and for which purposes they process it. Always review the terms and privacy documentation for any third-party service you rely on.

8. Your choices & controls

Within the limits of a public blockchain system, you have several ways to control how much information is exposed when using Electrum NEO Wallet:

• Wallet configuration. Choose RPC endpoints you trust. Advanced users can point the wallet at self-hosted infrastructure.
• Network hygiene. Use secure networks you control, keep your operating system updated and apply common security practices to reduce the risk of compromise.
• Website privacy tools. Configure your browser’s cookie and tracking settings, and use content blockers if you prefer to minimise analytics.
• Selective sharing. When requesting support or reporting a bug, only share the information that is necessary to explain the issue.

9. Changes to this privacy note

As the Electrum NEO Wallet project evolves, this privacy note may be updated to reflect changes in functionality, infrastructure or applicable regulations.

• We will publish the latest version of this page at the same URL.
• Material changes may be highlighted in release notes or project communications where appropriate.

Last updated: 3 February 2026

If you have questions about how this project approaches privacy and data, please contact the maintainers through the project’s public channels listed on the main website or repository.