Support and report review

TRS should be challengeable.

A trader must be able to question reconstruction, report an evidence gap, request source review or flag a privacy problem. Automated analysis should never be treated as unquestionable.

Before contacting support Keep the report or evidence package ID.

Include broker name, export type, reporting period, account label and the exact issue you want reviewed.

Credential safety Never send broker-login credentials.

Do not email broker passwords, withdrawal credentials, API secrets, one-time login codes or document passwords.

File rejectedFormat or source mismatch

Unsupported export, corrupted file, encryption, wrong broker family or incomplete evidence package.

Money mismatchReconciliation issue

Gross result, charges, deposits, withdrawals, cash flow or closing balance does not match your records.

Trade reconstructionTimeline or structure issue

Entries, exits, linked legs, rollovers, partial closes, holding periods or order states appear wrong.

Behavioural findingDiagnosis needs review

The evidence behind a finding needs explanation, review or a limitation note.

Source requestBroker not covered

You have a broker, exchange or platform export that is not listed in the coverage center.

PrivacyEvidence or deletion request

Questions about file retention, report history, export, deletion or account closure.

What helps support investigate

Report ID or evidence package ID.
Broker or platform name.
Export type, file family and reporting period.
The account label used in TradeGospel.
The exact row, trade, balance, finding or limitation that looks wrong.
Whether the issue affects money truth, chronology, source coverage or diagnosis interpretation.

What not to send

Do not email secrets.

Do not send broker-login passwords, one-time codes, withdrawal credentials, full API secrets or protected PDF passwords. If a protected document fails, describe the error without sending the password by email.

How review should work

Support should identify whether the issue is a source-format problem, account-context mismatch, source-reader limitation, reconstruction issue, report wording issue or privacy request. A corrected report should preserve prior evidence lineage and state why the change was made.

Operational channel

Use the in-product support workflow when available. Until it is operationally staffed, enquiries may be sent to [email protected]. The mailbox and response commitment must be confirmed before public launch.

Evidence reviewSource requestPrivacy requestSecurity report