Table of Contents
Privacy Settings
Control what's shared, what's stored, and how you connect—without sacrificing security or UX.
1. Telemetry & Analytics (Opt-in, minimal)
Default: Off (opt-in).
What we collect if enabled:
- • App events (aggregate): feature usage counts (e.g., opened Send screen), error rates, performance timings
- • Environment basics: app version, platform (browser/OS), language, screen size class
- • No wallet data: no addresses, balances, tx hashes, or contact labels are sent
- • No session replay, no keystrokes
Tooling: lightweight, privacy-preserving analytics (self-hosted or EU-hosted)
Control: Settings → Privacy → Analytics (toggle at any time)
Effect of OFF: zero analytics beacons; app behaves fully
2. RPC & Network Privacy
Current approach:
- • EVM networks: reputable third-party RPCs (e.g., Alchemy/Infura/QuickNode), with the option to add a custom RPC
- • Vite: official/community endpoints (configurable)
Your controls:
- • RPC selection: Settings → Networks → choose PRC default, add Custom RPC, or switch per chain
- • Proxy mode (optional): route read-only calls via a lightweight PRC proxy to reduce direct IP exposure to third parties. (Writes still go to your chosen RPC.)
Tip: For higher privacy, use a reputable VPN, choose privacy-respecting RPCs, and avoid logging into multiple personal accounts in the same browser profile.
3. Local vs Remote Data
Local (on your device/browser)
- • Encrypted keys and session
- • Address book/labels
- • Recent addresses
- • Settings (theme, language, privacy toggles)
- • Cached token list
- • UI state
- • "Mask balances" preference
- • Default explorer
- • dApp permissions history
Remote (our servers)
None required for core wallet.
We do not store your addresses, balances, or transactions.
Cloud backup/sync:
- • Not automatic. Cross-device usage is via seed (and passphrase, if used)
- • (Planned) optional encrypted settings export/import file you can store wherever you like
4. Privacy Toggles
You'll find these in Settings → Privacy:
Additional Settings:
- • Block explorer preference — Choose your explorer per chain (we don't auto-ping explorers with your addresses)
- • Clipboard safety — Auto-clear copied addresses after X seconds (configurable)
- • Price data source — Choose default price feed behavior (e.g., built-in proxy vs direct third-party)
- • Custom RPC — Add/choose your own RPC endpoints per network
5. Address Book & Labels (Local-only)
- • Local storage: Names/labels live only on your device
- • Export/Import (optional): Encrypted file you control
- • Contact privacy: We don't sync contacts; sending to a contact doesn't share that label anywhere on-chain
6. Transaction History & Explorers
- • On-chain is public: anyone can view transactions on a block explorer
- • In-app history: Cached locally for convenience; you can clear local history anytime (doesn't erase the chain)
- • Explorer links: We use your chosen explorer; no background lookup of your addresses
7. Best-Practice Playbook (Recommended)
Separate wallets for separate lives:
Additional recommendations:
- • Fresh addresses for sensitive flows (when supported)
- • Beware extensions & tab clutter: Use a clean browser profile for crypto
- • Use a passphrase (advanced) for sensitive holdings—only if you will never forget it
- • Device hygiene: OS disk encryption, strong screen lock, safe clipboard habits
- • VPN or Tor Browser for elevated privacy; expect some dApps/RPCs to block Tor
8. External Integrations & Data Sources
- Price data: Fetched from third-party price APIs; we send only asset identifiers / chain—not your addresses.
- On/Off-ramp partners (if used): When you choose a partner (e.g., buy crypto), you interact under their privacy policy; we pass only what's needed to start the flow (never keys).
- Telegram companion (optional): Tips/alerts only. No keys, seeds, or balances are stored or transmitted via Telegram. You can disconnect anytime.
- dApps (WalletConnect, injected): You approve per site; PRC shows clear permissions and lets you revoke later.
9. Frequently Asked Privacy Questions
Do you collect my addresses or balances?
No. We don't send addresses or balances to our servers. RPCs you choose will inevitably see requests they service.
Can PRC see my transactions?
Not from our servers. Transactions are public on the chain's explorer.
Does analytics track my wallet usage?
Only if you turn it on—and then only aggregate UX events (no addresses, no tx hashes).
Is there built-in coin mixing?
No. We don't offer mixing services. For privacy coins/features, research the legal and technical implications in your jurisdiction.
Will you add hardware-wallet support?
Planned. When available, hardware signing keeps keys off your online device.
10. Suggested Browser/OS Setup
Browser:
- • Brave/Firefox (strict tracking protection)
- • Disable third-party cookies
- • Separate "crypto" profile
Extensions:
- • Minimal—avoid unknown wallet/finance extensions
OS:
- • Keep updated
- • Enable full-disk encryption
- • Strong login/biometric
Network:
- • Reputable VPN when traveling or using public Wi-Fi
11. Quick Steps: Lock Down Your Privacy
12. Disclosures & Contacts
Legal & Documentation:
- Privacy Policy: /legal/privacyData rights, retention, partners
- Responsible Disclosure: /security/responsible-disclosurePGP key, scope
Contact:
- Security: [email protected]
- Support: [email protected]
Related Guides
Last updated: 2025-01-07