*** THE POLICY NO PROP FIRM PUBLISHES. SO WE DID. ***
Fair play, in writing.
The industry's open wound is the unexplained ban: "suspicious activity," a locked account, silence. Here is exactly how every breach and payout decision works at LikeFunded β who reviews, what you see, how fast, and how you appeal. Screenshot it; it's binding.
01 / THE FLOW β EVERY DECISION TAKES THIS PATH
Trigger to verdict in 5 steps
01
Trigger
A system flag against a numbered rule β never a vibe. The flag itself is logged.
β
02
Human review
A named risk reviewer examines the trades. Software flags; only humans decide.
β
03
Evidence shared
You get what we see: the trades, timestamps, and the rule β before any verdict lands.
β
04
Written verdict β€48h
Reason-coded: the numbered rule + the triggering data. Never just "suspicious activity."
β
05
7-day appeal
Reviewed by a different person than the first verdict. Their decision is final β and published in the stats.
while a review is open your account is paused, not terminated Β· reviews cannot exceed 48h without an interim written update
02 / REASON CODES β NO VAGUE CATCH-ALLS
Every verdict cites a number
"Gambling" and "coordination" can't be rubber stamps. Each code maps to a rulebook section with concrete examples β if your verdict cites a code, you can read exactly what it means.
CODE
RULE
CONCRETE EXAMPLE
WHAT YOU'RE SHOWN
FP-101
Daily loss limit (Rule 4)
Closed P&L crossed β5% of starting balance at 14:32 server time.
The breaching trade + equity curve.
FP-204
Copier scope (Rule 9)
Trades mirrored from an account you don't own β not lag on your own copier, which is fine to 2s.
The matched order pairs + account list.
FP-301
Feed exploit (Rule 11)
Systematic entries inside stale-quote windows β latency arbitrage, not fast trading.
Tick data for the flagged entries.
FP-402
Cross-trader hedging (Rule 10)
Opposite positions coordinated across different traders' accounts to farm one guaranteed win.