Privacy policy

Last updated: 15 October 2026. This policy covers lpsignal.app, its API (api.lpsignal.app), the Telegram bot and the LPSignal browser extension. Questions: support@lpsignal.app.

What we collect

Wallet features

Signing in and connecting a wallet use Reown (WalletConnect) AppKit: the site loads Reown’s wallet list in the background, also before you sign in, so Reown receives your IP address; a WalletConnect session is relayed through Reown, and the wallet you pick may contact its own provider (for example Coinbase Wallet). Adding or removing liquidity and swapping run in your browser: they read public blockchain nodes and ask the KyberSwap aggregator for quotes, which see your wallet address and IP address. Transactions are signed in your wallet and sent from it; the pending state that prevents duplicate transactions is kept in your browser.

Browser extension

The extension talks only to api.lpsignal.app. Without an API key it reads public signals anonymously and sends nothing that identifies you. If you paste an API key, it is stored in your browser (chrome.storage) and sent only to api.lpsignal.app to check your plan and receive your signals. Notification settings and the list of signals already shown stay in your browser. The extension has no access to the pages you visit and collects no browsing history.

AI apps (MCP)

When you connect an AI app (Claude, ChatGPT, Cursor and others) to your account through our MCP server, you sign in on lpsignal.app and approve it. We keep the app's name, its identifier and return address, what you approved and when, and when it last used the connection; its access and refresh tokens are stored only as hashes. An app that identifies itself by a web address (a client metadata document) has that document fetched by our server. The app can read what your account sees and nothing more; disconnect it on your account page. Records of a disconnected or expired connection are deleted 30 days later. The public MCP endpoint needs no sign-in and stores nothing about you beyond the request logs above.

How we use it

To run the service: sign you in, deliver signals by Telegram, webhook, WebSocket and the extension, bill your plan, prevent abuse, and understand which pages are used. We do not sell personal data and show no ads.

Who processes it

Stripe (card payments), Binance (receiving crypto payments), Google (Analytics, web fonts, the support mailbox), Reown (wallet sign-in and connection), Resend (support email replies), Telegram (delivering bot messages), Cloudflare (DNS and email routing), Hostinger (our server) and SoloWeave (its listing badge in the footer is loaded from soloweave.com, which sees your IP address). Each receives only what its part needs.

Retention and your choices

Account data is kept while your account exists. You can replace your API key and remove your webhook on your account page. To delete your account, or to ask what we hold about you, email support@lpsignal.app; we delete or anonymise it, except records we must keep for accounting. You can block analytics cookies in your browser.

Changes

We will update this page when what we collect changes; the date above says when it last did.