A Blue Guardian trader says a $5,000 account was marked breached even though the losses visible to them appeared to remain below the account’s $200 daily drawdown allowance, raising a narrower question about whether the firm can document the precise equity level that triggered its automated risk system.
The October 5 Trustpilot reviewer said they were trading a Blue Guardian 1-Step Standard account with a 4% maximum daily drawdown. According to the trader, an open position initially showed approximately $120 in losses because of the spread, later reached around $140 in negative floating P&L and incurred roughly $40 in commission before the account was marked breached.
The trader said their trade history showed total losses below $200 and repeatedly asked Blue Guardian for the exact equity value and timestamp at which the account crossed its drawdown threshold.
According to the complaint, support explained that the breach was calculated from equity but did not provide those two figures. The reviewer said they were initially promised an update within five minutes before support stopped responding and claimed to have screenshots and trade history documenting the case.
The allegation remains unverified. Dave Finances has not seen the screenshots, complete trading statement or Blue Guardian’s server logs, and the customer’s visible losses alone are not enough to establish that the account was incorrectly breached.
Blue Guardian’s $200 Limit Is Not Necessarily a Static $4,800 Floor
Blue Guardian’s published 1-Step Standard rules confirm that the maximum daily loss is 4% of the initial account balance.
On a $5,000 account, that fixed allowance is $200.
But the firm’s calculation has another component that is critical to this dispute.
At the daily reset, which Blue Guardian sets at 5 p.m. EST, the firm takes whichever is higher: the account balance or account equity. It then subtracts 4% of the initial balance from that figure to establish the new day’s breach level.
That means the relevant question is not simply whether the trader lost more than $200 from $5,000.
If the account had higher balance or equity at the previous reset, the breach floor could have been above $4,800. An open profitable position at the reset can also raise the starting equity used for the next day’s calculation even if that floating profit subsequently disappears.
Without the account’s balance and equity at the reset, the trader’s approximate $140 floating loss plus $40 commission cannot prove that the breach was mathematically impossible.
A Simple Server Log Could Resolve the Core Dispute
That is also what makes the case unusually testable.
Blue Guardian should have the data required to reconstruct an automated equity breach: the daily reference equity or balance, the resulting drawdown threshold, the lowest recorded account equity and the server timestamp at which that equity crossed the threshold.
The trader is not disputing that equity matters. The complaint is that those underlying figures have allegedly not been provided.
If Blue Guardian’s logs show, for example, that the reset reference was $5,100, the daily floor would be $4,900 rather than $4,800. An account could then breach despite remaining well above a $200 loss relative to the original $5,000 balance.
Alternatively, the server may have recorded a brief intraday equity drop that the trader did not see on screen. Spreads can widen, floating P&L can change between interface refreshes and commissions can affect account equity even when the closed-trade history appears to show a smaller loss.
But either explanation should produce a specific number and timestamp.
That distinction resembles a recent Propr dispute involving alleged platform lag and missing or incorrect trades, where reconstructing server-side events was more useful than relying solely on what a trader remembered seeing on screen.
The Visible Trade History May Not Equal the Lowest Intraday Equity
One source of confusion in prop-firm disputes is the difference between closed P&L and equity.
Trade history typically provides a clear record of completed trades, commissions and realized results. An equity-based drawdown system can also react to unrealized losses while positions remain open.
That means an account may technically cross a threshold for seconds and later recover before the trade closes.
Blue Guardian’s rules explicitly say account equity is relevant to its daily-loss calculation, while its overall drawdown rules also incorporate unrealized positions.
For this reason, the trader’s statement that trade-history losses remained below $200 is useful but not conclusive.
The stronger evidence would be an equity curve or server log showing the minimum equity reached during the position.
Other Traders Have Recently Asked Blue Guardian for Similar Execution Data
The October 5 allegation does not by itself demonstrate a systemic problem, but it is not the only recent review centered on missing underlying data.
A September 30 reviewer disputed a stop-loss execution and said Blue Guardian explained that rollover could widen spreads but did not provide the requested Bid/Ask tick data showing that the stop price was actually reached.
Another August reviewer described a $100,000 Instant Standard account where Blue Guardian reportedly identified an equity floor of $102,417.66 and a lowest equity of $102,414.80 — a breach of only $2.86. That reviewer did not dispute those figures but said the firm’s stated equity decline was $206 larger than the losses they could reconcile from the trading journal.
Those complaints are also unverified and involve different account structures. They cannot be combined into proof that Blue Guardian calculates drawdown incorrectly.
They do, however, point to the same evidentiary issue: traders asking for the underlying data behind automated breach decisions.
Automated Risk Rules Make Small Data Differences Expensive
Prop-firm accounts create unusually high consequences around small intraday movements because crossing a loss threshold can destroy the value of an otherwise profitable account.
A conventional brokerage customer who briefly exceeds an intended risk level generally suffers the additional trading loss. A prop trader may also lose the account itself and, depending on the firm’s rules, future access to accumulated simulated profits.
That makes the audit trail behind a breach commercially important.
Dave Finances has seen the same dynamic when firms enforce other automated or technical controls. FundingPips device-ID enforcement raised questions about what technical evidence supported account closures, while a Trade the Pool trader challenged a $50,000 payout denial after trades were reassessed during a later review.
In each case, the existence of a rule was only the first question. The second was whether the firm could show how the rule applied to the customer’s actual account data.
Guardian Shield Adds Another Layer, but It May Not Apply Here
Blue Guardian also operates a separate risk-control system called Guardian Shield on funded accounts.
For the 1-Step Standard model, the firm’s current rules say Guardian Shield generally closes open positions once floating P&L reaches a 2% loss. The first trigger reduces the trader’s profit split to 50%, while a second trigger permanently breaches the account.
That mechanism should not automatically be confused with the 4% daily-loss rule involved in the October 5 complaint.
The review identifies a 1-Step Standard account and says the trader was told the breach was based on equity, but it does not provide enough information to establish whether the account was still in evaluation or funded, or whether Guardian Shield had any role.
Separating those mechanisms is important because Blue Guardian currently offers several account types with different daily drawdown, maximum drawdown and Guardian Shield structures.
Five Numbers Would Determine Whether the Account Should Have Survived
The case does not require speculation about whether Blue Guardian’s rules are fair. It requires a small set of account-level records.
The account type and size are now known: 1-Step Standard and $5,000. That establishes a nominal daily-loss allowance of $200.
The remaining critical figures are the balance and equity at the 5 p.m. EST reset, the resulting daily breach threshold, the lowest server-recorded equity and the timestamp at which that low occurred.
If Blue Guardian provides those figures and they reconcile with its published formula, the trader’s argument based on approximately $180 in visible losses becomes much weaker.
If the firm’s own logs never show equity falling through the calculated threshold, the complaint becomes considerably more serious.
And if the records show a momentary breach caused by spread or another price-feed movement, the next question becomes whether Blue Guardian can provide the tick data supporting that equity calculation.
For now, the October 5 report is still a single unverified customer complaint.
But unlike many broad prop-firm accusations, this one has a relatively simple evidentiary endpoint. Blue Guardian does not need to disclose an internal risk model or reveal a proprietary algorithm.
It needs to show the number that breached the account, the number it was not allowed to cross and the moment the crossing occurred.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape.