Corrections policy

Errors are fixed in place

An error is corrected on the page itself and marked with a dated note saying what changed. We do not delete the old sentence and pretend it never existed, because a reader who quoted the earlier version deserves to see that it moved.

The note stays visible rather than being buried at the bottom. If a figure was wrong, the correction says what the figure was and what it is now, so the change can be checked against the broker's own documents.

How a Correction Is Recorded and Dated in the Public Log

A correction is recorded as a dated entry in a public log that names the page, the exact text changed, the reason, and the date the change went live. The date is the publication date of the corrected version, not the date a reader reported it and not the date the error was first introduced. Each entry carries a unique reference so a reader can cite it. The log is append-only: a later correction to the same passage appears as a new entry rather than overwriting the earlier one.

The entry states what the page said before and what it says now, in enough detail that a reader can see the size of the change. For a numerical correction, both the old and new figures are shown alongside the source that settles the matter. For a regulatory correction, the entry quotes the correct caveat: FxPro is licensed by the FCA (UK) and CySEC, does not hold an ASIC licence, and Australian residents therefore deal with an offshore entity. Dates are recorded in Australian Eastern time and shown in full.

Dating is deliberately conservative. If a correction is made in stages, each stage gets its own date. If a page is corrected before any reader could reasonably have relied on the wrong version, the entry still appears, marked as a same-day correction. The log does not backdate an entry to match the original publication date, and it does not remove the original date from the page. A reader can therefore see both when the page was first published and when each subsequent correction took effect.

Who Decides a Correction and the Timeframe for Publishing It

The decision to log a correction rests with the page's editor, who is the person accountable for the page's factual accuracy. A reader report does not automatically become a correction; the editor checks it against the source the page relies on and decides whether the text was wrong, incomplete or simply misread. That decision is recorded with the editor's role, not a personal name, so accountability sits with the function rather than an individual who may later move on.

The timeframe depends on severity. A reported error that affects a number a reader might act on — a margin figure, a pip value, a leverage statement or the regulator caveat — is checked and, if confirmed, corrected and logged within the same business day. A report that concerns wording or a non-numerical example is checked within five business days. If a report cannot be resolved in that window, the page carries a visible note saying the point is under review until it is settled.

The editor does not decide alone on the regulator caveat. Any change to the sentence stating that FxPro is licensed by the FCA and CySEC but does not hold an ASIC licence requires a second check before publication, because that sentence carries the most consequence for an Australian reader. The second check is recorded in the entry. Timeframes are stated in Australian Eastern time, and a missed timeframe is itself logged as an update so the delay is visible.

A change is not always an error

Sometimes nothing was wrong and the world moved: a broker changes its entity, its platform list or its leverage cap after we last checked. That is a re-check, not a correction, and it is labelled as such.

The distinction matters because it tells a reader whether the desk made a mistake or whether the broker changed its terms. Both get a dated note; only one is an error.

How Error, Update and Clarification Are Marked in the Log

Each log entry carries one of three labels — error, update or clarification — and the label determines what the entry must contain. An error entry must show the incorrect text, the corrected text, the source that settles it, and the date the correction went live. An update entry must show what was added or refreshed and why it was not previously included. A clarification entry must show the original wording and the tightened wording, and state what misreading it prevents.

The labels are not interchangeable and are not chosen for tone. An error is never relabelled an update to soften it, and a clarification is never used where the original was simply wrong. Where a single edit fixes an error and also adds new material, it is split into two entries so the error is visible on its own. The label appears at the start of the entry, in plain text, so it can be read without opening the page.

The marking scheme is applied consistently across every page that carries a log. A reader who learns that error means the old text was false can rely on that meaning everywhere. The three labels are defined once, in a fixed glossary attached to the log, and the definitions do not change without their own dated entry. That keeps the vocabulary stable even as the pages themselves are corrected and updated over time.

The Difference Between a Correction and an Update on This Page

A correction fixes something that was wrong; an update adds or refreshes something that was right when written but has since moved on. If a page stated a margin example for 1:200 leverage and the arithmetic was wrong, that is a correction. If the same page later adds a second worked example for a different position size, that is an update. The distinction matters because corrections imply the earlier version misled, while updates imply the earlier version was accurate for its time.

Updates are used for new information that does not contradict the old: a newly available platform, a change in the regulator caveat's wording that reflects a change at the regulator, or an added explanation of how PayID and bank transfer funding interact with margin. Corrections are used when the old text was false. A page can carry both, and the log marks each entry as one or the other so a reader is never left guessing which kind of change occurred.

The line is tested by asking whether a reader who acted on the old text was misled. If yes, it is a correction. If the old text was accurate but incomplete, it is an update. A clarification sits between them: the old text was not false but could be misread, so the wording is tightened and marked as a clarification rather than a correction. All three are dated and kept, and none is used to disguise a correction as a routine update.

What Counts as an Error Worth Logging on a Gold Trading Page

An error worth logging is any statement that would change a reader's trading decision or calculation if it were wrong. That includes a miscalculated margin figure, an incorrect pip value for XAU/USD, a stale reference price presented as current, a wrong lot size convention (1 standard lot = 100 oz), or a misstated regulator caveat. It does not include stylistic preferences, a reader disagreeing with a risk warning, or a market outcome that unfolded differently from an example. The test is whether the page asserts a fact that can be checked against a source.

Errors are logged when they affect a number a reader might act on. If a page says a 0.10-lot gold position at 1:200 needs about $85.50 margin and that figure is wrong for the stated leverage, it is an error. If a page says FxPro holds an ASIC licence when the correct position is that FxPro is licensed by the FCA and CySEC but does not hold an ASIC licence, that is an error. A typo that changes no meaning is noted but not treated as a correction event.

An error is not logged merely because a reader would have preferred different wording, a different example, or a stronger warning. Corrections are reserved for statements that are factually wrong, internally inconsistent, or contradicted by the source the page relies on. Where a figure depends on conditions the page cannot fix — such as a broker's live spread or a funding method's processing time — the page must say what the figure depends on rather than present a number. If it fails to do that, the omission is loggable.

Why the Correction Log Stays Public and Is Never Restricted

The log stays public because a reader cannot judge a page's reliability without seeing its history. A trading page that states margin figures, leverage caps and regulator caveats is only as trustworthy as its willingness to show where it was wrong. Keeping the log open means an Australian reader can check whether the $85.50 margin example at 1:200 has ever been corrected, and can see the exact wording before and after. A private log would give the page the benefit of the doubt it has not earned.

Public access also deters quiet edits. If every change must appear in a dated, append-only record, there is no way to alter a leverage statement, a pip value or a regulator caveat without it being visible. That matters most for the caveat that FxPro does not hold an ASIC licence and Australian residents deal with an offshore entity, because a reader relying on that sentence needs to know it has not been softened. The log is the evidence that it has not.

The log is not restricted to registered users, paid subscribers or clients. It is available to any reader on the same terms as the page itself, and it is not removed when a page is retired. No entry is deleted for being embarrassing, outdated or inconvenient. The only thing that changes in the log is that new entries are added. That rule is stated on the log itself so a reader can hold the page to it.

How to report one

Send the page address, the sentence you believe is wrong and, if you have it, the broker document that shows the correct position to editor@murraysandboxau.com. A link to the source is more useful than a description of it.

We check the source ourselves before changing anything. If the report is right, the page is corrected with a dated note; if it is not, we will tell you why we are keeping the sentence as written.