Privacy Policy

1 · Data We Collect (Spoiler: almost nothing)

• Local wallet data – encrypted key files, address book entries, and settings live only in your filesystem.
• Telemetry – none. We ship zero analytics or crash reporters.
• Website logs – the static site keeps standard web-server access logs for 7 days for abuse-mitigation. IPs are not correlated with wallet usage.
• Update checks – when you manually check for updates, the wallet queries GitHub releases over HTTPS; no identifiers are transmitted.

In short, we never collect anything that could tie your identity to on-chain activity.

2 · Remote Node Connectivity

By default the wallet connects to a community-run remote node. Requests are end-to-end encrypted over TLS and include only the data needed to detect your outputs (view-key–derived key images). Remote nodes cannot spend your funds or view past balances.

You may also configure Electrum XMR to route traffic through Tor or connect to your own full node for maximum metadata resistance.

3 · Cookies & Local Storage

The download site sets one short-lived session cookie to remember your language preference. No tracking, no third-party pixels. The cookie expires after 24 hours and is not shared with third parties.

4 · Security Measures

• All binaries are PGP-signed; hashes are published for independent verification.
• Desktop builds implement memory-hard encryption (scrypt) for wallet files.
• Continuous integration runs static-analysis and dependency-freshness checks on every commit.
• All network requests are pinned to official TLS certificates to prevent man-in-the-middle attacks.

5 · Third-party Libraries

Electrum XMR bundles open-source dependencies (Qt, Boost, OpenSSL). They are audited and vendored; no CDN calls are made at runtime.

6 · Your Rights

Because we store no personal data, requests for access, correction or deletion are generally moot. However, if you have questions, contact us at privacy@electrumxmr.org.

7 · Changes to This Policy

We may update this document for legal or technical reasons. Material changes will be announced on the project’s GitHub release notes.