QUANTPULSE

Privacy Policy

Last updated: October 2026

This policy explains what personal data QuantPulse ("we") processes when you use the QuantPulse platform, why, and what rights you have under the EU General Data Protection Regulation (GDPR). We are the data controller.

1. Data we process

Data	Why	Legal basis
Name, nickname, email, password (stored only as a hash), two-factor authentication secret	Your account, login, security emails	Contract (Art. 6(1)(b))
Login history: IP address, time, device / new-device checks	Account security, fraud and abuse prevention	Legitimate interest (Art. 6(1)(f))
Exchange API keys you add (read-only)	Showing your balances / positions and checking which pairs your account can trade. Keys are stored encrypted and are never shown to administrators.	Contract
Trading journal, positions, favourites, calculator and scanner settings, alerts	The features you use. Your trades, capital, amounts, P&L and percentages are private — nobody else sees them, not even administrators.	Contract
Telegram chat ID / bot settings (only if you connect Telegram)	Sending the alerts you switched on	Consent — you can disconnect any time
Academy progress, quiz results, XP; nickname on the leaderboard (only if you opt in)	Learning features and the leaderboard	Contract / consent for the leaderboard
Subscription and payment records: plan, amount, date, payment reference	Providing the paid service, accounting and tax obligations	Contract, legal obligation (Art. 6(1)(c))
Messages you send us (feedback, contact form)	Answering you	Legitimate interest

We never receive your card details — card payments are handled entirely by Stripe, crypto payments by NOWPayments.

2. Who receives data (processors)

Hosting — Hostinger: servers and database.
Stripe (card payments) and NOWPayments (crypto payments) — only when you pay; they process the payment under their own privacy policies.
Telegram — only if you connect it, to deliver your alerts.
Crypto exchanges (e.g. Binance, Bybit, MEXC) — your API keys are used only to call the exchange you added them for.
Email delivery — our mail provider, for account and subscription emails.
Embedded content — charts (TradingView), lesson videos (YouTube in privacy-enhanced mode) and the optional page translation (Google Translate) load from those providers when you open them; they can see your IP address.

Some of these providers are located outside the EU/EEA; transfers rely on the European Commission's adequacy decisions or Standard Contractual Clauses. We do not sell your data and do not use it for advertising.

3. How long we keep it

Account data — while your account exists. You can delete your account yourself in My Account; your data is then erased, except records we must keep by law.
Inactive accounts — after 6 months without login we email you; if you do not log in within the next 6 months, the account is deleted automatically.
Payment and invoice records — as long as accounting and tax law requires (in Lithuania generally up to 10 years).
Login history and security logs — as long as needed for account security, and deleted together with the account.

4. Cookies and local storage

We use only strictly necessary cookies: the session cookie that keeps you logged in and the CSRF security token. Your interface preferences (open tabs, filters, chart settings) are stored in your browser's local storage and never leave your device. The optional translation widget sets a "googtrans" cookie only when you choose a language. We do not use analytics or advertising cookies.

5. Your rights

You can ask us to access, correct, delete, restrict or export your data, object to processing based on legitimate interest, and withdraw consent at any time (e.g. disconnect Telegram, leave the leaderboard). Write to us via the contact form or Telegram; we answer within one month. You can also complain to the supervisory authority — in Lithuania the State Data Protection Inspectorate (vdai.lrv.lt) — or the authority of your EU country.

6. Security

Passwords are hashed, API keys are encrypted, the site runs over HTTPS, and two-factor authentication is available. Please use read-only API keys — QuantPulse never needs trading or withdrawal permissions.

7. Changes

If this policy changes in a material way, we will show a notice in the app or email you.

Service provider

QuantPulse
Telegram: @quantpulse_community