Transparency report

One report a month, made from the records.

Each report is put together by the databases themselves for one calendar month: how orders were filled, how long withdrawals took, the incidents recorded, changes to legal documents, and a few counts. Nobody writes it, so nobody can leave something out of it.

When each record begins

Orders filled (777 Raptor): 1 April 2026
Trading accounts (client portal): 17 June 2026
Withdrawal requests (client portal): 10 October 2026
Support tickets (client portal): no record yet
Incidents (this website): 2 October 2026

The date of the earliest row each source holds. A report says nothing about a time before its source began.

Reports

The months available.

Months are calendar months in UTC. The month now running is counted up to the moment its page is prepared and is labelled “in progress”; its figures change until the month ends. A complete month is still read from the records each time, so a later correction to a record shows in its report.

What each report holds, and from where.

Execution: Orders filled, slippage and fill time by instrument group, counted by the 777 Raptor terminal’s database. Live accounts and demo accounts are separate tables; demo fills are at simulated prices.
Withdrawal timing: How many withdrawal requests were settled, and the median and 90th percentile of the hours from request to settlement, from the client portal’s database.
Incidents: The incidents staff published that started in the month, with how long each lasted, from this website’s database. The full text of each is on System status.
Legal documents: Published documents in the client portal whose latest change falls in the month, with their version number. The portal keeps only the latest change of each, and the report says so.
Counts: Trading accounts opened, demo and live apart, and support tickets opened and resolved, from the client portal’s database.

What a report will not do

Carry a sentence written for the month. Every word on a report is the same for every month; only the figures differ. There is no commentary.
Publish a figure from a handful of cases. An execution statistic made from fewer than 20 orders, a withdrawal median from fewer than 5 requests and a count from 1 to 4 are withheld, in the database, before they leave it.
Show a person. The pages receive counts, shares, medians and percentiles, and the incidents and documents that are already public. No client, account, order, ticket or withdrawal leaves a database for them.
Fill a gap. A source that does not answer is “could not be read”. A month before a source began is “before records began”. Neither is ever a zero.

What GIO4X publishes about itself, and what is still open, is on the transparency page.

Continue

Fetching the page

What each report holds, and from where.

Execution

Orders filled, slippage and fill time by instrument group, counted by the 777 Raptor terminal’s database. Live accounts and demo accounts are separate tables; demo fills are at simulated prices.

Withdrawal timing

How many withdrawal requests were settled, and the median and 90th percentile of the hours from request to settlement, from the client portal’s database.

Incidents

The incidents staff published that started in the month, with how long each lasted, from this website’s database. The full text of each is on System status.

Legal documents

Published documents in the client portal whose latest change falls in the month, with their version number. The portal keeps only the latest change of each, and the report says so.

Counts

Trading accounts opened, demo and live apart, and support tickets opened and resolved, from the client portal’s database.

What a report will not do

Carry a sentence written for the month. Every word on a report is the same for every month; only the figures differ. There is no commentary.

Publish a figure from a handful of cases. An execution statistic made from fewer than 20 orders, a withdrawal median from fewer than 5 requests and a count from 1 to 4 are withheld, in the database, before they leave it.

Show a person. The pages receive counts, shares, medians and percentiles, and the incidents and documents that are already public. No client, account, order, ticket or withdrawal leaves a database for them.

Fill a gap. A source that does not answer is “could not be read”. A month before a source began is “before records began”. Neither is ever a zero.

What GIO4X publishes about itself, and what is still open, is on the transparency page.