BackpulsePrivacy Policy
Last updated: July 7, 2026
1. Information we collect
We collect information you provide directly (email, name on registration), usage data (API calls, backtest history, webhook signals) and technical information (IP address, browser type, access logs). We do NOT collect or store exchange login credentials (exchange API keys are encrypted to AES-256 standard).
2. How we use information
Information is used to: provide and improve Backpulse services; account authentication and security; send service-related notifications (no marketing spam without your consent); aggregated analytics to improve the user experience.
3. Information sharing
We do not sell your personal information. Information may be shared with: third-party service providers (Lemon Squeezy for billing, MongoDB Atlas for database) under appropriate data processing agreements; law enforcement when required by valid legal process.
4. Data security
We apply industry-standard security: HTTPS/TLS for all connections; AES-256 encryption for exchange API keys; HMAC-SHA256 authentication for webhooks; bcrypt for passwords. However, no system is completely secure.
5. Cookies and tracking
We use session cookies necessary for authentication. We do not use advertising tracking cookies. You can disable cookies in your browser but some features may not work.
6. Your rights
You have the right to: access your personal data; request correction or deletion; export your backtest data and signal history; cancel your account at any time. To exercise these rights, contact: [email protected].
7. Data retention
Account data is retained while the account is active. When you delete your account, personal data will be removed within 30 days. Anonymised aggregated data may be retained longer for service improvement purposes.
8. Chrome Extension — Data handling
The Backpulse Chrome Extension ("Extension") operates on TradingView.com pages and communicates with our API (api.backpulse.io). Below is a complete disclosure of data the Extension accesses, uses, stores and transmits. Data accessed: TradingView session cookies (via the cookies permission) — read-only, used solely to authenticate automated requests to TradingView when running backtests. Cookies are never forwarded to Backpulse servers and are never written or modified. TradingView page content (via the scripting and activeTab permissions) — the Extension reads strategy parameters, indicator settings and chart configuration from the TradingView DOM; only the parameters required to configure a backtest job are extracted. Data stored on your device (chrome.storage.local): Backpulse authentication token (JWT) to keep you signed in. Extension settings (selected exchange, webhook preferences, optimisation configuration) — this data does not leave your device unless you explicitly submit it as part of a job. Data transmitted to Backpulse servers (api.backpulse.io): Backtest job configuration (symbol, timeframe, strategy parameters) when you start an optimisation run. Webhook configuration when you save it. Authentication credentials (email/password) when you sign in via the popup. Data NOT collected by the Extension: Browsing history on any site other than TradingView.com. TradingView session cookies are not forwarded to our servers. Financial data, balances or positions from exchanges. Any personal information beyond what you explicitly enter. Third-party access: No extension data is shared with third parties beyond what is described under Section 3 (Information sharing) above.
9. Contact
If you have questions about this privacy policy, contact: [email protected] or via the Contact page. We respond within 72 hours.