Privacy

Onchain activity is public

Transactions, balances, and contract events are recorded on public blockchains. We do not control blockchain data and cannot delete or change it.

Offchain data we process

• Session cookies for Sign-In With Ethereum (SIWE) when you use authenticated features (e.g., posting to chat or redeeming referrals).
• Chat messages you send (room, timestamp, wallet address, and optional display name). Chat history is retained for up to 30 days.
• Moderation and abuse prevention data (bans, message deletions, and moderator action logs).
• Referrals data (referral codes and attribution events such as referrer/referred addresses and transaction hash).
• Browser storage (localStorage) for settings like Radar watches/inbox and your last connected wallet.
• Operational logs and rate limiting signals (such as IP address) used to keep the service reliable.

Telemetry minimization

• We use a minimal UI telemetry contract (ui_* events) to understand what works and to debug issues.
• We do not send raw wallet addresses, resolved names (ENS/Basename), or user-generated text (chat messages) to third-party analytics.
• All URLs, page titles, and paths are automatically scrubbed before leaving your browser: wallet addresses, shortened addresses, ENS/Basename names, and transaction hashes are replaced with safe placeholders.
• For tx lifecycle events (ui_tx_*), we may include the transaction hash (tx_hash) once available as a join key to public onchain outcomes.
• Analytics properties are intentionally low-cardinality (booleans/enums/small numbers), and we avoid unique IDs in event properties.
• All analytics traffic is routed through a first-party proxy on our servers. Your browser never contacts PostHog directly, and we do not forward your IP address.
• If enabled, sanitized ui_* events are processed by PostHog Cloud for product analytics, web analytics, and feature flags (and PostHog AI may use third-party LLM providers for analysis).
• Session replay may be enabled to record anonymized page interactions. All visible text and form inputs are masked before recordings are sent. Network request and response recording is disabled to prevent sensitive data from being captured.

Data retention

• SIWE session cookies expire quickly (minutes to hours; max 24h). We do not store SIWE signatures.
• Chat messages are retained for up to 30 days.
• Abuse prevention signals (rate limits, bans) are kept for ~7 days (max 30 days).
• Push notification subscriptions are removed on unsubscribe and cleaned up after ~180 days of inactivity.
• Operational logs (errors, latency, endpoints) are retained for ~14 days.
• If enabled, UI analytics events are retained for up to ~90 days.
• Error reports, performance traces, and error-session replays sent to Sentry Cloud are retained per Sentry Cloud plan settings (default up to ~90 days).

No sale of personal data

We do not sell personal data and we do not use it for third-party advertising.

Third-party infrastructure

• Cloudflare (hosting, Workers, and DDoS protection) may process network metadata such as IP address and user agent.
• Wallet providers and RPC endpoints process requests needed to read chain data and submit transactions.
• Indexing services and block explorers you use (e.g., when you open a tx link) have their own privacy practices.
• When you connect via a QR code (mobile wallet), your browser contacts WalletConnect/Reown relays (e.g., relay.walletconnect.com, pulse.walletconnect.com) to establish the pairing.
• If you opt in to push notifications, your browser creates a subscription with your browser vendor's push service (Firebase Cloud Messaging for Chrome/Edge, Apple Push Notification service for Safari, Mozilla autopush for Firefox). The push endpoint URL identifies that service and is stored so we can deliver alerts.
• The contact form loads Cloudflare Turnstile (challenges.cloudflare.com) to distinguish humans from bots. Turnstile may process device signals; the verification token is sent to our server and to Cloudflare for validation.
• Contact form submissions are delivered to our support inbox via Resend (resend.com). The message body and any reply-to email you provide are sent to Resend as part of email delivery.
• When chat AI moderation is enabled, chat message text is screened by the OpenAI Moderation API (api.openai.com) before being persisted. Only the message text is sent (no wallet address, room id, or other identifiers). Flagged messages and their category scores are stored in our moderation audit log.
• If enabled, PostHog Cloud receives sanitized ui_* telemetry for analytics, web analytics (traffic and referrers), feature flags, and session replay recordings with all visible text and inputs masked. Analytics traffic is routed through our own servers (first-party proxy) so your browser never contacts PostHog directly. We do not forward your IP address to PostHog. Wallet addresses, shortened addresses, ENS/Basename names, and transaction hashes are automatically stripped from URLs, page titles, and paths before any data leaves your browser. For tx lifecycle telemetry (ui_tx_*), we may include the transaction hash (tx_hash) once available as a join key to onchain outcomes. PostHog AI may use third-party LLM providers for analysis of anonymized telemetry.
• Sentry Cloud (error reporting and performance tracing) receives exception events, stack traces, breadcrumbs, browser and device metadata, and transaction timings. If you have accepted analytics consent and your session hits an error, a session replay of that session with all visible text and form inputs masked may also be sent to Sentry. Error-reporting traffic is routed through a first-party proxy on our servers (path /se/) so your browser never contacts Sentry directly, and we do not forward your IP address or cookies to Sentry. Wallet-address-shaped strings in breadcrumb data are replaced with a placeholder before leaving your browser. Exception capture and performance tracing are not gated by analytics consent so crashes can be fixed even if you opt out of analytics; error-session replay is gated by analytics consent and is stopped if you opt out.
• Typography assets are served from this origin. Your browser does not contact Google Fonts.

Changes

We may update this notice. If we make changes, we will update the date at the top of this page.