Corrections Policy

How we fix errors

When a factual error is found on this site, we correct it in the same article and add a dated note at the bottom of the page. The note says what was wrong, what it now says, and the date of the fix. We never silently edit an article and pretend it was always correct.

The original text is not kept online, but the correction note is permanent. If an error affected a ranking or a worked example, we say so in the note. Our goal is that a reader who saw the old version can see exactly what changed and why.

How to report an error

Send an email to editor@southcrossfx.com with the article title, the sentence or figure that is wrong, and the correct information if you have it. Attach a link to the broker's current document if the error is about a spread, margin, or regulation. We do not require a name, but we may ask a follow-up question if the report is unclear.

We read every correction report, but we do not promise a reply within a set time. If we agree that an error was made, the fix goes live as soon as we can verify the correct fact. If we disagree, we may write back explaining why, but we do not argue publicly.

Re-check vs error

A condition that merely changed since our check is not an error. For example, if a broker lowers its minimum deposit after we publish, that is a re-check, not a mistake. We will update the figure and add a note saying the condition changed, with the new date.

An error is a statement that was wrong at the time we wrote it. If we said a broker is regulated by a body it is not, that is an error. If a broker later loses that regulation, that is a change. We treat the two differently in our notes.

An error is a factual claim that misleads a trader

An error worth logging is any factual claim that could mislead a trader about costs, execution, regulation, or platform behaviour. That includes a wrong spread figure, an outdated margin requirement at a stated leverage, a broken contract size, or a claim that a regulator covers Australian clients when it does not. We log it if a reasonable reader would act on the statement and lose money or take on unexpected risk. Minor typos that do not change meaning are fixed silently, but they are not logged as corrections.

A wrong number in a worked example is always an error. For instance, if we wrote that a 0.10-lot gold position at 1:200 leverage needs $85.50 margin when the correct figure at a reference price of 4275.0 depends on the exact margin formula, that is a logged error because it changes a trader's capital plan. We also log errors in instrument specs: stating one pip on XAU/USD is 0.1 instead of 0.01, or that one lot is 10 oz instead of 100 oz, directly alters position sizing and risk.

An omission of a material fact counts as an error when it creates a false impression. If we describe FxPro as regulated without noting it is licensed by the FCA and CySEC but not by ASIC, Australian readers could wrongly assume local oversight. That caveat is part of our standard disclosure, and failing to state it is logged as an error. We also log a broken link to a regulator register or a platform download page, because it blocks verification of a claim.

Every correction is time-stamped and cross-referenced to the change

Each correction is recorded with the date and time of the edit, the exact text before and after, and a short reason tied to the fact changed. The log entry shows the page URL and the section heading, so a reader can jump straight to the corrected paragraph. We do not just say fixed a number; we show the old number, the new number, and why the old one was wrong. The time stamp uses Australian Eastern Standard Time, because that is the timezone of most of our readers.

The log is updated at the same moment the page is corrected, not later. If we change a margin figure from an incorrect value to a correct one, the log records that change with the date, the person who approved the correction, and a one-line note such as recalculated at reference price 4275.0 with 1:200 leverage. No correction is made without a log entry, and no log entry appears without the page already reflecting the fix.

We keep a running count of corrections on each page, visible in the log. For the gold page, the count stands at zero as of this writing, but if a future change is made, the count will increase and the entry will link to the exact diff. The log is not editable by the public; only our editorial team can add entries, and each entry is permanent. We do not delete or rewrite old corrections, even if the page is later overhauled.

A correction fixes a wrong fact, while an update adds new facts

A correction changes an existing statement from false to true, while an update adds new information that was not previously claimed. If we wrote that FxPro offers MT4 and MT5, and later the broker adds cTrader to its platforms, that is an update, not a correction, because the original statement was true at the time. If we wrote that FxPro offers only MT4 and MT5, and it had already offered cTrader, that is a correction because the original statement was false.

Updates are not logged in the corrections log unless they replace a fact that has become false. A change to the reference gold price from 4275.0 to a new level is an update, because the price is a moving data point and the old figure was correct when published. But a change to the contract size from 100 oz to 10 oz would be a correction if the real contract size was always 10 oz, and an update if the broker actually changed the contract size on a specific date.

The distinction matters for reader trust: a long corrections log full of updates would falsely suggest the page was riddled with errors, while hiding corrections as updates would conceal mistakes. We apply a simple test: would a reader who acted on the old text at the time of publication have been misled? If yes, it is a correction; if no, it is an update. Regulatory changes, platform additions, and price movements are updates; wrong formulas, wrong regulator names, and swapped numbers are corrections.

The public log proves we do not silently rewrite history

The corrections log stays public because it is the only way a reader can verify that we have not silently changed a claim after a trader lost money. If we published a wrong margin figure and then fixed it without a log, a reader who followed the old figure could not prove we ever made the error. A public, permanent log gives them evidence and a timeline. It also forces us to be careful before publishing, because every mistake will be visible forever.

A public log also shows how often we get things wrong and how quickly we fix them. A page with zero corrections over a year is a stronger signal of reliability than a page with hidden edits. We do not log updates in the corrections log, so the count is not inflated by routine price changes or platform additions. If a reader sees a low correction count on a page, they can trust that the page has been factually stable.

Finally, the public log is a requirement of our editorial standard for financial content. Trading is high-risk, and a reader must be able to audit every number we have published. We link the log from the page footer and from the corrections page itself. It is not a legal document, but it is our promise that we will not cover up a mistake. If we ever remove a log entry, that removal itself would be a violation of this standard.

Errors We Log: A Fact That Misleads a Trader

We log only errors that could materially change a trading decision. A wrong lot size on XAU/USD, a typo in a margin formula, or a claim that FxPro holds an ASIC licence when it does not are all logged because they mislead. Minor style fixes or wording preferences are not logged; the threshold is whether a trader could lose money or breach a regulation by relying on the stated fact.

An error worth logging must be a factual claim, not an opinion or a prediction. For example, if we wrote that a 0.10-lot gold position needs $85.50 margin at 1:200 leverage but the reference price was 4275.0, that is a logged error if the calculation was wrong. If we simply said the broker offers 'the spread your account type carries' without a number, that is not logged because it is an unsupported claim, not a false fact.

We also log errors in regulatory status because Australian readers rely on that. FxPro is licensed by the FCA (UK) and CySEC, but it does not hold an ASIC licence. If any page implied ASIC oversight, that would be logged immediately. The same applies to funding methods: if we said a card or bank transfer was unavailable when it is, or vice versa, we correct and log it because it affects how you move money.

How a Correction Is Recorded and Dated

Every correction is time-stamped with the exact date and time we made the change, in Australian Eastern Standard Time. The timestamp appears in the public log and in a visible note on the corrected page. We do not backdate or hide the timing; if a page was corrected on 15 March 2025 at 10:32 AEST, that is what the log shows, even if the original error was published weeks earlier.

The log entry includes a unique reference number that links to the specific change. We also state what the error was, what the corrected fact is, and why it matters. For example, if we once wrote that one standard lot of gold is 10 ounces, the correction would say: original error '10 oz', corrected to '100 oz', and note that a trader using the wrong figure would miscalculate position size and risk.

We record the correction on the page itself with a short note near the fixed text, plus the full entry in the public log. The note is plain text, no pop-ups or hidden metadata. This double recording ensures that anyone who read the old version can see what changed and when, without having to contact us or rely on memory.

Correction vs Update: When Facts Change

A correction fixes a fact that was wrong at the time of writing, while an update adds a new fact or changes a figure because the real world changed. For example, if we wrote that FxPro's minimum deposit is A$100 and that was always false, we correct it. If FxPro later raises the minimum to A$200, we update the page with the new number and date the update.

An update is not an admission of a past mistake; it is a reflection of new information. For gold trading, the reference price of 4275.0 is a snapshot. If we mention that price in an example and the market moves, we do not correct the old price; we update the example with a new reference price and note the date. The old example remains in the archive with its original timestamp.

Both corrections and updates are logged, but they are tagged differently in the public log. Corrections are marked 'correction' with the original error, and updates are marked 'update' with the new fact. This distinction matters because a correction tells you we made a mistake, while an update tells you the market or broker conditions changed. We never relabel a correction as an update to avoid embarrassment.

Why the Correction Log Stays Public

The public log proves we do not silently rewrite history. Every change to a page, whether a correction or an update, is listed with its date and reference number. Anyone can audit our record and see that we did not alter a page to make a past recommendation look better or hide a wrong cost figure. This is essential for trust in a high-risk market like gold trading.

A public log also protects you from misinformation. If you read a page yesterday that said a 0.10-lot gold position needs $85.50 margin and today it says $90.00, the log tells you why: either we corrected an error or we updated for a new reference price. Without the log, you might assume the number was always $90.00 and question your own calculations.

We keep the log public even when the error is embarrassing because accountability is part of an honest toolkit. Australian traders dealing with an offshore broker like FxPro, which lacks an ASIC licence, need to know that the information they rely on is accurate and that any mistake is openly acknowledged. The log is not a marketing tool; it is a compliance and trust measure.