Private Mode
Private Mode is the default LiqSense alert model: monitoring records persist no direct account-to-wallet relationship, while alert pull and decryption happen client-side.
What the monitoring backend can see
- Wallet address
- Chain and protocol
- Alert thresholds
- Subscription status
- Public alert encryption key
What stays in your encrypted vault
- Wallet label
- Strategy name and private notes
- Portfolio group
- Subscription read and management tokens
- Private alert decryption key
- Account-to-subscription mapping
How private alerts work
After you unlock your vault, your browser uses subscription credentials from the vault to pull encrypted alerts. LiqSense does not require your account session for private alert pull.
Private Push vs Convenience Mode
Optional Private Push (Web Push / VAPID) is part of Private Mode: a pseudonymous browser endpoint receives a content-free wake-up ping. Alert content still requires vault unlock and encrypted pull. Convenience Mode channels (Telegram, email ping) are opt-in per monitor and create an identity linkage on the server — they are never enabled by default.
Private Mode does not send Discord, SMS, WhatsApp, or Signal messages.
Removing a Convenience Mode link
Disconnecting a source removes its LiqSense server mapping. The global disconnect in the Alert Center removes every mapping for the linked email or Telegram identity. For email, LiqSense also cancels queued alert pings and erases the related Outpost recipient, message, audit, and provider-correlation records.
LiqSense cannot retract email or Telegram messages already delivered, or erase retention records controlled independently by those providers. Remove those through the provider when needed. Historical database backups may also retain a removed record until the infrastructure retention window expires. Telegram's /stopcommand also removes every Lending and LP mapping for that Telegram chat.
Aggregate product counters
LiqSense stores coarse, identifier-free totals (for example “monitor created” or “alert pulled”) so we can see whether launch funnels work. Counters never include user ids, emails, wallet addresses, or subscription tokens — see docs/PRODUCT_ANALYTICS.md in the repository.
Residual privacy risks
LiqSense application monitoring records do not persist a direct relationship between your account and your wallet addresses. Account-authenticated setup and network or infrastructure metadata may still permit correlation; this is not anonymity.
Private Mode avoids a persistent direct account-to-wallet relationship in application monitoring records, but it does not provide full anonymity. Authenticated creation requests, IP addresses, timing, infrastructure logs, browser fingerprinting, chain analytics, or user behavior may still allow correlation. Private Push adds a residual timing-correlation risk: the browser vendor's push service can observe that some LiqSense ping reached an endpoint near the time a monitored risk event occurred.