WalletConnect Pulse analytics on initialization without user consent (GDPR issue)

[TimDaub]

Issue

WalletConnect sends analytics requests to Pulse on connector initialization, before users interact with the wallet connection UI.

Tracking Observed

• WalletConnect Pulse: pulse.walletconnect.org/e?projectId=...
• Payload tracking wallet initialization
• This happens before any user clicks "Connect Wallet"

Note: Tracking after user initiates wallet connection would be acceptable, but tracking before any user interaction violates GDPR consent requirements.

Problem

• GDPR requires consent before tracking
• Users are tracked even if they never connect a wallet
• No documented way to disable Pulse analytics

Request

1. Defer Pulse analytics until user actually initiates wallet connection
2. Add option to disable Pulse tracking
3. Document the analytics integration and data collection

[linear[bot]]

APKT-4187