Privacy policy

The short version

SpikeWatch is a desktop application. Your trade history, API keys, and backtest data stay on your computer. We do not transmit your strategy code, your trades, or your exchange credentials to any server we operate.

What stays on your computer

Configured strategy parameters, your exchange API keys, the SQLite trade history database (trade_history.db), exported backtest JSONs, application logs, and your last-used window position and field values (Qt QSettings).

What we collect on this website

If you visit our website we collect anonymous, aggregated visit counts via a privacy-respecting analytics provider (no cookies, no fingerprinting). When you create a paid account we collect the email address you sign up with and, if you subscribe, the payment-processor token that lets us bill you.

What our payment processor sees

Payments are processed by a third-party PCI-compliant processor. We never see or store your card details — only a token that lets us charge you for the subscription you signed up for.

Third-party APIs the desktop app talks to

By default the application connects directly to public market-data endpoints at Binance (fapi.binance.com) and Bitget (api.bitget.com). When you enable live automation, the application uses the API keys you supplied to connect to your account at those same exchanges. Those exchanges have their own privacy policies.

Crash reports & telemetry

The desktop app does not send crash reports or telemetry to us by default. If we ever add opt-in error reporting, it will be off by default and clearly labelled.

Your data, your control

You can delete the application and everything it stored by removing the SpikeWatch folder from your home directory and (on Windows / macOS) the QSettings file maintained by the operating system. We have no copy.

Contact

Privacy questions: privacy@spikewatch.app.