Privacy Policy
Version 2026-09-22 (rev. 4)
1. Who is responsible
The controller is the operator of quantprop.app named in the Legal Notice ("QuantProp", "we"). For every question about your data, and to exercise your rights, write to info@quantprop.app. We have not appointed a data protection officer.
2. The short version
- We use no tracking, no analytics, no advertising cookies and no social-media plugins. We set one cookie, and only when you log in (section 4).
- We never see your card data (that stays with Stripe) or your ID document and selfie (that stays with Sumsub). We only receive the result.
- Your IBAN and your trading-platform credentials are stored encrypted.
- Other traders only ever see the display name you choose — or a pseudonym — never your e-mail address, real name, balances or results (section 6).
- You can download everything we store about you and delete your account yourself in Settings (section 11).
- Our servers and database run in Frankfurt (EU). Some of our service providers are US companies (section 9).
3. What we process, why, and for how long
| Data | Purpose | Legal basis (GDPR) | How long |
|---|---|---|---|
| E-mail address, password (stored as a hash), time of e-mail confirmation, your display name, your "hide me" setting, the cosmetics you have equipped, your profile picture if you upload one | your user account and login; display to other traders (section 6) | Art. 6 (1) b | until you delete your account; unconfirmed sign-ups are deleted after 7 days |
| Confirmation and password-reset links: only a hash of the link, its expiry | security of your account | Art. 6 (1) b, f | 24 hours (confirmation) or 30 minutes (reset), then deleted |
| Name for certificates ("certificate name") | certificates; matching the holder of your payout account | Art. 6 (1) b | until account deletion |
| Orders: plan, amount, discount code or voucher, payment reference, status, refund or chargeback, and a copy of the Terms version and the plan rules that applied when you bought | contract, bookkeeping | Art. 6 (1) b, c | 10 years (German commercial and tax law, § 257 HGB, § 147 AO) — kept without personal reference after account deletion |
| Consent records: time, text version, IP address and browser identifier when you tick the mandatory boxes at checkout, when you move an account to Funded, and before an identity check | proof that you consented; defence against unjustified chargebacks (section 7) | Art. 6 (1) b, f | with the order, account or check they belong to |
| Trading accounts and trading data: account ID, plan, phase, status, balances and rule status; simulated fills (symbol, side, quantity, price, profit or loss, time); daily closes | providing the service, evaluating the rules, calculating payouts, checking for prohibited practices | Art. 6 (1) b, f | with the account; afterwards only without personal reference |
| Trading-platform credentials (encrypted) | your access to the simulation platform | Art. 6 (1) b | until account deletion |
| Journal notes on your trades, your daily goal | quests and your own analysis; visible only to you (and to us in a support case) | Art. 6 (1) b | until account deletion |
| Season and league data: XP ledger, quest progress, QuantPass rewards and reset vouchers, Shield, your daily Trader Score values, league group and weekly results, team membership, weekly reports | Season, leagues, teams, weekly report (section 6) | Art. 6 (1) b; comparison with other traders Art. 6 (1) f | until account deletion; claimed rewards and used vouchers are kept as proof together with the orders they belong to |
| Payout details: account holder, IBAN (encrypted — we display only the last four digits), PayPal address; your self-declaration whether you receive payouts as a private individual or as a business, and your VAT ID if you give one | payouts; our bookkeeping and tax records (we do not assess your tax situation) | Art. 6 (1) b, c | until account deletion; the destination of paid payouts and the self-declaration are kept 10 years as a payment record |
| Payouts: amount, method, status, reference, the rules and payout policy version that applied to the request, and our internal review note when a payout is approved | contract, bookkeeping, fraud prevention | Art. 6 (1) b, c, f | paid payouts 10 years; for unpaid ones the destination is removed when you delete your account |
| Payout pause after a chargeback: the date until which payouts from your other accounts are paused (at most 180 days; lifted automatically when the dispute is closed) | fraud prevention (Terms, section 19) | Art. 6 (1) f | until the pause ends |
| Identity check: provider, status (pending, passed, failed), timestamps, the provider's case number, whether the name matched your certificate name | preventing fraud and payouts to the wrong person | Art. 6 (1) b, f; for the biometric part your explicit consent, Art. 9 (2) a (section 8) | until account deletion |
| If you are a partner with a creator code: the code bound to your account, commissions, partner payout requests | contract, bookkeeping | Art. 6 (1) b, c | with the payment records, 10 years |
| E-mail log: type of e-mail, status, time — never the content | delivery and proof | Art. 6 (1) b, f | until account deletion |
| Support cases and automatic rule-check notices, including our internal handling notes | support; enforcing the trading rules after hearing you (Terms, section 12.2) | Art. 6 (1) b, f | until account deletion |
| Security data: IP address when you reveal your platform credentials; rate-limit counters stored only as hashes (no plain IP address or e-mail) | security, abuse prevention | Art. 6 (1) f | IP address until account deletion; counters only for the duration of the limit window |
| Server logs of our hosting provider (IP address, time, requested page, status) | operation and security | Art. 6 (1) f | for a limited period set by the hosting provider |
| Deletion requests: time, status, reason for a hold | proof that we honoured your rights | Art. 6 (1) c | permanently, without personal reference after deletion |
| Staff audit log in our administration system: which staff member did what and when, with your user ID | accountability, fraud prevention | Art. 6 (1) c, f | permanently and unchangeable; contains no names or bank details |
We do not use your data for advertising and we do not sell it. There is no newsletter. We only send e-mails that belong to your contract (confirmation, account ready, breach, passed, payouts, security notices, deletion) and — if you leave it switched on — the weekly report (section 6).
4. Cookies and third-party content
We set one cookie: `__Host-quantprop.session`, your login session (HttpOnly, Secure, SameSite=Lax, valid for 7 days and renewed while you are active). It is strictly necessary for the login, so we do not show a consent banner (§ 25 (2) TDDDG). Our font is served from our own server. No third-party content is loaded on our public pages.
At checkout you are redirected to Stripe's payment page (section 7). During the identity check, Sumsub's verification component is loaded in your browser (section 8). Both set their own cookies under their own responsibility.
5. Automated decisions
Whether an account passes or is breached is decided automatically from the trading data, according to the published rules. This is necessary to perform the contract (Art. 22 (2) a GDPR). You can ask us to have a person review any such decision: info@quantprop.app.
Once a day we automatically check trading data for signs of prohibited practices (very short holding times, opposite positions across your own accounts, signs of automated trading, inactivity, the number of Funded accounts). A match only creates an internal notice. A person decides on any consequence, after hearing you (Terms, section 12.2). The Trader Score, leagues and teams have no effect on rules, payouts or prices.
6. Leagues, teams, Trader Score and weekly report
What other traders see. In leagues, teams and rankings other traders see only: the display name you set in Settings ("Name displayed on leaderboards and public events") or, if you have not set one, a pseudonym such as `trader_ab12`; your profile picture, if you have uploaded one; the cosmetics you have equipped; your rank, your Trader Score and its components; your league; and your team's name. Never visible to others: your e-mail address, real name, certificate name, balances, profits or losses, or account numbers. If you choose "Hide me" in Settings you appear everywhere as "Anonymous trader" without cosmetics and without your profile picture; your rank and score remain in the table so that the other traders' results stay verifiable. Legal basis: Art. 6 (1) b (the leagues are part of the service) and Art. 6 (1) f (comparative ranking); "Hide me" is how you object.
Trader Score. From the trades on your own simulated accounts we calculate a score (risk, profit, consistency, discipline) and store one value per trading day. League groups are drawn every Monday from all traders with an active account; a team's score is the average of its members' scores.
Journal notes and daily goal are visible only to you (and to us in a support case). Quests evaluate whether a note exists and how long it is — not what it says.
Weekly report. After a week in which you traded, we send a summary of your trading week by e-mail on Saturday. You can switch it off on the Analysis page, or with the unsubscribe link in every report e-mail (one click, no login). The report itself stays in your dashboard.
Certificates. If you share the link to one of your certificates, anyone with the link can see the certificate: your certificate name, type, account, date and — for payout certificates — the amount.
7. Payment (Stripe)
Payments are processed by Stripe Payments Europe, Limited, Ireland. You enter your payment data on Stripe's page; we never receive your card number. We receive the result, the amount, the payment method and a payment reference. Stripe acts partly as our processor and partly as an independent controller (fraud prevention, regulatory duties) and processes data worldwide (section 9). Stripe's privacy policy: https://stripe.com/privacy. Legal basis: Art. 6 (1) b; fraud prevention Art. 6 (1) f.
If a payment is charged back, we compile evidence that you ordered, consented and received the service and store it with Stripe: your e-mail address, the order and its consent record (time, text version, IP address, browser), when the account was provided and used (number and dates of trades, e-mails we sent you) and payouts we paid you. Whether it is submitted to your bank or card issuer is decided by a person. Legal basis: Art. 6 (1) f (defence of legal claims).
8. Identity check (Sumsub)
Before the first payout from an account we verify your identity once, through our provider Sumsub (https://sumsub.com/privacy-notice-service/). Your ID document and a selfie with liveness check go directly from your browser to Sumsub; we never receive or store the images. We receive the result (passed or failed), a case number and whether the name on the document matches your certificate name. Sumsub knows your case only under a random check ID — we do not pass your e-mail address or name to Sumsub.
The selfie comparison uses biometric data. Before the check starts you give your explicit consent in a separate checkbox (Art. 9 (2) a GDPR); we record the time, the text version, your IP address and browser. You can withdraw the consent at any time with effect for the future by writing to us; without the check we cannot pay out. Sumsub processes the data in the EU; where its sub-processors are outside the EU, standard contractual clauses apply. When you delete your account we also have your case deleted at Sumsub.
9. Service providers and transfers outside the EU
| Provider | Role | Where the data is | Safeguard for third countries |
|---|---|---|---|
| Vercel Inc., USA | hosting of the website and app, server logs | our functions run in Frankfurt; logs and edge network may be processed outside the EU | EU-US Data Privacy Framework (as stated by the provider), standard contractual clauses |
| Databricks, Inc. (Neon), USA | database | Frankfurt (AWS eu-central-1) | Data Privacy Framework (as stated), standard contractual clauses |
| Stripe Payments Europe, Limited, Ireland | payments, chargeback evidence | worldwide | Data Privacy Framework, standard contractual clauses |
| Plus Five Five, Inc. (Resend), USA | sending our e-mails | USA (your e-mail address, e-mail metadata and delivery logs) | standard contractual clauses |
| Sumsub | identity check | EU | standard contractual clauses / Data Privacy Framework for sub-processors |
| Cloudflare, Inc., USA | DNS and domain only — no traffic passes through Cloudflare | worldwide | Data Privacy Framework (as stated), standard contractual clauses |
| Heinlein Hosting GmbH (mailbox.org), Germany | our mailbox info@quantprop.app | Berlin | — |
| Simulation platform (Tradovate or Rithmic, USA) | the simulated trading account itself: it receives the data needed to create your account and login, which can include your e-mail address and name | USA | standard contractual clauses |
We have data-processing agreements with our processors (Art. 28 GDPR) and disclose the recipients of chargeback evidence in section 7.
10. Discord
Our community and support run on a Discord server. Joining is voluntary. Discord Netherlands B.V. is the controller for the platform (https://discord.com/privacy); data is also processed in the USA. We see what you post there and your Discord name. Please never post ID documents, passwords, bank details or order numbers on Discord — for anything about your account write to info@quantprop.app. Legal basis for our support and moderation there: Art. 6 (1) b, f.
11. Your rights — and how to use them right now
- Access and portability (Art. 15, 20). Settings → Privacy → "Download my data" gives you a JSON file with everything we store about you, immediately, including our internal handling notes on your support cases and payout reviews, your consent records and the rules that applied to each purchase. Not included: your password hash, encrypted values and the provider's internal IDs.
- Rectification (Art. 16). E-mail address, display name and certificate name in Settings. The certificate name is locked after your first identity check — write to us to change it.
- Erasure (Art. 17). Settings → Privacy → "Delete my account". You confirm with your password. The deletion takes effect after 30 days; until then you can cancel it in Settings. We then delete your payout details, identity-check records, certificates, support cases, e-mail log, platform credentials, journal notes, weekly reports, score history, quest progress, league entries, XP, Shield, unused vouchers, display name, profile picture and cosmetics; your team membership ends (a team without members is closed and its name removed); active trading accounts are closed; and your user record is anonymised irreversibly. Paid orders and paid payouts are kept for 10 years as required by law, without your e-mail address or name attached.
- The deletion is postponed while money or a dispute is open: an open payout request; payouts paused after a chargeback; a chargeback or PayPal dispute in the last 180 days; a card payment in the last 120 days or a PayPal payment in the last 180 days (they can still be charged back, and we need the records to defend the claim — Art. 17 (3) e). As soon as the last hold has passed, the deletion runs automatically.
- Restriction and objection (Art. 18, 21), withdrawal of consent (Art. 7 (3)): info@quantprop.app. For leagues and rankings, "Hide me" in Settings is the objection.
- Complaint. You can complain to a data-protection authority, in particular the one competent for our registered office, the Bavarian State Office for Data Protection Supervision (Bayerisches Landesamt für Datenschutzaufsicht, Ansbach).
12. Security
Encrypted connections everywhere; passwords stored as bcrypt hashes; IBAN and platform credentials encrypted with a separate key; e-mail confirmation on sign-up; sessions that we can revoke on the server; rate limits on login, sign-up, reset, checkout and payouts; a strict content-security policy; changing payout details requires your password and triggers an e-mail to you; administration in a separate application behind its own login with mandatory two-factor authentication, role-based permissions, a fresh second factor for every money-related action and an unchangeable audit log.
13. Changes
We update this policy when our processing changes and show the version at the top of this page.