Security and Data Handling
Your trading history should be reviewable without exposing execution access. Map.Trade is import-first by design — the product simply can’t do anything dangerous with your account.
- No broker password
- No trade execution
- EU data residency
Map.Trade does not provide buy/sell signals, execute trades, or manage funds. It helps traders review historical performance, risk, and behavior.
The strongest security model is the one where the product has no power to harm you. Map.Trade reads the history you upload — it never trades, never holds funds, and never asks for a broker password.
Our security commitments
We never ask for broker or trading-account passwords. You upload read-only files.
Everything is built from files you choose to upload — no live brokerage connection.
The product cannot place, modify, or close trades. There is no execution path.
We do not hold, move, or manage money. No custody, no withdrawals.
Your imported history defaults to the EU region.
Access uses short-lived tokens with rotating refresh tokens.
Data handling
Account access
What we’ll never do
Frequently asked questions
Do you need my broker password?
No. Map.Trade is import-first — you upload read-only files. We never request broker or account passwords and never place trades.
Can the product trade on my behalf?
No. There is no execution capability at all — it cannot place, modify, or close trades.
Where is my data stored?
The default data-residency region is the EU. Full processing details are being finalised during the private alpha.
How is my login secured?
Sessions use short-lived access tokens with rotating refresh tokens; further hardening is being rolled out toward general availability.
Related pages
Ready to review before you trade again?
Map.Trade does not provide buy/sell signals, execute trades, or manage funds. It helps traders review historical performance, risk, and behavior.