How this ledger is kept

This page explains how the readings on this site are taken, what a reading can and cannot show, and what the ledger leaves out.

What a reading is

A reading is one request to a public page, made by a script on a server, without logging in. For FxPro: Trading & Investing and FxPro Global: Trading Broker the day is 6 November 2026. The pages were read as the Google Play pages in the Pakistan view (country code PK, English text); the App Store's public lookup interface was asked for the same storefront. The raw answers were saved and every figure is parsed from the saved files. All dates are UTC.

How the figures are re-checked

Before a reading is kept, a second program reads the saved files by a different route (visible text against page data, lookup against product page, star counts against the number of ratings, versions against the current version) and compares. If anything differs the reading is not written. The check was tested against planted faults: a changed rating, a swapped developer, a changed count, a dropped declaration, an edited date.

What was asked of each source

Requests to one host were spaced at least eight seconds apart, far fewer than fifty were made to any host in a day, and a refusal would stop the run. The pictures are captures of the same public pages with a headless browser at a desktop and a phone width, with other people's reviews hidden. The broker's own ordinary pages answered with HTTP 403; its public text file was readable and is the only page of the broker quoted.

What the ledger leaves out on purpose

Everything behind a login: the screens of an account, identity checks, deposits, withdrawals, the order ticket and the fees. Reviews, which are other people's words. Scores and rankings. A rating or a declaration is reported as the page prints it, not as true.