Alpha Capital Trader Alleges Retrospective Device-ID Checks Led to Account Termination

The complaint, published on Trustpilot on October 13, 2026, introduces a new dimension to a series of recent disputes involving Alpha Capital Group’s Client/Device ID (CID) monitoring. The trader claims the firm’s compliance department acknowledged using newly introduced capabilities to examine historical device relationships, potentially including records associated with inactive accounts.

The customer, identified as Lucy, also claims to have served Alpha Capital Group Limited with a 14-day Letter Before Action after an unsuccessful appeal. Neither the purported compliance correspondence nor the legal notice has been independently authenticated.

The allegation raises questions about how proprietary trading firms use historical security records to enforce account-sharing restrictions and what evidence customers can present when challenging automated compliance findings.

UK Trader Says $296.73 Profit Was Lost After CID Flag

In her October 13 review, Lucy identified the affected account as 2937201 and said she had successfully completed Alpha Capital Group’s evaluation before generating approximately $296.73 in gross simulated trading profit.

She claims the account was terminated after she requested a performance-fee payout, with the firm’s compliance system identifying an alleged shared Client/Device ID.

According to the review, the account contained 27 MetaTrader 5 trades, all executed manually from a single mobile device. Lucy provided specific examples of her position sizing, including 0.01 lots in gold, 0.18 lots in USD/CAD and 0.13 lots in EUR/USD.

The trader maintained that her position sizes were consistent and that trade durations reflected normal human decision-making rather than automated execution or account management by another person.

She said she submitted an official MT5 server trading-log export in spreadsheet format, alongside screenshots of her mobile device’s hardware settings, to support her explanation.

Lucy alleges that Alpha Capital Group declined to evaluate that material and upheld the termination.

The trading records and correspondence have not been independently examined. Furthermore, the $296.73 figure describes gross profit in the complaint, rather than a separately verified cash entitlement after any applicable performance-fee split.

Alleged Compliance Response Points to Historical Device Checks

The most significant element of Lucy’s complaint concerns the firm’s alleged explanation of how her account was identified.

She quotes purported compliance correspondence referring to newly introduced capabilities for examining “historical account and device relationships retrospectively.”

According to Lucy, the company indicated that the detected relationship could have originated from older, inactive historical logs rather than activity occurring exclusively within her current funded account.

She interpreted this as evidence that a newly implemented detection process was being applied to historical records and used to determine the status of currently active trading accounts.

That interpretation has not been confirmed by Alpha Capital Group. The publicly available complaint does not establish when the technology was introduced, which historical records were examined, or whether any newly adopted trading rules were applied retroactively.

Retrospectively analyzing existing records is also different from retroactively introducing a contractual prohibition. A firm could legitimately use improved technology to detect an older violation of a rule that was already in force.

The unresolved issue is whether the historical evidence reliably demonstrated prohibited account access in Lucy’s case.

October 12 Complaints Also Challenged Device-ID Evidence

Lucy’s review follows several similar complaints published on October 12.

A Taiwan-based reviewer, Jalen hu, alleged that Alpha Capital Group terminated a funded account when approximately $7,000 USDT in performance rewards was due. The trader disputed an accusation involving overlapping MetaQuotes device identifiers and claimed the firm would not provide the relevant CID values, timestamps or linked account details.

Another reviewer, umberto, published purported correspondence identifying three device identifiers associated with nine other user accounts. That customer acknowledged using a virtual private server, an arrangement that can complicate the interpretation of device and account relationships.

On October 13, Austrian reviewer Matthias Hemetsberger separately alleged that a $4,978.26 payout was rejected and his account terminated after Alpha Capital Group identified device connections to other customers.

These complaints have not established that Alpha Capital Group’s findings were incorrect. However, the repeated disputes resemble earlier device-ID termination complaints involving FundingPips, where traders similarly questioned how account-linking systems distinguished authorized activity from prohibited access.

Alpha Capital Group Prohibits Third-Party Account Management

Alpha Capital Group’s published trading rules prohibit account management services, group trading and unauthorized coordination between traders.

The firm’s Help Center states that accounts must be operated by the individual registered as their owner. It also restricts shared IP access and requires advance notification for certain VPN and VPS arrangements.

According to its published policies, violations can result in account termination, removal of profits and restrictions on performance-fee payments.

These controls serve a legitimate purpose. Prop firms need to prevent customers from outsourcing evaluations, sharing credentials or using coordinated trading arrangements that undermine their assessment programs.

However, Alpha Capital Group’s publicly available guidance does not clearly explain the precise CID-matching thresholds, the treatment of historical device associations or the evidence required to overturn an account-sharing finding.

A related dispute recently examined by Dave Finances involved FunderPro’s account-sharing detection process, where a trader questioned whether ordinary internet-provider connections had been interpreted as evidence of prohibited access.

Although CID matching and IP-address matching are different technical mechanisms, both require careful interpretation before an account relationship can be classified as unauthorized.

Trader Claims to Have Issued 14-Day Legal Notice

Lucy says she has formally served a 14-day Letter Before Action on Alpha Capital Group Limited, signaling an intention to pursue the dispute through legal channels if it cannot be resolved.

The claim has not been supported by a publicly authenticated copy of the notice or proof of service. There is also no verified evidence that court proceedings have been filed over this particular account.

Under the UK’s Civil Procedure Rules governing pre-action conduct, parties are generally expected to exchange relevant information and attempt to resolve disputes before litigation. A 14-day response period is ordinarily considered reasonable for straightforward claims where no specific protocol applies.

The legal significance of Lucy’s allegation therefore remains limited to a reported pre-action step, not an established court case or judicial finding against the company.

Historical Device Matching Creates a Difficult Evidence Problem

The unusual feature of this case is the alleged connection between a current payout decision and device activity that may have occurred much earlier.

There is nothing inherently wrong with reviewing historical records. A compliance system that identifies previously undetected account sharing could help a firm enforce rules that traders agreed to when registering.

But a historical device match does not automatically explain who was operating an account, whether the access was authorized or whether suspicious behavior occurred during the relevant trading period.

Consider a device previously used by two unrelated traders at different times. That could indicate prohibited account sharing, but it could also reflect a secondhand device, a shared computer or another legitimate arrangement. The circumstances matter.

A virtual private server introduces additional complexity because multiple customers may use infrastructure operated by the same provider. Whether a particular CID genuinely identifies the same underlying device or session environment depends on how the identifier is generated.

The available evidence does not establish that Alpha Capital Group’s system produces false matches. It does establish that customers are questioning what those matches actually prove.

Manual Trading Records May Not Resolve an Account-Sharing Allegation

Lucy’s supporting evidence also needs to be considered carefully.

Consistent lot sizes and ordinary holding periods may support her description of a disciplined manual strategy. They do not conclusively establish that no other individual accessed her trading account.

Similarly, hardware screenshots may help establish possession of a particular phone without proving the complete history of every device or session associated with an account.

This distinction matters because trading behavior and account access are separate compliance questions.

If the firm alleges unauthorized access, the most relevant evidence would likely involve the disputed device relationships, login timestamps, account identities and circumstances surrounding the connections.

That does not require publishing another customer’s private information or revealing the entire detection system. A privacy-preserving explanation could still allow a trader to understand which historical sessions are being questioned.

Why Payout Reviews Carry Greater Financial Consequences

For customers, the financial implications extend beyond the balance displayed on a trading dashboard.

As explained in Dave Finances’ analysis of the difference between proprietary trading firms and brokers, retail funded-trading programs frequently operate using simulated capital, with traders receiving contractual performance rewards when specified conditions are satisfied.

In that arrangement, the firm controls the evaluation rules, compliance investigation and decision about whether simulated gains qualify for payment.

That makes the appeals process particularly important.

If a company introduces better historical monitoring, customers might discover a previously undetected compliance issue only after passing their evaluation and approaching a payout.

Such timing does not prove an attempt to avoid payment. But it can create a serious perception problem when the resulting decision is permanent and the supporting evidence remains undisclosed.

Other firms have faced similar questions about applying detailed trading restrictions. Dave Finances previously examined an Orbit Funded dispute involving a 15-minute hedging restriction, where the trader challenged whether the identified transactions actually met the firm’s stated violation criteria.

The same basic principle applies here: the evidence should be capable of demonstrating the specific rule violation alleged.

What Alpha Capital Group Needs to Clarify

The next development worth watching is whether Alpha Capital Group explains how its historical CID checks operate and what role those findings play in terminating active funded accounts.

Several questions are particularly important. Does a historical CID match automatically trigger termination, or must the compliance team identify additional evidence of account sharing? Are inactive accounts included in the review? Does a trader’s appeal receive an independent manual assessment?

There is also the question of when violations are identified. If historical data can now reveal previously undetected relationships, are all active accounts being reviewed consistently, or are additional checks concentrated around payout requests?

Alpha Capital Group has not publicly provided a case-specific explanation resolving Lucy’s October 13 allegations in the material reviewed for this article.

For now, neither the trader’s account nor the firm’s underlying compliance conclusion has been independently established as correct.

The wider issue is whether increasingly sophisticated fraud-detection systems are accompanied by equally reliable procedures for reviewing disputed results. That question matters far beyond the $296.73 involved in Lucy’s complaint, particularly when historical technical evidence can determine whether a trader retains access to a funded account and its potential future rewards.