How do you know about bugs without error tracking?

User reports. GitHub issues. Community channels. Direct emails. We're slower to find issues than wallets with embedded crash reporters, and we miss issues that don't get reported. We've decided that's the trade-off worth making.

Don't you need analytics to make good product decisions?

Many product teams say yes. We disagree, at least at our scale. Direct conversations with users, Discord, Telegram, GitHub feedback give us a richer picture than dashboard graphs would. The trade-off is slower detection of subtle problems. We accept that.

Is the website really tracker-free?

No client-side analytics, no marketing pixels, no retargeting cookies. We use server-side log processing for aggregate page-view counts. That's the entirety of what we know about visitors. The same principle that drives the wallet design applies to the site.

What happens to my data if you get hacked?

The data we don't collect can't be leaked. There's no centralized 'user database' with addresses, balances, or transaction patterns. A breach of our infrastructure cannot expose your private wallet usage information, because we never had it.

What if the policy changes later?

Adding telemetry would require shipping a new version. Open-source license + GitHub release process means any change is visible in the code before it ships. We commit to: no telemetry without explicit opt-in ever, every telemetry feature documented before release, reversible — you can use the older version.

No-Tracking Wallet Design — Why Sei Wallet Is Private

What telemetry-free actually means

A typical desktop or mobile wallet ships with several outbound data flows you might not realize are there:

Analytics SDK. Mixpanel, Amplitude, Segment, Google Analytics — recording feature clicks, screen time, balances when actions performed, time of day.
Error tracking. Sentry, Bugsnag — capturing crashes, often bundled with user identifiers, addresses, partial transaction details.
Marketing pixels. Facebook, Twitter, LinkedIn pixels — embedded in supporting web views or onboarding.
Update check pings. Periodic outbound calls including device fingerprints, OS version, installation IDs.
Crash reporters. OS-level uploads to vendor backends.

Even "privacy-focused" wallets often have several. Combined, they create a detailed picture of your usage on third-party servers.

Sei Wallet has none of them, except a manual opt-in update check.

What we don't collect

No address tracking. The wallet doesn't send your 0x... or sei1... addresses anywhere.
No balance tracking. We don't know what's in your wallet. Ever.
No transaction tracking. The wallet signs locally; signed transactions go directly to the chain RPC.
No usage analytics.
No device fingerprinting.
No third-party SDKs that phone home. No Sentry, Mixpanel, Segment, Amplitude, Google Analytics.
No marketing pixels in onboarding.

The single exception: clicking "Check for Updates" makes one HTTPS request to seiwallet.net to compare versions. Opt-in. Doesn't transmit identifiers beyond standard HTTP metadata. Doesn't run automatically.

Why we made this choice

The principle: a non-custodial wallet should be a tool that operates on the user's behalf, not an instrument the vendor can use to surveil or profile the user.

The practicality: the trade-offs are real. We trade off visibility into bugs, visibility into feature usage, A/B testing, push notifications. We rely on user reports, GitHub issues, community channels, direct feedback. We're slower to find problems and miss issues that don't get reported. We've decided that's worth it for the principle.

How to verify

Trust-but-verify is the right framing for any privacy claim:

1. Read the source code. Sei Wallet is open source under Apache 2.0 at github.com/seiwalletlabs/sei-wallet. Every dependency in the package manifest; every network call traceable in the source.

2. Run a network monitor. Little Snitch (macOS), GlassWire (Windows), or router-level monitoring. The wallet should make outbound calls only to your configured Sei RPC endpoint.

3. Check the build pipeline. Reproducible builds in development — clone repo, build locally, verify resulting binary hash matches published binary.

If you ever observe outbound requests beyond what's documented, that's a security disclosure: contact security@seiwallet.net.

What about the website (seiwallet.net)

seiwallet.net is also clean of analytics: no Google Analytics, no marketing pixels, no third-party tag managers, no retargeting cookies. Minimal first-party server-side log processing for aggregate page-view counts only.

Same principle: if we don't track you in the wallet, tracking you on the website to "optimize conversion" would be incoherent.

What about my privacy on the chain itself?

Telemetry-free wallet design only protects you from us — and from third parties we'd otherwise share data with. It does not make your on-chain activity private. The Sei chain is public. Anyone with your address can see your balance, staking history, token transfers, and dApp interactions.

The bottom line

We built Sei Wallet to be the kind of wallet we'd want to use. That meant a wallet that doesn't profile its users — not because it's a marketing position, but because we don't want our software to be a surveillance instrument.

You can trust this claim by reading the code, monitoring the network, or running the build yourself. If you find evidence to the contrary, please tell us.

Why we don't track you: telemetry-free wallet design