Frequently asked questions

WhaleTracker is a crypto futures analytics workspace: funding, open interest, liquidations, long/short, on-chain whale flows, signals, and tools like watchlist and trade journal. It is built for traders who want derivatives and flow context in one place.

No. Nothing here is investment, tax, or legal advice. Markets are risky; past backtests or signals do not guarantee future results. You are responsible for your own decisions.

Active crypto traders and analysts who use Binance-style perp data and optional on-chain context. Beginners can explore Free areas; Pro/Elite unlock deeper screens and Telegram digest features as described on Pricing.

Most futures metrics (prices, funding, OI, liquidations, etc.) are sourced from public exchange APIs (e.g. Binance Futures). On-chain sections use public chain data and heuristics; labels may be incomplete.

Rounding, timing, index vs last price, excluded symbols, or API cache can differ slightly. Use WhaleTracker as one lens, not the only source of truth.

No. Signals and strategies are models. They can lag, fail in new regimes, or miss fees and slippage. Always verify and size positions yourself.

Free covers core browsing with limits (see Pricing). Pro unlocks deeper history, more screens, and Telegram digest. Elite is for the highest tier features and roadmap items (some still marked “soon” in the UI).

Open Pricing in the sidebar and follow the flow shown there. In this kit, plan toggles may also exist under Account for demo purposes.

Refund rules depend on where you purchase (Stripe, App Store, etc.). Check the checkout page and terms at purchase time. This FAQ cannot override merchant policy.

In this application kit, account/demo data is stored in your browser (localStorage) unless you connect a real auth backend. Do not rely on browser storage as a secure vault for secrets.

WhaleTracker does not sell your alert preferences or Telegram settings for advertising. Chat IDs used for Telegram delivery are only used to send messages you request.

Never share API keys, seed phrases, or your Telegram bot token. The app only needs your numeric Chat ID to send alerts to you, not your private keys.

Telegram’s model is one bot per project. Each user has a private chat ID with that bot. The server sends to your ID only; you do not need a separate bot per customer.

“Digest now” sends one snapshot. Turn on auto-push on the Telegram alerts page: while the tab stays open, the server fingerprints your selected modules and sends Telegram when that data changes (signals, whales, market, etc.). For delivery without a browser, use server cron: GET /api/cron/telegram-digest with CRON_SECRET and TELEGRAM_CRON_CHAT_ID.

Some blocks need a public app URL on the server (NEXT_PUBLIC_APP_URL or Vercel). Others need external APIs. The digest tells you when a section was skipped or empty.

Optional hours in local browser time. If enabled, the app asks for confirmation before a manual digest, and automatic sends are skipped during that window.

“Digest now” is a snapshot at the moment the server builds the message — not a live ticker. Numbers refresh when you send again. There is no per-second stream inside that single Telegram message.

For manual “Digest now”, yes, when you click. For browser auto-push, keep the tab open. For 24/7 scheduled digests without a tab, configure cron on your server (see Telegram page help).

There is no fixed public SLA on every minute of data. The product evolves by continuous deployment: fixes and features land when they are ready. Watch your host’s changelog if you self-deploy.

TELEGRAM_BOT_TOKEN, a reachable HTTPS deployment, and usually NEXT_PUBLIC_APP_URL (or Vercel) so server-side digest code can call your own APIs (macro, sentiment, derivatives). Local dev can use a localhost fallback for those internal fetches.

The UI supports Russian, English, and Simplified Chinese where translated. Some pages or API labels may still be partially English.

Roadmap items ship as they are implemented. Watch release notes or Pricing for the latest. The UI shows what is already in the digest vs planned.

Check this FAQ, Pricing, Settings, and Telegram alerts help blocks. For production support channels (email, Discord), use whatever your deployment provides.