Find the service boundary
We record the canonical domain, redirects, registration history, archived pages and contact routes. Advertising links and lookalike pages are traced rather than assumed to belong to the service.
How Dubaicat checks AI-trading services
Dubaicat starts with the service itself: the domain a customer reaches, the company named in the terms, the task described as automated, and the parties that receive data or money. Records that agree, records that conflict and facts we could not obtain stay separate.
The same page holds the assessment rules and the publication list. It does not certify a service as safe, legitimate or profitable.
Published reviews
No assessments have been published as of .
What we check
The file follows a customer journey from the first domain visit through account closure or a withdrawal request. A step is reported only when the cited record or observed screen supports it.
Resolve the named parties
Names in the terms, privacy notice, payment screen and support correspondence are matched to company and regulator records for the relevant country. Incorporation proves that an entity exists; it does not establish permission to provide a financial service.
Describe the product without the label
Research, alerts, copy trading, rule-based orders, managed accounts and referrals are different offers. We identify the task performed, where execution occurs, which markets are supported and whether a customer can reach a demo, change settings or delete an account.
“AI-powered” remains the operator’s wording until a concrete automated function and its controls can be observed.
List access and custody
The file notes authentication, recovery, withdrawal controls, API permissions, key handling, data sharing, incident records and the route for revoking access. A request for a seed phrase, private key or unnecessary withdrawal authority stops the normal test.
Follow each payment
Minimum deposits, subscriptions, spreads, commissions, conversion charges, performance fees and withdrawal costs are taken from the plan and market actually visible during the check. We distinguish the payment recipient, asset custodian and execution venue instead of treating them as one party.
Deposit convenience does not stand in for a withdrawal test. Available methods, limits, stated timing, identity checks and any demand for another payment are recorded separately.
Rebuild performance claims
A return, win rate or backtest is usable only when its period, market, sample, benchmark, fees, slippage, drawdown and method can be identified. Screenshots, isolated trades and unexplained percentages remain claims, not representative results.
We look for simulated figures presented as live, favourable periods chosen after the fact and settings that cannot be reconstructed. A brief observation can reveal how controls behave, but not long-term profitability.
Assign responsibility for problems
We identify the channel and entity responsible for account, payment and security issues. When a question is sent, the record includes its date, channel and answer. Without direct contact, the page makes no claim about response time.
Turn complaints into checkable questions
User reports can point to a date, transaction, restriction or support exchange worth checking. Duplicate wording, coordinated bursts and unusual rating distributions affect the weight given to a pattern.
Repetition alone does not verify an allegation. Anonymous reports stay attributed, unnecessary personal data is excluded and factual claims are compared with records or reproducible product behaviour where possible.
Which sources carry weight
A source is useful for the question it can answer. A company register can identify an entity but cannot prove product performance; an account screen can show a setting but not regulatory permission.
- Official records: company filings, regulator entries and warnings, court or insolvency material, and jurisdiction-specific public data.
- Documents that bind the account: terms, privacy notices, fee schedules, risk notices, custody agreements, broker records and API documentation.
- Observed product paths: dated screens showing registration, settings, permissions, quoted fees, funding steps, support or withdrawals.
- Independent context: technical or market records used within their stated scope.
- Claims and reports: marketing copy, operator explanations, press material, social posts, testimonials and customer accounts. They show what was said, not whether it is correct.
For each central point, the file keeps the URL or record reference, responsible entity, relevant jurisdiction, source date, access date and the narrow statement that the source supports. Volatile pages are captured when doing so is lawful and technically possible.
Relevant primary starting points include the ICANN registration data lookup, the European e-Justice business-register search and ESMA’s MiCA register. The relevant target-country authority and permission scope still take priority. An alert database is not exhaustive, and absence from it is not proof of authorisation.
How far the check went
Each published file names the access that was actually available. Reading public records is not presented as an account test, and a demo is not presented as a funded withdrawal.
| Level | What it covers | What it cannot establish |
|---|---|---|
| Desk check | Public records, legal documents, product pages, fee disclosures, support information and relevant third-party records. | Private account behaviour, live execution or whether an advertised workflow functions as described. |
| Public or demo walkthrough | An unauthenticated interface, accessible demo, onboarding preview or paper-trading environment. | Production custody, real funding, withdrawal behaviour or live-market execution. |
| Registered-account walkthrough | Registration, identity flow, account settings, permissions, support access and non-funded product controls where permitted. | Actual deposit handling, live trading quality, real fees or withdrawal completion. |
| Funded transaction trace | A disclosed deposit, configured strategy or order path and withdrawal attempt, with dates, market conditions, account mode and relevant settings recorded. | Future returns, safety under every condition or performance across a full market cycle. |
Geographic restrictions, identity requirements, unavailable software, account refusal, security concerns or disproportionate capital requirements may prevent a level from being completed. The limitation belongs in the assessment.
How a note becomes a finding
A confident tone cannot repair a weak source. The wording attached to a finding reflects what the file contains at the stated date and in the stated market.
- Confirmed for scope
- A primary record or reproducible observation supports the statement within the stated date, market and scope.
- Source says
- An identified source makes the claim, but Dubaicat has not independently established it.
- Conflict
- A material claim conflicts with a stronger record or reproducible observation. The competing sources and scope of the conflict must be shown.
- Open
- Evidence is missing, access is limited, records disagree without a decisive source or the result cannot be reproduced. Unresolved does not mean false.
Source strength and possible harm are recorded separately. A serious claim may remain open; a minor detail may be firmly confirmed.
When we stop hands-on work
Missing information, a contradiction and confirmed misconduct are different findings. Any of the following can end account testing or prevent a favourable conclusion:
- a current regulator warning, confirmed clone or false claim of authorisation;
- an operator or payment recipient that cannot be reconciled with the service’s legal documents;
- a request for a seed phrase, private key, remote-device control or unnecessary withdrawal permission;
- guaranteed returns, fabricated performance evidence or material risk information hidden behind a deposit;
- pressure to deposit immediately or repeated contact designed to bypass informed consent;
- a demand for a new tax, insurance payment or release fee before existing funds can be withdrawn;
- contradictory withdrawal terms, unexplained recipient changes or evidence that account controls cannot be revoked;
- material identity, custody or money-path conflicts that remain unresolved after reasonable verification.
Stopping a test protects the researcher and does not by itself prove criminal conduct. Published wording must match the evidence available.
What the conclusion must say
Comparisons are meaningful only when the services were checked for the same market, period, customer type and level of access. Popularity, a promotional score or a long feature list does not supply that common basis.
The published conclusion records:
- the official service and operator supported by the available record;
- the target country, product type and date of assessment;
- the completed testing-depth level and access limitations;
- the material verified, attributed, contradicted and unresolved findings;
- the most serious risk and the evidence confidence attached to it;
- the conditions under which the conclusion would need to change.
A favourable finding is limited to the named product, operator, jurisdiction, date and sources in that file. Services with different custody models or automation functions are not forced into one numerical ranking.
Dubaicat does not generate scores from a formula. A number appears only if the underlying observations create a visible, reproducible basis; identity, permission, custody, payment and withdrawal problems outweigh cosmetic strengths.
What a verdict cannot promise
- It cannot guarantee that a service is safe, suitable or capable of producing returns.
- It cannot remain permanent after ownership, terms, access, fees, regulation or product mechanics change.
- Absence from a warning list is not proof that a service is authorised or trustworthy.
- Company registration is not the same as permission to provide a regulated financial service.
- A partner’s authorisation does not automatically cover the public brand or all of its products.
- Missing information is not proof of misconduct, although it may reduce confidence or prevent a positive conclusion.
- The assessment is editorial information, not personalised financial, legal or investment advice.
Corrections, replies and commercial links
A correction names the affected statement, the date of the change, the reason and the replacement source. A change to ownership, legal status, access, prices, custody, withdrawals or the conclusion triggers a dated review rather than an unmarked rewrite.
An operator can send evidence or dispute a finding at contact@dubaicat.io. The reply is attributed and checked; it does not create a right to select the wording or remove a supported finding.
A supplied account, waived fee, sponsorship or affiliate relationship is disclosed beside the relevant material. A paid destination is not used to establish the official domain or operator, and payment cannot hide a risk or buy a favourable conclusion.
Questions about our reviews
Does a check in one country apply everywhere?
No. Company identity, permissions, warning lists and consumer protections are checked for the country and service named in the assessment. A result from one market is not carried into another without a separate record.
What does Dubaicat publish if sign-up is blocked?
The assessment states where access ended and reports only the records or screens that were available. It does not describe a demo as a live account or infer a deposit, trade or withdrawal that did not occur.
Can customer complaints change a finding?
A complaint can identify a transaction, restriction or support exchange to investigate. It changes a factual finding only when the underlying event can be supported; repetition by itself is not verification.
How does Dubaicat handle a correction?
The page identifies the affected statement, the change date, the reason and the replacement source. An operator response is attributed and checked, but it does not create a right to remove a supported finding.